How to write a notice of delay that actually protects your time and money
Most delay claims aren't lost on the merits. They're lost on notice. The owner held the floor, the RFI sat for three weeks, the switchgear showed up late — everybody on the job knows it happened. But the contract says written notice within a set number of days, to a named person, by a named method, and the letter went out six weeks later as an email to the owner's rep. That's how a legitimate $80,000 delay turns into a negotiation you're starting from zero.
The free notice of delay letter template above is built to prevent that. It has two parts: a fill-in notice letter that covers everything a delay notice should say, and a delay event log that calculates each event's notice deadline from your contract's notice period and flags anything late or about to be.
This page and template are not legal advice. Your contract controls. Read the notice clause before you rely on anything here, and get construction counsel involved on significant claims.
Step one: read the notice clause (before you need it)
At the start of every job — not the day something goes wrong — find the clauses covering changes, claims, delays, and time extensions, and write down:
- The deadline. How many days, and from what: the event, or when you first recognized (or should have recognized) the impact. AIA A201-2017, for example, requires claims within 21 days after the event or after the claimant first recognizes the condition, whichever is later (§15.1.2). Subcontracts are often shorter so the GC can meet its own deadline upstream. Federal contracts have their own rules — under the FAR changes clause (52.243-4), costs incurred more than 20 days before written notice may not be recoverable, and differing site conditions must be reported promptly and before the condition is disturbed (52.236-2).
- Who gets it. Usually a named party at a named address — not "whoever runs the OAC meeting."
- How it's delivered. Certified mail, hand delivery, the project management system, or email — some contracts say email doesn't count.
- What it must contain. Some clauses require an estimate of the time and cost impact; others require detailed support within a second deadline.
- What you can recover. Look for a no-damages-for-delay clause (time only, no money, for certain delays), liquidated damages, and limits on home office overhead.
Put the notice period in the template's Default Notice Period cell on the Delay Event Log so every event you add gets its deadline calculated automatically.
What goes in a notice of delay letter
The letter tab walks through each section in order. Here's what belongs in each and why.
| Section | What to write |
|---|---|
| Notice type & delivery | Notice of Delay, Notice of Claim, or both; notice number; date; delivery method. Number your notices — NOD-001, NOD-002 — so every later letter can reference them. |
| To / From | The addressee the contract names, with CCs to the architect, owner's rep, or surety if the contract requires it. |
| Contract reference | Contract number and date, the notice clause by article or section, and the notice period. The template calculates the deadline date and tells you whether you're within it. |
| 1. Event description | Facts only: what happened, when, who directed it, and the state of the work at the time. No adjectives, no blame language. A judge, arbitrator, or owner's attorney may read this letter a year from now. |
| 2. Dates & status | Date the event began, date you first recognized the impact, whether it's ongoing, and delay days to date. |
| 3. Cause | The cause category (owner directive, differing site condition, late design information, late owner-furnished equipment, suspension, weather, interference) and a short narrative stating it was not caused by you or your lower tiers. |
| 4. Affected activities | Schedule activity IDs and descriptions, the crew affected, and whether each is on the critical path. Time extensions generally require critical-path delay; off-critical delay usually earns cost, not days. |
| 5. Schedule & cost impact | A preliminary time extension request and a cost estimate by category: extended field overhead, idle equipment, demob/remob, loss of productivity, acceleration, escalation, home office overhead. Label it preliminary. |
| 6. Reservation of rights | States you reserve all rights to time and money, including impacts not yet known, and that continuing to work isn't a waiver. |
| 7. Request | Ask for the time extension, the compensation, and written direction on how to proceed by a specific date. |
| 8. Mitigation | What you're doing to reduce the impact — reassigning crews, re-sequencing, releasing equipment. You have a duty to mitigate, and documenting it takes away the easiest counter-argument. |
| 9. Supporting documents | Daily reports, photos, the directive or correspondence, RFIs, schedule fragnet, manpower and equipment logs, cost records — with Attached / To follow flags. |
Timely beats complete
If you're close to the deadline and don't have the numbers yet, send the notice anyway. A short notice that identifies the event, says it's delaying the work, reserves your rights, and promises details to follow meets the purpose of most notice clauses — giving the other side a chance to investigate and mitigate. Then send a supplemental notice with the schedule analysis and pricing. The template's Notice Type dropdown includes Supplemental Notice and Updated Notice for exactly this.
Some courts will excuse a late notice when the owner had actual knowledge and wasn't prejudiced. Don't build your claim on that hope. The whole point of the Delay Event Log is that you never have to argue it.
How the Delay Event Log works
One row per event. You enter the event start date, end date (blank if ongoing), and notice-sent date. The log calculates:
- Delay Days — end minus start, or through today if the event is still going.
- Notice Deadline — event start plus your contract's notice period (or a row-specific period for events with their own clause).
- Timeliness — "On time," "LATE by X days," "X days left to send," or "OVERDUE – not sent," color-coded so a PM scanning the log sees the problem immediately.
It also tracks estimated cost, days requested, owner response, and days granted, with totals — so at any point you can say how many days you've asked for, how many you've gotten, and what's still waiting on the owner.
Common causes of compensable delay
- Owner holds and suspensions — "stop work in that area until we finalize the layout."
- Late or incomplete design information — RFIs answered late, conflicting drawings, ASIs that re-sequence work.
- Differing site conditions — rock, abandoned utilities, contaminated soil, anything that differs materially from the contract documents.
- Late owner-furnished equipment or materials.
- Access and permit delays the owner was responsible for.
- Interference by the owner's other contractors.
Unusually severe weather and force majeure events are often excusable — you get time — but non-compensable, meaning no money. The template's Delay Type field lets you state which you're asserting.
What delay costs look like
Delay costs are real but easy to under-document. The most common categories:
- Extended field overhead — superintendent, trailer, temporary facilities, small tools, per day of extension.
- Idle equipment and standby labor — lifts, gang boxes, and crews you couldn't reasonably release.
- Demobilization and remobilization.
- Loss of productivity — often measured by comparing productivity in unimpacted periods to impacted ones (a "measured mile").
- Acceleration — overtime or added crews to recover time, if directed.
- Material escalation and storage.
- Home office overhead — recoverable under some contracts and jurisdictions, excluded by others.
The single best thing you can do: start a cost code for the delay on day one and have the foreman code standby hours and equipment to it daily. Reconstructing costs from memory six months later rarely holds up.
The records that win delay claims
A notice letter is only as strong as the daily records behind it. You want dated daily reports that describe what was done and what couldn't be, dated photos of the condition, manpower and equipment logs, RFI and submittal logs with response dates, meeting minutes, and a schedule that was updated regularly before the delay happened. Field PM keeps daily reports, photos, RFIs, change orders, and schedule on the same job, time-stamped from the field — so when you need to prove a delay, the backup is already filed. Start a free 30-day trial.
Related free templates
- Pending Change Order Log — track the change that caused the delay from PCO to approved CO
- Change Order template — price the time and cost once the owner agrees
- RFI template — document the late answer that held up the work
- Daily Field Report template — the record every delay claim depends on
- Three-Week Look-Ahead — show the planned sequence the delay disrupted
- Backcharge Notice & Log — when a sub caused the delay
- Browse all free construction templates
