Extension of Time Under FIDIC: A Complete Guide
This guide walks through Extension of Time (EoT) under FIDIC — what creates the entitlement, how to calculate it, how to present a claim that survives scrutiny, and how to handle the hardest problem in delay analysis: concurrent delay. If your project is running late, this is the roadmap.
When Is the Contractor Entitled to EoT?
Under the FIDIC 1999 Red Book, Clause 8.4 lists the main causes that entitle the Contractor to an Extension of Time. The general principle is simple: where the Contractor is delayed by an event that is not its own fault, and that affects the critical path, the Time for Completion is extended by a fair amount.
The list of qualifying causes in Clause 8.4 includes:
- Variations and changes to quantities
- Causes of delay entitling EoT under specific clauses (unforeseen conditions, suspension, Employer's Risk)
- Exceptionally adverse climatic conditions
- Unforeseeable shortages of personnel or goods caused by epidemics or governmental action
- Delays caused by the Employer or authorities
Each cause brings its own specific trigger clause — 4.12 for ground conditions, 13 for Variations, 17 for Employer's Risks, and so on. Clause 8.4 is the procedural umbrella; the substantive entitlement lives in the specific clauses.
Key Takeaway: EoT entitlement exists where a listed cause in Clause 8.4 delays the critical path and the Contractor is not at fault. The specific cause clauses (4.12, 8.4(c), 13, 17, etc.) create the entitlement; Clause 8.4 sets the procedure.
The EoT Causes Under FIDIC
Each major EoT cause has its own logic, evidence requirements, and monetary treatment:
- Variations (Clause 13) — instructed changes to the Works. Time and money both available.
- Unforeseen Physical Conditions (Clause 4.12) — sub-surface or hydrological conditions. Time and reasonable cost.
- Exceptionally Adverse Weather (Clause 8.4(c)) — abnormal climatic conditions. Time only, no money.
- Employer's Risks (Clause 17) — events at the Employer's contractual risk. Time and cost.
- Suspensions (Clause 8.8) — Engineer-instructed suspensions. Time and cost.
- Delays by Authorities (Clause 8.5) — delays caused by permitting authorities where the Contractor had no fault. Time only in many cases.
- Force Majeure (Clause 19) — extraordinary events. Time; limited cost.
Matching the right cause to the right event matters. A delay caused by a late drawing is a different claim from a delay caused by weather, and the evidence and remedies differ. Claiming under the wrong clause is how well-founded delays end up unrecovered.
Key Takeaway: The seven main EoT causes each have their own clause, evidence profile, and remedy. Weather gives time only; Variations and unforeseen conditions give both. Match the cause to the right clause or lose the claim.
How to Calculate an EoT
EoT calculation is a programme exercise, not an arithmetic one. The goal is to show how much the critical path was extended by the specific delay event — not simply how many days the project is late overall.
The standard approach:
- Establish the baseline programme — the accepted planned programme at the start of the event, with a clearly identified critical path.
- Identify the delay event — the specific cause, start date, end date, and location in the programme.
- Model the impact — insert the delay into the programme and recalculate. The difference between the resulting completion date and the pre-impact completion date is the EoT.
- Account for mitigation — where mitigation measures were reasonably available, reflect them in the calculation.
- Check for concurrent delays — identify any other events operating on the critical path at the same time, and apply the chosen apportionment method.
The number of days claimed should follow directly from this programme analysis. A round number ("two months EoT") without a supporting programme rarely survives the Engineer's scrutiny.
Key Takeaway: EoT is calculated through programme analysis, not gut feel. Baseline, delay event, impact modelling, mitigation, concurrent delay check — the days fall out of the analysis.
Delay Analysis Methods
The Society of Construction Law Delay and Disruption Protocol sets out the main delay analysis methods used in practice. Each has strengths, weaknesses, and situations where it works best:
- Time Impact Analysis (Prospective) — the delay event is inserted into the accepted programme as it happens, and the predicted impact is measured. Works well for discrete events with clear start dates.
- Impacted As-Planned — delay events are inserted into the as-planned programme retrospectively. Simpler but less reliable where the actual sequence differed materially from the plan.
- Windows Analysis — the project is divided into time windows, and delay is analysed within each. Strong at separating multiple causes; data-heavy.
- As-Planned vs As-Built — the planned and actual sequences are compared directly. Simple to explain but weak at isolating cause and effect.
- Collapsed As-Built — the delay events are removed from the as-built programme to see what the completion date would have been without them. Useful retrospectively.
Pick the method that fits the available records, the timing of the claim, and the complexity of the delay. Serious EoT claims often require a delay analyst to produce and defend the methodology. Do not expect the Engineer to accept a method just because the Contractor chose it — the method itself can become a dispute.
Key Takeaway: Pick a delay analysis method suited to the records and the timing. SCL Protocol methods are the industry standard. On complex claims, use a delay analyst — the methodology will be scrutinised as much as the numbers.
How to Present Your EoT Claim
A presentable EoT claim contains:
- Narrative summary — what happened, when, why the Contractor is entitled to EoT
- Contractual basis — the specific clause(s) engaged and how
- Programme analysis — baseline, impact, calculated EoT in calendar days
- Supporting evidence — correspondence, daily reports, photographs, third-party records
- Mitigation statement — what the Contractor did to reduce the impact
- Concurrent delay treatment — if applicable, with the apportionment method clearly identified
- Conclusion and quantum — the specific EoT sought, in days
A good EoT claim reads like a short narrative with an annexed evidence bundle — not a legal pleading. The Engineer is an engineer first. Presenting the case technically, with the programme doing the heavy lifting, usually lands better than a lawyer-drafted submission full of argument.
Key Takeaway: Narrative, contractual basis, programme analysis, evidence, mitigation, concurrent delay, conclusion. Keep it technical; let the programme do the talking. Engineers respond to engineering, not advocacy.
Concurrent Delay — The Hard Part
Concurrent delay happens when two or more causes of delay operate on the critical path at the same time — typically one caused by the Employer and one caused by the Contractor. Every serious EoT claim eventually runs into it.
There is no single correct answer. Different jurisdictions and delay analysts approach it differently:
- Malmaison approach — where there is true concurrency, the Contractor gets the EoT but not the prolongation cost. Widely used in English-law contracts.
- Apportionment — the delay is apportioned between the two causes on a fair basis. Common in Scottish and some civil-law jurisdictions.
- Dominant cause — the delay is attributed entirely to whichever cause was dominant. Analytically clean but practically hard to apply.
- Net impact — the concurrent Contractor delay cancels the EoT claim entirely. Rare in modern practice but historically influential.
The right approach depends on the contract, the jurisdiction, and the facts. What matters is identifying concurrency honestly in the claim, rather than pretending the Contractor's own delays did not exist. Engineers spot that kind of omission quickly, and it weakens the entire submission.
Key Takeaway: Concurrent delay is the hardest problem in EoT. Several approaches exist (Malmaison, apportionment, dominant cause, net impact). Acknowledge concurrency honestly in the claim — pretending it does not exist damages credibility.
Common Mistakes in EoT Claims
- No baseline programme. An EoT claim without a clearly accepted baseline is hard to calculate and harder to defend.
- Ignoring the critical path. Delays to non-critical activities do not produce EoT. Submitting them suggests the Contractor does not understand the concept.
- Missing concurrent delay. Pretending the Contractor's own delays did not happen. The Engineer will find them.
- Late notice. Every EoT cause has a 28-day notice requirement through Clause 20.1. Missing it is usually fatal.
- Round-number claims. "We want 60 days" without a programme analysis supporting the number looks like a negotiation position, not a claim.
- Bundling multiple causes. Each cause should be separately analysed, even if the overall EoT is requested as a composite figure.
- No mitigation narrative. Failing to show what the Contractor did to minimise the impact. Mitigation is a contractual duty and its absence can reduce the award.
Key Takeaway: The recurring failures are no baseline, no critical-path focus, no concurrency honesty, late notice, round-number claims, bundling, and missing mitigation. Each of these sinks otherwise valid EoT claims.
Frequently Asked Questions
Which FIDIC clauses give a right to Extension of Time?
Clause 8.4 in the 1999 Red Book lists the main causes — Variations, delays by the Engineer or Employer, exceptionally adverse weather, Unforeseen Physical Conditions, Employer's Risk events, and suspensions. Each specific cause clause also references entitlement. The 2017 Edition consolidates these but the principle is the same.
Is Extension of Time automatic when a delay occurs?
No. EoT requires proper notice under Clause 20.1 within 28 days of awareness, detailed particulars within 42 days, and a delay analysis linking the event to the critical path. Missing any of these can invalidate an otherwise legitimate claim.
What is concurrent delay, and how does it affect EoT?
Concurrent delay is when two or more causes of delay — usually one Contractor-caused and one Employer-caused — operate on the critical path at the same time. Different jurisdictions and delay analysis methods treat this differently. Some apportion, some grant full EoT, some deny it entirely. It is one of the most disputed areas in delay analysis.
Does Extension of Time always come with prolongation cost?
Not always. Weather delay (Clause 8.4(c)) gives time only, not cost. Variations and Unforeseen Physical Conditions typically give both. Check the specific clause giving the entitlement — each has its own answer on money.
What delay analysis method does the Engineer prefer?
Most FIDIC contracts do not specify, leaving the choice to the Contractor. The Society of Construction Law Delay and Disruption Protocol sets out the main methods — prospective time impact analysis, as-planned vs as-built, windows analysis, and retrospective techniques. Pick the method that best fits the available records and the event's timing.