Of all the contentious provisions in international construction contracts, few have generated more disputes — or more anxiety among contractors — than the 28-day notice requirement embedded in Clause 20.1 of the FIDIC 1999 suite. Known colloquially as the “time-bar,” this clause has been the graveyard of otherwise meritorious claims, wiping out entitlements worth millions of dollars on technical grounds entirely unrelated to the merits of the underlying claim.
When FIDIC released the Second Edition of its Rainbow Suite in 2017 — the Red Book (Conditions of Contract for Construction), Yellow Book (Conditions of Contract for Plant and Design-Build), and Silver Book (Conditions of Contract for EPC/Turnkey Projects) — one of the most anticipated reforms was precisely in this area. The old single Clause 20 dealing with claims, disputes and arbitration was split into two: a new Clause 20 dealing entirely with claims, and a new Clause 21 dealing with disputes and arbitration.
But has the 2017 revision truly tamed the time-bar beast, or merely given it a new coat of paint? This is a question of acute practical significance for contractors, employers, engineers, and legal practitioners operating under FIDIC contracts worldwide.
The 1999 Regime: A Draconian Guillotine
To appreciate what changed in 2017, we must first understand what the 1999 Red Book’s Clause 20.1 actually said — and why it caused so much controversy.
Under the 1999 edition, a contractor who considered itself entitled to any extension of time and/or additional payment was required to give notice to the Engineer “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.” Failure to comply with this 28-day notice requirement had a dramatic consequence: the contractor’s claim was extinguished entirely. Clause 20.1 stated in terms that the Engineer was not required to take the claim into account and “the Contractor shall not be entitled to additional payment.”
The provision created three major difficulties in practice:
1. The Trigger Problem
Exactly when does a contractor “become aware, or should have become aware” of the event or circumstance giving rise to the claim? This question, deceptively simple on its face, has been the subject of extensive litigation and arbitration. In complex projects, a single delay or disruption event may only become apparent as critical-path delay weeks or months after it first manifests. Subterranean conditions, for example, may start affecting progress before the contractor can quantify — or even recognise — that they constitute a differing site condition entitling them to relief under Sub-Clause 4.12.
2. The Continuing Events Problem
For continuing events or circumstances — those that unfold over an extended period rather than crystallising at a single point — the 1999 clause was awkward. Was the 28-day clock triggered at the outset of the event, at each new development, or at some other point? Clause 20.1 provided for monthly interim claims for continuing events, but the interaction between the initial notice obligation and the ongoing nature of the event was fertile ground for dispute.
3. The Proportionality Problem
Perhaps most significantly, the 1999 time-bar was widely criticised as disproportionate. The automatic forfeiture of a claim — regardless of its merit, regardless of whether the employer suffered any prejudice from the late notice, and regardless of the reason for the delay — was seen by many as fundamentally unjust. Courts in various jurisdictions wrestled with whether such a clause was enforceable, whether it engaged penalty doctrines, and whether equity could intervene to relieve against its harsh operation.
Several high-profile arbitrations saw contractors lose claims worth tens of millions of dollars solely because notice was given 30 or 35 days after the triggering event rather than within 28. The merits of the underlying claim were never examined. The time-bar had functioned as a sword rather than a procedural safeguard.
The 2017 Revolution: What Actually Changed?
FIDIC’s 2017 revision addressed the claims mechanism comprehensively. The new Clause 20 is significantly more detailed than its 1999 predecessor, running to several sub-clauses that carefully prescribe the steps a claiming party must follow.
A Bilateral Regime
One of the most important — and underappreciated — changes in 2017 is that the claims mechanism in Clause 20 now applies to both the Contractor and the Employer. Under the 1999 edition, the time-bar in Clause 20.1 applied only to contractor claims; employer claims were dealt with separately under Sub-Clause 2.5, which operated differently. The 2017 edition creates a single, unified claims process applicable to both parties, which is a significant step toward procedural symmetry.
This matters in practice. An employer seeking to recover liquidated damages, or to deduct the cost of remedying defects, or to make a claim arising from the contractor’s default, is now subject to substantially the same procedural requirements as the contractor. The playing field has been levelled in a meaningful way.
The Notice Requirement: Still 28 Days, But Differently Framed
The 2017 edition retains the 28-day notice window, but the trigger is reformulated. Under Sub-Clause 20.2.1, a claiming party must give a Notice of Claim “as soon as practicable, and no later than 28 days after the claiming party became aware, or should have become aware, of the event or circumstance giving rise to the Claim.”
On its face, this looks similar to 1999. The critical difference lies in what follows. The 2017 clause expressly provides that if the claiming party fails to give the notice within 28 days, it “shall not be entitled to any additional payment, the Contract Price shall not be reduced (in the case of the Employer as the claiming party), the Time for Completion shall not be extended, and the other party shall be discharged from any liability in connection with the event or circumstance.”
The consequences of late notice are thus spelled out with even greater clarity and severity in 2017. There is no ambiguity — a failure to give timely notice extinguishes the claim.
The Engineer’s Obligation to Warn
Here, however, the 2017 edition introduces an important procedural safeguard that was absent in 1999. Sub-Clause 20.2.4 provides that if the claiming party has not given notice within 28 days, but the Engineer becomes aware (or should have become aware) of the event or circumstance, the Engineer shall notify both parties. This notification by the Engineer does not restart the clock — it does not create a fresh 28-day period — but it creates a mechanism by which the claiming party’s attention may be drawn to a potential claim before it is definitively lost.
This Engineer notification obligation is genuinely new. Under 1999, the Engineer had no comparable duty. A contractor who missed the 28-day window in 1999 would simply find its claim rejected, often only when it finally submitted its full claim months later. The 2017 provision at least creates an early-warning system.
The Detailed Claims Process: Contemporary Records and Interim Claims
Sub-Clause 20.2.3 of the 2017 edition requires the claiming party to keep contemporary records — a requirement that was present in 1999 but is now articulated with greater precision. The Engineer has the right to monitor and inspect these records, and the claiming party must permit such inspection. Importantly, keeping contemporary records is not a condition precedent to entitlement, but failure to do so will affect the ability to substantiate the claim.
For continuing events, the 2017 edition requires the claiming party to submit interim claims at monthly intervals and a final claim within 28 days of the end of the event or circumstance. This is broadly consistent with the 1999 approach.
The Engineer’s Agreement or Determination
One of the most significant procedural changes in 2017 is the enhanced role of the Engineer in resolving claims. Under the new Sub-Clause 3.7, the Engineer is required to act neutrally in making any determination — no longer acting solely as the employer’s agent. The Engineer has a 42-day period (extendable by agreement) to reach an “agreement or determination” on a claim.
Crucially, the 2017 edition requires the Engineer to consult with both parties and attempt to reach agreement before making a unilateral determination. This collaborative process — absent from the 1999 scheme — represents a significant shift in the Engineer’s function and creates a genuine opportunity for early resolution of claims before they escalate to the Dispute Avoidance/Adjudication Board (DAAB).
Judicial and Arbitral Responses: Where Are We Now?
The 2017 editions are still relatively young, and the body of case law and arbitral decisions interpreting them remains thin compared to the well-developed jurisprudence on the 1999 suite. However, several important themes are emerging.
The Time-Bar Remains Harsh
Notwithstanding FIDIC’s revisions, the fundamental nature of the time-bar has not changed. Courts in England and Wales, Singapore, the UAE, and other jurisdictions where FIDIC contracts are commonly used have generally enforced time-bar provisions strictly, subject to arguments based on prevention, waiver, or estoppel. The 2017 edition’s clearer language is likely to make such arguments harder, not easier, to sustain.
Prevention Principle Arguments
One recurring argument in time-bar cases is that the employer’s own conduct prevented the contractor from giving timely notice — for instance, because the employer concealed information about the triggering event, or because the employer’s own breaches made it impossible for the contractor to identify the event within 28 days. Such prevention arguments may have somewhat more purchase under the 2017 regime given the Engineer’s notification obligation under Sub-Clause 20.2.4, but they remain difficult to establish in practice.
The Good Faith Debate
In civil law jurisdictions — where many FIDIC projects are located, particularly in the Middle East and Continental Europe — the harsh operation of the time-bar is frequently met with arguments based on good faith and abuse of rights. Some arbitral tribunals have been receptive to the argument that it is unconscionable for an employer to invoke a time-bar where the employer knew of the underlying event, suffered no prejudice from late notice, and the contractor’s failure to give timely notice was due to circumstances beyond its control.
FIDIC’s introduction of the Engineer’s notification obligation in Sub-Clause 20.2.4 of the 2017 edition may be seen as an implicit acknowledgment of this concern. If the Engineer — who is in close contact with the project — is required to notify the claiming party of potential claims, the argument that strict enforcement of the time-bar is unconscionable becomes more difficult to sustain where the Engineer has in fact given such notification.
Practical Guidance: Operating Under the 2017 Claims Regime
Whether you are advising a contractor, an employer, or an Engineer on a FIDIC 2017 project, the following practical points should be at the forefront of your approach to claims management.
For Contractors
Identify triggers early and act immediately. The 28-day clock is unforgiving. Do not wait until a delay or cost impact is quantified before giving notice. The notice requirement is triggered not by the full understanding of the impact, but by awareness of the event or circumstance. An early, brief notice preserves entitlement even if the full quantum is not yet known.
Maintain a claims register. A systematic, project-wide register of potential claims — updated weekly — is essential on any FIDIC project. This register should track the date of each triggering event, the date of any notice given, and the status of any ongoing claim. Responsibility for maintaining the register should be clearly assigned.
Keep contemporary records religiously. The claims process under Sub-Clause 20.2.3 requires contemporaneous records. These are not merely evidence — they are the foundation of every claim. Daily site records, resource allocations, correspondence, minutes of meetings, and programme updates should all be preserved in a form that can be readily extracted and presented as part of a claim submission.
Do not assume the Engineer will notify you. While Sub-Clause 20.2.4 obliges the Engineer to notify a claiming party of potential claims in certain circumstances, this obligation is qualified. Do not rely on it as a backstop. The primary obligation to give notice remains with the claiming party.
For Employers
Understand that you are also subject to the time-bar. The bilateral nature of the 2017 claims regime means that employer claims — including claims for liquidated damages, defect rectification costs, and other deductions — are also subject to the notice requirements in Clause 20. Employers (and their advisers) who have historically focused only on the contractor’s notice obligations must now turn their attention to their own.
Do not use the time-bar as a weapon of convenience. While the time-bar is enforceable, employers who invoke it purely tactically — particularly where they knew of the underlying event, suffered no prejudice, and the contractor’s delay in giving notice was minor — risk findings of bad faith in civil law jurisdictions and may face adverse costs consequences in international arbitration.
For Engineers
Understand your notification obligation. Sub-Clause 20.2.4 creates a positive duty on the Engineer to notify parties of potential claims. This is a new and significant obligation under the 2017 edition. Engineers who fail to give such notification when they should have done so may face arguments that the employer has been prejudiced or that the time-bar should not be enforced against the contractor.
Act as a neutral in the Agreement or Determination process. The 2017 edition’s emphasis on the Engineer’s neutrality under Sub-Clause 3.7 is fundamental. An Engineer who manifestly favours the employer in the claims process — by dismissing contractor claims without proper consideration, or by determining claims in the employer’s favour without genuine analysis — undermines the entire architecture of the 2017 dispute avoidance framework.
Conclusion: Progress, But Vigilance Remains Essential
The FIDIC 2017 claims mechanism represents a genuine improvement on the 1999 regime. The bilateral application of the notice requirements, the Engineer’s notification obligation, the enhanced role of the Engineer as a neutral in the Agreement or Determination process, and the clearer articulation of the consequences of non-compliance all represent meaningful reforms.
But the fundamental reality has not changed: the time-bar is still a formidable procedural weapon, and contractors who fail to give timely notice risk losing meritorious claims entirely. The 2017 edition has not tamed the beast so much as made its rules of engagement slightly clearer and its operation slightly more balanced.
For practitioners — whether lawyers, engineers, project managers, or contract administrators — the message is consistent with what it has always been under FIDIC: understand the claims mechanism intimately, build robust claims management processes into your project from day one, and never underestimate the importance of notice.
In future posts, we will examine specific aspects of the FIDIC 2017 claims regime in greater depth, including the Dispute Avoidance/Adjudication Board (DAAB) — one of the most significant innovations of the 2017 suite — and the interaction between the Engineer’s Agreement or Determination and the DAAB process.
This article is published for general information purposes and does not constitute legal advice. Construction law is a specialist field and parties to FIDIC contracts should seek professional legal advice in relation to their specific circumstances. CMGuide Pty Ltd provides construction claims, contract management, and contractual advisory services. For more information, visit cmguide.com.au.