What is FIDIC Clause 20.1?
FIDIC Clause 20.1 is the most commercially consequential clause in any FIDIC Red Book contract. It governs the Contractor's entitlement to make claims for additional payment or extension of time. The clause creates a strict procedural requirement: if you do not notify the Engineer within 28 days of becoming aware of the event giving rise to a claim, your entitlement is extinguished.
Not reduced. Not delayed. Extinguished.
"If the Contractor considers himself to be entitled to any extension of the Time for Completion and/or any additional payment, under any Clause of these Conditions or otherwise in connection with the Contract, the Contractor shall give notice to the Engineer, describing the event or circumstance giving rise to the claim. The notice shall be given as soon as practicable, and not later than 28 days after the Contractor became aware, or should have become aware, of the event or circumstance."
Why 28 Days is Non-Negotiable
The 28-day notice requirement is a condition precedent. In English law and across most GCC jurisdictions, a condition precedent must be strictly satisfied before any entitlement arises. Courts and arbitral tribunals have consistently upheld time-bar provisions in FIDIC contracts, even where:
- The employer suffered no prejudice from the late notice
- The claim was otherwise entirely valid
- The amount at stake was substantial
The SCL Protocol and major arbitral decisions including those from the ICC and DIAC confirm this position. Contractors cannot rely on good faith arguments or equitable doctrines to escape the consequence of a missed notice.
The commercial reality of modern construction projects is that the Employer needs certainty. The 28-day window provides this. It ensures that events are investigated while evidence is fresh and that the project budget can be adjusted in real-time. From a legal perspective, failing to comply with Clause 20.1 means you have effectively waived your right to the claim before it was even quantified.
What Triggers the 28-Day Clock?
The clock starts when the Contractor "became aware, or should have become aware" of the event. This is a dual test combining:
Actual awareness: The date you actually knew about the event. This is often documented in internal emails or site reports.
Constructive awareness: The date a reasonable contractor in your position should have known. This is the dangerous part. Courts will assess what your site team knew, what was in the site diary, and what instructions were issued.
Common trigger events include:
- A variation instruction issued by the Engineer
- An employer delay event (late drawings, delayed access, changed sequence)
- A force majeure event (weather, pandemic, political risk)
- A changed physical condition under Clause 4.12
- A suspension under Clause 8.8
Many contractors mistakenly believe that the clock starts when they have finished quantifying the claim. This is a fatal error. The obligation is to notify of the event, not the impact.
What the Notice Must Contain
The notice must describe "the event or circumstance giving rise to the claim." Subsequent case law has clarified that this requires more than a bare reservation of rights. A compliant notice should:
- Identify the specific event or circumstance
- Reference the relevant contract clause
- Give a preliminary indication of the nature of the claim
- Be addressed to the correct party (the Engineer, not the Employer)
- Be sent via the contractually specified method
A compliant notice must include:
- Reference to Clause 20.1 or the specific clause giving rise to entitlement
- Description of the triggering event
- Date of occurrence or discovery
- Preliminary indication of time and cost impact
- Correct addressee: the Engineer
- Delivery via contractual notice method
The language of the notice is critical. It must be clear that it is a formal notice under Clause 20.1. Phrases like "we might claim for this later" or "this is causing us some difficulty" are generally insufficient to satisfy the requirement of a formal notice.
The Flow-Down Problem for Subcontractors
On most GCC and UK projects, subcontracts include flow-down provisions that attempt to mirror the main contract notice requirements. However, subcontract notice periods are frequently shorter than the main contract period.
A main contract giving 28 days paired with a subcontract giving 14 days creates a 14-day commercial gap. If the subcontractor fails to notify within 14 days, they lose their entitlement against the main contractor. The main contractor retains its 28-day window against the employer, but cannot recover subcontract costs they cannot claim from below.
This gap is one of the most common sources of uninsured commercial exposure in construction. Main contractors often use these shorter windows as a commercial shield, while subcontractors often sign them without realizing they have halved their window for recovery. Lexilio's cross-document conflict detection was built specifically to identify and flag these gaps during the tender and mobilization phases.
How Contractors Lose Millions
The pattern is consistent across projects:
Stage 1: An employer instruction arrives changing the sequence of works. The site team notes it in the programme but does not classify it as a claim event because they believe they can "make up the time."
Stage 2: The commercial team becomes aware 3 weeks later when reviewing the monthly report. They note it for the next application, still focusing on quantification rather than notification.
Stage 3: The monthly application is submitted on day 35. This is the first time the Engineer receives formal word of a potential claim. The Engineer immediately rejects the claim based on the time-bar.
Stage 4: The claim, worth $400,000 in delay costs, is extinguished. The Contractor has no legal entitlement to recover a single cent.
The entire sequence takes less than five weeks and costs the Contractor their entire claim. This is not a hypothetical. It is a pattern that repeats on major infrastructure projects across the UK, UAE, Saudi Arabia, and Qatar every year. The loss is compounded because the Contractor still has to perform the extra work or bear the delay costs, effectively paying for the Employer's changes out of their own margin.
FIDIC 2017 Silver Book: A Stricter Regime
The 2017 edition of the FIDIC Silver Book (and the rest of the Rainbow Suite) tightened the notice regime further. Under Clause 20.2, the 2017 form requires:
- An initial notice within 28 days
- A fully detailed claim within 84 days
- Interim claims for continuing events
The 2017 forms also introduce a "Notice of No-objection" from the Engineer. If the Engineer fails to issue a notice of no-objection within a certain timeframe, the notice is deemed valid. Conversely, if the Engineer objects to the notice's validity (e.g., on time-bar grounds), the Contractor must include this in their detailed claim.
Failure to meet any of these deadlines under the 2017 form has consequences that extend beyond time-bar to include loss of the right to refer the dispute to the DAAB (Dispute Avoidance/Adjudication Board) and ultimately to arbitration.
The Human Factor in Notice Failures
Why do highly experienced site teams fail to send notices? Often, it is a matter of project culture.
- Fear of Confrontation: Project Managers often worry that sending a formal notice will damage the relationship with the Engineer or Employer. They prefer "collaboration."
- Optimism Bias: Teams believe they can mitigate the delay or absorb the cost. By the time they realize they can't, the 28 days have passed.
- Administrative Burden: Site teams are focused on building. Writing formal letters is seen as a distraction.
- Lack of Clarity: Teams aren't sure if an event "counts" as a claim yet.
The reality is that formal notices are a contractual requirement, not a hostile act. A professional Engineer expects them. Lexilio removes these human barriers by automating the identification and drafting process.
How Lexilio Solves This
Lexilio extracts every notice obligation from your FIDIC contract at upload. The platform:
- Identifies every clause that creates a notice obligation.
- Maps the trigger events for each obligation.
- Builds a live compliance calendar showing every upcoming deadline.
- Drafts a clause-accurate notice letter the moment a trigger event is recorded.
- Flags flow-down gaps between your main contract and subcontracts.
When an Engineer issues a variation instruction, your team records it in Lexilio. The platform identifies the Clause 20.1 obligation, calculates the 28-day deadline, and drafts the notice immediately. Your commercial team receives an alert. The notice goes out on day 1, not day 35.
By turning the contract from a static PDF into a set of active commercial alerts, Lexilio ensures that your entitlement is protected by default.
Key Takeaways
- FIDIC Clause 20.1 creates a strict 28-day condition precedent.
- Missing the deadline extinguishes your entitlement regardless of the validity of the underlying claim.
- The clock starts when you knew or should have known, not when you formally decided to claim.
- Subcontract notice periods are often shorter, creating flow-down gaps.
- A compliant notice must describe the event, reference the clause, and reach the Engineer within 28 days.
The cost of a missed notice is too high to leave to manual tracking. In a world of increasing project complexity and tightening margins, contract intelligence is no longer optional.
Lexilio reads FIDIC contracts automatically.
Missing a Clause 20.1 notice extinguishes your claim. Lexilio tracks every notice deadline automatically.
See the Notice Tracker · View pricing
Lexilio is the construction commercial intelligence platform. It extracts every notice obligation from your contract suite, builds a live compliance calendar, and drafts clause-accurate notices the moment a trigger event occurs. Available for FIDIC, NEC, JCT, and AIA contracts.
