EOT under FIDIC: your programme is a condition of entitlement

Most contractors treat the programme as a reporting obligation and the claim as a separate exercise in letter-writing. Under the 2017 FIDIC forms they are the same exercise. Sub-clause 8.3 says what the programme must contain and when; sub-clause 20.2 sets the notice bar that kills late claims; and buried in the general requirements is the provision that allows the Engineer to reduce an extension of time because the programme did not comply. Claims do not usually fail on the merits. They fail here.

Three provisions decide the argument

The 2017 second editions of the Red, Yellow and Silver Books restructured claims and tightened the programme obligation at the same time, and the two changes work together. Whatever your view of the drafting, the machinery is coherent: the contract wants a live, compliant programme in place before anything goes wrong, so that when something does, the effect can be measured against it.

• Sub-clause 8.3 (Programme) — what the programme has to contain, when it must be submitted, and what happens when it stops reflecting reality.
• Sub-clause 20.2 (Claims for Payment and/or EOT) — the 28-day Notice of Claim, the fully detailed Claim, and the consequences of missing either.
• Sub-clause 20.2.7 — the general requirement that ties the two together, and the one that surprises people.

Sub-clause 8.3: the programme is a specified deliverable

The Contractor must submit an initial programme within 28 days of receiving the Notice of Commencement. That is not a courtesy submission; 8.3 carries a long and specific list of what the programme has to show, and it is worth reading as a checklist rather than as prose. In summary, it must set out:

• the Commencement Date and the Time for Completion of the Works and of each Section;
• the dates on which the Contractor will be given right of access to and possession of the parts of the Site;
• the order in which the Contractor intends to carry out the Works, including the anticipated timing of design, Contractor's Documents, procurement, manufacture, inspection, delivery to Site, construction, erection, installation, testing and commissioning;
• the review periods for Contractor's Documents and the sequence and timing of inspections and tests specified in the Contract;
• for a revised programme, the changes from the previous one; and
• a supporting report describing the methods the Contractor intends to adopt, the major stages, and the resources — Contractor's Personnel by discipline and Contractor's Equipment — required on Site for each major stage.

Two of those items do most of the work in a later dispute. Access and possession dates convert a vague grievance about site availability into a measurable variance. And the supporting report on resources and methods is what turns a bar chart into a statement of intent that can be tested — it is, in substance, a schedule basis document by another name, and contractors who write one properly at tender stage are in a materially better position two years later.

The review clock, and what "no-objection" is not

The Engineer has 21 days after receiving the initial programme, or 14 days after a revised one, to give a Notice of No-objection or to state the extent to which the programme does not comply with the Contract. If the Engineer says nothing within that window, a Notice of No-objection is deemed to have been given.

Note what that machinery does and does not do. The Engineer cannot simply reject the programme into silence — the obligation is to state the extent of non-compliance, which is a reasoned response, not a refusal. And a Notice of No-objection does not make the programme correct, does not transfer risk, and does not relieve the Contractor of any obligation under the Contract. Practitioners who assume that a no-objected programme has been "approved" and is therefore beyond challenge are in for a bad afternoon in cross-examination.

The obligation is continuous. If the programme ceases to reflect actual progress, or is otherwise inconsistent with the Contractor's obligations, the Contractor must submit a revised programme — in practice within 14 days of the Engineer's notice saying so. This is the provision that makes a stale programme a breach rather than merely a nuisance, and it is the hook that 20.2.7 later hangs on.

Sub-clause 20.2: the notice bar

The claims regime runs on two clocks and both are unforgiving.

The Notice of Claim must be given as soon as practicable and no later than 28 days after the Contractor became aware, or should have become aware, of the event or circumstance. The consequence of missing it is stated in terms: the Time for Completion shall not be extended, the Contractor is not entitled to additional payment, and the Employer is discharged from liability in connection with the claim.

The 2017 drafting is not quite as absolute as the 1999 wording it replaced. A late notice can be revived where the receiving party disputes it and the Engineer, in reviewing the position, considers there are circumstances that justify it — with the degree to which the delay in notifying prejudiced the other party's ability to investigate being a central consideration. That is a lifeline, not a plan. It requires you to argue about whether you should have the entitlement instead of about the entitlement itself, and it is materially harder to win.

The fully detailed Claim follows within 84 days of awareness (or as agreed), and must include a statement of the contractual or other legal basis, the supporting records and the substantiation of the EOT and/or additional payment claimed. For a time claim, "substantiation" means a demonstration of critical delay — which brings us back to the programme, because there is nothing else to demonstrate it against.

20.2.7: the provision that decides more claims than anyone admits

Among the general requirements sitting under 20.2 is the one worth committing to memory. Where the Contractor has failed to comply with sub-clause 8.3, the extension of time to which it would otherwise be entitled may be reduced to the extent that the failure has prevented or prejudiced proper investigation of the claim.

Read that as an evidential rule rather than a penalty and it becomes obvious what it is doing. The Engineer is being asked to determine whether an employer risk event caused critical delay. The only instrument for answering that question is the programme. If the programme was never submitted, was submitted without the access dates, or has not been revised since month four of a fifty-month job, the Engineer genuinely cannot investigate — and the contract puts the consequence of that on the party who was obliged to maintain it.

This is why "our planner is behind on the updates" is not an internal housekeeping matter. It is a live commercial exposure with a clause number attached.

Where FIDIC time claims actually fail

In our experience of reviewing submissions and the expert reports that follow them, failures cluster into four patterns, and only the last one is about delay analysis at all.

The fourth is the one this site exists to address, and it is worth being blunt about the mechanism. A claim for critical delay is an argument that a specific event moved a specific path that drove the completion date. If the completion date is being held by a "Finish On or Before" constraint rather than by logic, there is no driving path to point at. If a third of the network has open ends, delay does not propagate and the analysis shows an impact of zero. If negative float is scattered through the file, the critical path is ambiguous and the other side's expert gets to choose which version to argue from. None of these are exotic failures; they are the ordinary output of a programme built to be submitted rather than built to be used, and they are all detectable in minutes.

Concurrency, and why FIDIC sends you elsewhere

Sub-clause 8.5 sets out the causes of delay that entitle the Contractor to an extension. On concurrency, the 2017 editions do something unusual: where a delay caused by the Employer is concurrent with a delay for which the Contractor is responsible, the entitlement is to be assessed in accordance with the rules and procedures stated in the Particular Conditions — and if none are stated, taking due regard of all relevant circumstances.

In other words, FIDIC declines to settle the argument and hands it back to the parties. If your Particular Conditions are silent, you are into the general law of the governing jurisdiction and the analytical positions set out in the SCL Protocol — the dominant cause approach, the apportionment approaches, and the distinction between true concurrency and sequential events that happen to overlap in a window. We have covered that ground in detail in the concurrent delay article; the FIDIC-specific point is narrower and more actionable: check whether your Particular Conditions state a rule, because if they do, that rule beats every textbook position, and it is frequently drafted to the Employer's advantage.

Records, and the clause everyone forgets

Sub-clause 4.21 requires monthly progress reports, and among the required contents is a comparison of actual against planned progress. It is easy to treat as bureaucracy. It is, in fact, the mechanism that creates the contemporaneous record on which every later analysis depends — and it is the one place where the contract obliges the Contractor to state, month by month, where the project stood against the programme.

The SCL Delay and Disruption Protocol's second edition is method-neutral by design, but it is emphatic on this point: the value of a delay analysis is determined overwhelmingly by the quality of the contemporaneous records behind it, and the parties should be establishing and maintaining a proper baseline and update discipline for exactly that reason. Read alongside 4.21 and 8.3, the message is consistent from three independent directions. The records you create today are the evidence you get to use later, and there is no retrospective substitute.

A defensible FIDIC programme submission

What we look for, and what we advise contractors to be able to produce on request within an hour:

None of that is a delay claim. All of it is what makes a delay claim possible. The contractors who recover time on international projects are not, in general, the ones with the cleverest analysis — they are the ones whose document control made the analysis available.

On your own schedule: test whether your programme could survive an expert re-run — logic, constraints, float and driving-path integrity, parsed in your browser with nothing uploaded.