Notice discipline under FIDIC is the single highest-leverage commercial control on any project running under the Rainbow Suite. Every experienced claims practitioner knows this. What is less commonly discussed — because it doesn't lend itself to slogans — is which specific elements of notice discipline actually determine whether entitlement survives, and which elements matter far less than most contractors assume.
This article draws on patterns observed across contractor-side engagements over multiple years, multiple jurisdictions and multiple contract flavours (Red, Yellow, Silver Books, with typical Employer amendments). It sets out what we've seen actually move the needle on entitlement outcomes — and what we've seen get treated as important but rarely does.
The 28-day window under FIDIC 1999 and 2017 editions
The FIDIC 1999 editions impose a 28-day period for the Contractor to give notice of a claim under Sub-Clause 20.1 (Red and Yellow Books) or 20.2 (Silver Book). The 2017 editions retain the 28-day period but under differently numbered clauses. The clause language treats the 28-day period as a condition precedent — failure to notify within the period is intended to extinguish entitlement.
In practice, the enforceability of the condition precedent varies by jurisdiction. English courts have generally upheld strict time-bar treatment where the language is clear (Obrascon, Multiplex). Middle Eastern jurisdictions have shown more variability, with some courts admitting equitable arguments around notification. Civil law jurisdictions apply their own principles to condition precedents.
What matters practically for the contractor: assume the time bar operates. Do not rely on jurisdiction-specific arguments about enforceability. Get the notice in within 28 days, in the right format, to the right recipient, referencing the right clause. Everything downstream depends on this discipline holding.
What form does the notice actually have to take?
This is where a lot of contractor teams get themselves into trouble. FIDIC does not specify a form. It requires the Contractor to give notice describing the event or circumstance giving rise to the claim. What we have seen work in practice: a document titled 'Notice of Claim under Sub-Clause 20.1' (or the applicable edition), addressed to the Engineer, referencing the specific clause, describing the event and reserving rights on cost and time impact pending particulars.
What we have seen fail: emails with contested subject lines, letters that describe an event but do not identify themselves as claim notices, notifications sent only to the Employer without copying the Engineer, notices that identify the event but do not reference the entitlement clause. All of these have been rejected in Engineer determinations we have seen.
The remedy is not complex. Have a standard notice template. Use it every time. Ensure the notice identifies itself as a notice of claim under the specific clause. Send it to the Engineer with a defined copy list. Log it. Do this for every event without exception — including events where the internal team is unsure whether they amount to a claim.
The 42-day particulars requirement
Sub-Clause 20.1 (1999) requires the Contractor to submit particulars within 42 days after the Contractor became aware, or should have become aware, of the event. The 2017 edition operates similarly with revised drafting.
The 42-day period is where a lot of claims either get built into defensible submissions or degrade into placeholders. What we have seen work: the particulars submitted within 42 days include a preliminary quantum assessment (even if reserved), a preliminary time impact assessment (even if reserved), and a clear reservation of rights for supplementary particulars pending further analysis. What we have seen fail: 'we reserve our rights on cost and time' with no further content — this has been treated as inadequate particulars by multiple Engineer determinations we have seen.
The lesson: the particulars submission is not just a procedural marker. It is the substantive first statement of the claim. Treat it as such.
What matters less than most contractors assume
The physical format of the notice (letter versus formal document versus email attachment) matters less than most contractors assume, provided the notice is clearly identifiable, references the clause, and is properly addressed. What matters is whether the notice was given, when, and whether it substantively communicated the required content.
The signatory of the notice matters less than most contractors assume, provided the signatory holds authority under the contract or under the contractor's internal delegation. What matters is that the notice was authorised.
The specific wording of the reservation-of-rights language matters less than most contractors assume, provided the reservation clearly indicates that cost and time impact remain to be quantified. Elaborate reservation language does not add strength; simple, clear reservation language does the job.
The compounding value of discipline
Contractors that operate consistent notice discipline across every project on their portfolio see a compounding effect. Notices become routine. The internal team stops treating them as adversarial acts. The Engineer's Representative stops treating them as escalations. The record base accumulates continuously rather than being reconstructed at close-out.
This is where the shared-capability model delivers particular value. Ashforte runs notice discipline as a standardized workstream across the contractor's live projects — same templates, same review, same log, same cadence. Consistency across the portfolio is the mechanism that turns notice discipline from a burden into a routine commercial control.
For any contractor running multiple live FIDIC-based projects, notice discipline is the single most important element of the contract management function to standardize. Everything downstream — entitlement recovery, claim defensibility, close-out negotiation — depends on it holding.