Blog Details

Every delay claim begins with a single question: what kind of delay actually occurred? It sounds basic, but the answer determines everything that follows. Whether an Extension of Time is available, whether costs can be recovered, and how the claim must be evidenced. Misclassifying a delay at the outset is one of the most common reasons claims unravel later in the process.

Construction delays aren't a single category. They fall into distinct types, each carrying different contractual consequences. Understanding this classification isn't academic, it's the foundation every credible claim is built on.

Excusable vs. Non-Excusable Delay

The first and most fundamental split is whether a delay is excusable or non-excusable.

An excusable delay is one caused by circumstances outside the contractor's control including adverse weather beyond what was reasonably anticipated, employer-instructed variations, force majeure events, or third-party interference not attributable to the contractor. These delays typically entitle the contractor to relief, whether that's additional time, additional cost, or both, depending on the contract terms.

A non-excusable delay, by contrast, arises from the contractor's own default such as poor planning, inadequate resourcing, or failure to manage subcontractors effectively. These delays offer no relief and may expose the contractor to liquidated damages.

This distinction is the first filter every claim must pass through. Get it wrong, and the entire claim is built on the wrong foundation.

Compensable vs. Non-Compensable Delay

Within excusable delays lies a second, equally important distinction: is the delay compensable or non-compensable?

A compensable delay entitles the contractor to both time and money, typically when the employer is the direct cause, such as late issuance of drawings, delayed access to site, or instructed changes to scope.

A non-compensable delay may still justify an extension of time, but without additional cost recovery. Many force majeure clauses operate this way: the contractor gets relief from liquidated damages, but bears its own costs during the delay period.

This is where many claims overreach. Contractors sometimes assume that any excusable delay automatically comes with a right to costs. It doesn't. The contract language determines this, clause by clause, and claims that ignore this distinction tend to lose credibility quickly during review.

Critical vs. Non-Critical Delay

The third classification axis cuts across the first two: does the delay actually affect the completion date?

A critical delay impacts activities on the critical path, directly pushing back project completion. A non-critical delay affects an activity with float, time built into the programme, meaning the project can still finish on schedule despite the disruption.

This is where programme analysis becomes unavoidable. A delay event might be real, well-documented, and entirely the employer's fault yet if it didn't affect the critical path, it doesn't support an EOT claim. Conversely, even a small delay event can carry significant weight if it hits the critical path at the wrong moment.

This is precisely why narrative-only claims, without supporting programme evidence, rarely hold up. The classification of "critical" cannot be asserted; it has to be demonstrated.

Why This Framework Matters in Practice

These three classifications, excusable/non-excusable, compensable/non-compensable, and critical/non-critical, aren't separate boxes to tick. They interact. A delay can be excusable but non-compensable. It can be compensable but non-critical, and therefore irrelevant to an EOT claim even though it caused real cost. Each combination changes what the contractor is actually entitled to claim, and under which clause.

This is also where many claims fail before they're even properly reviewed. A claim built without first correctly classifying the delay tends to conflate these categories, treating every disruption as both excusable and compensable, when the contract and the facts may support neither.

Building Claims on the Right Foundation

Classification isn't a formality buried in delay analysis reports. It's the lens through which every subsequent step of a claim, entitlement, causation, notice, programme impact, and mitigation, must be assessed. A delay event correctly classified from the outset shapes a claim that's coherent, defensible, and aligned with what the contract actually allows.

Claims built on an unclear or incorrect classification rarely recover later, no matter how strong the supporting documentation becomes. The classification comes first. Everything else follows from it.