Delay Notice Template: A Sample Letter You Can Adapt

It is Thursday afternoon. The drawings the Contractor was promised three weeks ago still have not arrived, and the clock on the notice deadline is ticking down. The Project Manager opens a blank document, types the word "Dear", and freezes. This guide hands you the rest of that letter — a delay notice template you can fill in, plus the rules that keep it valid.

What a Delay Notice Is — and Why Speed Beats Polish

A delay notice is a short letter that tells the Engineer an event has happened that is delaying the Works. It is not the claim. It is the alarm that protects the right to claim later.

Under the FIDIC 1999 Red Book, the Contractor must give this notice within 28 days of becoming aware of the event. Miss that window and the entitlement can be lost entirely, no matter how good the underlying case is.

This is where many strong claims quietly die. The delay was real, the cause was the Employer's, the cost was huge — but the notice went out on day 31, and the time bar slammed the door. Contracts have a way of humbling everyone equally.

So the priority is speed, not polish. A plain, accurate notice sent on day 5 beats a beautifully drafted one sent on day 30. Nobody ever won an arbitration because their notice had elegant prose. They won because it was on time and said the right things.

The Anatomy of a Strong Delay Notice

Every valid delay notice contains the same building blocks, whatever the cause. Get these in and the notice does its job:

• A clear label — state plainly that this is a notice of delay or a notice of claim under the contract.
• The clause relied on — the contract sub-clause that gives the entitlement, plus the claims clause (FIDIC 1999 Clause 20.1).
• The date of awareness — when the Contractor knew, or should have known, the event was causing delay. This date starts the clock.
• A factual description — what happened, where on the Site, and when.
• The effect — how the event is delaying the Works and affecting the programme.
• A reservation of rights — a statement that detailed particulars will follow within the contractual period.

Notice what is missing from that list: programme analysis, day counts, and cost figures. Those belong in the particulars, not the notice. Trying to prove the full claim in the first letter is like trying to plaster a wall before the blockwork is dry.

Keep the description factual and avoid emotion. The Engineer is reading dozens of these. A calm, dated, clause-referenced notice reads as professional. A furious one reads as a negotiation that has already gone wrong.

Delay Notice Template — Copy and Adapt

Here is a skeleton you can fill in. Replace everything in square brackets with your own facts, then delete the brackets. The same structure works for a Weather Delay, a Variation, Unforeseen Physical Conditions, late Access to Site, or Delayed Drawings — only the clause and the description change.

Two warnings on the placeholders. First, the "[42] days" figure is the FIDIC 1999 default for particulars — if a bespoke contract sets a different period, use that number, not 42. Second, the "[X.X]" clause is the cause clause, which changes with the delay type. The next section maps those out.

If hand-building this every time feels slow, that is exactly the gap ChatNotice was built to close — you describe the event in plain language and it drafts the notice with the right clause already in place.

Worked Example: A Filled-In Delay Notice

Here is the same template filled in for a Delayed Drawings situation — the Contractor cannot start foundation works because the Engineer has not issued the rebar drawings. Notice how short it is.

That is the whole notice. No spreadsheets, no programme printout, no thousand-word argument. It names the clause, fixes the awareness date, describes the event in two sentences, and reserves the rights. Job done.

Which Clause Does Your Delay Fall Under?

The skeleton stays the same, but the cause clause changes with the type of delay. Under the FIDIC 1999 Red Book, the common ones are:

• Weather Delay — exceptionally adverse climatic conditions, Sub-Clause 8.4(c). Gives time only, not cost.
• Variation — instructed changes to the Works, Sub-Clause 13. Time and cost both available.
• Unforeseen Physical Conditions — sub-surface or hydrological conditions a competent Contractor could not have foreseen, Sub-Clause 4.12. Time and reasonable cost.
• Access to Site — failure to give possession or right of access, Sub-Clause 2.1. Time and cost.
• Delayed Drawings — late issue of drawings or instructions by the Engineer, Sub-Clause 1.9. Time and cost.

Matching the right clause to the event matters more than it looks. A delay caused by a late drawing is a different animal from a delay caused by rain, and the remedy is different too — one gives money, the other does not.

One trap worth flagging: a Variation is the odd one out on timing. The clock runs from the date of the instruction, not from when the Contractor first felt the effect. Every other delay type runs from awareness. The 2017 Second Edition tidies the wording, but the logic holds.

Notice vs Particulars vs Claim — Don't Confuse Them

These three words get used as if they mean the same thing. They do not, and confusing them is how good claims get filed badly.

• The notice — the fast alarm. Short, dated, clause-referenced. Due within 28 days under FIDIC 1999. Its only job is to protect the entitlement.
• The particulars — the detailed claim that follows. Programme analysis, day counts, costs, and evidence. Due within 42 days under FIDIC 1999.
• The claim — the overall entitlement the Contractor is pursuing. The notice opens it; the particulars build it; the Engineer determines it.

Think of it like a fire alarm and a fire report. The alarm goes off the moment there is smoke — fast and simple. The report comes later, with photographs, timelines, and damage assessments. You would never delay pulling the alarm to finish writing the report.

The mistake is treating the notice as if it were the particulars. The Contractor spends three weeks perfecting a delay analysis, then serves it on day 30 as the "notice". The analysis may be brilliant, but the alarm was late, and lateness is what the time bar punishes.

Common Delay Notice Mistakes

Most rejected notices fail for the same handful of reasons. None of them are clever — they are just easy to make under pressure on a busy Site:

• Sent late. The single most common killer. The 28-day clock runs from awareness, and it does not pause for weekends or holidays.
• No clause cited. A letter that complains about a delay without naming the contract sub-clause is a complaint, not a notice.
• No awareness date. Without a clear date, the Engineer cannot test the notice against the deadline — and a missing date invites a challenge.
• Vague effect. Saying the Works are "affected" without saying how leaves the notice weak. Name the activity and why it matters.
• Buried in an email chain. A notice mentioned halfway down a long email about something else is easy for the Engineer to argue was never a notice at all.
• Wrong particulars deadline. Writing the 28-day figure where the 42-day particulars period belongs. Two different deadlines — never swap them.

The cure for all six is a template you trust. When the skeleton already prompts you for the clause, the date, and the effect, it is much harder to leave one out at five o'clock on a Friday.

Sending, Logging, and Proving Delivery

A perfect notice that cannot be proven delivered is only half a notice. If a dispute ever turns on whether the notice arrived on time, the burden of proving it usually sits with the Contractor.

Start with the contract. Many FIDIC contracts have a notices clause that names the valid address and method — sometimes a specific email, sometimes a physical address. Send by that method first; anything else can be argued as not a proper notice.

Then keep the proof. For email, save the sent message with its timestamp and any delivery or read receipt. For a registered letter or courier, keep the signed proof of delivery. The belt-and-braces approach is to use the contractual method and confirm by email the same day.

Finally, log it. Record the notice in a simple register — date sent, clause, event, method, and where the proof of delivery is filed. Future you, six months into a determination, will be grateful. Site memory fades fast; a register does not.

Frequently Asked Questions