Back to Insights

The FIDIC notice nobody served: how a missed deadline quietly kills a claim

Aven-AI InsightsContracts & Claims7 min read
Construction workers on a partly-built concrete structure on an active site beneath an overcast sky.

Citable answer: A missed FIDIC notice can quietly kill a claim because entitlement often depends on serving notice within a defined period, commonly 28 days. Aven-AI is built to flag that clock early, cite the contract clause, and draft the notice for human review before the window closes.

There is a particular kind of loss on construction projects that leaves no mark at the time. No money changes hands. No one shouts. The works carry on. Months later, when the contractor finally puts in a claim for the extra time and cost it genuinely incurred, the Engineer points to a single sentence in the contract and the entitlement is gone. Not reduced. Gone.

That sentence is the notice requirement in FIDIC Sub-Clause 20.1, and the claim it kills was usually a good one.

What the clause actually says

Under the FIDIC 1999 forms (the Red, Yellow and Silver Books), Sub-Clause 20.1 requires that a contractor wishing to claim additional time or money "shall give notice to the Engineer, describing the event or circumstance giving rise to the claim … 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." The clock does not wait for you to quantify the claim or be certain of its merit. It runs from awareness of the event.

The sting is in the next part. If that notice is not given within 28 days, the clause provides that "the Time for Completion shall not be extended, the Contractor shall not be entitled to additional payment, and the Employer shall be discharged from all liability in connection with the claim." Writing on the Privy Council's recent treatment of the sub-clause, the construction team at Charles Russell Speechlys describe this as language "in classic condition precedent form" — the relief is conditional on the notice, and without the notice there is no relief (Charles Russell Speechlys).

The courts have backed the clause, hard

This is not a theoretical risk that tribunals soften in practice. Three significant decisions have treated Sub-Clause 20.1 as a true condition precedent. As Fenwick Elliott record in their case analysis, in Obrascon Huarte Lain SA v HM Attorney General for Gibraltar [2014] EWHC 1028 (TCC) — arising from the road and tunnel under Gibraltar airport's runway — Mr Justice Akenhead accepted that Sub-Clause 20.1 imposed a condition precedent on the contractor to notify (Fenwick Elliott). The Privy Council took the same view in NH International (Caribbean) Ltd v National Insurance Property Development Co Ltd [2015] UKPC 37, and, as Charles Russell Speechlys note, has reaffirmed that strict reading in its more recent FIDIC decision (Charles Russell Speechlys).

The point those cases drive home is uncomfortable for site teams: the strength of the underlying claim does not save it. As Howard Kennedy put it in their commentary for the International Construction Knowledge Hub, the defining feature of a condition precedent is dependency — one thing must happen before the other can (Howard Kennedy). A perfectly valid entitlement to twelve weeks of extension of time is worth nothing if the notice was served on day 31.

Why good teams still miss it

Nobody decides to skip a notice. The notice gets missed because of how a delay actually feels on site. The early signs of a delaying event are ambiguous. Ground conditions look "a bit off" before anyone confirms they are different. An information request is slow before it is formally late. By the time the team is certain there is a claim, the 28 days has often been quietly burning since the first signs — because the clause runs from when the contractor "should have become aware," not from when it was certain.

Then there is volume. A live project generates hundreds of instructions, RFIs, minutes and emails a week. Buried in that traffic is the one event that started a 28-day clock. The information to serve the notice exists. The deadline simply was not connected to it in time.

How to protect the entitlement

The fixes are unglamorous and they work:

  • Treat awareness, not certainty, as the trigger. When an event might found a claim, start the clock in your own records that day.
  • Serve early and refine later. A protective notice that flags the event preserves the position; the detailed particulars follow. Fenwick Elliott, in their analysis of the time bar under common and civil law, stress that the function of the notice is to protect the position early — the detailed claim can be developed afterwards (Fenwick Elliott).
  • Comply with form and route. Notice to the right person, in the contractual manner, within time.
  • Keep the record that proves the date. When the dispute comes, the date of awareness and the date of service are what get argued.

Where a governed AI layer helps

This is a tracking problem before it is a legal one. A contract-aware system that reads the conditions, recognises when an event on site looks like the start of a 28-day clock, and flags it to the contracts team — leaving the human to decide and serve — closes the exact gap where good claims die. It does not replace judgement. It makes sure the deadline is never the reason you lost.

This article is general information about FIDIC contract administration, not legal advice. The treatment of notice provisions varies by contract, amendment and governing law — take advice on your specific contract.

Sources & further reading

Ready to put this into practice?

See how Aven-AI flags notice, time-bar, programme and QHSE risks before the window closes.

Request early access