7 Common Pitfalls When Managing NEC4 Compensation Events as a Contractor
- Sep 4, 2025
- 9 min read
Updated: 1 day ago
NEC4 compensation events are meant to keep time and money discussions current, so projects do not drift into end-of-job claims. In the real world, contractors still lose entitlement for one simple reason: the CE process is run loosely, without deadlines, without a testable programme story, and without an audit-ready evidence pack.
That is happening in a market where formal dispute activity remains high. The latest major UK adjudication research published by King’s College London and the Adjudication Society highlights record levels of referrals and points to inadequate contract administration and lack of competence as leading causes of disputes. That is exactly the territory CEs sit in.
This guide is written for planners, QSs and commercial leads working under NEC4 ECC (Options A, C and E especially). It focuses on the seven failure modes we see most often, and the practical controls that prevent CEs turning into margin leakage.
March 2026 update
This article has been reviewed and refreshed to reflect current NEC4 compensation event practice, including contractor time-bars, the Accepted Programme at the dividing date, the distinction between Early Warnings and CE notices, and what makes a quotation decision-grade. We have also added practical FAQ guidance and a related note on handling multiple compensation events more cleanly.
Use this as a quick CE health check in progress meetings and weekly commercial reviews.
Pitfall | What it looks like on site | What it costs you | The control that fixes it |
1. Missing the 8-week time bar | “We will notify later once we know the cost” | Lost entitlement, even if the event is genuine | CE trigger log, weekly triage, notify early |
2. CE notices that are not decision-grade | Vague notice, no dates, no clause hook, no scope boundary | PM rejects, requests rework, or drifts | One page CE notice format with dates, clause and impacted interfaces |
3. Wrong programme reference | Quoting off a later programme revision | Pushback, arguments, reduced credibility | Assess against the Accepted Programme current at the dividing date |
4. Quotation submitted without a programme story | Spreadsheet plus narrative, no impacted chain | Endless “revise and resubmit” | Decision Pack: programme extract, assumptions, evidence index |
5. Early Warnings not used properly | EWN forgotten, no risk reduction actions | Lower assessment under 63.7 | EWN linked to CE, mitigation actions logged and programmed |
6. Forecast cost done badly | Actuals only, no risk, no time-related cost logic | Money left on the table | Forecast based build-up tied to programme and mitigation |
7. Weak audit trail | Missing contemporaneous records and version control | Negotiated down, delayed payment | Evidence index, strict file naming, programme version register |
THE 7 PITFALLS
Pitfall 1: Failing to notify within the contractual time limits
What it looks like
The team waits until the impact is fully known, or until the issue is “resolved”, then notifies late.
Why it hurts
Under NEC time bar is not theoretical. Under clause 61.3, if the contractor fails to notify a compensation event within 8 weeks of becoming aware of the event (subject to the clause 61.1 exception where the PM should have notified), there may be no change to Prices, Completion Date or Key Dates.
NEC’s own guidance is explicit that the 8 weeks runs from awareness of the underlying event, not from realising it is a “compensation event”.
What to do instead
Treat CE notification as a planning control, not a QS task.
Keep a simple “CE trigger log” (date first aware, potential clause, who owns the notice, target submit date).
Run a weekly 15-minute CE triage: what must be notified this week, what needs a quotation, what is waiting on PM response.
P6 / planning practical
Add a “CE potential” activity code or notebook field to affected activities in your short-term lookahead. When the lookahead is reviewed, the CE trigger log is reviewed at the same time.
Pitfall 2: CE notices that are not decision-grade
What it looks like
A notice that says “delay due to access” or “late information” with no hard dates, no interface IDs, and no clear link to clause 60.1.
Why it hurts
A PM cannot respond properly if the notice is not specific. Drift starts here: back-and-forth emails, or “not a CE” replies that could have been avoided with a tighter notice.
Fix: the 1-page CE Notice format
Put this in your team’s template library:
Event summary (one paragraph)
Dates (event occurred, awareness date, notice date)
Clause hook (which clause 60.1 item, or instruction reference)
Impacted interfaces (what you were waiting for, where it hits the logic)
Immediate mitigation started (what you did within 48 hours)
This improves response speed because it gives the PM something testable, not a narrative.
Pitfall 3: Disconnect between CE assessment and the Accepted Programme
What it looks like
The contractor submits a quotation based on a later revised programme (or a planning “what-if”) rather than the Accepted Programme current at the dividing date.
Why it fails under NEC4
NEC guidance is clear: if a programme was issued after the dividing date, it can be irrelevant to the CE assessment. The assessment is based on what the Accepted Programme current at the dividing date showed.
A practical consequence is that improvements shown only in a later programme may simply become contractor-owned terminal float, which can weaken the CE time narrative if the dividing date basis is wrong.
Fix
State the dividing date basis on the cover sheet of every quotation.
Use a programme extract that clearly shows the impacted chain as it existed on the Accepted Programme at the dividing date.
If the Accepted Programme is badly out of date, follow NEC’s own practice note approach: agree a programme to use for the assessment, or the PM may assess under clause 64.
Pitfall 4: Submitting quotations without a programme story
What it looks like
A cost build-up plus paragraphs. The time impact is asserted, not demonstrated.
Why it hurts
NEC4 is meant to be prospective and logic-driven. Without a programme story, the PM cannot validate “time consequences” in a controlled way, so the quotation cycles.
Fix: the CE Decision Pack
You do not need a long document. You need a consistent one.
CE Decision Pack contents:
Cover sheet: what decision is needed, by when
Programme extract: the impacted chain and interfaces
Assumptions register: 5 to 10 assumptions max
Cost build-up summary: structured and traceable
Evidence index: what records support the story
NEC’s own practice note supports producing a programme specifically to explain and support the CE assessment (used for assessment, not for acceptance). That is exactly what your “programme extract” is doing.
Pitfall 5: Treating Early Warnings as paperwork
What it looks like
No EWN until it is too late, no risk reduction actions, or EWNs issued but not linked to any mitigation plan.
Why it hurts under NEC4
If the contractor failed to give an early warning of an event that becomes a compensation event, the PM can state that when instructing a quotation (clause 61.5), and the CE is assessed as if the early warning had been given (clause 63.7). In practice, that can reduce the CE assessment.
Also, NEC guidance is clear that compensation events are assessed assuming the contractor acts promptly and competently (63.7). Waiting for agreement before acting can backfire commercially.
Fix
Link EWNs to CEs in your registers.
When an EWN is issued, log dated mitigation actions and decision-by dates.
Reflect mitigation in the programme, even if it is provisional. A mitigation that is not planned is rarely treated as credible.
Pitfall 6: Inaccurate cost forecasting and missing time-related logic
What it looks like
The quotation is based on actuals only, or it forgets time-related prelims, disruption logic, and risk allowances. Alternatively, everything is bundled into one “global” number with no traceability.
Why it hurts
If the PM cannot see the cost logic, they will challenge it. If the programme story is weak, you will struggle to justify prolongation and disruption as consequences.
Fix: cost the CE like a forecast, not a claim
Build a simple structure:
Defined cost forecast by resource and work package
Time-related cost tied to a clear change in planned Completion or Key Dates
Risk allowance with a rationale aligned to competent and prompt mitigation, as NEC practice notes expect
Practical tip
Separate “direct cost of change” from “time consequence cost”. If time impact is not accepted, you still preserve the direct cost element cleanly.
Pitfall 7: No audit trail and weak version control
What it looks like
Evidence sits in inboxes. Programme files are overwritten. Photos and diaries are not time-stamped or are not linked to CE references.
Why it hurts
Under pressure, the party with clean contemporaneous records has leverage. The party without them negotiates down.
Fix: build a CE evidence index from day one
Create one folder per CE with a strict naming standard:
CE-012 Notice
CE-012 Programme Extract Rev A
CE-012 Assumptions Register Rev A
CE-012 Evidence Index Rev A
Keep a simple programme version register so you can always prove what was accepted and when.
A 30-day “make this perfect” implementation plan
Week 1: set up the CE trigger log, EWN to CE cross-references, and a weekly triage slot.
Week 2: standardise the 1-page CE Notice and the Decision Pack cover sheet.
Week 3: introduce the programme extract standard.
Week 4: add the evidence index and file naming rules.
If you want NEC4 Compensation Events to stop being slow and painful, treat them like an operating system: deadlines, repeatable pack structure, and a programme reference that is contract-correct. That is how you protect margin without turning every conversation into a dispute.
Recent precedent worth knowing (adjudication and NEC compensation events)
UK Grid Solutions and Amey Power Services v Scottish Hydro Electric Transmission [2024] CSOH 5 is a useful reminder that NEC disputes still get judged on process discipline and how cleanly the parties present the assessment. The court enforced an adjudicator’s decision on an NEC Option A job involving a compensation event and rejected challenges that the adjudicator failed to deal with a set-off defence. The practical takeaway for contractors is simple: keep CE notices timely, keep the baseline and dividing date position explicit, and build decision-grade packs with a clear audit trail.
When does the 8-week time bar start for an NEC4 compensation event?
Under NEC4 ECC, the 8 weeks generally starts when the contractor became aware of the underlying event itself, not when the team later decided it was a compensation event. The main exception is where the event is one the Project Manager should have notified under clause 61.1. That is why a simple trigger log with “date first aware” is commercially vital.
Does an Early Warning count as a compensation event notice under NEC4?
No. Early warning and compensation event notification are separate processes. Issuing an Early Warning does not replace a CE notice, so a contractor can still lose entitlement if the CE itself is not notified in time. However, failing to give an early warning can still reduce the assessment because the CE may be assessed as if the contractor had warned earlier and mitigated promptly.
Which programme should be used to assess a compensation event under NEC4?
The correct contractual basis is the Accepted Programme current at the dividing date, not a later revised programme, corrected update or internal what-if file issued afterwards. A separate programme extract can be produced to explain the assessment, but that support programme is for the CE assessment only and does not become a newly Accepted Programme by itself.
What should be included in an NEC4 compensation event quotation?
A proper quotation should deal with both money and time, even where one element is zero. It should show the forecast defined cost effect, the time effect on planned Completion or Key Dates, the assumptions relied on, and a clear programme basis for the impacted chain. That is the difference between a quotation that can be assessed and one that just creates another revise-and-resubmit cycle.
Can multiple compensation events be assessed together under NEC4?
Usually, no as a default working method. Multiple compensation events are generally stronger when assessed separately and sequentially against the Accepted Programme current at each event’s own dividing date, unless the events arose close together and the parties expressly agree a combined approach. On your site, this is also a strong internal-link opportunity to your newer article on separate assessment of multiple compensation events.
Need firmer control of compensation events on a live project?
If quotations are drifting, the programme basis is unclear, or change is becoming harder to value and defend, early contract-aligned support can make the position easier to manage.
References
Great insights! Managing compensation events under NEC4 can definitely be challenging. I’ve found that one of the biggest pitfalls is failing to keep accurate contemporaneous records—especially when dealing with subcontractor delays
Great content! Really useful