HomeBlog › Time-Bars
Time-Bars

FIDIC Sub-Clause 20.1: the 28-day notice window, explained properly

A January 2026 Privy Council ruling just confirmed, again, that this clause means exactly what it says. Here is how the clock actually runs, and where it usually gets missed.

In January 2026, the Privy Council handed down Uniform Building Contractors Ltd v Water and Sewerage Authority of Trinidad and Tobago [2026] UKPC 2, a decision that construction lawyers across the Gulf had been waiting for: another top-level confirmation that FIDIC's Sub-Clause 20.1 notice requirement is, in the Board's own words, drafted in classic condition precedent form. It is not the first time a senior court has said this, and it will not be the last. The Dubai International Financial Centre Court of Appeal reached the same conclusion in 2022, in Panther Real Estate Development LLC v Modern Executive Systems Contracting LLC, and made clear it would apply that condition strictly.

For a contracts manager on a FIDIC project, this single point of contract mechanics decides more claims than any argument about the underlying delay itself. Here is exactly how it works.

The clock does not start when you think it does

Sub-Clause 20.1 of the FIDIC 1999 Red and Yellow Books requires the Contractor to give notice of a claim not later than 28 days after the Contractor became aware, or should have become aware, of the event or circumstance giving rise to it. That single phrase, “became aware, or should have become aware,” is doing more work than most contracts teams realize: the clock does not run from the date the delaying event actually happened. It runs from the date its consequences became, or should reasonably have become, apparent to the contractor. Those two dates are very often not the same day, and the gap between them is where disputes over the deadline itself begin.

DAY 0

Event or circumstance occurs

Late drawings issued, site access denied, an instruction changes scope. The clock has not started yet on its own.

DAY X

Awareness (the real trigger)

The point at which the contractor became, or reasonably should have become, aware that the event would give rise to a claim. This can lag the event by days or weeks.

DAY X+28

Notice deadline

The Sub-Clause 20.1 notice is due. Miss it and, on the strict reading upheld again in January 2026, the right to an extension or additional payment can be lost entirely.

DAY X+42 (1999) / X+84 (2017)

Fully detailed claim due

Particulars, cause and effect, and supporting records follow the initial notice. FIDIC 2017 extended this window but added its own internal time-bar for the Statement of Contractual Basis.

+42 DAYS

Engineer's response

Under both editions, the Engineer or Employer's Representative is expected to respond within 42 days of receiving the fully detailed claim.

Why courts keep enforcing it strictly

The reasoning is consistent across the case law: prompt notice lets an issue be investigated while it is still current, and it gives the employer a real chance to reconsider an instruction before its financial consequences compound. That principle, most associated with the English case Multiplex Constructions v Honeywell Control Systems, is exactly why FIDIC drafted the clause as a strict precondition rather than a procedural courtesy. It is not there to trap contractors; it is there to keep both sides working from the same facts while those facts are still fresh.

Prompt notice lets both sides investigate a delay while the facts are still fresh.The reasoning English courts have used to justify enforcing Sub-Clause 20.1 strictly

FIDIC 1999 vs FIDIC 2017: the window widened, but the trap didn't disappear

Days from awareness to each deadline
1999: Notice
28 days
1999: Detailed claim
42 days
2017: Notice
28 days
2017: Detailed claim
84 days

FIDIC 2017's Clause 20.2 kept the 28-day notice period identical to 1999, but extended the fully detailed claim deadline to 84 days. That sounds like relief, and in one sense it is; in another, the 2017 edition also introduced its own internal time-bar around the Statement of Contractual Basis, so the extra room comes with a new procedural step that did not exist before. One useful nuance from recent case commentary: courts distinguishing FIDIC's two notice stages have found the initial 28-day notice a genuine condition precedent, while the later detailed-claim submission is generally treated as directory rather than an absolute bar in itself, though delay in submitting it can still count against the contractor when the Engineer weighs the claim.

Where the real damage happens: Particular Conditions

The standard 28 days is the default, not a guarantee. Gulf employer amendments routinely shorten notice periods, add extra condition-precedent language, or tighten what counts as a compliant notice. A contracts manager who has memorized the standard FIDIC clause from a previous project can walk straight into a shorter window on the next one without ever noticing the change, because nobody reads a 200-page contract line by line looking for a single altered number buried in the Particular Conditions.

28 days
Standard FIDIC 1999/2017 notice window from awareness
0
Grace period once a strict condition precedent is enforced

What this means in practice

  • Track awareness date separately from event date. They are legally different triggers, and disputing which one applies is a common fallback argument.
  • Assume your Particular Conditions have changed the default until you have checked. A shortened notice period is one of the most common Gulf employer amendments.
  • File the short notice first, then build the detailed claim. The 28-day letter does not need to be the finished argument, it needs to exist, on time.
  • Recent case law (DIFC 2022, Privy Council January 2026) shows courts are not softening on this. Plan around the strict reading, not the lenient one.

DraftMyEOT reads your actual Particular Conditions against the standard FIDIC baseline and flags every place they diverge, before the clock runs out.

Start a 48-hour draft →

This article is general information about how these contract mechanisms typically work. It is not legal advice, and it is not a substitute for review of your specific contract by a qualified professional.