The NEC4 early warning process is a practical management discipline, not a procedural formality.
Clause 15.1 requires the Contractor and Project Manager to notify each other as soon as either becomes aware of a matter that could affect the Prices, Completion, Key Dates or the performance of the works in use.
Used properly, early warnings give the project team time to act before a developing issue becomes a delay, forecast movement or formal dispute. Used badly, they become late notifications, generic risk-register entries and missed opportunities to reduce exposure.
The central principle is straightforward:
Notify early. Discuss the risk constructively. Allocate action. Keep a reliable record.
For SME and Tier 2 or Tier 3 contractors, this process provides a proportionate form of NEC contract administration. You do not need an oversized corporate system. You do need a disciplined process that connects notices, programme decisions, cost forecasts and site action.
What Clause 15.1 requires
Under NEC4 ECC clause 15.1, the Contractor and Project Manager must give an early warning as soon as either becomes aware of a matter which could:
- increase the total of the Prices;
- delay Completion;
- delay meeting a Key Date; or
- impair the performance of the works in use.
The Contractor and Project Manager may also notify other matters which could increase the Contractor’s total cost.
The notification must be given in writing. Early warning notifications are separate communications and must be in a form that can be read and copied. An informal comment in a progress meeting, an unrecorded telephone conversation or an isolated reference within a broader report may not provide the clarity and audit trail expected from a properly administered NEC4 contract.
A good early warning should identify:
- the matter giving rise to concern;
- the potential effect on cost, time, Key Dates or performance;
- the evidence currently available;
- the action already being taken; and
- the assistance, decision or mitigation required from the other party.
Keep the wording factual and forward-looking. The purpose is to create an opportunity for intervention, not to allocate blame before the consequences are known.
Why early warnings matter commercially
The early warning process creates a formal route for collaboration and mitigation. Once a matter is notified, the Project Manager records it in the Early Warning Register.
This creates several commercial benefits.
Earlier intervention
A potential access problem can be reviewed before it affects planned activities. Design information can be prioritised before a workfront becomes unavailable. Supply chain concerns can be escalated before they affect procurement or delivery dates.
Better forecast integrity
Early warnings should inform the commercial forecast and programme controls process. The register should not sit separately from the project programme, risk register, procurement information and cost forecast.
This is a key part of project controls for contractors. When the information remains connected, you can see whether a developing issue is likely to affect margin, cash flow, planned output or entitlement.
More effective mitigation
An early warning meeting should produce decisions and actions. Attendees should consider proposals to avoid or reduce the effect of each matter, agree responsibilities and establish when the outcome will be reviewed.
Protection against an avoidable assessment reduction
If the Contractor fails to give an early warning of a matter which an experienced contractor could have given, the Project Manager may later assess a related compensation event as if the early warning had been given.
That can reduce the time and cost recoverable by the Contractor. The commercial consequence is simple: a late warning can weaken your position even where the underlying problem was not caused by you.
Early warning is not a compensation event notification
An early warning and a compensation event notification perform different functions.
An early warning identifies a matter that could create an adverse effect and gives the parties an opportunity to reduce or avoid that effect. It is prospective and risk-focused.
A compensation event notification under clause 61 concerns an event which may change the Prices, the Completion Date, Key Dates or other contractual parameters. It initiates the compensation event process and must be administered in accordance with the contract’s notification and assessment provisions.
An early warning does not, by itself, notify a compensation event. Equally, giving a compensation event notification does not remove the need to give an early warning where the relevant risk should have been notified earlier.
Where both processes apply, keep the records linked but distinct. The early warning explains the developing risk and mitigation. The compensation event notice starts the contractual process for assessing the event.
The NEC4 early warning process
The process can be understood as seven connected steps:
1. Become aware
↓
2. Notify in writing and separately
↓
3. Add the matter to the Early Warning Register
↓
4. Hold the early warning meeting
↓
5. Agree actions, mitigation and ownership
↓
6. Reissue the register within one week
↓
7. Monitor actions through to closure
1. Become aware of a relevant matter
The process starts when the Contractor or Project Manager becomes aware of a matter which could affect Prices, Completion, a Key Date, performance in use or, where applicable, the Contractor’s total cost.
Examples may include:
- unexpected ground conditions;
- delayed or restricted access;
- design information not being available when required;
- a developing supply chain or manufacturing risk;
- adverse weather with a potential effect on planned work;
- a third-party interface affecting planned activities; or
- a decision that may change the sequence or efficiency of the works.
The test is not whether the impact is already certain. The question is whether the matter could produce one of the consequences identified in clause 15.1.
Do not wait until the delay has occurred. Early warning means early awareness, not confirmed damage.
2. Notify in writing and separately
The Contractor or Project Manager gives a written early warning as soon as it becomes aware of the matter.
The notification should be specific enough to support action. “Potential delay to works” is unlikely to be sufficient on its own. A stronger notification identifies the affected activity, the current evidence, the potential consequence and the decision or assistance required.
Issue early warnings promptly. Do not hold them for the next monthly report or scheduled meeting.
3. Add the matter to the Early Warning Register
The Project Manager records the matter in the Early Warning Register. The register should provide a controlled record of:
- early warning reference;
- date notified;
- description of the matter;
- potential impact;
- proposed mitigation;
- action owner;
- target date;
- current status; and
- closure or residual risk.
Under NEC4, the Project Manager prepares and issues the first Early Warning Register within one week of the Starting Date. The Project Manager also instructs the Contractor to attend the first early warning meeting, which takes place within two weeks of the Starting Date.
The register then becomes the live record of early warning matters and agreed responses.
4. Hold the early warning meeting
The Project Manager and Contractor attend early warning meetings, together with others whose involvement is necessary to resolve the matter.
Depending on the issue, this may include subcontractors, designers, specialists, planners, supervisors or supply chain representatives.
The meeting should review the register and focus on risk reduction. Useful questions include:
- What is the earliest credible impact?
- What can be changed now to avoid or reduce it?
- Which party controls the required action?
- What information or decision remains outstanding?
- Does the programme or forecast require updating?
- When will the action be reviewed?
The meeting should remain proportionate. A developing site issue may require a prompt discussion with the relevant people rather than waiting for a formal monthly session.
5. Agree actions, mitigation and ownership
An early warning without an action is only a recorded concern.
The meeting should establish what will happen next, who owns it and when the outcome will be tested. Actions should be written in operational terms, such as:
- confirm revised access arrangements by a stated date;
- assess alternative sequencing for an affected workfront;
- obtain supplier confirmation of manufacturing capacity;
- issue outstanding design information for review;
- undertake further investigation of ground conditions; or
- update the programme and commercial forecast following a decision.
Ownership must be clear. Shared awareness does not create shared accountability.
6. Reissue the Early Warning Register within one week
Following the meeting, the Project Manager revises the Early Warning Register to record the decisions and agreed actions, then issues the revised register to the Contractor within one week of the meeting.
This timescale matters because the register is a control record. If decisions remain in personal notes, meeting minutes or separate email chains, the project loses a reliable view of what has been agreed.
The revised register should show the current position, not simply repeat the previous version.
7. Monitor actions through to closure
Actions should be monitored until the matter is resolved, the risk has been avoided, the impact has been accepted or the issue has moved into another contractual process.
Closure should be evidence-led. Do not close a matter simply because no further update has been received.
Record what changed, what evidence supports closure and whether any residual risk remains. If the issue develops into a compensation event, delay matter or programme change, link the records so the project history remains clear.
Making early warnings a live management habit
The strongest NEC4 projects do not treat early warnings as exceptional documents. They build them into routine commercial and programme controls.
A practical operating model is to review potential early warnings during:
- weekly programme reviews;
- commercial forecasting;
- procurement and supply chain meetings;
- design coordination meetings;
- access and logistics reviews;
- risk workshops; and
- senior governance reporting.
The Early Warning Register should be cross-referenced to the project risk register, but the two records should not be treated as identical.
A risk register may describe a broad uncertainty. An early warning should identify a matter of which a party has become aware and which could produce a defined contractual consequence.
The register should also be tested against the compensation event log. This helps the team identify matters that require a separate contractual notification and prevents the early warning process from becoming detached from commercial administration.
Common weaknesses to avoid
Avoid:
- issuing warnings only after the effect has occurred;
- using generic wording with no identifiable action;
- combining multiple unrelated matters in one notification;
- treating the register as a historical list rather than a live control;
- failing to allocate an owner and target date;
- waiting for a formal monthly meeting when immediate action is required; and
- assuming that an early warning is equivalent to a compensation event notification.
The commercial objective is not to maximise the number of early warnings. It is to ensure that matters requiring joint management are identified early enough for the parties to make informed decisions.
Proportionate systems are better than oversized processes. A smaller contractor needs a process that people can use consistently, not a complicated dashboard that no one keeps current.
Final points for project teams
Clause 15 works when the process is timely, specific and connected to delivery control.
The essential sequence is:
- identify the matter as soon as it becomes known;
- notify it separately in writing;
- record it in the Early Warning Register;
- bring the relevant people together;
- agree mitigation and ownership;
- reissue the register within one week of the meeting; and
- monitor the actions until closure.
The process is contractual, but its value is operational. Better information reaches the people who can act while there is still time to influence the outcome.
If your NEC4 administration is producing notices but not decisions, the process needs attention. If your register does not connect to the programme, forecast and compensation event log, you do not yet have effective project controls.
Sources and further reading
- NEC4 Engineering and Construction Contract
- NEC Contracts: Seven practical tips for making NEC early warnings more effective
- NEC Contracts: Early warning of a defect : frequently asked question
- NEC4 ECC clause 15 and associated contract provisions
- NEC4 early warning guidance and practice note
- BHD Limited NEC advisory services
- BHD Limited commercial desk
Need practical NEC4 contract administration support?
BHD Limited supports contractors and SMEs with NEC4 contract administration, early warning registers, compensation event management, programme controls and commercial forecasting.
We work with contractors across the West Midlands, Staffordshire and Shropshire. We get onto the numbers early, test the records and tell you what needs action.
If you have a live early warning, an incomplete register or a concern about missed notices, contact BHD Limited for an initial conversation and a straight view of the position.