Notice Type

FIDIC Early Warning Notice: When and How to Send One

Last updated August 2026 · 10 min read

The concrete supplier calls on a Wednesday to mention a kiln outage that might push back next week's delivery. Nothing has gone wrong yet — no drawing is late, no clause has been breached. Does the Contractor have to say anything? Under FIDIC, yes — but the clause that requires it has no deadline and no sanction, which is exactly why it gets ignored, or confused with the formal claim notice. This guide covers what that clause actually requires, what a good early warning notice says, and how it differs from the formal notice the Contractor may still need to send later.

What an Early Warning Notice Is — and What FIDIC Actually Requires

An early warning notice is a short, forward-looking letter that flags a matter which may affect the Works before it actually does. It is not a response to a delay that has happened — it is a heads-up about one that might.

FIDIC does require this. Sub-Clause 8.3 (Programme) of the FIDIC 1999 Red Book obliges the Contractor to "promptly give notice to the Engineer of specific probable future events... which may adversely affect the work, increase the Contract Price or delay the execution of the Works." The 2017 edition goes further: Sub-Clause 8.4, "Advance Warning," places a matching duty on both Parties, not just the Contractor. (Note the renumbering: the 1999 edition's Extension of Time clause, including weather delay at 8.4(c), sits at 8.4 — 2017 moved it to 8.5, freeing up 8.4 for Advance Warning.)

What neither provision attaches is a deadline or a sanction. Missing the moment forfeits nothing — which is exactly why an early warning is, in practice, treated as a soft, collaborative notice rather than a claim-protecting one. That distinction is the point of this guide.

💡

Key Takeaway: FIDIC does require advance warning of probable future events — Sub-Clause 8.3 (1999, Contractor only) or Sub-Clause 8.4 (2017, both Parties). But neither carries a deadline or sanction, and neither reserves any entitlement to time or Cost.

Why Bother, If There's No Sanction for Skipping It

Because Sub-Clause 8.3/8.4 has no teeth, it is easy to treat as optional paperwork. Doing it properly still pays off, for reasons that have nothing to do with compliance:

It buys time to help. A permit expedited or a sequencing change made isn't possible once the delay has already landed.
It keeps the relationship collaborative. An Engineer hearing about problems early reads the Contractor as organised, not defensive.
It builds a useful paper trail. A dated early warning shows the risk was flagged early — useful context, though it doesn't itself protect the entitlement.

💡

Key Takeaway: An early warning is worth doing properly because it gives the other side time to react, keeps the relationship collaborative, and builds a credible record — not because Sub-Clause 8.3/8.4 has any teeth if you skip it.

Early Warning vs the Formal Claim Notice — Don't Confuse Them

This is the mistake worth avoiding above all others: treating the early warning as if it does the job of the formal notice. It does not — the two run on different logic.

Direction. An early warning flags a probable future event. A claim notice responds to one that has happened, or is already delaying the Works.
Deadline. Sub-Clause 8.3/8.4 carries no day-count sanction. A claim notice under Sub-Clause 20.1 (1999) or 20.2 (2017) is due within 28 days of the Contractor becoming aware the event is delaying the Works or increasing Cost.
Clause cited. An early warning cites Sub-Clause 8.3 or 8.4 — not the claims clause. A claim notice must additionally cite the cause clause and Sub-Clause 20.1/20.2.
Entitlement. An early warning reserves nothing. A claim notice is what protects the entitlement.

If the kiln outage does slip the pour, the formal notice is still due within 28 days of that later awareness date — not the date of the early warning.

💡

Key Takeaway: An early warning never substitutes for the formal notice. If the flagged risk becomes real, the 28-day clock for the Sub-Clause 20.1/20.2 notice starts from the date the Contractor became aware the event is actually delaying the Works.

Early Warning Notice Template — Copy and Adapt

Here is a skeleton citing Sub-Clause 8.3 (FIDIC 1999). Swap in 8.4 for the 2017 edition, or check the actual clause number for a bespoke contract. Replace everything else in square brackets, then delete the brackets.

[Date] To: [Engineer's / Employer's name and company] Project: [Project name and contract reference] Early Warning under Sub-Clause [8.3 / 8.4] — [Brief description of the matter] The Contractor gives notice under Sub-Clause [8.3 / 8.4] of the Conditions of Contract of a specific probable future event which may adversely affect the work, increase the Contract Price, or delay the execution of the Works. This notice is given at the earliest opportunity to allow proposals for mitigation to be considered jointly. The Contractor became aware of the matter on [awareness date]. [Factual description of the matter — what has happened or been notified, and by whom]. If the matter materialises as anticipated, it is likely to affect [affected activity/milestone], with a possible impact in the order of [likely impact, e.g. "5-7 days"]. The Contractor is [taking / considering] the following mitigation measures: [mitigation steps, or state "none identified at this stage"]. This notice is given without prejudice to any rights or obligations of either Party under the Contract. It is not a notice of claim under Sub-Clause 20.1/20.2, and the Contractor reserves all rights should the matter in fact delay the Works or affect Cost. [Name] [Designation, for the Contractor]

⭳ Download this template as a Word document — free

If a properly worded draft — with the right sub-clause number for your edition already in place — sounds faster than filling in brackets by hand, that is the gap ChatNotice's Early Warning Notice tool was built to close.

💡

Key Takeaway: Cite Sub-Clause 8.3 (1999) or 8.4 (2017) — check which edition and number your contract actually uses. Keep the without-prejudice closing line regardless; it is what keeps this from being read as a claim.

Worked Example: A Filled-In Early Warning Notice

Here is the same template filled in for a likely material-supply disruption flagged well before it becomes a real problem.

4 June 2026 To: Ms L. Vantongeren, Resident Engineer, Vantongeren Associates Project: Riverside Logistics Hub — Contract RLH-2025-03 Early Warning under Sub-Clause 8.3 — Possible Delay to Grade C40 Concrete Deliveries The Contractor gives notice under Sub-Clause 8.3 of the Conditions of Contract of a specific probable future event which may adversely affect the work, increase the Contract Price, or delay the execution of the Works. This notice is given at the earliest opportunity to allow proposals for mitigation to be considered jointly. The Contractor became aware of the matter on 4 June 2026. On that date the Contractor's concrete supplier advised of a kiln outage that may delay Grade C40 deliveries scheduled to begin 15 June 2026. If the matter materialises as anticipated, it is likely to affect the Block C slab pour, with a possible impact in the order of 5-7 days. The Contractor is sourcing an alternative supplier and reviewing whether finishing trades on Block C can be resequenced to absorb part of the delay. This notice is given without prejudice to any rights or obligations of either Party under the Contract. It is not a notice of claim under Sub-Clause 20.1, and the Contractor reserves all rights should the matter in fact delay the Works or affect Cost. R. Adeyemi Project Manager, for the Contractor

Short and specific. It names the risk, the likely effect, and what is already being done — everything the Engineer needs to decide whether to help, nothing that oversteps into a claim the event has not yet become.

What a Good Early Warning Notice Includes

Five things, every time, regardless of how the matter came to light:

The matter itself — what has happened or been notified, described factually.
The awareness date — when the Contractor first learned of it. No clock runs on this date, but it matters for the paper trail.
The likely impact — which milestone, and a rough magnitude if one can honestly be estimated.
Mitigation steps — what is being done to reduce the impact. This turns the letter from a complaint into a collaboration.
A without-prejudice statement — confirming the notice is goodwill, not a claim, and all rights are reserved if the matter materialises.

💡

Key Takeaway: The matter, the awareness date, the likely impact, the mitigation steps, and a without-prejudice line. Leave out programme analysis and cost figures — those belong in a claim, not a warning.

Common Mistakes

Early warning notices are low-risk by design, but a few habits undercut them:

Treating it as the formal notice. The 28-day claim clock is not satisfied by an early warning — the formal notice is a separate letter with its own trigger date.
Citing the wrong sub-clause number. 8.3 is 1999 numbering (Contractor only); 2017 moves it to 8.4 (both Parties) and shifts the 1999 EOT/weather clause from 8.4 to 8.5. Mixing these up misstates the Contractor's position.
Sending it too late to matter. A warning sent the day before impact is not early — it is a delay notice with extra steps.
Skipping mitigation. Naming a risk without saying what is being done reads as an alarm, not a collaboration.
Dropping the without-prejudice line. Without it, a goodwill note can later be read as more than intended.

💡

Key Takeaway: Don't let an early warning stand in for the formal notice, don't mix up the 1999/2017 sub-clause numbers, and don't send it late, thin on mitigation, or without the without-prejudice line.

Frequently Asked Questions

Does FIDIC require the Contractor to send an early warning notice?

Yes, in principle. Sub-Clause 8.3 of the FIDIC 1999 Red Book requires the Contractor to promptly notify the Engineer of probable future events that may adversely affect the work, increase the Contract Price, or delay completion. FIDIC 2017 renumbers this to Sub-Clause 8.4 and extends the duty to both Parties. Neither carries a deadline or a sanction for missing it, so in practice it is treated as a soft, goodwill-style notice, not a claim-protecting one.

Is there a deadline for sending an early warning notice?

No day-count deadline applies, because Sub-Clause 8.3/8.4 is not the claims clause — unlike a Sub-Clause 20.1 or 20.2 claim notice, which is due within 28 days of awareness. Even without a deadline, an early warning loses its value the longer it is held back; the point is to flag the risk while there is still time to react jointly.

Does an early warning notice protect my right to an extension of time or cost?

No. It shares information early but does not preserve entitlement. If the flagged matter turns into an actual delaying event, the Contractor must still send the formal notice under Sub-Clause 20.1 (1999) or 20.2 (2017) within 28 days of awareness, and detailed particulars within 42 days (1999) or 84 days (2017).

Can I cite a clause number in an early warning notice?

Yes — cite Sub-Clause 8.3 for FIDIC 1999, or 8.4 for the 2017 edition. Check the actual contract first, since bespoke or MDB-harmonised amendments sometimes renumber or replace this clause. Keep the without-prejudice wording regardless, so the notice cannot be read as a claim.

What should I do after sending an early warning notice?

Keep a copy and log the date sent. If the risk materialises, follow immediately with the formal notice under the applicable delay clause and Sub-Clause 20.1/20.2 — and start that clock from the awareness date of the delaying event itself, not the early warning.

Authoritative Sources

This guide reflects the FIDIC Conditions of Contract and established construction-law authority:

FIDIC Conditions of Contract — the official contract suite from the International Federation of Consulting Engineers, setting out the Sub-Clause 20.1/20.2 claims procedure an early warning does not replace.
SCL Delay and Disruption Protocol — the Society of Construction Law's guidance on collaborative, early notification practice, distinct from the strict contractual notice regime.

About the Author

Muhammad M. Jiwani is a Project Director with 15 years' experience on major infrastructure and energy projects administered under FIDIC contracts. He writes from first-hand experience serving notices and managing contractual claims on live projects.

Draft your early warning notice now.

Book a demo