Weather Delay Notices Under FIDIC: Clause 8.4(c) Explained
This guide walks through Clause 8.4(c) weather delays under the FIDIC 1999 Red Book: what actually qualifies as "exceptionally adverse," what evidence you need, how to time the notice, and the mistakes that quietly kill weather claims. If you work in the Gulf, South Asia, or any region where monsoons, sandstorms, or heatwaves drive your programme, this is where the money hides.
What Counts as Weather Delay Under FIDIC?
Weather delay under Clause 8.4(c) refers to delay caused by "exceptionally adverse climatic conditions" that are beyond what an experienced contractor should reasonably have expected for the project's location and time of year. It is a narrow entitlement — not every rainy day qualifies, and most do not.
The entitlement is for additional time only. Clause 8.4(c) does not give the Contractor any right to additional payment. This surprises people every single project. Teams build elaborate cost claims around rain days, only to discover that FIDIC treats weather as a shared risk: the Contractor absorbs the cost, the Employer absorbs the time impact by granting an extension.
There is a simple logic behind that split. Both parties know the site. Both know the climate. Neither controls the weather. So FIDIC says: the time gets reset to where it should have been, but nobody pays for an act of nature.
Key Takeaway: Clause 8.4(c) gives time only, not money. Contractors absorb the cost of weather delay; the Employer absorbs the programme impact through an Extension of Time.
The Clause 8.4(c) Test: "Exceptionally Adverse"
The whole game turns on one phrase: "exceptionally adverse." If the weather was what a reasonable contractor should have expected, there is no claim. If it was significantly worse, the claim lives.
Tribunals typically apply a two-part test:
- Statistical exceptionality — was the weather materially worse than the historical norm for that specific location and month? This is a data question.
- Actual impact — did the weather in fact disrupt progress on activities that could not reasonably have been mitigated? This is a records question.
Both parts must be satisfied. You can have exceptional weather that did not affect the programme (no claim). You can have ordinary weather that disrupted a badly planned sequence (also no claim). The sweet spot — exceptional weather that hit activities on the critical path — is where valid claims live.
"Exceptional" is not a vague word. It is a statistical one. If the 15-year average rainfall for your site in April is 40mm, and your April delivered 180mm, that is defensible. If it delivered 55mm, good luck. Arbitrators can read a chart.
Key Takeaway: The test is statistical exceptionality plus actual impact. Exceptional weather that did not hit the critical path does not produce a claim — and neither does ordinary weather dressed up with strong adjectives.
What Evidence You Need to Prove It
Weather claims live or die on evidence. The strongest ones walk in with five things:
- Historical meteorological data — ideally 10+ years from the official national weather service, for the station closest to site. This establishes the norm.
- Actual weather records — daily readings during the event period, again from an official source or your own on-site station if calibrated.
- Daily site reports — recording which activities stopped, partial working, personnel affected, and duration. This is where most projects fail. No daily records, no claim.
- Photos and videos — timestamped, ideally drone footage showing conditions on site. A photo of a flooded excavation hits harder than a paragraph describing one.
- Programme analysis — showing that the affected activities were on the critical path, or how the delay consumed float that was later needed.
On-site weather stations are worth their weight in gold — literally. For a few thousand dollars, you get contemporaneous, calibrated, timestamped records of exactly what hit your site, not what hit the airport 40km away. On large projects, it pays for itself after the first claim.
Key Takeaway: Weather claims are built on historical data, actual readings, daily site reports, photos, and programme evidence. Missing any one of these creates a gap the Engineer will happily fall into.
When the 28-Day Clock Starts for Weather Events
Here is where most weather claims quietly die: the Contractor waits for the weather to "settle down" before notifying. By the time the team decides the event is worth a notice, three weeks have passed, and the 28-day window is already bleeding.
For Clause 8.4(c) purposes, awareness begins when the weather event starts materially affecting the Works. Not when it finishes. Not when the impact is fully quantified. The first day your concrete pour was cancelled, your crane stopped working, or your earthworks flooded — that is the start of the clock.
Treat each distinct weather event as its own trigger. A storm in week 1 and another in week 4 need two separate notices with two separate awareness dates. Bundling them into one end-of-season notice is the single most common way contractors in monsoon regions lose legitimate entitlement.
If the weather is an ongoing pattern (a sustained monsoon spell, for example), send an initial notice when the impact begins and supplement it with interim updates. Do not wait for the sky to clear.
Key Takeaway: The 28-day clock starts when the weather first affects the Works, not when it stops. Send a separate notice per event — do not bundle a whole season into one late submission.
How to Structure a Weather Delay Notice
A solid weather delay notice covers seven elements. None of them requires a lawyer — the good ones read like a site engineer's summary, written clearly.
- Reference the contract — state that this is a notice under Clauses 8.4(c) and 20.1 of the Conditions of Contract.
- Identify the event — the specific weather event, its type (rainfall, heat, wind, sandstorm), and the dates it affected the site.
- State the awareness date — usually the first day of material impact.
- Describe the impact — which activities were affected and how progress was disrupted. Keep it factual.
- Flag the comparison to historical norms — reference that the weather exceeded normal expectations for the location and season. Attach data if available.
- Reserve time, not cost — state clearly that the Contractor seeks an Extension of Time. Do not request money — it will just flag you as someone who has not read the clause.
- Confirm 42-day particulars — state that detailed particulars will follow within 42 days as required.
Two pages is plenty. A five-page weather notice is almost always a sign that someone is trying to pre-argue the claim in the notice itself. Save the argument for the 42-day submission.
Key Takeaway: Keep the notice factual and short. Reference the clause, identify the event, state the awareness date and impact, ask for time (not money), and confirm 42-day particulars will follow.
Common Mistakes That Kill Weather Claims
The same errors keep recurring across projects, regions, and experience levels. Contracts have a way of humbling everyone equally.
- Claiming money instead of time. Clause 8.4(c) gives only time. A notice that asks for additional payment under this clause signals that the team does not understand the entitlement.
- Bundling multiple events late. Classic monsoon-season mistake. Every weather event needs its own timely notice.
- No historical comparison. Saying it rained a lot is not evidence. Saying it rained 340% of the 12-year April average is.
- Weak daily records. If your daily site reports say "Rained. Slow progress" with no detail, you have no claim.
- Confusing weather with force majeure. Weather is Clause 8.4(c). Force majeure is Clause 19. They have different thresholds, different entitlements, and different deadlines.
- Ignoring the mitigation duty. If you had float, you were expected to use it. If you could have rescheduled affected work, you were expected to. A claim that ignores mitigation will be reduced or rejected.
- Skipping the impact on critical path. Exceptional weather that hit non-critical activities rarely produces a time extension. Show the critical-path impact or show something else.
Key Takeaway: The recurring killers are claiming money instead of time, bundling events, weak daily records, and no historical comparison. A well-evidenced notice on critical-path activities is hard to refuse.
Weather Delay vs Force Majeure — Know the Difference
These get confused constantly, and the confusion shows up in rejected notices with a depressing frequency. They are different instruments for different situations.
- Weather delay (Clause 8.4(c)) — covers weather that is worse than normal for the location. Gives time only, no money. Easier to prove and common on most projects.
- Force majeure (Clause 19 in the 1999 Red Book) — covers extreme events outside either party's control that could not have been prevented, like war, rebellion, or natural disaster. Gives time and, in limited cases, money. Much harder to prove and rarely succeeds.
A hurricane that destroys site infrastructure can qualify as force majeure. A bad rainy week cannot, no matter how dramatic the LinkedIn posts about it. Using the wrong clause is how contractors telegraph that they do not know the contract — and the Engineer will happily reject on that basis alone.
When in doubt, ask: was this weather exceptional for this location and season, but still within the range of things that happen? That is 8.4(c). Or was this a catastrophic, essentially unprecedented event? That is Clause 19 territory, and it needs a different notice, different evidence, and different expectations.
Key Takeaway: Clause 8.4(c) covers exceptional but plausible weather; Clause 19 force majeure is reserved for catastrophic events. Using the wrong clause is the fastest way to have a notice dismissed.
Frequently Asked Questions
Does every rain day entitle the Contractor to an extension of time?
No. Only exceptionally adverse weather qualifies — weather that is significantly worse than what a reasonable contractor should have expected for that location and time of year. Normal seasonal rain, even if annoying, is a programme risk that sits with the Contractor.
What historical weather data is enough to prove a Clause 8.4(c) claim?
Ideally 10 years or more of official meteorological data covering the exact site area or the nearest comparable station. The aim is to show that the weather during your event exceeded the historical norm for that specific period. Short-range or unofficial data rarely convinces an Engineer.
Can I claim for heat, humidity, or wind, or only for rain?
Any weather variable can trigger Clause 8.4(c) if it is exceptionally adverse and actually impacts the Works. Extreme heat, humidity, sandstorms, high winds, and fog have all supported successful claims. The test is impact on the programme, not the type of weather.
Is a weather delay notice the same as a force majeure notice?
No. Weather delay under Clause 8.4(c) gives only time, not money. Force majeure is a higher threshold (Clause 19 in the 1999 Red Book) reserved for truly extraordinary events such as war, epidemic, or natural disaster. Confusing the two is one of the fastest ways to have a notice rejected.
Do I need to notify for each weather event or can I bundle a whole season?
Treat each distinct weather event as its own notice with its own awareness date. Bundling a whole rainy season into one notice at the end is how teams lose the 28-day clock on the earlier events. Notify each event on time, then correlate the cumulative impact in the 42-day particulars.