What early warnings are supposed to do
Early warnings are the most distinctive feature of the NEC contract family and one of the most consistently underused. Under NEC4, the mechanism is set out in Clauses 15 and 16. Clause 15 requires each party to notify the other as soon as they become aware of any matter that could increase the total Prices, delay Completion, delay meeting a Key Date, or impair the performance of the works in use. Clause 16 governs the risk reduction meeting, which is the forum where the parties discuss the notified matters and agree what to do about them. The mechanism is designed to surface problems early, jointly, and in a structured way.
The design intent is preventative. By requiring notification as soon as a party becomes aware of a risk, NEC4 puts the parties in a position to discuss the matter before it becomes an entrenched commercial problem. The risk reduction meeting provides a structured forum for that discussion, separate from the operational project meetings and focused specifically on forward-looking risk rather than current status. Clause 16.3 lists what the meeting is for: considering how the matter can be avoided or reduced, seeking solutions that benefit both parties, deciding the actions to be taken and by whom, and recording the decisions in the Early Warning Register.
The Early Warning Register — previously called the Risk Register in NEC3 — is the documented record of everything notified and the actions agreed against each entry. It is a live document, updated after each risk reduction meeting, and it is visible to both the Project Manager and the Contractor throughout the project. It is not a static artefact produced once and forgotten; it is the running ledger of joint risk management under the contract.
What actually happens on many NEC4 contracts is different. Early warnings are notified reluctantly, often only when the event has already occurred and the notification is covering the notifying party's contractual position. Risk reduction meetings are held if at all, typically as an agenda item in the monthly progress meeting rather than as a separate forum. The Early Warning Register is maintained as a formal document but rarely referenced in decision-making. The mechanism is followed procedurally but not used substantively, and the commercial and schedule benefits that NEC4 intended are largely lost.
What counts as an early warning
Clause 15.1 is broader than most teams treat it. The clause requires notification of any matter which could increase Prices, delay Completion, delay meeting a Key Date, or impair performance of the works in use. The word is "could", not "will". Any matter that has a real possibility of producing one of these effects should be notified, regardless of whether the effect has actually occurred, and regardless of which party is responsible for the underlying cause.
This is wider than most contractors assume. A supply chain issue that the contractor has become aware of, and that could delay a specific activity, is an early warning — even if the contractor believes they can mitigate it. A design query that is taking longer than expected to resolve, and that could affect a downstream activity, is an early warning — even if it has not yet caused delay. A regulatory change announced by government, which could require rework on compliance elements, is an early warning — even before the specific impact has been assessed.
It is also wider than most project managers assume. Client-side decisions that could trigger compensation events — design changes under consideration, access issues being negotiated, deferrals being discussed — are early warnings that the client (through the Project Manager) should notify. The obligation is symmetrical. Project Managers who treat early warnings as something contractors do and clients receive have misread the contract. A PM who is aware of a matter that could cause a compensation event and does not notify it early is in breach of Clause 15.1, with the same consequences as a contractor in the same position.
Some matters are explicitly not early warnings. Risks that are listed in the Contract Data part one — employer's risks — are not events the contractor needs to notify as early warnings if they arise in expected ways. Events that have already occurred and have already had their effect are compensation events (if they fall within Clause 60.1) rather than early warnings. The test for early warning is prospective: something that could happen, or has started to happen but whose full effect is still to come. Retrospective notification of an event that has already completed its impact is a compensation event notification, not an early warning.
The time bar is "as soon as" — Clause 15.1 says each party notifies the other as soon as either becomes aware. There is no explicit number of days. The practical interpretation is that delay in notification, once the notifying party became aware, will be evidence that the mechanism was not followed properly. On disputes, tribunals and adjudicators have consistently taken a strict view: if a contractor was clearly aware of a matter in March and did not notify it until June, that three-month delay is itself a breach of Clause 15.1, with the consequences discussed below.
Running an effective risk reduction meeting
The risk reduction meeting under Clause 16 is where the early warning mechanism delivers its value. Clause 16.1 requires either party to instruct the other to attend a risk reduction meeting, with the meeting held at a time and place chosen by the instructing party. The meeting must consider how to avoid or reduce the effects of the notified matters, and the outputs must be recorded in the Early Warning Register.
The practical design of an effective meeting looks like this. It is held separately from the operational progress meeting, not as an agenda item within it. Combining the two means the risk discussion is rushed, dominated by current-issue firefighting, and produces shallow outputs. Separating them gives the risk meeting the time to produce substantive actions. The frequency is usually monthly, sometimes fortnightly on fast-moving projects. Attendees are the Project Manager, the Contractor's representative, and subject matter experts for the matters on the register. Senior commercial personnel should be available but not dominant; the meeting is about risk mitigation, not commercial positioning.
The agenda is: review of the Early Warning Register; discussion of new matters notified since the last meeting; discussion of matters where actions from the last meeting have not progressed; forward look at anticipated matters; agreement of actions against each item, with owners and target dates; update of the Early Warning Register. The meeting should produce a revised register at the end, not just a set of minutes. The register is the working document; the minutes are supporting.
The culture of the meeting matters. An effective risk reduction meeting is collaborative and problem-solving in tone. The parties are looking for mitigations that benefit both, as Clause 16.3 requires. A meeting that devolves into commercial positioning — "that's a contractor responsibility", "that's a client issue", "we don't accept that's a risk" — is not delivering the benefit the clause intended. The clause specifically says the meeting should seek solutions that will bring advantage to both parties; that is the tone that should be set, and Project Managers who chair the meeting have responsibility for setting it.
Common failures in running the meeting: senior leaders who only attend quarterly and dominate when they do, changing the tone and the outputs; failure to close out actions from previous meetings, so the register accumulates stale entries; treating the register as a record rather than a live document, with entries that have not been updated for months; and conflating the risk reduction meeting with the risk register update for governance purposes, which produces procedural reporting rather than substantive discussion. The meeting is a working session, not a reporting forum.
The consequences of failure to notify
Failing to give an early warning has specific contractual consequences under NEC4, and they are more significant than most parties appreciate until they matter in a dispute. The key provisions are Clauses 61.5 and 63.7 (numbering varies slightly by NEC4 form), which set out what happens to compensation event assessments where the contractor should have given early warning and did not.
Clause 61.5 provides that the Project Manager may, when notifying a compensation event, state that the Contractor did not give an early warning which an experienced contractor could have given. If the Contractor disputes this, the matter can be referred under the dispute resolution procedures. Clause 63.7 (63.5 in some forms) then provides the substantive consequence: if the Contractor did not give an early warning which an experienced contractor could have given, the compensation event is assessed as if the Contractor had given the early warning — meaning the assessment excludes the additional impact that could have been avoided if the early warning had been given when it should have been.
The effect can be significant. If a contractor identifies a supply chain delay in February that would, if notified, have allowed a reduction in impact through alternative sourcing, but does not notify until May when the alternative is no longer available, the compensation event assessment in May can be reduced to reflect what the impact would have been had the early warning been given in February. The contractor bears the cost of the difference — which is the cost of their own failure to notify.
The reverse case applies to Project Managers. A Project Manager who fails to give early warning of a matter the client is aware of — a likely design change, an access restriction, a regulatory development — is in the same breach position. Clause 60.1(6) (failure to respond or act within the period required by the contract) and Clause 60.1(18) or similar (a breach of contract not listed elsewhere) may be engaged. A systematic pattern of client-side non-notification can itself form the basis of a contractor's claim under the contract.
The practical consequence for both parties is that the early warning mechanism is not optional — it is a commercial discipline that protects the notifying party as much as it informs the other party. Contractors who treat early warnings as "admission of failure" and avoid notifying are setting themselves up to lose compensation event assessments later. Project Managers who treat them as "contractor's problem" and do not reciprocate are creating grounds for challenge that will play out in the contract's dispute mechanisms or in subsequent negotiations.
The link to compensation events
The early warning mechanism sits upstream of the compensation event mechanism, and understanding the relationship is essential to using both effectively. An early warning is a prospective notification of a matter that could have an effect. A compensation event notification (under Clause 61) is a retrospective notification of an event that has occurred and falls within the Clause 60.1 list. They are different mechanisms for different purposes.
The link is that many matters that start as early warnings become compensation events when they actually occur. A notified early warning about a supply chain delay becomes a compensation event notification when the delay is confirmed and its impact is measurable. A notified early warning about a design query becomes a compensation event if the resolution of the query meets the Clause 60.1 criteria (typically 60.1(1) — the Project Manager gives an instruction changing the Works Information). The early warning does not itself produce an extension of time or additional cost; the compensation event does.
The practical workflow is to treat each early warning as a potential compensation event and track it through both mechanisms. The Early Warning Register captures the notification and the ongoing mitigation. When the event actually occurs, a compensation event notification is made under Clause 61, referencing the earlier early warning. The assessment under Clause 63 then values the time and cost impact on the Accepted Programme and the Defined Cost. If the early warning was given properly, the assessment captures the full impact (net of any successful mitigation). If the early warning was not given — Clause 63.7 applies — the assessment is reduced by what the mitigation could have achieved.
The early warning does not freeze the contractor's position or waive any rights. A contractor who gives an early warning and then later finds the matter does not produce a compensation event is not disadvantaged — they have simply notified a risk that did not materialise, and no consequence flows from it. Contractors who withhold early warnings "to preserve options" are misreading the contract. The protection runs in the opposite direction: giving the early warning preserves the full assessment value if the event does occur.
The less obvious link is to the Accepted Programme. Clause 32 requires the contractor to revise the programme to reflect instructed compensation events, changes in resources, and actual progress. Matters that are the subject of early warnings — particularly those likely to become compensation events — should be reflected in the revised programme through updated activities, new activities, or time risk allowances as appropriate. A contractor who does not update the programme in response to emerging matters, and then claims the full impact when the matter crystallises, is in a weaker position than one whose programme has been kept current. The risk reduction meeting outputs should feed directly into the programme revision cycle, not sit as a parallel record.
Common mistakes on real projects
The most common mistake is treating early warnings as a contractor's tool used defensively. Contractors notify early warnings primarily to protect their compensation event position, with little expectation that the notification will produce joint mitigation. Project Managers receive early warnings primarily as commercial signals of likely claims to come, with limited engagement in mitigation discussion. The mechanism functions as a notification exchange rather than as a collaborative risk management tool, and the potential value of early joint mitigation is lost.
The second common mistake is the combined progress and risk meeting. When the risk reduction meeting is an agenda item within the operational progress meeting, the risk discussion is rushed, the attendees are the operational team rather than the risk team, and the outputs are shallow. The discipline of a separate meeting — on a different date, with a defined agenda focused on risk, attended by the right people — produces materially better outputs. Teams that resist holding a separate meeting usually cite efficiency; the actual effect is that the early warning mechanism is starved of time and attention.
The third common mistake is the Early Warning Register as a formal document rather than a live one. The register fills up, entries age, actions drift, and the document becomes an artefact maintained for governance rather than a working tool. The discipline of updating the register in the meeting — not as a post-meeting administrative task — keeps it live. Entries that have been closed out should be archived; entries that have not been progressed should be flagged and chased; new entries from ongoing work should be added continuously, not just at formal notification.
The fourth mistake is selective notification. Contractors sometimes notify the easy early warnings and withhold the difficult ones, hoping the difficult matters will resolve without the political exposure of notification. Project Managers sometimes reciprocate by withholding notification of client-side matters that would give the contractor advantage. Both behaviours break the mechanism. A pattern of selective notification, once visible to the other party, degrades the trust that makes collaborative risk management work, and the contract then operates in a more adversarial register where the early warning mechanism produces little value.
The fifth mistake is failure to close the loop with the programme. Matters discussed in risk reduction meetings produce actions; the actions change the project's expected trajectory; the programme should reflect the changes. If the programme is updated only on compensation events, and early warnings do not reach the programme until they crystallise, the programme lags reality by months. A contractor whose programme does not reflect notified early warnings will find compensation event assessments weaker than they should be, because the assessment is against a programme that does not show the full picture of known matters.
What to do on Monday morning
If you are running an NEC4 contract and the early warning mechanism is underused — which, honestly, is most contracts — the improvements are specific and achievable within a month. First, separate the risk reduction meeting from the progress meeting. Set a separate date, a separate agenda, and a separate attendee list. This single change, sustained over three months, typically transforms the quality of the early warning mechanism.
Second, audit the Early Warning Register. Identify entries that are stale, entries with no recent update, entries without clear owners, and entries that should have been closed. Do a one-off cleanup, and then establish the discipline that the register is updated in the meeting, not offline. A register that reflects reality is usable; a register that does not is noise.
Third, change the culture around notification. Contractors' PMs should encourage their teams to notify early — not as a commercial manoeuvre but as a protection — and make clear that non-notification carries the contractual consequence under 63.7. Client-side PMs should reciprocate, giving early warning of client matters proactively, and responding to contractor notifications with engagement rather than defensive positioning. This is not a policy change; it is a tone change, and it usually starts with the senior PM on one side modelling the behaviour and the other side responding.
Fourth, link the register to the programme update cycle. Every programme revision under Clause 32 should cross-reference the Early Warning Register: which notified matters are reflected in the revised programme, which are not (and why), which have produced new activities or time risk allowances. This keeps the programme honest and ensures that early warnings actually influence the live project representation rather than sitting in a parallel record.
Fifth, report the mechanism upward. The monthly steering group pack should include the count of early warnings notified this month, the count closed, the count outstanding, and any material ones with ongoing actions. Steering group visibility into the mechanism signals its importance and applies pressure to maintain the discipline. Teams that run the mechanism without senior visibility tend to let it decay; teams whose senior leaders ask about it regularly keep it alive.
The final point is that the early warning mechanism is one of the most elegant features of NEC4 — a structured, bilateral, forward-looking risk management tool built into the contract itself. Using it well protects both parties, produces better project outcomes, and reduces the volume and intensity of the compensation event disputes that consume disproportionate commercial attention on weaker-run NEC contracts. The mechanism is there; the question is whether the project team has the discipline to use it. Most do not, and most of those lose significant value as a result.