10 Common Mistakes That Invalidate FIDIC Notices
This guide walks through the ten most consistent claim-killing mistakes in FIDIC notice drafting, grouped by type: timing errors, content errors, delivery errors, and follow-up errors. If you run a contracts function, treat this as the audit checklist you wish someone had given you on your first project.
Why Notices Fail More Often Than Claims
The uncomfortable truth is that most FIDIC claims are not lost on the merits. They are lost on procedure. Engineers and tribunals respect the two-stage structure — notice first, particulars second — and they enforce it strictly. A contractor can have a perfectly valid entitlement and still walk away empty-handed because of a procedural misstep.
Why are notices so prone to failure? Three reasons. First, they are urgent — 28 days is short. Second, they are often drafted under pressure by site teams focused on delivery, not contracts. Third, the consequences of getting them wrong only show up months later, when memory has faded and evidence has gone cold.
Every mistake on this list has been seen on real projects. Most have been seen many times. Each is avoidable with the right system.
Key Takeaway: Claims are rarely lost on merit. They are lost on procedure. The notice is where most procedural failures happen, and they are almost all avoidable.
Mistakes 1–3: Timing Errors
1. Waiting to quantify before notifying
The single most common killer. Teams want to include the full cost and time impact in the notice before sending it. By the time the analysis is complete, the 28-day window has closed. The fix is simple and painful to accept: notify first, quantify later. The notice is not a claim — it does not need numbers.
2. Starting the clock from the wrong date
Many contractors assume the 28-day clock starts when a problem "becomes serious" or "is agreed to be a claim." It does not. The clock starts at awareness — the moment a reasonable contractor should have recognized the event for what it was. Starting it from a later date is how teams convince themselves they still have time when they do not.
3. Bundling multiple events into one late notice
Classic mistake on weather claims and ongoing variations. Each distinct event is its own notice with its own awareness date. Bundling creates two problems: the earlier events are late, and the overall notice is confused about what it is actually notifying.
Key Takeaway: The timing killers — waiting to quantify, misreading awareness, bundling events — all stem from the same root: treating the notice as a polished deliverable rather than a fast, factual trigger document.
Mistakes 4–6: Content Errors
4. Missing or wrong clause reference
A notice that does not invoke Clause 20.1 — or invokes the wrong sub-clause for the event — gives the Engineer a free rejection. The notice must identify both Clause 20.1 (the procedural anchor) and the substantive clause creating the entitlement (8.4(c) for weather, 4.12 for unforeseen conditions, 13 for variations, and so on).
5. Writing the notice like a legal brief
A notice is not an argument. It is a short, factual warning that an event has occurred and a claim will follow. Notices that try to pre-argue the case with adjectives, legal language, and accusations tend to be long, late, and rejected. Save the argument for the 42-day particulars.
6. No awareness date stated clearly
If the notice does not say when the Contractor became aware of the event, the Engineer will pick a date — usually the earliest plausible one — and may time-bar the claim on that basis. State the awareness date clearly and defensibly. If there is genuine uncertainty, say so and give a range.
Key Takeaway: A good notice names the clauses correctly, states the awareness date clearly, and reads like a factual engineering report — not a legal letter. The adjectives and arguments belong in the 42-day submission.
Mistakes 7–8: Delivery & Recipient Errors
7. Sending to the wrong recipient
Under the 1999 Red Book, the notice goes to the Engineer — not the Employer's Project Manager, not the site representative, not the project director. The contract specifies the Engineer as the recipient for a reason: the Engineer has the determination function. Notices to the wrong person can be treated as unserved, regardless of whether the information reached the right people through other channels.
8. Using the wrong delivery method
Most FIDIC contracts specify the communication methods that count as valid service — usually formal letter delivered by hand, registered post, or a specified electronic system. A WhatsApp message to the Engineer's personal phone, no matter how friendly the relationship, is not a formal notice. When the contract permits multiple methods, pick the most provable one. When in doubt, use two.
Key Takeaway: Right document, right person, right method. A compliant notice delivered to the wrong recipient or through the wrong channel is often treated as no notice at all.
Mistakes 9–10: Follow-Up Errors
9. Sending the notice and going silent
The notice preserves the right to claim. The 42-day particulars exercise that right. Teams that send a strong notice and then let the follow-up slide end up with a preserved right they never use, which is about as valuable as a lottery ticket you forgot to check. Submit the detailed particulars on time. Every time.
10. No interim updates on ongoing events
When an event continues past 42 days, the Contractor must submit interim particulars and monthly updates. Many teams send one notice, one 42-day submission, and then nothing — assuming the claim is "open." It is not. The Engineer reads silence as the event ending, and the entitlement to further relief can be lost without anyone noticing until the final account.
Key Takeaway: A strong notice is worthless without follow-up. Submit the 42-day particulars on time, and keep submitting monthly updates as long as the event's effects continue. Silence kills claims quietly.
How to Build a Notice Review Checklist
Every one of the ten mistakes above can be caught by a one-page review checklist used before any notice is signed out. A good checklist asks:
- Is this within 28 days of the correctly identified awareness date?
- Does it reference Clause 20.1 and the specific substantive clause?
- Is the awareness date stated explicitly?
- Is the event described factually, without argument or legal language?
- Is the claim type (time, money, or both) stated clearly?
- Does it confirm that 42-day particulars will follow?
- Is it addressed to the Engineer as defined in the contract?
- Is it being sent by the contractually specified delivery method?
- Is it logged in the claims register with its 42-day deadline?
- Is someone accountable for the 42-day submission?
Ten questions. Five minutes. A fraction of the cost of losing even one claim. The teams that use a checklist like this religiously are the teams that rarely get time-barred — not because they are smarter, but because they have removed heroics from the process.
Key Takeaway: A one-page checklist catches nine out of ten of the mistakes on this list. Use it before every notice leaves the office. The teams that use one lose fewer claims — the ones that rely on experienced judgment alone do not.
When to Get Outside Help
Not every notice needs a claims consultant. But some do. The rough rule of thumb: if the claim value is large, the contractual basis is unusual, or the Employer has already signalled an aggressive stance, bringing in external help at the notice stage — not the arbitration stage — pays for itself many times over.
Claims consultants earn their fee when they catch the mistakes a stretched site team would miss: a creative way to evidence awareness, a second contractual basis the first pass overlooked, a structural issue in the claims register that is about to bite on the next event. The cost is a small fraction of the value at risk, and the return is measurable.
The worst time to call a consultant is the week before arbitration. By then, the mistakes are baked in. The best time is the day the event happened.
Key Takeaway: For high-value or complex claims, bring in a Claims Consultant at the notice stage — not the arbitration stage. The earlier the help, the more salvageable the claim.
Frequently Asked Questions
What is the single most common FIDIC notice mistake?
Waiting to quantify the impact before sending the notice. Teams want a complete picture before they write, and by the time the picture is complete, the 28-day window has closed. Notify early on the facts you have; quantify in the 42-day particulars.
Can a contractor ever recover after sending a late notice?
Sometimes, through arguments like prevention, estoppel, or ambiguity — but each of these is uncertain, expensive, and decided in arbitration. Recovery is rare enough that it should never be part of the plan. Design the process to comply, not to recover.
Does a notice need to be a formal letter, or can it be an email?
Check the contract's communications clause. Many FIDIC contracts require formal written communications delivered by hand or registered post. Where email is permitted, it is safest to send both formats to avoid any dispute about valid service.
Should the notice be signed by the Project Manager or the Contractor's director?
The contract usually specifies the authorized representative. In most cases a notice signed by the Contractor's authorized representative on site (typically the Project Manager) is sufficient. If there is any doubt, signing by a director adds belt-and-braces protection at no cost.
How many notices are too many on a single project?
There is no such thing as too many on a well-run project. Each distinct event deserves its own notice. Contractors who worry about looking confrontational by issuing too many notices are usually the ones who end up losing claims. The Engineer expects notices — it is how the contract works.