What Is an Extension of Time (EOT)?

Most contracts list the specific events that qualify for an EOT, and, just as importantly, the events that don’t. What counts varies by contract, but a broadly consistent pattern appears across standard forms.

• Qualifying delays — client-instructed variations that add scope or time, latent site conditions not reasonably foreseeable at tender, delay caused by the principal or their other contractors, authority or statutory approval delays, and genuinely exceptional weather beyond the allowance already built into the program.
• Non-qualifying delays — ordinary weather within the program’s normal allowance, the contractor’s own inefficiency or poor sequencing, and, depending on the contract, a subcontractor’s delay that the principal had no hand in.
• Concurrent delay — where a qualifying and non-qualifying delay overlap, treatment varies significantly by contract, so the specific wording matters more than any general rule of thumb.

Claiming an EOT is a process, not an assumption. The contractor generally must give written notice of the delay event within a strict timeframe, often as short as five or ten business days, after becoming aware of it, followed by a fuller claim once the actual delay and its effect on the program can be measured.

A solid EOT claim identifies the delay event, shows how it affects the critical path of the program rather than some slack activity, and states the number of days claimed. The superintendent or certifier then assesses the claim and either grants the full period, a lesser period, or rejects it with written reasons, and most contracts allow the contractor to dispute that assessment through the contract’s dispute resolution process if they disagree.

• Notice of delay — given within the contractual timeframe, identifying the event as soon as it becomes apparent.
• Detailed EOT claim — showing the cause, the critical path impact, and the number of days requested, usually supported by an updated program.
• Assessment — the superintendent or certifier grants, reduces or rejects the claim, with reasons given for anything less than the full amount claimed.
• Revised completion date — if granted, the new date becomes the reference point for liquidated damages and, often, for a related prelims cost claim.

An EOT is, by itself, a time-only remedy — it moves the completion date without automatically entitling the contractor to a cent more. Many contracts deliberately separate the two: time is dealt with through the EOT clause, while any additional cost the delay caused, most commonly the extra weeks of time-related preliminaries such as supervision, site facilities and insurances, is claimed separately as delay costs or prolongation costs.

Whether delay costs are recoverable at all depends heavily on the cause of the delay and the specific contract wording — a delay caused by the client typically supports both an EOT and a cost claim, while some genuinely neutral events, certain weather clauses for instance, may justify time only, with each party bearing its own cost of the delay.

The clearest financial consequence of an EOT is its effect on liquidated damages, the pre-agreed daily or weekly rate charged if the contractor finishes after the date for practical completion. Every day added by an approved EOT is a day liquidated damages cannot be charged against, which is exactly why the claim is fought so closely from both sides.

A client has a real interest in keeping the completion date as early as defensible, since it maximises the period liquidated damages could apply; a contractor has an equally real interest in having every genuine delay recognised, since an unclaimed or rejected EOT leaves them exposed to damages for a delay that, in truth, wasn’t their fault.

The superintendent, contract administrator or certifier named in the contract assesses EOT claims, not the client directly, and not the contractor unilaterally. Their role is to apply the contract’s criteria objectively, though in practice the assessor is often engaged and paid by the client, which is one reason contractors keep their own independent delay records rather than relying solely on the assessor’s conclusions.

On larger and public-sector projects, a planner or programmer is often engaged specifically to prepare and defend the delay analysis behind an EOT claim, since demonstrating genuine critical path impact, rather than simply pointing to a delay that occurred, is usually the crux of whether a claim succeeds.

EOT is often mentioned alongside similar-sounding mechanisms, but each addresses a different problem:

• EOT vs variation — a variation changes the scope of work and may itself justify an EOT if it adds time; the EOT specifically addresses the program impact, while the variation addresses the scope and its price.
• EOT vs liquidated damages — liquidated damages are the daily or weekly charge for late completion; an EOT is the mechanism that determines what the real completion date should be before any damages are calculated.
• EOT vs delay costs — an EOT extends time; delay or prolongation costs compensate for the money lost during that extended time, and are usually claimed under a separate clause with its own tests.

Most EOT disputes come back to a small number of avoidable mistakes rather than a genuine disagreement about whether a delay occurred.

• Missing the notice deadline — the single most common and most costly mistake, since many contracts bar a claim entirely if notice isn’t given within the required time, regardless of how genuine the delay was.
• Claiming a delay to an activity with float in the program, rather than demonstrating actual impact to the critical path.
• Not keeping a contemporaneous record — site diaries, correspondence, updated programs — that shows the delay as it happened, rather than reconstructing it later from memory.
• Assuming an approved EOT automatically includes extra payment, when most contracts require delay costs to be claimed and proven separately.
• Bundling multiple delay events into one vague claim instead of identifying each cause and its specific effect on the program.