FIDIC Sub-Clause 20.1: the notice that decides every claim

On the FIDIC 2017 Red, Yellow and Silver Books, one clause does more to decide who recovers than any other: Sub-Clause 20.1, the Claims procedure. Every other entitlement provision in the contract is filtered through it. Get the notice right and the merits are heard. Get it wrong and the entitlement simply does not exist, however compelling the underlying argument.

Eight years after the 2017 edition landed, 20.1 is still the clause that catches contractors out most often. What follows is a working contractor’s guide: what the clause actually says, where engagements go wrong on it, and what makes a notice survive a Dispute Avoidance/Adjudication Board (DAAB) reference or an arbitral cross-examination.

What Sub-Clause 20.1 actually says

The 2017 editions consolidated what the 1999 edition spread across several sub-clauses. The clause now applies in the same way to both Employer and Contractor when claiming additional payment, an extension of time, or other relief.

The mechanism is sequential. Every step matters.

1. Notice of Claim within 28 days. Sub-Clause 20.2.1 requires a Notice to the other party (with a copy to the Engineer on Red and Yellow) within 28 days of the claiming party becoming aware, or having reason to be aware, of the event giving rise to the claim.
2. Fully detailed claim within 84 days. Sub-Clause 20.2.4 requires a fully detailed claim within 84 days of awareness. It must set out the contractual or legal basis, the facts, and the relief sought, including quantum and time impact where relevant.
3. Continuing notices for continuing effects. Where the event has a continuing effect, the claiming party keeps contemporary records and submits further interim claims at monthly intervals.
4. Engineer’s agreement or determination. The Engineer (Red and Yellow) then proceeds under Sub-Clause 3.7 to consult, agree, or determine the claim inside the prescribed timeframes.

The 28-day Notice of Claim is the gatekeeper. If it is not served properly and on time the claim is barred, subject to the limited relief mechanism in Sub-Clause 20.2.5 (covered below).

The five places contractors fail

1. The 28-day clock starts earlier than you think

Awareness is the trigger. The clock starts when the contractor became aware, or should have become aware, of the event. That is a constructive-knowledge standard, not actual knowledge. If a reasonable contractor in your position would have appreciated the significance of an instruction, a site condition, or a change in scope, the clock is running. It does not matter whether your project team registered the issue as a potential claim at the time.

This is the trap I see most often. The team has been given an instruction, has spotted a buildability issue, or has hit a marginal ground condition, and decides to assess it for a few weeks before notifying. By the time they do, the 28 days has expired against an earlier “should have known” date, and the Employer has a strong time-bar argument.

Fix: notify on a low threshold. The notice is cheap. The bar is unforgiving. If there is a realistic chance the matter becomes a claim, serve the Notice now and refine the detail inside the 84-day window.

2. The notice is not clearly a Notice of Claim under 20.2.1

Form matters. The 2017 contracts define a “Notice” (capital N) at Sub-Clause 1.3: it must be in writing, identified as a Notice, and state the clause under which it is given. A letter that flags an issue and asks for instructions is not a Notice of Claim. An email complaining about a delay is not a Notice of Claim. A bullet on a progress meeting agenda is definitely not a Notice of Claim.

Tribunals have held contractors to the strict form. A Notice of Claim has to:

• Be in writing and identified as a “Notice”
• State that it is given under Sub-Clause 20.2.1
• Be delivered using the contract’s prescribed method (Sub-Clause 1.3 sets out acceptable forms; check the Particular Conditions for variations)
• Identify the event and the date it occurred

Fix: every project should have a standard Notice of Claim template that hard-codes the form requirements. Sign-off sits with the commercial lead, not the project engineer.

3. The 84-day fully-detailed claim is treated as optional

The 28-day Notice gets attention because the cliff-edge is obvious. The 84-day fully-detailed claim is treated more casually, which is a mistake. Sub-Clause 20.2.4 has its own deadline and Sub-Clause 20.2.5 imposes its own (softer but real) consequences for failure.

The fully detailed claim must:

• State the contractual and/or legal basis and identify the specific clauses relied on
• Set out the facts, with reference to contemporary records
• State the relief claimed, with a build-up on quantum and a delay analysis tied to the Programme

Contractors routinely submit either a strong relief section with a vague legal basis, or a strong legal basis with no proper delay analysis. Both are vulnerable. The Engineer can determine that the claim has not been properly substantiated, and the contractor goes into the determination on the back foot.

Fix: the fully detailed claim is a quasi-legal document. The same rigour you would put into a DAAB referral or an arbitration brief belongs in the 84-day submission.

4. Records are reconstructed, not contemporary

Sub-Clause 20.2.3 requires contemporary records. Contemporary means made at the time, not assembled retrospectively. A daily site diary written up the day it happened is contemporary. A narrative written six months later from memory and emails is not.

Once a dispute reaches a DAAB or arbitration, contemporaneity becomes a weapon. A contractor with daily records of an obstruction (site diary, date-stamped photographs, contemporaneous emails to the Engineer) is in a transformative position next to a contractor relying on witness recollection.

Fix: contemporary records is a project-management discipline, not a claims activity. Site teams should record everything as it happens, every day, whether a claim is in the air or not. The records that win claims are the records made before anyone knew there would be one.

5. The Sub-Clause 20.2.5 relief mechanism is misunderstood

Sub-Clause 20.2.5 in the 2017 edition introduced a partial relief mechanism. Where the claiming party fails to serve the Notice inside 28 days, the Engineer (or other determining party) may still consider the claim, but only where certain conditions are met. One condition is that the other party should not have suffered prejudice from the late notice. That is a softer position than the 1999 edition’s harder time bar.

It is also widely misread as a safety net that takes the pressure off the 28-day window. It is not. The relief is discretionary, fact-specific and hard to obtain. The claiming party carries the burden of demonstrating the conditions are met. And the prejudice question is often where relief fails, because Employers will almost always assert prejudice in the form of lost opportunity to mitigate.

Fix: treat 20.2.5 as a remedy of last resort, not a workaround. Plan the project on the basis that the 28-day window is hard. If you do find yourself relying on 20.2.5, prepare the application with the same care as the substantive claim and address each condition head-on.

What a winning Sub-Clause 20.1 file looks like

A claim file that holds up under DAAB or arbitration scrutiny has six characteristics:

• A Notice of Claim served inside 28 days, in Sub-Clause 1.3 form, identified as a Notice, citing 20.2.1, and capturing the event and date.
• A fully detailed claim served inside 84 days, with contractual basis, facts (referenced to records), and relief with a build-up.
• Contemporary records kept daily: site diary, photographs, instructions log, emails, weather where relevant.
• A live, updated Programme showing the event’s impact on critical-path activities and the resulting time impact, prepared with the planning team.
• Continuing notices at monthly intervals where the event has a continuing effect.
• A clear audit trail from Notice through fully-detailed claim through Engineer’s determination, with all communications captured.

Get those six right and the merits are heard on their merits. Get them wrong and a strong claim collapses on procedural grounds before the tribunal looks at the facts.

Why this matters more on Gulf projects

The Gulf market is FIDIC-dominated. Particular Conditions on UAE, Saudi and Qatar projects routinely modify Sub-Clause 20.1 in small but consequential ways. Shorter notice periods. Tighter awareness wording. The 20.2.5 relief mechanism removed. Additional formality requirements bolted on. What works on a UK FIDIC project will not always pass on the same form in Riyadh or Abu Dhabi.

At pre-contract stage, the Particular Conditions amendments to 20.1 are worth a focused review. Where the Employer has removed the 20.2.5 relief mechanism or shortened the notice window, the contractor’s risk profile changes materially; the risk should be priced in, or qualified out.

At delivery stage, the discipline of Sub-Clause 20.1 is what separates contractors who recover from contractors who do not. The same pattern shows up on NEC compensation events: an unforgiving notice regime that rewards procedural discipline. And when a dispute escalates to DIAC arbitration, the Sub-Clause 20.1 file becomes the spine of the entire claim case.

The bottom line

Sub-Clause 20.1 is not hard to comply with on any single event. It is hard to comply with on every notifiable event, on every project, under live delivery pressure. That is the whole point of the clause: it filters out claims from contractors whose commercial discipline does not match their substantive entitlement.

Contractors who treat the 28-day window as a hard deadline, use a standard Notice template, keep contemporary records as a default rather than an exception, and treat the 84-day fully-detailed claim as a quasi-legal document recover materially more than those who do not. The clause is simple. Following it consistently is the work.