Why Your Delay Claim Is Being Rejected: Excusable, Compensable, and Concurrent Delays Explained

A rejected delay claim is rarely rejected because the delay itself didn't happen. Rather, parties fight about responsibility for the delay, or whether the delay claim sorts cleanly into the categories a contract (or the law governing that contract) uses to decide who bears the cost. Most delay analysis frameworks across jurisdictions and contract forms tend to divide delay into a few recurring buckets, though the exact labels and consequences depend heavily on the specific contract language and the governing law. This blog post provides a brief overview of each of these categories, and where each claim can end up breaking down.

The first category is excusable delay, which generally refers to a delay caused by something outside the contractor's control and not attributable to the contractor's own performance, e.g., weather beyond what was reasonably anticipated, a differing site condition, a government action, or an owner-caused disruption like late design information or delayed access to the site. An excusable delay commonly entitles the contractor to additional time, but whether it also comes with additional money depends on a second distinction that many contractors conflate with the first: excusable delay and compensable delay are not automatically the same thing. A delay can be excusable (meaning the contractor isn't at fault and may be entitled to a schedule extension) without being compensable (meaning it doesn't necessarily come with a right to money), and many contracts specifically carve out categories like unusually severe weather or general force majeure events as time-only relief.

Compensable delay generally requires something more than excusable delay: that the delay was caused by the owner, or by a party the owner is contractually responsible for, and that the contractor followed whatever notice and documentation procedures the contract requires to preserve the claim. This is where many delay claims are actually rejected or lost: on whether the contractor gave the kind of timely, specific written notice most contracts treat as a condition precedent to recovering money at all. A contract might require notice within a matter of days of when the delay was first recognized, describing the cause, the anticipated schedule impact, and whether the contractor is seeking time, money, or both, and missing that window can waive an otherwise valid claim regardless of how clearly the owner caused the delay.

The third and likely the most contested category is concurrent delay: where two or more independent delays, at least one attributable to each side, affect the same activity on the project's critical path during the same period. Concurrent delay tends to complicate compensability because many contracts and even some courts take the position that when both parties contributed to a delay on the same critical path activity, the contractor generally cannot recover money damages for that period, even though a time extension may still be appropriate. Proving concurrency actually exists rather than simply asserting it is difficult in practice. A true concurrent delay analysis usually requires a critical path method schedule showing that both delay events independently affected the same activities during the same window, not just that both events happened to occur somewhere on the project around the same time. In court or arbitration, this will generally require a construction delay expert.

This is also where a claim's outcome often hinges less on what happened in the field and more on what the contract actually says, since concurrent delay is treated very differently from one contract form to another. Some contracts allocate concurrent delay risk explicitly, some are silent and leave the issue to whatever default rule the governing jurisdiction applies, and some construction manager at risk or guaranteed maximum price structures build in their own delay and contingency mechanisms that change how a GMP number absorbs schedule impacts before a formal delay claim is even necessary. A contractor evaluating whether a claim is likely to succeed should generally start with the contract's specific delay, notice, and change order provisions rather than assuming a general industry standard will control, since the label a party puts on a delay matters far less than what the underlying contract does with that label.

Documentation discipline is critical to every delay event and claim. Contemporaneous notice, a maintained schedule baseline, and cost records segregated by cause can separate a delay claim that survives scrutiny from one that gets dismissed as speculative. A contractor unsure whether a specific delay event on a specific contract rises to excusable, compensable, or concurrent status is generally better served getting that question answered before submitting a claim than after it's rejected.

This post is for general informational purposes only and does not constitute legal advice. For guidance specific to your project and contract, contact Elkhoury Law PLLC.