Five ways contractors lose money on NEC compensation events (and how to stop)

The NEC family (NEC3 and NEC4) is the most popular contract form on major UK infrastructure work, and it shows up increasingly on international projects too. Its collaborative mechanics (early warnings, short notice periods, quotation-based assessments) are designed to reward contractors who engage early and administer the contract properly.

That’s also what makes it unforgiving. Miss a deadline, under-price a quotation, or treat a compensation event (CE) like a loose-leaf variation claim and you will walk away from money you were entitled to. Below are five traps I see contractors fall into repeatedly, on water frameworks, flood defence, rail, and building alike.

1. Notifying late (and losing the event entirely)

Under NEC3 and NEC4, the contractor must notify a CE within eight weeks of becoming aware of the event (clause 61.3). Miss that window and unless the Project Manager should have notified you, you are barred from recovery. Not reduced. Barred.

In practice, eight weeks evaporates quickly when site teams are focused on delivery and commercial teams are firefighting a live programme. The trap isn’t usually gross negligence; it’s optimistic ambiguity. The team thinks, “this might be a CE, we’re waiting for more facts”, and by the time the picture is clear, the clock has run.

The fix: treat notification as a cheap, procedural step. If it might be a CE, notify it. The Project Manager can always determine later that it isn’t one. You cannot resurrect a lost notice.

2. Letting the Project Manager’s assessment stand unchallenged

If the contractor fails to submit a quotation within the required period, or the Project Manager decides the contractor hasn’t assessed the CE correctly, the Project Manager makes their own assessment (clauses 64.1–64.4). Those self-made assessments tend to favour the client (unsurprisingly), and contractors often swallow them without challenge because the commercial team is already onto the next thing.

The fix: Treat every Project Manager assessment as a draft that can be reopened on reasoned grounds. Option W1/W2 dispute procedures exist for a reason. If you have a credible, evidenced counter-view, say so in writing before the event is buried in the next cost report.

3. Pricing the quotation as if it were a variation

A CE quotation is a forecast of the Defined Cost plus Fee (clause 63.1), not a rate-based valuation. Contractors trained on JCT or FIDIC or bespoke variation clauses instinctively reach for the tendered rates and bolt on a bit of prelims. Under NEC that’s leaving money on the table, particularly where the CE disrupts planned sequencing or throws off resource loading.

The fix: Build the quotation from the Schedule of Cost Components. Price the real impact on people, plant, subcontractors, and time. If the CE is properly assessed, you are entitled to recover the actual commercial consequence, not what a tender rate notionally covered.

4. Ignoring the programme (clause 31/32)

Every CE quotation must include an assessment of its impact on the Accepted Programme. No programme, no credible time assessment. And the NEC gives the Project Manager a specific tool: if the programme doesn’t comply with clause 31.2 or isn’t being updated under clause 32, a quarter of the Price for Work Done to Date can be retained (clause 50.3).

I have seen contractors lose five- and six-figure time-related recovery simply because their programme wasn’t current, wasn’t submitted under 32.2, or didn’t show the critical path clearly enough for the Project Manager to accept the CE’s time impact.

The fix: Programme hygiene is a commercial activity, not a planning one. Keep it current, keep it compliant, and make the programmer part of the CE quotation process from day one.

5. Treating early warnings as admin, not strategy

Early warnings (clause 15 / clause 16 in NEC4) are the most misunderstood mechanism in the NEC family. Contractors often view them as a confession of failure and hold back, which is exactly backwards. Failing to give an early warning that a reasonable contractor would have given is a ground on which a CE can be reduced (clause 63.7 in NEC4).

Conversely, a prompt early warning, followed by a risk-reduction meeting, creates a contemporaneous record that protects recovery when the event crystallises. It is not a weakness to flag risk early. It is the system working.

The fix: Make early warnings a default, not an exception. One line in the register costs nothing. Not giving one when you should have can cost you the quantum.

The bottom line

NEC rewards discipline. Every one of the five traps above traces back to the same thing: commercial teams under-resourced or under-experienced, treating the contract’s procedural rhythm as optional rather than load-bearing. The notices, quotations and programme submissions are not paperwork. They are the entitlement mechanism. Skip them and the entitlement does not exist, however strong the underlying case.

Running a live NEC project and not certain your CE pipeline, programme and early-warning register are working in step? That is a commercially expensive gap, and it is one of the most common things we are asked to look at.