How to Write a FIDIC Clause 20.1 Notice: Complete Guide
This guide walks through everything you need to know about Clause 20.1 notices under the FIDIC 1999 Red Book — what they are, when to send them, what to include, and how to avoid the mistakes that quietly kill millions in legitimate claims every year. Whether you're a Project Manager writing your first notice or a Contracts Engineer refining your process, this is the practical roadmap.
What Is a Clause 20.1 Notice?
A Clause 20.1 notice is the formal first step in the FIDIC claims process. It is a written notification from the Contractor to the Engineer stating that an event has occurred (or a circumstance has arisen) that the Contractor believes entitles them to additional time, additional payment, or both.
The notice is not itself a claim. It is a prerequisite to making one. Think of it as a contractual alarm bell — you're putting the other side on record that something has happened and you intend to pursue it.
Without this notice, delivered within the required timeframe, most FIDIC contracts treat your right to claim as forfeited entirely. No notice, no claim. It's that brutal — FIDIC doesn't care how valid your reasons are if you forgot to ring the bell.
The purpose is straightforward: give the Engineer and Employer early warning so they can investigate, mitigate, and keep proper records while the event is still fresh. It protects both parties.
Key Takeaway: A Clause 20.1 notice is not a claim — it is the mandatory first step that preserves your right to make one. Skip it, and you lose the claim entirely.
When Must You Send It?
The obligation to notify is triggered when the Contractor becomes aware (or should have become aware) of the event or circumstance giving rise to the claim. This is not when you finish calculating the impact or when you decide the cost is significant enough to pursue. It is the moment of awareness.
In practice, this means different things for different events:
- Unforeseeable physical conditions — when your crew first encounters the condition on site
- Late drawings or instructions — when you realize the delay will affect progress
- Exceptionally adverse weather — when the weather event begins impacting works
- Employer-caused delays — when the Employer's action (or inaction) starts affecting the programme
- Variation impacts beyond the variation itself — when you identify consequential effects on other work
The critical point: "should have become aware" means you cannot claim ignorance if a competent contractor in your position would have recognized the issue. Tribunals assess this objectively. Waiting until the damage is fully quantified is one of the most common — and most expensive — mistakes in FIDIC claims.
Key Takeaway: The clock starts at awareness, not at quantification. If a reasonable contractor would have spotted the issue, you're deemed aware — even if you hadn't calculated the impact yet.
The 28-Day Deadline
Under the FIDIC 1999 Red Book, the Contractor must deliver the notice within 28 days of becoming aware of the event. This is a condition precedent — a hard gate. If you miss it, the contract says the Employer is discharged from liability for that event, and the Engineer is not required to consider the claim.
Twenty-eight days sounds generous until you're managing multiple work fronts, dealing with subcontractors, and waiting for someone to "just confirm the numbers." I've seen teams draft notices in 20 minutes and teams that agonize for three weeks trying to make it read like Shakespeare.
The 20-minute version, sent on time, is worth infinitely more than the polished version sent on day 29. Nobody ever won an arbitration because their notice had better grammar.
Some jurisdictions have challenged the strictness of this time-bar through case law. But relying on a tribunal to override the contract language is a gamble no serious contractor should take. The safest approach is simple: treat 28 days as an absolute deadline, build a tracking system, and when in doubt, send the notice early.
Key Takeaway: The 28-day deadline is a condition precedent under the 1999 Red Book. Miss it by even one day and you risk losing the entire claim — no matter how legitimate.
What to Include in Your Notice
The contract does not prescribe a rigid format, but over decades of arbitration and adjudication, a clear best-practice structure has emerged. Your notice should include:
- Title and reference number — clearly label it as a "Notice of Claim under Clause 20.1" with a unique tracking reference
- Date of awareness — state when you became aware of the event (this establishes your 28-day compliance)
- Description of the event — a concise factual account of what happened, with dates, locations, and affected works
- Contractual basis — identify which clause(s) you believe entitle you to relief (e.g., Clause 8.4 for weather, Clause 4.12 for unforeseeable conditions)
- Nature of claim — state whether you are claiming extension of time, additional payment, or both
- Intention to submit particulars — confirm that detailed particulars will follow within 42 days as required
- Ongoing impact statement — if the event is continuing, say so explicitly (this affects the requirement for interim updates)
Keep it factual. This is not the place for persuasion, legal argument, or emotional language. Your notice should be shorter than your morning site briefing — if it's longer than two pages, you're writing the claim, not the notice. You're establishing a record, not making your case. The case comes later in the detailed particulars.
One point that catches people: you do not need to quantify the impact at this stage. The notice is about what happened and why you believe it triggers entitlement. The numbers come in the 42-day submission.
Key Takeaway: Include the event description, awareness date, contractual basis, and type of claim sought. Keep it factual and concise — detailed cost and delay analysis comes later.
Step-by-Step: Drafting the Notice
Here's the practical workflow I recommend, refined over years of writing and reviewing these notices across GCC mega-projects:
Step 1: Identify and log the event immediately. The moment something happens that might entitle you to a claim, log it. Date, time, location, personnel involved. Don't wait to see if it gets worse. A one-line diary entry on day one is your insurance policy.
Step 2: Determine the contractual trigger. Which clause is engaged? Is this a Variation (Clause 13), Unforeseen Physical Conditions (Clause 4.12), Employer's Risk (Clause 17), or something else? Get this right early — it shapes the entire notice.
Step 3: Confirm the awareness date. When did you (or should you have) become aware? Be honest with yourself. If the Engineer later argues you knew earlier, you need a defensible answer.
Step 4: Draft using plain, factual language. State what happened. Reference the clause. Declare your intention to claim time, money, or both. Confirm that particulars will follow. One to two pages is enough for most notices.
Step 5: Review and send. Have your contracts team review for completeness, not perfection. Then send it through the contractually specified channel (usually formal letter to the Engineer). Keep proof of delivery.
The entire process — from event to sent notice — should take days, not weeks. If your team spends more time drafting a notice than the Engineer spends rejecting it, something has gone wrong. Build a template. Standardize your references. Make notice-writing a reflex, not a project.
Key Takeaway: Draft quickly, review for completeness (not perfection), and send through the correct contractual channel. A good notice sent on time beats a perfect notice sent late.
Common Mistakes That Kill Claims
After reviewing hundreds of FIDIC claims, I've seen the same mistakes destroy legitimate entitlements over and over. Some of these will seem obvious — and yet they keep happening on billion-dollar projects run by experienced teams. Contracts have a way of humbling everyone equally.
- Waiting to quantify before notifying. The most common killer. Teams want to include the cost impact before sending the notice. By the time the numbers are ready, 28 days have passed. Notify first, quantify later.
- Sending a general letter instead of a formal notice. A letter that says "we are experiencing delays" without referencing Clause 20.1 or stating an intention to claim is not a valid notice. Be explicit about what you're doing.
- Wrong recipient or delivery method. The notice must go to the Engineer (under the 1999 Red Book), not the Employer's Project Manager, not the Site Supervisor. Check your contract for required delivery methods.
- Bundling multiple events into one notice. Each event should have its own notice with its own awareness date. Bundling creates confusion and gives the other side ammunition to argue that individual events were notified late.
- Including legal arguments or blame. The notice is a factual record, not a legal brief. Save the arguments for the detailed claim. Inflammatory language in a notice only damages your credibility.
- Failing to follow up with particulars. Sending the notice and then going silent is almost as bad as not sending it. You must submit detailed particulars within 42 days, or provide interim updates if the event is ongoing.
Key Takeaway: The biggest claim-killer is waiting too long. Notify early, keep it factual, send it to the right person, and always follow up with the 42-day particulars.
After the Notice — The 42-Day Particulars
Sending the notice is the easy part — think of it as knocking on the door. The 42-day particulars are what you actually bring to the meeting. Within 42 days of becoming aware of the event, the Contractor must submit a fully detailed claim — the "particulars" — setting out the factual and contractual basis, the time impact analysis, and the cost substantiation.
If the event has a continuing effect, you must submit interim particulars at monthly intervals and a final detailed claim within 42 days of the event's effects ending. This is where many teams fall down. They send a strong notice on time, then let the follow-up slide for months.
The 42-day submission should include:
- Detailed description of events with supporting evidence (photos, correspondence, daily reports)
- Delay analysis tied to the baseline programme
- Cost breakdown with supporting documentation
- Clear statement of the extension of time and/or additional payment claimed
Think of the notice as opening the door. The 42-day particulars are walking through it with your full case.
Key Takeaway: The notice opens the door; the 42-day particulars are your full case. Include delay analysis, cost breakdowns, and supporting evidence. For ongoing events, submit monthly interim updates.
Frequently Asked Questions
What happens if I miss the 28-day deadline?
Under the 1999 FIDIC Red Book, missing the 28-day deadline is a time-bar. The Contractor loses entitlement to additional time or payment for that event. Some jurisdictions have softened this through case law, but you should never rely on that. Treat 28 days as a hard deadline.
Does the notice need to mention Clause 20.1 specifically?
Yes. Best practice is to reference the clause explicitly. A general letter complaining about delays may not qualify as a valid notice if it doesn't clearly invoke the contractual claims mechanism. Make the intent unmistakable.
Can I send a Clause 20.1 notice by email?
Check your contract's communication provisions. Many FIDIC contracts require formal written notices delivered by hand or registered post. Email alone may not satisfy the requirements unless the contract explicitly permits it. When in doubt, send both.
What is the difference between a notice and a claim?
The notice is the first step — a formal alert that an event has occurred and you intend to claim. The full claim (detailed particulars) comes later, within 42 days. Think of the notice as the starting gun and the claim as the full race.
How detailed should the notice be?
Concise but specific. Identify the event, reference the clause, state your intention to claim, and mention the awareness date. You do not need full cost breakdowns or detailed schedules at this stage — those come in the 42-day particulars.