Extension of time claims submitted to USACE, Port Authority, state DOTs, and other public authorities are rejected more often than they should be — not because the delay did not happen, but because the claim package does not meet the internal standard of proof that the agency reviewer applies.
Understanding that standard before you prepare the claim is the difference between a negotiated settlement and a protracted dispute.
What Public Agencies Are Actually Evaluating
When a public agency reviewer receives an Extension of Time (EOT) claim, they are working through a sequence of questions. Did the delay actually occur? Was it caused by the owner or a compensable force majeure event? Did it affect the critical path at the time it occurred? Was the contractor diligent in mitigating the impact? And does the schedule analysis demonstrate all of the above using methodology consistent with the contract?
A claim that cannot answer all five of these questions with contemporaneous documentation will not be approved — regardless of how large the delay was or how clearly the contractor was impacted.
The Schedule Analysis
Most public agency scheduling specifications require TIA methodology for delay quantification. The TIA must be based on the accepted schedule update in effect at the time the delay event occurred — not the original baseline. It must insert the specific delay event with appropriate duration and logic, and demonstrate the resulting push to the critical path and project completion.
Common mistakes: using the baseline instead of the contemporaneous update, inserting the delay as a constraint rather than an activity, failing to address float consumption before the critical path was impacted, and not addressing concurrent contractor-caused delays.
The Entitlement Documentation
The schedule analysis answers how long the delay was. The entitlement documentation answers why the owner is responsible for it. This requires the contract clause that creates the entitlement, the specific event or action that triggered it, the date it occurred, and the notice provided to the owner. Missing any of these elements gives the reviewer grounds to deny entitlement regardless of the schedule analysis.
Formatting for Agency Review
Public agency reviewers process many claims. A claim that is clearly organized — executive summary, entitlement basis, schedule analysis, supporting documentation — gets a fair review. A claim that buries the critical path analysis in 200 pages of attachments without a clear narrative creates work for the reviewer and reduces the likelihood of approval.
Structure the claim the way you would structure a report for someone who is skeptical and time-constrained, because that is exactly who is reading it.
Notice Requirements Are Frequently the Real Downfall
Contractors often build a technically sound schedule analysis and lose the claim anyway on a threshold issue: notice. Most public agency contracts require written notice of a delay event within a specified window — commonly 10 to 21 days — and a follow-up claim submission within a further deadline. These provisions are enforced literally. A reviewer who agrees the delay was owner-caused and agrees the schedule impact is well documented can still deny the claim outright if notice was late, because the contract makes timely notice a condition precedent to entitlement, not just a formality. Track notice deadlines the same way you track schedule float — as something that, once lost, cannot be recovered later in the process.
Concurrent Delay: Where Most EOT Claims Are Actually Won or Lost
Concurrent delay — where an owner-caused delay and a contractor-caused delay affect the critical path during the same period — is the single most litigated issue in EOT claims, because the outcome changes the result entirely. Under the majority approach followed in federal contract law and most state public works frameworks, true concurrent delay generally entitles the contractor to a time extension without compensable damages: time, but not money. If the contractor-caused delay is on a separate, non-critical path, or occurred at a different time than the owner-caused delay, it does not qualify as concurrent and the analysis changes again.
This is precisely why windows analysis exists as a distinct methodology from a simple TIA: it is built specifically to identify which delays were active on the critical path during which discrete time period, and by which party, so that concurrency can be demonstrated or ruled out with the schedule data itself rather than asserted in a narrative. A claim that ignores concurrent delay — either the contractor's own contribution or evidence the agency will raise — invites the reviewer to make that determination without your analysis, which rarely favors the claimant.
Building the Record Before You Need It
The strongest EOT claims are assembled from records that were created contemporaneously for other reasons — daily reports, RFI logs, monthly schedule narratives, meeting minutes — rather than reconstructed after the fact specifically to support the claim. Reviewers can generally tell the difference between a delay narrative built from records created in real time and one written retrospectively to fit a conclusion. Maintaining thorough, honest contemporaneous documentation throughout the project, independent of whether a claim is anticipated, is what makes the eventual EOT submission a matter of assembly rather than reconstruction.
It is worth treating every monthly schedule update as a small piece of a claim you may never file, rather than as a compliance formality. The narrative that explains a delay clearly the month it happens is a far stronger piece of evidence than the same explanation written from memory eight months later, after positions have hardened and the paper trail has to be reconstructed from emails and meeting notes instead of a report written for that exact purpose.
One more practical point worth building into your claims process: track the specific reviewer standard for the agency you are working with, not just the general framework. USACE, Caltrans, and individual state DOTs each have their own scheduling specifications, their own preferred documentation format, and often their own informal expectations that experienced local counsel or a scheduling consultant who has worked with that specific agency will know. A claim built to a generic standard, rather than the standard the actual reviewer on your project applies, gives up an advantage you do not need to give up.