Delay Claim Documentation: Building the Paper Trail That Wins

A construction delay claim is a request for additional time (and often additional cost) due to events that extended the project beyond its scheduled completion. Claims are filed when delays caused the contractor to incur extended costs or missed a scheduled completion date due to causes the contractor says weren't their fault. The contract determines how claims are processed; the evidence determines whether they succeed.

Delay claims almost always fail when documentation is weak. An owner or arbitrator reviewing a claim looks for contemporaneous records — documentation created at the time the events occurred, not reconstructed after the fact. Reconstructed records carry less evidentiary weight because memory fades, incentives shift, and specificity is lost. The contractor who documents daily wins claims the contractor who documents in response to the claim doesn't.

What Needs to Be Proved

A delay claim typically has to establish several things:

Each of these elements has its own evidence requirements. A complete claim package addresses each with supporting documentation.

Documentation That Matters

The primary documentation streams for delay claims:

Good delay claim preparation starts at contract signing, not when the delay happens. A project with disciplined daily reports, an active schedule with regular updates, and a clean RFI log has the evidence ready when needed. A project with spotty documentation has to scramble at claim time.

Time Impact Analysis

A Time Impact Analysis (TIA) is the primary analytical technique for quantifying the delay. The TIA uses the CPM (Critical Path Method) schedule to calculate how a specific delay event affected the project's completion date.

The basic TIA methodology: take the baseline schedule current as of just before the delay event. Insert the delay event into the schedule as an activity. Rerun the schedule to see how the critical path and the project completion date change. The difference between the original and updated completion dates is the TIA's estimate of the delay event's impact.

TIAs require a CPM schedule that's being actively maintained. A schedule that hasn't been updated in six months can't be used for a credible TIA on an event from last month. Contractors who let their schedule drift lose the ability to prepare defensible delay claims — this is why schedule maintenance is a core project management discipline.

Critical Path and Float

Not every delay creates project-level impact. An activity with float (slack time in the schedule) can be delayed up to its float amount without affecting the project's completion date. Only delays to critical path activities, or delays that consume all available float, extend the project.

A delay claim for an activity that had 20 days of float and was delayed 10 days has zero project-level impact. The contractor can't claim a 10-day extension for an event that only used up some of the float. Understanding which activities are on the critical path — and how much float non-critical activities have — determines whether a delay is claimable at all.

Float ownership is also a contract question. Some contracts say float is "owned" by the contractor (delays that consume float but don't extend the project can still be claimable for cost impact). Some say float is shared or owner-controlled (delays that consume float aren't claimable until all float is used). Knowing the contract's float provisions early affects how delay claims get structured.

Concurrent Delay

Concurrent delay is when multiple delays are contributing to the same extension period simultaneously — some caused by the contractor, some by the owner, some by neither. Courts and arbitrators handle concurrent delay variously: some split the delay, some allow the contractor time but not cost, some allow neither time nor cost if the delay would have occurred anyway due to the contractor's own issues.

For the contractor, documenting and arguing concurrent delay is complex. The daily reports and schedule evidence have to identify specifically which delays were occurring on which days, who caused each, and whether any single delay independently caused the project extension. Thin documentation favors the owner in concurrent delay disputes; strong documentation favors the contractor.

Cost Impact Documentation

When a delay claim includes a cost impact, the cost has to be documented item by item. Typical cost components include:

Each category needs specific documentation. Extended general conditions are proven by the monthly GC cost schedule. Idle equipment is proven by equipment log books. Labor inefficiency is often argued via productivity analysis comparing pre-delay and post-delay productivity. The evidence builds the claim.

Notice Requirements

Most contracts have notice requirements for delay claims — a specified window (often 7-21 days) within which the contractor must notify the owner in writing of a delay event. Miss the notice window, and the claim may be waived regardless of its merits.

Notice doesn't require full claim preparation — it requires timely acknowledgment that a delay event occurred and that the contractor intends to pursue a claim. A simple letter or email noting the event, the date, and the intent to preserve the claim suffices. More detailed claim submission follows later. Skipping the initial notice in favor of a later complete package can lose the claim on a technicality.

Bottom Line

Delay claims succeed or fail on documentation and analysis. Daily reports, RFI logs, submittal logs, weather records, and schedule updates are the evidence base. Time impact analysis is the analytical technique that quantifies the impact. Notice requirements preserve the right to claim. Contractors who document disciplined daily, run schedule analyses contemporaneously, and give notice within contractual windows have claims that survive challenge. Contractors who reconstruct later have claims that often don't.