NEC4 early warnings are not paperwork for its own sake. Used properly, the Clause 15 process gives you a structured way to identify problems early, involve the Project Manager and take action before a risk becomes a delay, cost overrun or contractual dispute.
For contractors and smaller project teams, that matters. You may not have a full commercial department or dedicated contract administrator on every job. But you still need to protect your programme, margin and entitlement.
The principle is simple:
Raise the risk early. Record it clearly. Agree an action. Keep the contractual notifications separate.
This article explains how the NEC4 ECC early warning process works, how it connects to compensation event management and the practical habits that make it effective.
What is an NEC4 early warning?
Under Clause 15.1, the Contractor and Project Manager notify each other as soon as they become aware of a matter that could:
- Increase the total of the Prices
- Delay Completion
- Delay meeting a Key Date
- Impair the performance of the works in use
The Contractor gives the notice to the Project Manager through the communication system specified in the contract. That might be a project platform, document management system or another stated method. An informal conversation on site is not a substitute for the contractual communication.
The Project Manager has a reciprocal obligation to notify the Contractor where they become aware of a relevant matter.
An early warning is forward-looking. It identifies something that could cause a problem. It does not need to prove that the problem will happen.
It is also not an admission of liability. Giving an early warning does not mean that you accept responsibility for the matter, accept that it is a compensation event or agree that additional time or money is due.
It means you are putting the issue in front of the people who may be able to avoid or reduce its effect.
When should you raise one?
Raise an early warning as soon as you become aware of a matter that could affect cost, time, a Key Date or performance.
Do not wait until:
- The delay is certain
- The full cost has been calculated
- The design issue has stopped work
- The Project Manager has confirmed the problem
- Your commercial team has completed a detailed claim assessment
That is too late for an effective risk-management process.
You do not need perfect information. You need enough information to describe the matter, explain the possible consequence and identify the action or decision required.
A useful early warning should state:
- What has happened or what you have identified
- When you became aware of it
- Which part of the works, programme or supply chain it may affect
- The possible impact on Prices, Completion, a Key Date or performance
- What information is currently missing
- What action could avoid or reduce the impact
- Who needs to make a decision and by when
Keep the wording factual and constructive. Do not turn an early warning into an argument about blame. State the commercial concern clearly, then give the other party something they can act on.
The Early Warning Register and your risk register
The Project Manager maintains the contractual Early Warning Register. Each early warning should be recorded with the matter, actions and relevant updates.
You should also maintain your own working copy.
That copy helps your site, commercial and project teams track what they raised, what the Project Manager has recorded and what still needs attention. If the register is not current, your team can lose sight of deadlines and assume that someone else is dealing with the problem.
The Early Warning Register and your internal risk register should connect, but they are not identical.
The Early Warning Register
The Early Warning Register is a contractual management tool. It records notified matters that fall within the Clause 15 process and the agreed actions for avoiding or reducing their effects.
Your internal risk register
Your internal risk register is broader. It may include:
- Procurement risks
- Labour and resource risks
- Health and safety concerns
- Design development risks
- Supply-chain performance
- Commercial exposure
- Cash-flow pressures
- Business or operational risks
Some items will appear in both registers. For example, a late design package may be an internal programme risk and an NEC4 early warning.
But not every item in your risk register is an early warning. A minor internal administrative concern may never have a potential effect under Clause 15.
Equally, an early warning is not automatically a compensation event. It may be avoided through prompt action. It may be a Contractor risk. It may become a Project Manager instruction later. Its contractual status depends on what happens and on the terms of the contract.
Plain-English register fields
Your working register should make responsibility and timing obvious. Useful fields include:
| Field | What it should show |
|---|---|
| Reference | Unique early warning number |
| Date notified | When the notice was issued |
| Matter | Clear description of the issue |
| Source | Site, design, supply chain, programme or other source |
| Potential effect | Possible impact on cost, time, Key Date or performance |
| Immediate action | What needs to happen now |
| Action owner | Named person responsible |
| Due date | Date for completing the action |
| Project Manager response | Decision, instruction or agreed position |
| Status | Open, monitoring, resolved or transferred |
| CE reference | Related compensation event number, if applicable |
| Latest update | Current position and next step |
| Closure reason | Why the risk is no longer open |
Do not close an item simply because it appeared on a meeting agenda. Close it only when the risk has ceased, has been resolved, has been transferred into a compensation event process or no longer requires action for a recorded reason.
Early warning is not compensation event notification
This distinction is one of the most important parts of NEC4 contract administration.
An early warning is:
- Prospective
- Risk-focused
- Raised as soon as you become aware of a possible matter
- Intended to support mitigation and joint decision-making
A compensation event notification is:
- Contractual
- Linked to an event identified under Clause 60 or the relevant contract amendments
- Used to start the process for changing the Prices, Completion Date or Key Dates
- Subject to specific notification and assessment requirements
The two processes often connect. They do not replace one another.
An early warning is not a Clause 61.3 notification. Do not rely on an early warning to preserve entitlement under the eight-week time bar. If you become aware that a compensation event has occurred, notify it separately and within the required period, unless the contract places the notification obligation on the Project Manager or another exception applies.
The NEC4 compensation events introduction explains the wider notification, quotation and assessment process. You should also check your own Contract Data and amendments because these can change the practical position.
Worked example: a design drawing cannot be built
Imagine your design coordinator identifies that a drawing issued for construction cannot be built as shown. The issue could require redesign, abortive work, additional labour or a change to the programme.
You should not wait for the full cost or delay analysis.
First, issue an early warning to the Project Manager. Describe the drawing, explain why it appears unbuildable, identify the possible consequences and propose an urgent design review.
The Project Manager may then review the matter and issue an instruction changing the Scope or directing a different solution.
That instruction may create a compensation event, depending on the precise circumstances and the contract wording. If it does, the Contractor must issue a separate compensation event notification under Clause 61. The early warning does not perform that function.
The sequence is therefore:
- The Contractor identifies a possible design problem.
- The Contractor issues an early warning under Clause 15.
- The parties review the issue and agree or receive an action.
- The Project Manager issues an instruction where the Scope must change.
- The Contractor separately notifies the compensation event under Clause 61 where required.
- The Contractor records the time and cost effects through the compensation event process.
Early action gives the team a chance to correct the design before construction is affected. Separate contractual notices protect the Contractor’s position when the event has actually occurred.
Practical habits for site and commercial teams
The Clause 15 process works best when it becomes part of normal project controls rather than a monthly administrative exercise.
Capture issues through daily reporting
Site managers should record emerging matters in daily reports, site diaries and design coordination records. Include the date, people involved, affected activities, instructions received and immediate consequences.
The commercial team can then assess whether the issue needs a formal early warning, a compensation event notification or both.
Review open warnings every week
Use the weekly commercial or contract administration meeting to review every open early warning.
For each item, confirm:
- What has changed since the last review
- Whether the risk still exists
- What action has been completed
- Who owns the next action
- Whether the deadline has passed
- Whether escalation is required
- Whether a Project Manager instruction is needed
- Whether a separate compensation event notification is required
Do not let the meeting become a passive review of old wording. The purpose is to make decisions and move actions forward.
Assign owners and deadlines
Every action needs a named owner and a date. “Design team to review” is not enough. Identify the person responsible, the information they must provide and the date by which the decision is needed.
If nobody owns the action, the risk remains open regardless of how often it appears in the register.
Escalate before the deadline is missed
If a response, drawing, access date or decision is approaching a critical point, escalate it through the agreed project channels. Record the escalation.
Early warning is not a reason to delay a formal notice. It is a reason to act before delay becomes unavoidable.
Close with evidence
Close an early warning when:
- The risk has been avoided
- The issue has been resolved
- The matter has passed without effect
- The required change has been instructed and transferred into the compensation event process
- The parties have agreed a clear alternative position
Record why it was closed and link any related instruction, programme update or compensation event reference.
NEC4 early warning checklist
Before issuing an early warning, check:
- Could this matter affect Prices, Completion, a Key Date or performance?
- Has the Contractor become aware of it?
- Have you notified the Project Manager through the specified system?
- Is the notice separate and clearly identifiable?
- Have you described the facts without overstating them?
- Have you explained the possible consequence?
- Have you proposed an action or decision?
- Have you recorded the notice in your own working register?
- Have you checked whether a separate Clause 61 notification is also required?
- Have you assigned an owner and deadline?
Early warning is about control, not presentation.
The better you identify matters, record actions and notify the correct contractual event, the firmer your grip on cost, time and entitlement.
BHD Limited supports contractors and SMEs with NEC contract administration and project controls. We can help you maintain usable registers, manage early warnings, track compensation events and produce records that withstand scrutiny.
If you have an open issue on an NEC4 project, contact us for a straight view of what needs to happen next.