Almost every construction contract sets a completion date and a penalty (liquidated damages) for finishing late. An Extension of Time (EOT) is the mechanism that moves the completion date when the delay is caused by an event the contractor isn't responsible for. Win the EOT and the liquidated damages fall away for that period; lose it and you're exposed even if the delay genuinely wasn't your fault.
Grounds for an EOT
EOT is available for delay caused by employer-risk events. The exact list depends on the contract, but typically includes:
- Variations and additional work instructed by the Engineer/Employer.
- Late possession of site, late drawings, or late instructions.
- Exceptionally adverse weather beyond what could reasonably be foreseen.
- Force majeure / exceptional events (as defined in the contract).
- Suspension of works ordered by the Employer.
- Delays attributable to the Employer, the Engineer, or other contractors under the Employer.
Notice — the condition precedent that sinks most claims
This is the single most common reason valid EOT claims fail. Standard forms require the contractor to give notice within a stated period of becoming aware of the delaying event — and they make that notice a condition precedent to entitlement.
- FIDIC 1999 (Red Book) — Clause 8.4 governs EOT; Clause 20.1 requires the claim notice within 28 days of the event, failing which time is not extended.
- FIDIC 2017 — the claims machinery moves to Clause 20.2, with the 28-day notice preserved as a gateway.
- Indian standard forms (CPWD, NHAI/MoRTH, state PWD) each carry their own notice and hindrance-register requirements — read your specific clause.
If in doubt whether an event will cause critical delay, notify anyway within the contractual window. A protective notice costs nothing; a late notice can forfeit a legitimate entitlement entirely.
Cause, effect and the critical path
It isn't enough to show an employer-risk event happened. You must show it caused delay to completion — i.e. it hit the critical path of the programme. A two-week delay to an activity with three weeks of float delays nothing. This is why a properly maintained, resource-loaded programme (baseline plus updates) is the backbone of any EOT case.
Concurrent delay
Concurrency — where an employer-risk delay and a contractor-risk delay overlap in the same period — is one of the hardest areas. Approaches differ (and the contract may address it), but broadly: where two effective causes are concurrent, the contractor is often entitled to the EOT (time) but not to the associated prolongation cost (money) for that period. Get the analysis right; concurrency is where claims are won and lost in adjudication.
Delay-analysis methods
Time is not money — prolongation cost
An EOT extends the time; it does not by itself pay you for the extra time on site. To recover the cost of prolongation (extended site establishment, staff, plant standing time, overheads), you make a separate cost claim, and you generally must show the delay was an employer-risk event that also carries a cost entitlement (not, for instance, neutral weather). Keep the time claim and the money claim distinct and separately evidenced.
Records win claims
- The baseline programme and every accepted update.
- Contemporaneous progress records, S-curves and daily progress reports (DPRs).
- Site diaries, weather logs, labour and plant returns.
- All notices, instructions, RFIs and correspondence, dated and logged.
- A hindrance / delay register maintained in real time — not reconstructed at claim time.
InCore captures the delay record where it happens: coded delays and weather are logged on the Digital DPR from the field, the baseline-vs-actual programme drives the S-curve, and every event is time-stamped with sign-off. When it's time to build the EOT case, the contemporaneous evidence is already there — not reconstructed months later.