A contractor on a USD 14m highway project in the UAE loses critical access to a workfront because the Employer's approvals are late. The delay is real, the records are there, the programme impact is obvious, but nobody issues the FIDIC Red Book 28-day notice. The claim is extinguished. Full stop.
What Is FIDIC Red Book Clause 20.1?
FIDIC Red Book Clause 20.1 is the provision in the 1999 edition that governs the Contractor's obligation to notify a claim for an extension of time, additional payment, or both.
It is not an administrative preference. It is a condition precedent to entitlement.
Under Sub-Clause 20.1 of the 1999 Red Book, where the Contractor considers itself entitled to an extension of time or additional payment, the Contractor must give notice to the Engineer. That notice must 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 giving rise to the claim.
That phrase is where claims are lost: "became aware, or should have become aware".
It does not mean when the commercial team quantified the claim, when the delay analyst finished the fragnet, or when the Project Director decided the claim was worth pursuing. The clock starts when the Contractor knew, or objectively ought to have known, that an event or circumstance may give rise to entitlement.
If access is not provided on the contractual date, the trigger may be that date. If IFC drawings are late, the trigger may be when the delay to issue became apparent. If an instruction changes the scope, the trigger may be the instruction itself, even if the Employer refuses to call it a variation.
Sub-Clause 20.1 applies to the Contractor. The notice must be sent to the Engineer and identify the event or circumstance giving rise to the claim. It does not need to be fully particularised on day one, but it must be a valid notice of claim.
The 2017 Red Book changed the structure. Claims are addressed under Clause 20 and disputes under Clause 21. The 2017 edition introduced a more detailed procedure for Notices of Claim, fully detailed claims, responses, and time limits. The old Dispute Adjudication Board became the Dispute Avoidance and Adjudication Board, or DAAB.
But the commercial message did not soften. The FIDIC Red Book 2017 claims procedure made notice discipline more important because both parties operate within a structured claims administration system. Entitlement is not enough. Notice is part of entitlement.
What Happens If You Miss the 28-Day Deadline?
If the Contractor misses the FIDIC 28-day notice requirement under Sub-Clause 20.1 of the 1999 Red Book, the claim is time-barred.
No extension of time.
No additional payment.
No Employer liability.
The critical wording is brutal. If the Contractor fails to give notice within 28 days, "the Time for Completion shall not be extended", the Contractor "shall not be entitled to additional payment", and the Employer is "discharged from all liability".
That is why FIDIC Red Book Clause 20.1 is not a paperwork issue. It is a recovery issue. It is a margin issue. It is a project survival issue.
Commercial teams often try to argue around the deadline by saying the Employer knew about the event. That may be true from meeting minutes, correspondence, photographs, inspection requests, programme updates, and site records. But knowledge of the facts is not the same as a contractual notice of claim.
The Employer may know the site is flooded. The Engineer may have walked the workfront. The Project Manager may have acknowledged the late drawing. None of that satisfies Sub-Clause 20.1.
A common pattern looks like this.
An exceptional weather event hits a road project. The site team focuses on dewatering, resequencing plant, protecting temporary works, and recovering access. The QS starts collecting records. The planner reviews the critical path. Everyone agrees there will be a claim, but nobody sends the formal notice because the team wants to understand the impact first.
The notice goes out on day 31.
The Engineer rejects the claim in full. Not because the weather event did not occur, the records were poor, or the delay analysis was weak. The claim is rejected because the FIDIC notice deadline construction teams were required to meet had already expired.
That is the sting of a FIDIC contractor claims time-bar. The merits become secondary. The procedural failure becomes decisive.
In practice, the Employer's response is usually concise: the Contractor failed to comply with Sub-Clause 20.1, the condition precedent was not satisfied, and the Employer has no liability.
At that point, the Contractor is left trying to argue waiver, estoppel, prevention, governing law constraints, or some other route around the time-bar. Those arguments may exist in some jurisdictions and fact patterns, but they are not a commercial strategy. They are litigation salvage, and a Tier 1 or Tier 2 contractor should not be relying on salvage.
The correct approach is simple: issue the notice early, issue it clearly, and reserve the right to submit particulars once the effects are properly known.
1999 Red Book vs 2017 Red Book: What Changed?
The 1999 Red Book placed the Contractor's claims procedure in Sub-Clause 20.1. The Contractor gave notice within 28 days, then submitted a fully detailed claim within 42 days after becoming aware of the event or circumstance, or within another period agreed or approved. The Engineer then responded.
The 2017 Red Book reorganised the claims and disputes machinery. Claims are dealt with under Clause 20. Disputes are dealt with under Clause 21. The procedure is more developed and more balanced in form, applying claims administration to both Employer and Contractor claims.
The 2017 edition also gives greater procedural definition to the steps following a Notice of Claim. It distinguishes between the initial notice and the detailed claim submission, and sets out consequences for failures to comply with time limits.
The Engineer's role also changed in emphasis. Under the 2017 edition, the Engineer is expected to act in a more procedurally defined way when making determinations. The claims process is less informal and more rules-driven.
The DAB also became the DAAB. That change matters because the 2017 suite was intended to encourage dispute avoidance, not just dispute adjudication after positions have hardened. But dispute avoidance does not rescue a contractor that missed its notices.
The practical difference is this: the 1999 Red Book punishes missed notices severely, and the 2017 Red Book gives everyone more process to manage. More process means more deadlines and more opportunities to lose position by silence or delay.
Some project teams assume that because the 2017 edition is more elaborate, it must be more forgiving. That is the wrong conclusion. The FIDIC Red Book 2017 claims procedure makes notice management more critical, not less. A contractor now needs to track the initial notice, detailed claim, Engineer responses, deeming provisions, disagreement notices, and escalation into DAAB territory.
This is why mature commercial teams do not manage FIDIC notices from inbox memory. On complex projects, especially across FIDIC contracts in UAE and KSA, the claims calendar needs to be treated like a live contractual control system.
The Most Common Triggers Contractors Miss
- Employer-caused delays, including late drawings and late access: The clock usually starts when the Contractor becomes aware that the Employer has failed to provide an input, approval, drawing, access, possession, or decision by the required date. The common mistake is waiting until the delay appears on the accepted programme or affects the critical path. The consequence is that the Contractor may lose the EOT and prolongation cost even though the delay was plainly Employer-caused.
- Variation instructions without a formal VO: The clock may start when the Contractor receives an instruction, direction, drawing revision, site order, response to RFI, or other communication that changes the work, even if nobody calls it a variation. The common mistake is continuing the work while waiting for the formal Variation Order. The consequence is that the Employer later argues the Contractor failed to notify its claim for time or cost within the required period.
- Exceptional weather events: The trigger is not necessarily the date the full delay is calculated. It may be when the weather event occurs and the Contractor becomes aware that it may impact progress or cost. The common mistake is treating weather as a records exercise first and a notice obligation second. The consequence is a time-barred EOT claim, followed by exposure to delay damages for a period the Contractor may not have caused.
- Force majeure events: Under the FIDIC framework, force majeure or exceptional event relief depends on strict contractual administration. The clock may start when the event prevents or impedes performance, or when the Contractor becomes aware of the relevant impact. The common mistake is assuming that major external events are self-evident and therefore do not need immediate notice. The consequence is loss of relief that may otherwise have protected time, cost, or termination rights.
- Employer's risk events under Clause 17: Events allocated to the Employer's risk can still require timely contractual notice if the Contractor seeks time or money. The trigger is often the occurrence of damage, loss, interference, or disruption that the Contractor knows may give rise to entitlement. The common mistake is assuming risk allocation alone preserves the claim. The consequence is that the Contractor may prove the event was an Employer risk but still lose the financial or time recovery because the notice was late.
How to Build a Clause 20.1 Compliance System
A proper Clause 20.1 compliance system starts with the assumption that every potential entitlement event is perishable.
That means the project needs a live method for identifying, escalating, drafting, issuing, and tracking notices. It cannot depend on one Commercial Manager remembering every date while managing applications, subcontract accounts, variations, forecasts, and board reporting.
The first control is contemporaneous records. Daily site diaries, labour returns, plant sheets, progress photographs, delivery logs, inspection records, access records, RFI registers, drawing registers, and weather data should all be maintained with the expectation that they may support a notice or detailed claim later.
But records alone do not protect entitlement. A beautiful site diary does not stop the 28-day clock.
The second control is a correspondence log that identifies contractual events, not just communications. Every instruction, response, drawing issue, access constraint, approval delay, rejection, suspension, disruption, and change in sequence should be coded against contractual consequences. The question is not only "what happened?" It is "does this start a notice period?"
The third control is ownership. Clause 20.1 compliance is a commercial team responsibility. Site teams are essential because they see the event first, but they should not be expected to decide whether a FIDIC notice is required. Their job is to report triggers immediately. The commercial team's job is to protect entitlement.
The fourth control is escalation. Any event with potential time impact, cost impact, resequencing impact, productivity impact, or subcontract exposure should trigger commercial review within 24 hours. If the project team is unsure, the default should be to issue a carefully drafted protective notice.
The fifth control is calendar-based tracking. A construction notice deadline tracker should record the event date, awareness date, latest notice date, notice status, owner, correspondence, detailed claim deadline, and next action. It should also record whether the notice has been issued under the correct clause, to the correct recipient, and through the correct channel.
This last point is often missed. A notice is only useful if it complies with the contract's communication provisions. Sending a casual email to the wrong distribution list may not be enough.
A good protective notice does not need to overstate the claim. It should identify the event, state that the Contractor considers it may be entitled to an extension of time, additional payment, or both, refer to the relevant Sub-Clause, reserve rights, and confirm that particulars will follow.
For senior commercial teams, the discipline is cultural as much as procedural. Notices are not aggression. Notices are contract administration. FIDIC does not give you 28 days after certainty. It gives you 28 days after awareness, including when you should have been aware.
What Lexilio Does
Lexilio is a construction commercial intelligence platform that extracts every notice obligation from your contract, builds a project-specific compliance calendar, and drafts the exact Clause 20.1 notice the moment a trigger event is identified. Commercial teams using Lexilio never miss a notice deadline because the system tracks every obligation and alerts before the clock runs out. You can upload your FIDIC contract suite and have your full notice calendar in under 2 minutes. Get started free
Under FIDIC Clause 20.1, the contract does not care how strong your entitlement is. It cares whether you gave notice in time.
