A notice of delay in a construction contract is a formal communication that alerts the contractually required recipient that an event has occurred, or is occurring, which may delay the works.
A notice of delay in construction contracts is often treated as routine administration. In practice, it is much more important than that. A construction delay notice can operate as an early warning control that helps project teams identify delay risk, preserve potential extension of time pathways, protect records, and reduce claim exposure before the issue becomes a formal dispute. This article includes an adaptable notice structure, but it is not a universal or project-specific legal template and does not provide legal, contractual, or financial advice. It is a practical contract administration and risk intelligence guide for project managers, commercial managers, contracts managers, contract administrators, planners, project directors, contractors, subcontractors, consultants, asset owners, and construction and infrastructure teams who need better visibility of delay risk.
Delay is one of the most common pressure points in construction projects. HKA’s Eighth Annual CRUX Insight material is based on more than 2,200 projects, US$2.43 trillion in total project value, and 114 countries, and reports that disputed costs average around one-third of contract budgets on distressed projects. KPMG’s 2025/2026 Global Construction Survey reports that 43% of 375 surveyed industry leaders are experiencing increased supply chain risks and pressures, while its Australian findings identify risk management, data capability, technology and efficiency as key priorities.
That is why notice of delay construction contracts should not be viewed as paperwork after the fact. It should be treated as part of the project’s risk control system.
What is a notice of delay in construction contracts?
A notice of delay in construction is a formal communication that alerts the other party, superintendent, principal, employer, contract administrator, or relevant contract representative that an event has occurred, or is occurring, which may delay the works.
In many construction contracts, the notice of delay is not the same as an extension of time claim. It is usually an early notification that a delay event exists or may exist. The EOT claim may come later, depending on the contract process, required assessment, delay analysis, and supporting particulars.
Issuing a notice does not automatically preserve entitlement, prevent a time bar, or establish a right to additional time or money. The notice must be assessed against the complete contract, including the trigger, deadline, recipient, delivery method, required content, continuing-notice obligations, separate EOT or cost-claim requirements, and applicable law.
In simple terms:
| Item |
Practical meaning |
Why it matters |
| Delay event |
Something has happened that may affect progress |
Helps identify the cause early |
| Notice of delay |
A communication that alerts the relevant party |
Helps preserve the contractual pathway |
| EOT claim |
A request for more time under the contract |
Requires evidence, analysis and entitlement assessment |
| Delay records |
Documents supporting cause, effect and timing |
Helps verify what happened |
| Claim exposure |
The risk that delay turns into cost, dispute, liquidated damages, acceleration or entitlement conflict |
Helps management act early |
A notice of delay under construction contract is therefore both a communication tool and a risk control. It tells the project that something has changed. The commercial value comes from what the team does next.
Why notice of delay requirements matter
Notice requirements matter because construction contracts are usually time-sensitive. A project may have strict dates for practical completion, milestone completion, access, approvals, separable portions, commissioning, handover, and defect rectification. A delay to one activity can affect downstream trades, plant, labour, subcontractors, testing, authority approvals, and revenue-generating operations.
The purpose of a delay notice construction process is generally to create early visibility. When a delay is notified early, the project team has a better chance to investigate the facts, protect records, assess mitigation options, and manage programme impacts.
The risk is not only whether a notice exists. The risk is whether the notice is issued on time, sent to the correct person, contains the required information, connects to the right contract clause, and is supported by evidence.
| Requirement area |
Common risk if missed |
Practical control |
| Timing |
Notice issued late or outside the contract period |
Maintain deadline alerts from the date the team becomes aware of delay |
| Recipient |
Notice sent to the wrong person or wrong email address |
Check the contract communication clause |
| Content |
Notice does not describe cause, impact or affected works |
Use a structured internal notice review process |
| Evidence |
No programme update, photos, site diary or correspondence |
Start evidence collection immediately |
| Follow-up |
Initial notice issued but no updated particulars provided |
Track notice close-out actions |
| Internal escalation |
Project team knows about delay but commercial team is not alerted |
Use delay risk dashboards and trigger registers |
A notice of delay is often the first visible signal that a contract pathway may be required. If the pathway is not managed properly, the issue can move from a site problem to a commercial exposure.
What should a notice of delay include?
The contract should always be checked first because the required information varies. As a practical starting point, construction teams should consider whether the notice clearly records the following information:
| Notice field |
Practical information to check |
| Project and contract details |
Project name, contract number, parties, notice date and relevant reference number |
| Contract basis |
Relevant delay, notice, EOT and communication clauses |
| Delay event |
What occurred, when it began, when the team became aware and whether it is continuing |
| Affected work |
Activities, workfronts, milestones, separable portions or completion dates that may be affected |
| Known impact |
Current or anticipated effect, clearly distinguishing confirmed facts from matters still being assessed |
| Mitigation |
Steps taken or proposed to avoid, reduce or manage the delay |
| Supporting records |
Instructions, programme data, site diaries, photos, correspondence, weather or supplier records |
| Next contractual step |
Updated particulars, continuing notice, EOT claim, cost claim or other follow-up required by the contract |
Any reservation of rights should be drafted for the specific contract and reviewed appropriately. Generic wording does not cure non-compliance with a contractual notice requirement.
Notice of delay and extension of time claims
An extension of time notice construction process is closely connected to delay notice management. A notice of delay may identify the event. An EOT notice construction process may then require the contractor to explain how the event affects the critical path, completion date, milestones, or approved programme.
| Notice of delay |
Extension of time claim |
| Usually an early warning or notification |
Usually a formal request for additional time |
| May be issued before full impact is known |
Usually requires particulars and supporting analysis |
| Focuses on the event and potential delay |
Focuses on entitlement, causation and time impact |
| Helps preserve the pathway |
Seeks assessment or determination |
| Often short and time-sensitive |
Usually more detailed and evidence-heavy |
This distinction is important because a project team may think, “We have already told them about the delay,” when the contract may require more than one step. Some contracts require an initial notice, then updated notices, then a detailed EOT claim within a specified timeframe. Others may require immediate notice followed by particulars when available.
A notice of delay supports an EOT pathway by creating a contemporaneous record of when the delay event was identified, what caused the potential delay, which activities or milestones may be affected, who was notified, what mitigation actions were being considered, and what evidence existed at the time.
This does not automatically prove entitlement. It helps create the evidence trail needed for proper assessment.
Notice of delay and time bars
Notice of delay and time bars in construction contracts are a major commercial risk area. A time bar is a contractual mechanism that may restrict or limit a party’s ability to claim if notice is not given within the required time. The effect depends on the contract wording, applicable law, facts and circumstances, so project teams should seek appropriate professional advice where required.
From a practical risk management perspective, the important point is simple: late notices can create avoidable claim exposure.
| Day |
Project event |
Risk if unmanaged |
Better control |
| Day 0 |
Site access delayed or approval not received |
Team treats it as operational inconvenience only |
Log potential delay event immediately |
| Day 1–2 |
Site team discusses issue informally |
No formal contract pathway triggered |
Commercial review of notice requirement |
| Day 3–7 |
Programme impact starts to emerge |
Evidence becomes scattered |
Capture site diary, photos, correspondence, affected activities |
| Day 7–14 |
Delay continues |
Mitigation actions unclear |
Update programme and internal risk register |
| Day 14–28 |
Notice or particulars may be due under some contracts |
Potential time bar or entitlement dispute |
Submit required notice or follow-up in accordance with contract |
| After deadline |
Claim prepared late |
Increased dispute risk and weaker evidence |
Escalate and obtain professional advice where needed |
The lesson is not that every contract has the same deadline. It does not. The lesson is that each project needs a system that links events to notice obligations quickly.
What records should support a notice of delay?
A strong notice of delay records and evidence process does not start when the claim is being written. It starts when the project first becomes aware of the delay risk.
The best evidence is usually contemporaneous. That means records created at the time of the event, not reconstructed months later. In delay disputes, teams often lose time trying to recreate what happened from emails, photos, meeting minutes, programmes and site diaries. This can be avoided if delay notice requirements are connected to record collection from the start.
| Evidence type |
What it helps show |
Practical example |
| Contract clause reference |
Which notice pathway may apply |
EOT clause, delay event clause, communication clause |
| Programme baseline |
Planned sequence before the delay |
Approved programme or accepted schedule |
| Programme update |
Actual impact or forecast impact |
Updated programme showing affected activities |
| Site diary |
What happened on site each day |
Labour, plant, access, weather, workfront availability |
| Correspondence |
When parties became aware |
Emails, letters, superintendent instructions |
| Photos and videos |
Physical condition or obstruction |
Access issue, incomplete predecessor work, site condition |
| Meeting minutes |
Discussions and decisions |
Delay discussed in progress meeting |
| RFIs and approvals |
Design or information delays |
Late design response affecting procurement |
| Procurement records |
Supply chain delay evidence |
Purchase orders, supplier notices, delivery dates |
| Mitigation records |
Steps taken to reduce delay |
Resequencing, alternative workfronts, additional crews |
| Cost records |
Possible downstream cost exposure |
Labour standby, extended preliminaries, acceleration records |
The goal is not to over-document everything. The goal is to capture the right evidence early enough that the project can understand cause, effect and risk.
How missed delay notices increase claim exposure
A missed notice construction contract issue can increase claim exposure in several ways.
First, it may create entitlement risk. If the contract requires a notice within a specific period, late notice may become a major point of disagreement. This can affect EOT assessment, delay damages, liquidated damages, prolongation costs, acceleration, and dispute positioning.
Second, it weakens evidence. The later a delay is notified, the harder it may be to verify what happened, whether the event affected the critical path, and what mitigation was possible. Memories fade. Site conditions change. Programmes are overwritten. Subcontractor records become harder to obtain.
Third, it reduces management options. Early notice gives the parties time to discuss resequencing, alternative access, design prioritisation, additional resources, temporary works, partial handover, or mitigation. Late notice often leaves only argument, negotiation or dispute.
Fourth, it affects trust. A principal or superintendent may question why an issue was not raised earlier. A contractor may feel exposed if the operational team knew about the delay but the commercial team did not act. This is how a simple delay event becomes a relationship issue.
A good notice process is not about being aggressive. It is about making risk visible early enough to manage.
Common delay notice risk indicators
Construction teams should pay attention to early indicators that a delay notice may be required. These indicators do not automatically mean entitlement exists. They mean the team should check the contract, assess the facts, and decide whether a notice obligation has been triggered.
| Risk indicator |
Possible delay pathway |
Why it matters |
| Late site access |
EOT, resequencing, preliminaries |
May affect start or critical workfront |
| Late design information |
EOT, variation, disruption |
Can affect procurement and construction sequence |
| Principal-directed change |
Variation, EOT, cost impact |
Scope change may affect time and resources |
| Authority approval delay |
EOT, mitigation planning |
External dependency may affect commissioning |
| Unforeseen condition |
Latent condition, EOT, variation |
May require urgent notice and evidence |
| Weather event |
EOT if qualifying under contract |
Needs weather data and site impact records |
| Supply chain delay |
EOT or procurement risk |
Requires supplier records and programme impact |
| Interface delay |
EOT, coordination risk |
May involve multiple parties and handover points |
| Testing or commissioning delay |
EOT, completion risk |
Can affect practical completion and revenue dates |
A practical contract administration system should convert these indicators into alerts, actions and evidence requirements.
Weather delay notices and supporting records
Weather is the largest additional search opportunity currently associated with this article, but a construction weather delay does not automatically create an entitlement to time or money. The team should check how the contract defines qualifying weather, exceptional or inclement weather, the relevant baseline or threshold, notice timing, mitigation obligations and the required method of proving programme impact.
| Weather-delay record |
What it may help establish |
| Contemporaneous site diary |
Conditions observed, affected workfronts, labour, plant and work actually performed |
| Reliable weather data |
Rainfall, temperature, wind or other relevant conditions for the project location and period |
| Photos and videos |
Site condition, access limitations, flooding, safety constraints or physical effects |
| Programme records |
Planned activities, actual progress, affected sequence and any critical-path consequence |
| Mitigation records |
Resequencing, alternative workfronts, protection measures, recovery planning or resource changes |
| Correspondence and instructions |
When the parties became aware, directions given and decisions made |
A weather-delay letter should state only what is known at the time and identify what remains under assessment. If the duration or programme effect is not yet known, check whether the contract requires an initial notice followed by updated particulars or a separate EOT claim.
Notice of delay checklist for construction teams
This checklist is not a legal template. It is a practical internal control tool to help teams think clearly before, during and after issuing a delay notice.
| Step |
Question |
Action |
| 1 |
What happened? |
Describe the event in plain language |
| 2 |
When did the team become aware? |
Record the awareness date and source |
| 3 |
Which work area is affected? |
Identify activity, workfront, milestone or separable portion |
| 4 |
Which contract clause may apply? |
Check delay, EOT, notice and communication clauses |
| 5 |
Is there a notice deadline? |
Record the deadline and responsible person |
| 6 |
Who must receive the notice? |
Confirm address, role and required method |
| 7 |
What must the notice include? |
Check required details, cause, likely impact and particulars |
| 8 |
What evidence exists now? |
Capture diary, photos, emails, instructions and programme data |
| 9 |
What follow-up is required? |
Track updated particulars, EOT claim or mitigation records |
| 10 |
What is the exposure if missed? |
Assess entitlement, time, cost, LDs, relationship and dispute risk |
Adaptable notice of delay structure
The following is an illustrative structure for internal drafting and review. It must be adapted to the specific contract, facts, required delivery method and applicable law before use.
Subject: Notice of Delay – [Project] – [Contract number] – [Event]
To: [Contractually required recipient]
Date: [Date]
Relevant clause: [Clause number and title] We give notice that [describe the event factually] occurred or became apparent on [date/time] and may delay [identify affected activity, milestone, separable portion or completion obligation]. The presently known effect is [describe confirmed or anticipated impact]. The full time and cost consequences are [known / not yet known / being assessed]. Mitigation undertaken or proposed includes [list reasonable actions]. Relevant contemporaneous records include [identify programme, diary, instruction, correspondence, weather, supplier or photographic evidence]. We will provide [updated particulars / continuing notice / EOT claim / other required submission] in accordance with [relevant clause], subject to the contract requirements and information becoming available.
[Insert any project-specific reservation or closing wording only after appropriate review.]
This structure is deliberately neutral. It should not be copied without checking who must issue the notice, who must receive it, when it is due, how it must be served and whether the contract requires prescribed wording or additional particulars.
For internal governance, project teams can also use a simple risk scoring model:
| Factor |
Low risk |
Medium risk |
High risk |
| Notice deadline |
More than 14 days away |
7–14 days away |
Less than 7 days or already passed |
| Programme impact |
Non-critical activity |
Possible critical path impact |
Critical path or milestone impact |
| Evidence quality |
Complete records |
Some gaps |
Limited or reconstructed records |
| Stakeholder alignment |
Issue accepted |
Facts partly disputed |
Cause or responsibility disputed |
| Cost exposure |
Minimal |
Potential prolongation or disruption |
Significant cost, LD or acceleration exposure |
This type of scoring helps commercial managers prioritise which delay events need immediate attention.
Notice of delay vs extension of time claim
Many project teams confuse notice of delay vs extension of time claim. This creates risk because the project may issue one document and assume all requirements have been satisfied.
| Question |
Notice of delay |
EOT claim |
| Purpose |
Alert that delay has occurred or may occur |
Request additional time |
| Timing |
Usually early |
Usually after impact can be assessed |
| Detail level |
May be preliminary |
Usually more detailed |
| Evidence |
Initial records |
Full particulars, programme analysis, supporting documents |
| Commercial impact |
Preserves visibility and pathway |
Seeks assessment of entitlement |
| Risk if missed |
Potential pathway or time-bar issue |
Potential rejection, dispute or exposure |
The safest internal control is to treat the notice as the beginning of a workflow, not the end of the workflow.
What happens after a notice of delay is issued?
Issuing the initial notice should trigger a controlled follow-up process. The responsible team should confirm delivery, preserve the issued version and evidence of service, diarise continuing-notice and claim deadlines, update the programme and records, assess mitigation, and determine whether a separate EOT or cost claim is required.
| Follow-up action |
Control objective |
| Confirm compliant service |
Verify the correct recipient, address, method, date and delivery record |
| Track contractual deadlines |
Record updated particulars, continuing notices, EOT and cost-claim dates separately |
| Maintain contemporaneous evidence |
Continue collecting programme, site, correspondence, mitigation and cost records |
| Assess programme effect |
Distinguish delay to an activity from delay to a contractual milestone or completion date |
| Review the response |
Record any request for particulars, rejection, direction, mitigation proposal or determination |
| Escalate material exposure |
Bring significant entitlement, delay-damages, cost or dispute risk to qualified reviewers and management |
A notice sent to a subcontractor about its delayed performance is a different communication from a contractor’s notice to a principal or superintendent about a delay event. The issuing party, purpose, contract clause, required content and potential consequences should not be assumed to be the same.
Perfomir’s practitioner review framework
Based on Hamid Mir’s more than 20 years of construction and infrastructure project experience, Perfomir applies a four-part review sequence: identify the event, check the contract pathway, preserve the evidence, and track every required follow-up. The framework is intended to help project and commercial teams organise review—not replace project-specific legal, contractual, programme or delay analysis.
How Contriqo by Perfomir helps identify delay notice risk
Contriqo by Perfomir is designed to help construction and infrastructure teams see contract risk earlier. It does not replace professional judgement and does not provide legal, contractual or financial advice. Its value is in organising contract information, surfacing obligations, and helping project teams identify risk signals before they become disputes.
| Problem |
Typical project pain |
How Contriqo by Perfomir helps |
| Notice clauses are buried in the contract |
Teams do not know which clause applies |
Extracts and organises notice obligations, EOT clauses and related risk themes |
| Delay events are discussed informally |
Commercial team finds out too late |
Connects project events to potential notice obligations |
| Deadlines are missed |
Time bars and entitlement issues emerge |
Flags timing risk and supports deadline visibility |
| Evidence is scattered |
Delay claim is hard to support later |
Helps map delay events to records, correspondence and clause pathways |
| Management lacks visibility |
Risks stay buried in site-level communications |
Provides dashboard-level visibility of notice, claim exposure and delay risk themes |
| Lessons are not captured |
Same notice mistakes repeat across projects |
Builds a structured risk intelligence layer across contract administration |
In practical terms, Contriqo helps teams move from reactive contract administration to earlier risk visibility. A delay notice should not sit unnoticed in someone’s inbox. It should connect to the contract, the programme, the project record, and the commercial risk register.
Related Perfomir resources:
Check What Your Contract Requires
Upload one contract for a free risk preview. Identify delay clauses, notice obligations, time requirements and potential claim exposure before taking the next step.
Analyse Your Contract Free Practical takeaways
A notice of delay is not just an administrative letter. It is an early warning control.
When used properly, it helps construction teams identify delay events earlier, preserve potential EOT pathways, protect contemporaneous evidence, improve communication between site, programme and commercial teams, reduce the chance that a manageable delay becomes a major claim exposure, and support better contract risk management across the project lifecycle.
The key is not to issue notices mechanically. The key is to understand what the contract requires, what the project facts show, what records exist, what deadlines apply, and what risk the organisation is carrying.
In a construction environment where delay, cost pressure, supply chain uncertainty and disputes remain significant, notice discipline is a commercial control. Contriqo by Perfomir helps make that control visible by connecting contract obligations, project events, notice pathways and claim exposure in one risk intelligence view.
Important note: This article is general information only and should not be relied on as legal, contractual or financial advice. Project teams should review the specific contract and seek appropriate professional advice where required.
References
