Notice of Delay Template with Deadline Tracking
Log every delay event, track notice deadlines automatically, and issue contractually compliant notices before entitlement slips.
- Free Excel download
- Automatic deadline countdowns
- AIA · JCT · NEC4 guidance included

A complete delay notice workflow in one Excel file
A delay notice template to fill in and issue, plus a delay event log to track every open event and deadline on the project.
- Issue notice in minutes, not hours
Fill in the event details, export to PDF, sign, and send. The form is ready to use and structured around what the contract actually requires. - Protect your right to claim costs, not just time
Reservation of rights language is built into the notice. A time-only notice can be challenged as having waived cost entitlement. This prevents that argument by default. - Send a notice that's harder to reject
Structured sections cover event description, affected activities, schedule impact, mitigation steps, and supporting documents. These are the elements that determine whether a notice holds up.
- Never miss a notice deadline again
Enter your contract notice period once. Every event gets a deadline calculated automatically and a live countdown showing days remaining. - See exactly where you're exposed
Red flags a missed deadline. Amber means five days or fewer remain. A summary at the top shows total events, notices issued, and overdue items in one view. - Build a record that holds up in a dispute
Each event captures what happened, when you first knew, critical path impact, whether notice was issued on time, and whether costs were reserved. - One log, no more chasing email threads
Site teams log events. The office tracks compliance. Everyone works from the same log with no gaps between what happened and what's on record.
- Contract-specific guidance for AIA, JCT, and NEC4
Notice requirements, when the clock starts, and what happens if you miss the deadline, covered for each contract form in plain language. - Step-by-step from first awareness to close
Five steps: set up the log, log the event, watch the deadline, issue the notice, track to close. Written for PMs who need to use this on a live project today. - The five most common notice failures, called out
Waiting too long, vague descriptions, wrong addressee, missing cost reservation. Flagged explicitly so you know what to watch for.
Built for the people responsible when entitlement is lost
If you're responsible for delivering the project or protecting the contract position, this log was built for your workflow.
- Project Manager
Know exactly which delay events are open, how many days you have left to issue notice, and what's already been protected. Walk into every owner meeting with a log that's current and defensible. - Project Executive
Stop finding out about missed notice windows after the fact. A consistent log format across projects means you can see notice compliance and open exposure before it becomes a dispute. - Contracts Manager
Get a delay record that's already structured the way a claim needs it. Notice issued, costs reserved, critical path impact, and concurrent delay all captured at the point of event. - Quantity Surveyor
See clearly which events have been noticed and which haven't, and whether costs have been reserved. Use that record to build the EOT claim rather than reconstruct the history from email chains.
Frequently Asked Questions
A Notice of Delay is a formal written notification from a contractor to the project owner or employer that a delaying event has occurred, or is likely to occur. Its purpose is to preserve the contractor's right to claim an Extension of Time (EOT) and, where applicable, additional costs.
Under most standard contract forms, including AIA A201, JCT, and NEC4, issuing notice is a condition precedent to making an EOT claim. If the notice deadline is missed, the right to claim can be extinguished entirely, even if the delay was wholly the other party's fault. Issuing the notice does not constitute an admission of responsibility; it is a protective measure.
Under AIA A201, Section 15.1.3.1, the contractor must provide written notice within 21 days of the event giving rise to the claim, or within 21 days of first recognising the condition, whichever is later. This distinction matters: the clock runs from awareness, not necessarily from when the event occurred.
Differing site conditions carry a shorter 14-day notice window under Section 3.7.4. Always check your specific contract for any owner amendments that shorten the standard AIA periods.
NEC4 operates a two-track notice system. An Early Warning Notice (EWN) under Clause 15.1 must be issued as soon as you become aware of any matter that could delay Completion, increase cost, or impair performance. It is a proactive risk management tool.
A Compensation Event Notice (CEN) under Clause 61.3 must be issued within 8 weeks of becoming aware that a compensation event has occurred. This is a strict time bar: if the contractor fails to notify within 8 weeks, the right to any adjustment of Prices, Completion Date, or Key Dates is lost. Employer amendments (Z clauses) often shorten this period — sometimes to as little as 2 to 4 weeks.
This template supports your EWN obligations. The CEN is a separate, critical contractual requirement that must not be overlooked.
A Notice of Delay preserves entitlement. It flags that a delaying event has occurred, identifies the affected activities, and reserves the contractor's rights. It does not need to quantify the full impact at the point of issue. A preliminary estimate is sufficient to meet most contract requirements.
An Extension of Time (EOT) claim substantiates that entitlement. It includes a full schedule analysis demonstrating the cause and effect linkage between the delay event and the delay to completion, detailed time impact, and where applicable, cost particulars. The EOT claim follows after the event has fully developed.
The notice must be issued promptly. The EOT claim can follow. Confusing the two, or waiting to understand the full impact before notifying, is how contractors lose otherwise valid claims.
A contractually compliant Notice of Delay should include:
Contract clause reference: cite the specific clause requiring the notice. A notice without its contractual basis is easier to challenge.
Description of the event: what occurred, when it first became apparent, and the circumstances giving rise to the delay. Vague descriptions ("site conditions caused delay") are easy to reject.
Affected activities: identify the work packages and any critical path impact.
Estimated delay duration: a preliminary estimate that can be updated later.
Mitigation: steps being taken to minimise the impact.
Reservation of rights: preserving entitlement to both time and costs separately.
Supporting documents: photographs, weather records, schedule extracts, correspondence.
Distribution: all parties named in the contract's notice provisions.
Yes. The workbook is designed for any contracting party with notice obligations: general contractors, specialist contractors, or subcontractors. The Contract Notice Period (Days) field is fully configurable, which matters for subcontracts where notice periods are often significantly shorter than main contract terms, sometimes as few as 5 to 7 days.
Always read your specific subcontract. The template guidance explicitly flags that subcontract periods can be shorter than you expect.