Commercial · NEC

Why most NEC compensation events become disputes

The compensation event is the most contested mechanism in NEC contracts. The cause is rarely the contract itself — it is how the parties choose to run it.

The NEC suite was written to do something that earlier construction contracts did not: to manage change as it happens, openly, before it hardens into a claim. The compensation event procedure is the heart of that ambition. It gives the parties a defined route to adjust the Prices and the Completion Date as risks materialise, with timescales, quotations and a clear decision-maker. On paper, it should make end-of-contract disputes rare.

In practice, compensation events are the single most common flashpoint on NEC projects. They sit at the centre of most adjudications, most strained client–contractor relationships, and most programmes that quietly lose financial control. The interesting point — and the useful one — is that this almost never happens because the contract is defective. It happens because the way the mechanism is operated drifts away from the way it was designed to work.

Having reviewed a good number of these situations after they have gone wrong, the same handful of root causes appear again and again. None of them is exotic. All of them are avoidable.

1. The contract is run as a claims process, not a management process

The defining idea of NEC is that change is dealt with in near-real time. An event arises, it is notified promptly, a quotation is prepared on a forward-looking basis, the Project Manager responds within a set period, and the matter is closed while everyone still remembers the facts. The mechanism assumes momentum.

What frequently happens instead is that compensation events are logged, parked, and left to accumulate. The contractor builds a register of open items; the client's team, often stretched, does not have the capacity to assess them as they arrive. Six or twelve months later there are dozens of unresolved events, the people involved have moved on, and the project arrives at a single, enormous reckoning. At that point the relationship is adversarial, the evidence has decayed, and the only realistic forum is a formal one.

This is the most important failure to understand, because it is cultural rather than contractual. The contract did not create the backlog. A decision — usually an unspoken one — to treat compensation events as a claims exercise to be settled later, rather than a management task to be discharged now, created the backlog.

2. There is no reliable Accepted Programme to assess against

Time is where compensation events become genuinely contentious, and the programme is the instrument that is supposed to resolve it. NEC assesses the effect of an event on planned Completion by reference to the Accepted Programme — the contractor's current, agreed plan, complete with the logic, resources and float that show how the works are actually being delivered.

When the Accepted Programme is current and properly maintained, the time effect of an event is largely a matter of analysis. When it is not — when the programme is months out of date, was never formally accepted, or bears little relationship to how the job is really being built — there is nothing solid to assess against. The parties are then left arguing about delay in the abstract, each with its own narrative, and neither able to prove its case cleanly.

A surprising proportion of compensation event disputes are, at root, programme disputes wearing a commercial disguise. The absence of a living, accepted programme is one of the most reliable predictors that a project's change account will end up in difficulty.

3. Early warnings are skipped, then used as a weapon

The early warning mechanism is one of NEC's most valuable features and one of its most neglected. The parties are required to warn each other of matters that could affect cost, time or quality, and to meet to consider how to deal with them. The contract then has teeth: if a contractor fails to give an early warning of something an experienced contractor should have raised, the resulting compensation event can be assessed as if that warning had been given — which usually means a lower figure.

On well-run projects the early warning process genuinely reduces the impact of events, because problems are confronted while options still exist. On poorly-run projects, early warnings are treated as paperwork, ignored when it matters, and then produced months later as ammunition in an argument about entitlement. A mechanism designed to prevent disputes becomes a contributor to them, purely because it was operated as a formality.

4. Quotations and assessments argue about the wrong thing

NEC assesses compensation events on the basis of their forecast effect on Defined Cost, plus the Fee, judged at the time of assessment. This is deliberate. It rewards forward planning and discourages waiting to see how things turn out. It also runs directly against the instinct of many commercial teams, who are more comfortable arguing about what something actually cost than forecasting what it will cost.

Disputes follow when the parties quietly switch the basis of assessment — when quotations are padded against an uncertain future, or when a Project Manager rejects a forecast simply because actual cost later differed. The contract is clear that the agreed assessment is not reopened just because the forecast proves imperfect. Teams that do not internalise this end up re-litigating settled events, and trust erodes quickly once that starts.

5. The Project Manager does not keep pace

The procedure depends on the Project Manager doing two things reliably: responding to notifications and quotations within the contractual periods, and making their own assessment where a quotation cannot be accepted. The contract even provides for deemed acceptance if the Project Manager goes silent — a provision that exists precisely because the drafters anticipated this failure.

When the Project Manager is under-resourced, or treats compensation events as a low priority, the whole mechanism stalls. Quotations sit unanswered. Assessments are not made. The contractor, faced with silence, either escalates or stockpiles. Either way the project loses the real-time discipline that makes NEC work, and the eventual settlement becomes far larger and far more contested than it needed to be. Adequate, capable resourcing of the Project Manager function is not an administrative nicety; it is a precondition for the contract operating as intended.

6. The scope is ambiguous, so entitlement is ambiguous

Many compensation events turn on a single prior question: was this matter within the contractor's obligations, or was it a change? That question is answered by the Scope (the Works Information, in older editions). Where the Scope is clear, well-structured and complete, the answer is usually obvious and the event is straightforward. Where it is vague, internally contradictory, or full of gaps, every grey area becomes a negotiation, and a proportion of those negotiations become disputes.

The cost of a weak Scope is paid not at tender but throughout delivery, one contested event at a time. A great deal of compensation event trouble is built in before a spade goes in the ground, in documents that were rushed, inherited, or never properly reconciled.

The contract did not create the dispute. The way the parties chose to run it did.

What good looks like

The common thread across all six causes is discipline applied early, not cleverness applied late. The projects that keep their change accounts under control tend to share the same unglamorous habits:

• Compensation events are notified, quoted, assessed and closed in something close to real time — not warehoused for a final settlement.
• The Accepted Programme is treated as a live management tool and kept current, so the time effect of any event can be assessed against something real.
• Early warnings are raised honestly and acted on in risk reduction meetings, because the parties want fewer problems, not better ammunition.
• Assessments are made on a forecast basis and then left settled, with both teams understanding why the contract works that way.
• The Project Manager function is resourced to respond within the contractual periods, every time.
• The Scope is interrogated for gaps and contradictions before award, when they are cheap to fix.

None of this requires a different contract. NEC already provides the framework; the question is whether a project has the capacity, the behaviours and the assurance to use it as designed. Most disputes are not a failure of the words on the page. They are a failure to run the process the words describe.

The most useful intervention, in our experience, is rarely a legal one. It is an honest, independent look at how the mechanism is actually being operated — ideally before the backlog forms, while there is still time for discipline to do its work.