NEC4 Early Warnings: The Clause 15 Process, Explained with a Simple Flowchart

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 cost, time, Key Dates or the performance of the works in use.

Used properly, early warnings give the project team an opportunity to act before a developing issue becomes a delay, a forecast movement or a formal dispute. Used badly, they become late notifications, generic risk-register entries and missed opportunities to reduce exposure.

For contractors, Project Managers, commercial managers, quantity surveyors and programme controls professionals, the central principle is straightforward:

Notify early, discuss the risk constructively, allocate action and maintain a reliable record of what was agreed.

What Clause 15.1 requires

Under NEC4 ECC clause 15.1, the Contractor and Project Manager must give an early warning by notifying the other as soon as either becomes aware of a matter that 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. This requirement is important. A comment made informally 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:

1. the matter giving rise to concern;
2. the potential effect on cost, time, Key Dates or performance;
3. the evidence currently available;
4. the action already being taken; and
5. the assistance, decision or mitigation required from the other party.

It should be 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. The register then provides a shared view of developing issues, proposed responses, owners and outstanding decisions.

This has several commercial benefits.

Earlier intervention

A potential access problem can be reviewed before it affects planned activities. Design information can be prioritised before a planned 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. They provide evidence for testing assumptions around cost, risk, productivity, procurement, access and time risk allowances.

The register should not sit separately from the project’s risk register, programme and forecast. It should connect those control systems so that emerging issues are reflected consistently in management information.

More effective mitigation

The early warning meeting is intended to produce decisions and actions. It is not simply a forum for reading out the register. 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

Early warnings also have a direct contractual significance. 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 assessment can reduce the time and cost recoverable by the Contractor. The consequence is not that every late notification automatically removes entitlement. The issue is whether the Contractor failed to notify a matter that an experienced contractor would have notified, and what difference earlier notification would have made to the assessment.

Early warning is therefore both a management obligation and an important part of protecting the integrity of later compensation event assessments.

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, the project team should keep the records linked but distinct. The early warning should explain the developing matter and mitigation opportunity. The compensation event notification should identify the contractual event and the basis on which it is being notified.

The NEC4 early warning process

The process can be understood as seven connected steps.

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. It is whether the matter could produce one of the consequences identified in clause 15.1.

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.

Early warnings should be issued promptly rather than held 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:

• the early warning reference;
• date notified;
• description of the matter;
• potential impact;
• proposed mitigation;
• action owner;
• target date;
• status; and
• closure or residual risk.

Under NEC4, the Project Manager issues the first register within one week of the Starting Date and instructs the Contractor to attend the first early warning meeting. The register is then maintained as 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 is outstanding?
• Does the programme or forecast require updating?
• When will the action be reviewed?

The meeting should be 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. For example:

• 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 reissued register should distinguish between open matters, actions completed, risks avoided, matters passed to another process and issues requiring further escalation.

7. Monitor actions through to closure

The process does not end when the meeting finishes or when the register is reissued. 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. A matter should not be closed simply because no further update has been received. The project team should confirm whether the underlying risk has disappeared and whether the programme, forecast or compensation event position requires adjustment.

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 identify whether a developing issue has progressed into a formal event and whether the records show when the parties became aware of the relevant circumstances.

Common weaknesses to avoid

Several practices undermine the value of clause 15:

• 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.

Final points for project teams

Clause 15 works when the process is timely, specific and connected to delivery control.

The essential sequence is:

1. identify the matter as soon as it becomes known;
2. notify it separately in writing;
3. record it in the Early Warning Register;
4. bring the relevant people together;
5. agree mitigation and ownership;
6. reissue the register within one week of the meeting; and
7. monitor the actions until closure.

For contractors, early notification supports mitigation and reduces the risk of a later assessment being made as though an experienced contractor had warned earlier. For Project Managers, it provides a structured route to manage emerging risks before they become more expensive or disruptive. For the wider project team, it creates a shared record of decisions, actions and residual exposure.

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.

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
• Nick Garvey: programme, cost and risk commentary

Social-sharing summary

NEC4 early warnings are a core management process, not a paper exercise. This practical guide explains clause 15.1, the Early Warning Register, meeting requirements, mitigation actions, the one-week reissue period and the distinction between early warnings and compensation event notifications.

---

About the Author

Nick Garvey is a chartered construction professional (MCIOB, FCaSA, FQSi) with more than 25 years of experience in commercial leadership and project controls across defence infrastructure, government estates, highways, facilities management and public-sector programmes. He leads cost, schedule, risk and performance reporting on major defence infrastructure programmes, chairs risk reviews at senior governance level, and writes about earned value management, quantitative risk analysis, NEC4 contracts and forecast integrity.

All views my own, shared in a personal capacity.