NEC4 Early Warning Notice: EVM Triggers & Risk Management

<div class="ge-article-wrapper"><nav class="ge-toc" aria-label="Table of contents"><p class="ge-toc-label">In this article</p><ul class="ge-toc-list"><li><a href="#what-clause-16-actually-requires">What Clause 16 Actually Requires</a></li><li><a href="#how-evm-metrics-work-as-early-warning-data">How EVM Metrics Work as Early Warning Data</a></li><li><a href="#worked-example-cpi-drop-on-a-15m-highways-package">Worked Example: CPI Drop on a £15M Highways Package</a></li><li><a href="#the-early-warning-register">The Early Warning Register</a></li><li><a href="#setting-your-early-warning-thresholds">Setting Your Early Warning Thresholds</a></li><li><a href="#common-mistakes">Common Mistakes</a></li><li><a href="#frequently-asked-questions">Frequently Asked Questions</a></li></ul></nav><article class="ge-article-body"><p>An NEC4 early warning notice is a formal notification under clause 16 that something could increase the total of the Prices, delay Completion, delay meeting a Key Date, or impair the performance of the works in use. It's one of the most powerful mechanisms in the <a href="/en/nec4">NEC4 contract</a>, and it's the one most teams treat as an afterthought. Here's what most commercial managers miss: your <a href="/en/earned-value/definitions/earned-value-management">earned value management</a> data is generating early warning signals every month. You're just not reading them that way.</p><p>The NEC4 early warning notice isn't about predicting the future. It's about raising a flag when something measurable has changed, and <a href="/en/earned-value/definitions/cost-performance-index">CPI</a> dropping from 1.02 to 0.88 in two reporting periods is as measurable as it gets. This page explains how EVM metrics function as a quantitative early warning system, and how to connect your monthly performance data to the clause 16 notification process.</p><h2 id="what-clause-16-actually-requires">What Clause 16 Actually Requires</h2><p>Either party, the Contractor or the Project Manager, can notify an early warning. You don't need certainty. You need awareness of a matter that <em>could</em> affect cost, time, or performance. The contract deliberately sets a low threshold because the entire philosophy of NEC4 is collaborative risk management.</p><p>The obligation is at clause 16.1: the Contractor and the Project Manager give an early warning by notifying the other of any matter which could cause the outcomes listed above. There's no time bar on early warnings (unlike <a href="/en/nec4/eight-week-time-bar">compensation events under clause 61.3</a>), but late notification can still hurt you. The Project Manager can notify a <a href="/en/earned-value/definitions/compensation-event">compensation event</a> and instruct that any additional cost caused by the failure to give early warning is not included in the assessment.</p><p>That's the stick. But the carrot is more important: early warnings trigger risk reduction meetings, and risk reduction meetings are where experienced teams actually solve problems instead of arguing about them six months later.</p><h2 id="how-evm-metrics-work-as-early-warning-data">How EVM Metrics Work as Early Warning Data</h2><p>Here's where it gets interesting. Most people think of early warnings as qualitative observations, "we've noticed the ground conditions are worse than expected" or "the design information is late." And those are valid. But your <a href="/en/earned-value/definitions/earned-value">earned value</a> data is generating quantitative early warning signals on a monthly cycle.</p><pre class="ge-ascii-diagram ge-anim"> EVM METRICS AS EARLY WARNING TRIGGERS ========================================== Monthly EVM Report ┌─────────────────────┐ │ <a href="/en/earned-value/definitions/planned-value">PV</a> = £4.2M │ │ EV = £3.7M │──── SPI = 0.88 ──┐ │ <a href="/en/earned-value/definitions/actual-cost">AC</a> = £4.3M │──── CPI = 0.86 ──┤ │ BAC = £15M │ │ └─────────────────────┘ ▼ ┌─────────────────────────┐ │ EARLY WARNING │ │ THRESHOLD CHECK │ │ │ │ CPI &lt; 0.90? ──► YES │ │ SPI &lt; 0.90? ──► YES │ │ EAC &gt; BAC+5%? ──► YES │ │ CV trend 3mo? ──► ↓↓ │ └──────────┬──────────────┘ │ ▼ ┌─────────────────────────┐ │ CLAUSE 16 NOTIFICATION │ │ │ │ "CPI has dropped to │ │ 0.86 over two periods. │ │ EAC now £17.4M against │ │ BAC of £15M. This │ │ matter could increase │ │ the total of the │ │ Prices." │ └──────────┬──────────────┘ │ ▼ ┌─────────────────────────┐ │ RISK REDUCTION MEETING │ │ (Clause 16.3) │ │ │ │ - Root cause analysis │ │ - Recovery options │ │ - Programme impact │ │ - Updated risk register │ └─────────────────────────┘ </pre><p>A <a href="/en/earned-value/definitions/cost-performance-index">CPI</a> below 0.90 is telling you the project is burning through budget 10% faster than planned. That's a matter that could increase the total of the Prices. A <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> below 0.90 means you're delivering progress at 90% of the planned rate. That's a matter that could delay Completion.</p><p>These aren't opinions. They're calculations. And they make far stronger early warning notifications than vague concerns about weather or labour shortages.</p><h2 id="worked-example-cpi-drop-on-a-15m-highways-package">Worked Example: CPI Drop on a £15M Highways Package</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> You're the QS on a £15M highways improvement package under NEC4 Option C. The project started in January 2025 with an 18-month programme. At month 4 (April 2025), you run your EVM report.</p><p><strong>The numbers:</strong></p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Metric</th><th>Month 3</th><th>Month 4</th><th>Change</th></tr></thead><tbody><tr><td>PV</td><td>£2.8M</td><td>£4.2M</td><td>+£1.4M</td></tr><tr><td>EV</td><td>£2.7M</td><td>£3.7M</td><td>+£1.0M</td></tr><tr><td>AC</td><td>£2.6M</td><td>£4.3M</td><td>+£1.7M</td></tr><tr><td>CPI</td><td>1.04</td><td>0.86</td><td>-0.18</td></tr><tr><td>SPI</td><td>0.96</td><td>0.88</td><td>-0.08</td></tr><tr><td>EAC</td><td>£14.4M</td><td>£17.4M</td><td>+£3.0M</td></tr></tbody></table></div><p><strong>What happened:</strong> Month 4 included a large earthworks section. Actual ground conditions required significantly more excavation than the site investigation suggested. Labour and plant costs overran by £700K in a single period. The EAC has jumped from £14.4M to £17.4M, a potential £2.4M overrun against the <a href="/en/earned-value/definitions/budget-at-completion">BAC</a> of £15M.</p><p><strong>The early warning:</strong> You notify the Project Manager under clause 16.1: "CPI has dropped from 1.04 to 0.86 between period 3 and period 4. <a href="/en/earned-value/definitions/estimate-at-completion">EAC</a> is now £17.4M against a target of £15M. This is driven primarily by unforeseen ground conditions in the earthworks package. This matter could increase the total of the Prices."</p><p><strong>The risk reduction meeting (clause 16.3):</strong> Within two weeks, the PM convenes a risk reduction meeting. Root cause analysis confirms the ground conditions differ from the site investigation report. This is potentially a <a href="/en/nec4/compensation-events">compensation event under clause 60.1(12)</a>. The meeting agrees three actions: (1) notify the CE formally under clause 61.3, (2) revise the earthworks methodology to reduce unit costs going forward, (3) update the programme to reflect the actual production rates.</p><p><strong>Outcome:</strong> Because the early warning was quantified with EVM data, the risk reduction meeting focused on solutions rather than blame. The CE was notified within 8 weeks. The revised methodology saved £180K on the remaining earthworks. Without the early warning data, this conversation might not have happened until month 8, by which time the CE notification window would have closed.</p></div><h2 id="the-early-warning-register">The Early Warning Register</h2><p>Every early warning goes on the early warning register, which both parties maintain. On projects I've worked on, I've seen registers that are just a list of dates and one-line descriptions. Useless.</p><p>A proper early warning register should include the EVM data that triggered it:</p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Ref</th><th>Date</th><th>Raised By</th><th>Description</th><th>CPI at Notification</th><th>SPI at Notification</th><th>EAC Impact</th><th>Status</th></tr></thead><tbody><tr><td>EW-001</td><td>15 Apr 2025</td><td>Contractor QS</td><td>Ground conditions worse than SI, earthworks CPI at 0.71</td><td>0.86</td><td>0.88</td><td>+£2.4M</td><td>CE notified</td></tr><tr><td>EW-002</td><td>22 May 2025</td><td>Project Manager</td><td>Design information for structures late by 3 weeks</td><td>0.91</td><td>0.82</td><td>+£0.6M</td><td>Risk reduction meeting held</td></tr><tr><td>EW-003</td><td>10 Jun 2025</td><td>Contractor QS</td><td>SPI trend shows 3 consecutive months below 0.90</td><td>0.90</td><td>0.84</td><td>TBC</td><td>Under review</td></tr></tbody></table></div><p>That register tells a story. Anyone picking it up, an adjudicator, a project director, a new PM, can see exactly what was flagged, when, and why. The EVM data makes each entry auditable rather than anecdotal.</p><h2 id="setting-your-early-warning-thresholds">Setting Your Early Warning Thresholds</h2><p>There's no contractual threshold that says "notify when CPI drops below X." That's a project-specific decision. But here's what I've found works on most UK infrastructure projects:</p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Trigger</th><th>Threshold</th><th>Rationale</th></tr></thead><tbody><tr><td>CPI single-period drop</td><td>> 0.10 from previous period</td><td>A sudden deterioration worth investigating</td></tr><tr><td>Cumulative CPI</td><td>< 0.90</td><td>Historical data shows recovery below 0.90 is rare</td></tr><tr><td>SPI cumulative</td><td>< 0.90</td><td>10% behind programme is a meaningful delay signal</td></tr><tr><td>EAC vs BAC</td><td>> 5% overrun</td><td>Material enough to warrant formal notification</td></tr><tr><td>CV trend</td><td>3 consecutive negative months</td><td>Systemic issue, not a one-off</td></tr><tr><td>SV(t)</td><td>> 1 month behind</td><td><a href="/en/earned-value/definitions/earned-schedule">Earned schedule</a> measure, more reliable than SPI late in project</td></tr></tbody></table></div><p>Don't set thresholds too tight. If you're notifying early warnings every time CPI dips to 0.98, you'll create notification fatigue and the PM will stop paying attention. Too loose, and you miss the window where intervention actually helps.</p><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Treating early warnings as blame</strong>: The whole point of clause 16 is proactive collaboration. I've seen teams avoid raising early warnings because they think it looks bad. It's the opposite. Not raising one when you should have? That's what looks bad, especially when the PM assesses your CE and deducts for the failure to give early warning.</li></ol><ol><li><strong>Ignoring EVM trend data</strong>: A single month's CPI of 0.92 might be noise. Three months declining from 1.05 to 0.98 to 0.92 is a trend. Too many teams wait for the CPI to breach a threshold instead of watching the direction of travel.</li></ol><ol><li><strong>Not connecting early warnings to compensation events</strong>: An early warning isn't a CE notification. But it's often the precursor to one. If your early warning register shows a matter that turns out to be a client risk event, you still need to notify the CE separately under clause 61.3 within 8 weeks. The early warning doesn't substitute for CE notification.</li></ol><ol><li><strong>Vague notifications</strong>: "We're concerned about costs" is a weak early warning. "CPI has dropped to 0.86 and <a href="/en/earned-value/definitions/estimate-at-completion">EAC</a> now exceeds the target by £2.4M, primarily driven by earthworks overruns in section 3" is a strong one. The more specific you are, the more productive the risk reduction meeting.</li></ol><div class="ge-product-note ge-anim"><p><strong>How Gather helps.</strong> Gather's AI reads your site diaries daily and maps progress against your cost-loaded programme, giving you accurate earned value data without manual spreadsheet updates. <a href="https://gatherinsights.com/contact">Book a demo</a> to see it working on a live NEC4 project.</p></div><h2 id="frequently-asked-questions">Frequently Asked Questions</h2><h3>Is there a time limit for issuing an NEC4 early warning?</h3><p>No. Unlike compensation event notifications (which have an <a href="/en/nec4/eight-week-time-bar">8-week time bar under clause 61.3</a>), there's no contractual deadline for early warnings. But timing matters commercially. If you could have raised an early warning at month 4 and didn't raise it until month 9, the Project Manager can reduce the CE assessment to account for the additional cost caused by the late notification. The earlier you flag it, the stronger your position.</p><h3>Can the Project Manager reduce a compensation event because of a missing early warning?</h3><p>Yes. Clause 63.7 allows the Project Manager to assess a compensation event as if the Contractor had given an early warning. In practice, this means any additional cost that could have been avoided with earlier notification gets stripped out of the CE assessment. On one project I worked on, a late early warning cost the contractor roughly £120K on a single CE, the PM argued (successfully) that earlier intervention would have avoided two weeks of abortive work.</p><h3>What's the difference between an early warning and a compensation event notification?</h3><p>Different purposes, different clauses. An early warning (clause 16) flags a risk or developing issue before it crystallises. A compensation event notification (clause 61.3) formally notifies a specific event that has happened or is about to happen. Think of early warnings as the smoke alarm and CEs as the fire report. You can, and should, have an early warning that later becomes a CE. But an early warning alone doesn't give you the right to additional time or money. The CE process does that.</p><h3>How do I use EVM data in risk reduction meetings?</h3><p>Bring the numbers. Show the <a href="/en/earned-value/s-curve-tracking">S-curve</a> with PV, EV, and AC plotted. Highlight the specific packages where CPI has deteriorated. Present the <a href="/en/earned-value/definitions/estimate-at-completion">EAC</a> forecast and what it means for the target. Then focus the conversation on root causes and recovery actions. I've found that data-driven risk reduction meetings take half the time and produce twice the outcomes of meetings based on subjective updates. The data depoliticises the conversation.</p></article></div>