Most delay disputes are not arguments about whether a project ran late. Everyone in the room already agrees it ran late. The argument is about which of four categories the delay falls into, because the category decides who pays for it.

Owners lose this argument more often than they should. Not because they were wrong about the delay. Because they never sorted it correctly, and by the time a claim is on the table the contractor has already framed the classification in its own favor.

Here is the framework, sorted the way it actually matters: by who recovers time, and who recovers money.

The two questions that classify every delay

Strip away the vocabulary and every delay gets sorted by two questions.

Is it excusable? Is the contractor entitled to more time on the schedule.

Is it compensable? Is anyone entitled to money on top of that time.

Those two questions produce the four categories below. A third question sits underneath both of them: is the delay critical, meaning does it sit on the critical path or only burn float. A delay that consumes free float moves nobody’s completion date and pays nobody. We will come back to criticality, because it is where a lot of weak claims quietly fall apart.

Type 1: Excusable and compensable

This is the delay the owner causes. Or more precisely, the delay caused by anyone acting on the owner’s behalf. The design team that approved a submittal 38 days late. Owner-furnished equipment that arrives six weeks after the date written into the contract. A change directive issued without a time extension attached to it.

When the cause traces back to the owner’s side, the contractor is usually owed both time and money. More schedule, plus the cost of carrying crews, equipment, and overhead while sitting on site longer than planned.

This is the category owners least expect and pay for most often. The reason is simple. Owners watch contractor performance closely and watch their own performance barely at all. The submittal log, the equipment procurement schedule, the decision turnaround on RFIs. Those are owner obligations, and when they slip they generate compensable delay the owner never saw coming.

Watch how this gets misclassified. A mechanical sequence shows up four weeks late. The contractor logs it as an equipment delivery delay. The schedule analyst signs it off. But the air handlers shipped late because the submittal was approved a month behind, which compressed the fabrication window, which pushed the delivery. The mechanical delay was a procurement delay wearing a costume. Trace it back five steps and it is an owner-side delay. Stop at the symptom and the owner just absorbed a cost that wasn’t theirs to absorb, or paid for one that was and never knew it.

Type 2: Excusable, non-compensable

Neither side is at fault. Unusually severe weather beyond what the baseline accounted for. A force majeure event. A regulatory action nobody controlled.

The contractor gets a time extension. No money changes hands. The risk is shared, which in practice means each party eats its own costs for the delay period.

The fight in this category is almost always about the word “unusually.” Three days of rain in a region that gets rain is not an excusable weather delay. Ten-year storm conditions might be. The baseline schedule should already carry an allowance for normal weather, and a contractor claiming weather delay has to show the conditions exceeded that allowance. Owners give away time here by accepting weather claims that should have been priced into the schedule from day one.

Type 3: Non-excusable

The contractor’s own delay. An undermanned crew. Material the contractor was responsible for procuring and ordered late. Rework driven by its own defective installation.

No time. No money. Depending on the contract, the owner may be entitled to liquidated damages for the period the contractor ran past the completion date.

This is the category the contractor works hardest to move a delay out of. Every non-excusable delay it can reclassify as excusable buys time and erases liquidated damages exposure. Most classification disputes are really a contractor trying to relocate a Type 3 delay into Type 1 or Type 2.

Type 4: Concurrent delay

Two delays hitting the critical path in the same window, one owner-caused and one contractor-caused. This is where money usually disappears.

The general principle most forums land near: a contractor can recover a time extension for a concurrent delay but not the compensation, and an owner generally cannot collect liquidated damages for a period in which it was also causing critical delay. Time gets extended. Money gets cancelled out on both sides.

There is no single national test for concurrency. Courts and boards split on how to apportion it, and even the definition of “concurrent” is contested between jurisdictions and standards. That uncertainty is exactly why concurrency is the contractor’s favorite shield. If a contractor running behind can surface one owner-caused delay onto the critical path in the same window, the owner’s liquidated damages claim is suddenly in question. We treat the concurrency analysis as its own discipline, and it deserves more room than this piece gives it.

Criticality comes first

None of the four categories matter if the delay never touched the critical path.

A delay that consumes only free float changes no completion date and pays nobody. A delay that consumes total float compresses the schedule and exposes the project to risk but still may not extend the finish. Only a delay on the critical path, or one that drives an activity onto it, moves the completion date.

This is why schedule logic is upstream of every classification question. If the critical path is wrong, because the predecessor logic is sloppy or half the schedule is tied together with finish-to-start zero-lag relationships that don’t reflect how the work actually sequences, then every classification built on that critical path is wrong too. The most expensive delay disputes we see are not won or lost on the delay. They are won or lost on whether the schedule was built to survive scrutiny in the first place.

The four types at a glance

Type	Cause	Contractor gets time?	Money changes hands?	Who is exposed
Excusable, compensable	Owner or owner’s agents	Yes	Yes, owner pays contractor	Owner
Excusable, non-compensable	Neither party (weather, force majeure)	Yes	No	Shared
Non-excusable	Contractor	No	Possibly LDs to owner	Contractor
Concurrent	Both parties, same window	Usually yes	Usually cancelled out	Both, money rarely moves

Classification is really a causation fight

Here is the part nobody likes to hear. The argument over which box a delay belongs in is never actually about the box. It is about the cause. Causes get paid. Symptoms get argued.

The mechanical delay that was really a procurement delay is the whole problem in miniature. Whoever controls the causation narrative controls the classification, and whoever controls the classification controls who pays. Contractors understand this. They build their delay narratives backward from the category they want to land in. Owners tend to react to the delay as reported, accept the surface cause, and discover the real predecessor only when a claim forces the question.

By then the documentation that would have settled it is twelve months old and incomplete.

What this means for an owner before there is a claim

The classification fight is won during construction, not during litigation. A few things separate owners who hold their position from owners who give money away:

• Track your own obligations as closely as the contractor’s. Submittal turnaround, RFI response time, owner-furnished equipment delivery, and decision latency are the most common sources of compensable delay, and they are entirely within the owner’s control to monitor.
• Insist on a schedule built to be analyzed. Clean critical-path logic, justified constraints, and relationships that reflect real sequencing. A schedule that cannot be analyzed cannot defend you.
• Document causation in real time. Not the symptom, the cause. The day the submittal review slips is the day to note why, not eighteen months later when the contractor’s narrative is the only one with dates attached.

Do that work and most delays sort themselves cleanly. Skip it and you are negotiating from the contractor’s version of events.

Frequently asked questions

What is the difference between excusable and compensable delay? Excusable means the contractor is entitled to more time. Compensable means someone is also entitled to money. A delay can be excusable without being compensable, as with severe weather, where the contractor gets time but no payment. A compensable delay is almost always excusable as well.

Can a contractor get paid for a weather delay? Usually not. Severe weather beyond the baseline allowance typically earns a time extension but no compensation. It sits in the excusable, non-compensable category, and the costs are shared. Routine weather that the baseline should have anticipated earns neither.

Who proves a delay was concurrent? The party trying to use concurrency carries the burden of showing two independent critical-path delays overlapped in the same period. Because the standards and case law are not uniform, the analysis turns heavily on the quality of the schedule and the contemporaneous records.

Does float belong to the owner or the contractor? Neither owns it by default, and how float is consumed shapes almost every delay analysis that follows. It is a question worth its own discussion, which we take up separately.