An Early Warning Notice (EWN) is a formal contractual notice used under NEC contracts to flag issues at an early stage, before they develop into disputes, delays, or claims.
Early Warning Notices are not designed to apportion blame or advance claims. Instead, they form part of the NEC’s proactive risk management philosophy, encouraging collaboration and transparency so that issues can be addressed early, mitigated effectively, and recorded properly.
Under the NEC Engineering and Construction Contract (ECC), parties are required to notify one another as soon as they become aware of a matter that could increase cost, delay completion, impair performance, or affect the quality of the works. In NEC4, this obligation sits under clause 15 (previously clause 16 in NEC3).
In practice, EWNs act as an early intervention tool, allowing the project team to manage risks collectively rather than reactively once problems have already crystallised.
Summary
This article covers:
- What an Early Warning Notice is and why it is required under NEC contracts
- When an Early Warning Notice must be issued
- Who is responsible for issuing Early Warning Notices
- How early warnings should be drafted, managed, and recorded in practice
- Early Warning Meetings and the Early Warnings Register
- The difference between Early Warning Notices and compensation events
- The contractual and commercial risks of failing to comply with early warning obligations
The Purpose and Legal Basis of Early Warning Notices
The NEC suite of contracts embeds proactive risk management into the parties’ legal obligations, rather than treating it as a matter of good practice or project culture. Early Warning Notices sit at the heart of this philosophy and are intended to ensure that emerging risks are identified and addressed before they crystallise into delay, additional cost, or formal claims.
Under NEC4 Engineering and Construction Contract clause 15 (formerly clause 16 in NEC3), both the Contractor and the Project Manager are under a positive obligation to notify other parties of matters that they become aware of which could affect time, cost, quality, or performance. The emphasis is on early awareness, not certainty. Parties are expected to raise issues when they first recognise a potential impact, even where the full consequences are not yet known.
Crucially, the early warning mechanism is not designed to allocate blame or establish fault. Nor is it a preliminary step in pursuing a claim. Instead, it provides a structured framework for transparency and joint problem-solving, enabling the project team to explore mitigation measures, allocate responsibility for actions, and minimise adverse outcomes.
From a legal perspective, proper compliance with early warning obligations demonstrates good contract administration and supports the NEC’s core objective of reducing disputes through early intervention.
When You Must Issue an Early Warning Notice
Under NEC contracts, the obligation to issue an Early Warning Notice is triggered as soon as a party becomes aware of a matter that could affect the time, cost, quality, or performance of the works. The threshold is deliberately low. The issue doesn't need to have already caused delay or additional cost, nor does the impact need to be fully understood or quantified at the point of notification.
This requirement often causes difficulty in practice. Parties may hesitate to issue an early warning where the risk appears minor, speculative, or capable of resolution without formal escalation. However, the NEC places the emphasis firmly on early disclosure rather than certainty. If a reasonable assessment suggests that a matter could impact the project, an Early Warning Notice should be issued.
Typical examples include potential resource shortages, emerging design coordination issues, delayed information or approvals, unforeseen site conditions, supply chain disruption, or interface risks between contractors or trades. Matters arising from external factors – such as weather events or regulatory changes – may also trigger the obligation where they threaten the programme or cost.
Timing is critical. Early warnings are intended to allow the project team to mitigate risk while options remain available. Delayed notification can undermine that purpose and may expose a party to adverse contractual consequences later. From both a legal and commercial standpoint, erring on the side of early notification is generally the safer approach.
Who Can Serve an Early Warning Notice?
Early Warning Notices are not solely the responsibility of the Contractor. Under NEC4 contracts, both the Contractor and the Project Manager are under a contractual obligation to notify of matters they become aware of which may affect time, cost, quality, or performance.
In practice, Contractors most frequently issue Early Warning Notices because they are closest to site activity, resources, and delivery risks.
However, the Project Manager’s role is equally important. Where the Project Manager becomes aware of a potential issue, they are required to issue an early warning in their own right. This is frequently the case when the matter arises from design coordination, delayed instructions, or employer-driven changes.
This shared obligation is intentional. The NEC does not treat early warnings as a one-sided risk-transfer mechanism, but as a joint tool for managing uncertainty across the project. Employers should be mindful of this, particularly where the Project Manager is acting as their agent and is responsible for maintaining the Early Warning Register.
Failure by the Project Manager to issue an early warning where required can have practical consequences. It may limit opportunities for mitigation, weaken the project’s risk management processes, and contribute to disputes later.
How to Issue an NEC Early Warning: Process Step-by-Step
The NEC contracts do not prescribe a fixed early warning template, but they do require the notice to be issued in writing and communicated in accordance with the contract’s agreed notification procedures. Your contract will stipulate the early warning process you should follow.
In practice, the effectiveness of an early warning often depends less on formality and more on clarity and timing.
Any named party must issue an EW immediately upon becoming aware of a matter that could potentially impact the project timeline, budget, quality or performance.
An effective Early Warning Notice should do two things:
- Clearly identify the matter giving rise to concern
- Explain why it could affect the time, cost, quality, or performance of the works
- Outline proposed mitigations where applicable
While a full analysis is not required at this stage, the notice should provide sufficient information to allow the Project Manager and wider project team to understand the nature of the risk and its potential implications.
Where possible, the notice should also outline any proposed mitigation measures or next steps. This reinforces the collaborative purpose of the early warning process and helps move the discussion away from fault or entitlement and towards practical problem-solving.
Once issued, the Early Warning Notice should be submitted via the contract’s designated communication mechanism and recorded on the Early Warning Register.
The matter should then be reviewed at the next early warning meeting, or sooner if the risk is urgent.
Keeping clear, consistent records of early warnings and follow-up actions is essential, particularly on complex projects where multiple risks may be running concurrently.
Early Warning Meetings and the Early Warning Register
Once an Early Warning Notice has been issued, the focus shifts from notification to management. NEC contracts envisage that early warnings are actively discussed, monitored, and progressed through early warning meetings, rather than simply recorded and left unresolved.
The Early Warning Register plays a central role in this process. Typically maintained by the Project Manager, the register provides a live record of all identified risks, the parties responsible for addressing them, and the agreed mitigation measures. Keeping the register up to date is essential, particularly on complex or fast-moving projects where multiple early warnings may be running at the same time.
Early warning meetings allow the project team to review the register collectively, assess how risks are developing, and agree practical steps to reduce their impact. These discussions should focus on solutions, sequencing, and coordination, rather than contractual positioning. From a governance perspective, properly managed early warning meetings also create a clear audit trail, demonstrating that risks were identified promptly and addressed collaboratively.
Where disputes later arise, a well-maintained Early Warning Register and accurate meeting records can provide valuable evidence of how risks were managed, what mitigation was considered, and whether parties acted reasonably in response to emerging issues.
Early Warning Notices vs Compensation Event Notices
Early Warning Notices and Compensation Event Notices serve different but complementary functions under NEC contracts, and confusing the two can lead to missed entitlements or procedural failures.
An Early Warning Notice is concerned with potential risk. Its purpose is to alert the project team to a matter that could affect time, cost, quality, or performance, allowing mitigation measures to be explored before the impact crystallises. It is a risk management tool, not a mechanism for adjusting the contract price or programme.
Compensation Event Notices, by contrast, address actual changes to the works or new circumstances that entitle the Contractor to additional time and/or money under the contract. These events must be notified in accordance with the strict contractual timescales that apply.
Importantly, issuing an Early Warning Notice does not remove the need to notify parties of a compensation event where one arises. The two processes operate in parallel. A party may properly issue an early warning and later submit a compensation event notice once the contractual trigger has occurred.
Understanding this distinction is critical. Failure to follow the correct procedure for either process can result in loss of entitlement, even where the underlying issue was identified early.
Consequences of Failing to Give an Early Warning
Failing to issue an Early Warning Notice in accordance with the NEC contract can have significant contractual consequences. The early warning mechanism is not merely procedural; it is closely linked to how compensation events are assessed and how risk is allocated between the parties.
Under NEC rules, where a party fails to give an early warning that could have reduced the impact of a compensation event, that event may be assessed as if the early warning had been given. In practice, this means that the assessment of time and cost may reflect mitigation measures that could reasonably have been implemented had the risk been identified earlier.
This can result in reduced entitlement to additional time, disallowed costs, or a less favourable assessment of the compensation event overall. The effect is particularly acute where early notification would have allowed alternative sequencing, resource planning, or design coordination to avoid or limit disruption.
Beyond the strict contractual consequences, late or missing early warnings can also weaken a party’s commercial position. They may undermine credibility in negotiations, increase the likelihood of disputes, and make it harder to demonstrate that risks were managed proactively. For all parties operating under NEC contracts, timely compliance with early warning obligations is therefore both a legal and commercial necessity.
NEC Early Warnings: Best Practice and Common Mistakes
Effective use of Early Warning Notices requires more than procedural compliance. In practice, the way early warnings are managed can have a material impact on project outcomes and on the parties’ ability to protect their contractual positions.
Common Mistakes When Using Early Warning Notices
Issuing EWNs Too Late
Despite their central role in NEC contracts, Early Warning Notices are frequently misunderstood or misused in practice. One of the most common mistakes is issuing early warnings too late. Parties may delay notification in the hope that an issue resolves itself or because the potential impact is not yet clear.
However, the NEC threshold is deliberately low: once a party is aware of a matter that could affect time, cost, quality, or performance, an early warning should be issued. Waiting for certainty can significantly undermine the purpose of the mechanism.
Assuming the Risk Does Not Warrant an EWN
Another recurring issue is failing to issue an early warning at all because the risk appears minor or speculative. While not every issue warrants formal notification, reluctance to raise early warnings often stems from concern about escalation rather than contractual compliance. This can result in missed opportunities to mitigate risk and weakened positions later in the project.
Overuse of EWNs
Overuse of early warnings can also be problematic. Issuing excessive or overly cautious notices may dilute their effectiveness and make it harder for genuinely critical risks to receive proper attention. Early warnings should be proportionate and focused on material risks rather than used as a blanket protective measure.
Assuming EWNs are Adversarial
A further mistake is treating early warnings as defensive or claim-driven documents. Drafting notices in adversarial language can undermine the collaborative intent of the NEC and prematurely entrench positions.
Neglecting the Early Warning Register
Finally, poor maintenance of the Early Warning Register, including incomplete records or a lack of follow-up, remains a common weakness and can leave parties exposed if disputes arise.
Best Practice for Managing Early Warning Notices
Keep EWNs Timely and Appropriate
Effective early warning management begins with timely and proportionate notification. Parties should err on the side of early disclosure where there is a credible risk to the project, while exercising good judgement to avoid unnecessary or speculative notices. Early warnings should be issued as soon as the potential impact is identified, not when it becomes unavoidable.
Use Clear Language
Clear and neutral drafting is equally important. Well-prepared Early Warning Notices focus on the nature of the risk, its possible implications, and, where appropriate, suggested mitigation measures. Avoiding emotive or claim-focused language helps maintain collaboration and keeps discussions solution-oriented.
Leverage Early Warning Meetings
Active use of early warning meetings is another key element of best practice. These meetings should be used to review risks, agree on mitigation strategies, and allocate responsibility, rather than simply noting issues for the record. The Early Warning Register should be treated as a live management tool, updated regularly and used to track progress against agreed actions.
Keep EWNs Separate from Compensation Events
Finally, early warnings should be managed alongside – but separately from – compensation event procedures. Clear alignment between the two processes helps ensure that risks are identified early while contractual rights are preserved where formal changes arise. Consistent, well-documented early warning practice improves project outcomes and strengthens all parties’ positions if disputes cannot be avoided.
NEC Early Warning Notices as a Contractual Risk Tool
Early Warning Notices are a fundamental feature of NEC contracts and play a critical role in managing risk, protecting programme and cost, and reducing the likelihood of disputes. When used properly, they support the NEC’s core objective of proactive and collaborative project management, allowing issues to be addressed while there is still scope to mitigate their impact.
For contractors, employers, and project managers alike, understanding when an early warning must be issued – and how it should be managed once raised – is essential. Early warnings are not claim notices, nor are they merely administrative formalities. They are contractual obligations with real legal and commercial consequences if overlooked or mishandled.
Good early warning practice requires judgement, discipline, and consistency. Timely notification, clear communication, active engagement through early warning meetings, and accurate record-keeping all contribute to more effective risk management under NEC contracts.
Where projects encounter complexity, competing pressures, or emerging disputes, specialist advice on NEC contract administration can help ensure early warning procedures are used correctly, and contractual positions are protected.
Witan Solicitors advises clients across the construction and infrastructure sectors on NEC compliance, risk management, and dispute avoidance throughout the project lifecycle.
Frequently Asked Questions
What is an Early Warning Notice under an NEC contract?
An Early Warning Notice is a formal, contractual notification used under NEC contracts to identify matters that could affect time, cost, quality, or performance, allowing risks to be addressed before they escalate.
When must an Early Warning Notice be issued?
An Early Warning Notice must be issued as soon as a party becomes aware of a matter that could impact the project, even if the full consequences are not yet known.
Who is responsible for issuing Early Warning Notices?
Under NEC4, both the Contractor and the Project Manager are obliged to issue Early Warning Notices under NEC contracts when they become aware of relevant risks.
Who is responsible for managing early warnings?
Responsibility for managing early warnings under NEC contracts typically sits with the Project Manager, who maintains the Early Warning Register and convenes early warning meetings. However, effective management relies on active participation from both the Contractor and the wider project team to identify risks, agree on mitigation measures, and monitor progress.
How is an Early Warning Notice different from a compensation event?
An Early Warning Notice identifies potential risks, whereas a compensation event deals with actual contractual changes that may entitle the Contractor to additional time or money.
What happens if an Early Warning Notice is not issued?
Failure to issue an Early Warning Notice can affect how compensation events are assessed and may reduce a party’s entitlement to time or cost, as well as increasing the risk of disputes.
