Extension of Time

Definition

Extension of Time (EOT) is the contractual mechanism by which a contractor's completion date is pushed forward — without liability for liquidated damages — when delay events outside their control consume float on the critical path. EOTs are decided on evidence, not on argument: a credible baseline, contemporaneous records, and an accepted delay analysis method.

Why It Matters

EOTs separate genuine, compensable disruption from contractor underperformance. They are also the most disputed item on most large contracts. Done well, they preserve commercial relationships and finish projects on a defensible date. Done poorly, they trigger years of litigation.

The Process

• Notice. Within the contract notice period — often 14 to 28 days — the contractor must issue formal notice of a delay event.
• Substantiation. The contractor submits a delay analysis, typically using Time Impact Analysis or a windows method.
• Review. The engineer or contract administrator reviews against contemporaneous records and the baseline.
• Determination. An EOT is granted, partially granted, or rejected — with reasons.
• Update. The schedule baseline is updated; revised completion date issued.

Real-World Example

On a NEC4 hospital project, a six-month design release delay by the client absorbed the entire 47 working-day float on the structural critical path. The contractor submitted a windows analysis showing 42 days of compensable delay; the engineer accepted 38 after one window was rejected for poor records. The project finished 38 days late, with no liquidated damages, no claim, and a working relationship intact. The TIA had cost the contractor approximately $90,000 in consultant fees and recovered roughly $2.4M in LDs not levied.

Real-World IT Analogue

Programme commitments in enterprise IT have an EOT equivalent: rebaselining the milestone when an external dependency — a vendor API, a regulator approval, a partner go-live — slips. The discipline is identical: written notice at the time, evidence of the dependency on the critical path, and a formal rebaseline rather than silent slippage.

Key Takeaways

• EOTs are decided on records, not on arguments.
• Notice timeliness matters as much as the merit of the delay.
• Only delay on the critical path qualifies — non-critical delays may need separate disruption claims.
• The baseline must be defensible; an unaccepted baseline kills EOTs before they start.

Expert Tips

• Issue notices on time, even when liability is unclear; silence is binding.
• Maintain contemporaneous daily reports, photos, and time-stamped emails — claims rise or fall on records.
• Use the analysis method your contract names; switching method mid-project undermines credibility.
• Negotiate prospectively where possible; retrospective EOTs are harder and more contested.
• Document all concurrent delays — the contractor's own delays running in parallel reduce entitlement.

Common Mistakes

• Missing the notice period — fatal on most contracts.
• Claiming EOT for delays that did not actually consume critical-path float.
• Treating EOT and prolongation cost as the same claim — they are usually separate entitlements.
• Submitting analysis based on a target schedule rather than the contract baseline.
• Forgetting concurrent delay; assessors do not.
• Letting the schedule update lag the events; reconstruction analyses are weaker than contemporaneous ones.

Practical Lessons Learned

• Projects with weekly schedule updates win EOTs; projects with monthly updates argue them.
• The strongest EOT claims are quiet ones — notice, evidence, determination, no theatre.
• EOT culture starts at kickoff; teams that prepare for delay analysis from day one rarely need litigation.

Related Encyclopedia Entries

• Delay Analysis
• Time Impact Analysis
• As-Built Schedule
• Change Order Management
• Float Management
• Baseline Schedule

Related Research Articles, Case Studies & Tools

• Project Controls Academy: Forensic Scheduling
• Schedule Health Checker
• Failure Database
• Learning Tracks: Claims & Disputes
• Hospital EOT case study
• EOT determination outcomes