Compensation events: how NEC prices and times change

Every NEC contract carries one promise that sets it apart from the older forms used across South African construction: change is dealt with as it happens, priced before it is done, and then locked. That promise lives in section 6 — the compensation event.

On a JBCC or FIDIC job, variations, claims and delays tend to pile up and get argued out at the end, often years later in adjudication or arbitration. NEC takes the opposite view. A compensation event (CE) is the single, unified mechanism for dealing with every type of change — whether it changes the work, the money, the time, or all three. There is no separate "variations" clause, no separate "claims" clause and no separate "extension of time" clause. There is one process, and once you learn it, you apply it to everything.

This article walks through what a CE is, the defined list in clause 60.1, the four-step procedure (notify, quote, assess, implement), and the principle that makes NEC genuinely different — forward pricing. It also sets out, clearly, where NEC4 departs from NEC3, because the differences matter on a live contract.

What is a compensation event?

A compensation event is an event that, under the contract, is at the Client's risk (NEC4) or the Employer's risk (NEC3) — and which therefore entitles the Contractor to have its effect assessed. That assessment looks at two things:

• the effect on the Prices (how much the Contractor is paid); and
• the effect on the Completion Date and any Key Dates (how much time the Contractor is given).

In other words, money and time are assessed together, in the same breath, for the same event. That is a deliberate design choice. It removes the artificial split between "what it costs" and "how long it takes" that causes so much grief on traditional South African contracts, where a contractor might secure a variation order but still battle for the associated extension of time months later.

Note the change in vocabulary between editions. NEC3 refers to the Employer and the Works Information; NEC4 renames these the Client and the Scope. The concept is identical — the document that says what the Contractor must build, and to what standard — but if your team runs both NEC3 and NEC4 contracts (as many SOEs and municipalities do during the transition), getting the terminology right avoids confusion in notifications.

The defined list: clause 60.1

You cannot make something a compensation event simply because it feels unfair. A CE is only a CE if it appears in the defined list in clause 60.1 (or in the relevant secondary Option, or has been stated elsewhere in the contract data). That list is the engine of the whole section. Common entries include:

• the Project Manager gives an instruction changing the Scope / Works Information (this is the NEC equivalent of a variation);
• the Client / Employer does not allow access to and use of a part of the site by the access date shown on the Accepted Programme;
• the Project Manager or Supervisor does not reply to a communication within the time the contract allows;
• the Project Manager instructs the Contractor to stop or not to start work;
• the Supervisor instructs a search and no Defect is found;
• physical conditions within the site that an experienced contractor would have judged to have such a small chance of occurring that it would have been unreasonable to allow for them; and
• weather measured against the contractual baseline — a weather measurement recorded in a calendar month that, compared with the weather data, is shown to occur on average less frequently than once in ten years.

The weather and physical conditions tests are objective and evidence-based, which is exactly why getting reliable site weather records and ground-condition data matters so much on South African projects — from highveld summer storms to dolomitic ground on the West Rand. The test is not "was it bad weather"; it is "was it worse than the once-in-ten-years baseline in the contract data".

The procedure: four steps

Once an event has happened, the contract sets out a disciplined, time-bound sequence. Treat each step as a deadline, not a suggestion.

1. Notification (clause 61). Either the Project Manager notifies the Contractor of a CE (for example, when issuing an instruction that changes the Scope), or the Contractor notifies the Project Manager of an event it believes is a CE. Notification is the trigger for everything that follows.
2. Quotation (clause 62). The Contractor submits a quotation showing the proposed change to the Prices and any delay to the Completion Date and Key Dates. The Contractor has three weeks to submit after being instructed to do so, and the Project Manager replies within a defined period. The Project Manager can ask for alternative quotations based on different ways of dealing with the event.
3. Assessment (clauses 63 and 64). A CE is assessed as its effect on Defined Cost plus the Fee, not on the contract rates or a market price. Time is assessed as the effect on planned Completion shown on the Accepted Programme. If the Contractor fails to submit a required quotation, or submits one that does not comply, the Project Manager makes its own assessment under clause 64.
4. Implementation (clause 65). The CE is implemented — the agreed (or assessed) changes to the Prices, Completion Date and Key Dates take effect.

The reliance on Defined Cost plus the Fee is why robust cost records are non-negotiable on an NEC job. The assessment is a forecast of the cost of the work the event causes, built up from people, equipment, plant and materials, subcontractors and a charge — not pulled from a bill of quantities. South African teams moving from re-measurable contracts often underestimate how much record-keeping discipline this demands.

NEC does not ask "what was it worth?" at the end of the job. It asks "what will it cost and how long will it take?" before the work is done — and then holds everyone to that answer.

Forward pricing: the principle that locks it in

Here is the part that surprises newcomers. Once a compensation event is implemented, it is not revisited — even if the forecast turns out to be wrong. If the Contractor priced an instructed change at a certain figure and the work later proves cheaper or dearer, the implemented assessment stands. The risk of the forecast being inaccurate sits with the party who made it.

This is "forward pricing", and it is the source of NEC's cost certainty. By dealing with each event when it arises and then closing it out, the contract avoids the end-of-job reckoning that dominates traditional disputes. The Client gets a running, current view of the final price. The Contractor gets paid for change in close to real time. The trade-off is that both sides must engage promptly and honestly — a lazy or padded forecast is a problem you cannot undo.

NEC3 versus NEC4: what changed

If your organisation runs both editions — common across South African public-sector and parastatal portfolios — you need to know exactly where the rules diverge. The structure of section 6 is broadly the same, but NEC4 made several practical improvements.

Deemed acceptance of the Contractor's quotation (clause 62.6)

This is the headline change. Under NEC4, if the Project Manager does not reply to a Contractor's quotation within the time allowed, the Contractor can notify that failure — and if the Project Manager still does not respond, the quotation is treated as accepted. This deemed acceptance under clause 62.6 is a significant shift of pressure onto the Project Manager. NEC3 had no equivalent: under NEC3, a silent Project Manager simply left the CE unresolved, which often suited a Client who wanted to defer decisions. NEC4 removes that hiding place.

The eight-week time bar (clause 61.3)

Clause 61.3 contains the much-discussed time bar. Where the Contractor should have notified a compensation event but did not, it loses its entitlement if it does not notify within eight weeks of becoming aware that the event had happened — unless the Project Manager should have notified the event but did not. In practice this is a hard backstop, and it is one of the most common reasons contractors forfeit otherwise valid entitlements. Diarise it.

Finalising Defined Cost

NEC4 introduced a clearer mechanism for finalising the Defined Cost of cost-reimbursable and target-cost work, with defined periods for the Contractor to submit and the Project Manager to assess the final figures, and a default position if those periods lapse. The aim is to stop final accounts drifting indefinitely — a chronic problem under NEC3 Options C, D and E, where the closing-out of Defined Cost could remain open long after Completion. For SA teams on target-cost contracts, this tightening is one of the more useful reasons to adopt NEC4.

Bringing it together

The compensation event is the heartbeat of an NEC contract. Master the rhythm — notify under clause 61, quote under clause 62, assess on Defined Cost plus the Fee under clauses 63 and 64 against the Accepted Programme, and implement under clause 65 — and you have mastered how NEC handles change. Respect the deadlines, especially the eight-week time bar, keep clean cost records, and treat every implemented CE as final. Do that, and the dreaded final-account battle largely disappears.