NEC3 vs NEC4: the differences that matter (and whether to switch)

NEC4 is not a reinvention of NEC3 — it is a careful tightening of a contract that already worked. The philosophy is untouched: mutual trust and co-operation, early warning, compensation events and a live, accepted programme. What changed is the wording, who holds the initiative, and — crucially — what happens when someone says nothing. For South African teams choosing an edition or weighing a migration, those changes are real but manageable. This is the side-by-side that actually matters.

NEC3 was published in 2005 and amended in 2013; NEC4 followed in 2017. Both are in active use on South African programmes right now, and they will co-exist for years yet. A roads framework let under NEC3 in 2020 does not become invalid because a newer edition exists, and many public bodies still administer large NEC3 portfolios. At the same time, new procurements increasingly specify NEC4. So the practical question for most teams is not "which is better" in the abstract — it is "which edition is on this contract, and how do the differences change the way I work?"

What stayed the same

Start here, because it is the bigger truth. If you already run NEC3 well, you already understand most of NEC4. The core mechanisms carry across almost unchanged:

• The spirit of mutual trust and co-operation remains the opening obligation of the contract — collaboration is still a contractual duty, not a slogan.
• Early warning still requires either party to notify a matter that could affect price, time or quality as soon as they become aware of it — the duty is identical, only the clause number moved.
• Compensation events still live in section 6 (clauses 60 to 66), still follow notify-quote-assess, and still keep the accepted programme as the basis for assessing delay.
• The programme is still the live management document the whole contract turns on — submitted, accepted and revised, showing the Accepted Programme, terminal float, time risk allowances and the method of working.
• The main Options (A to F) and the structure of Contract Data and secondary Options are the same shape.

Because of that continuity, retraining people on NEC4 is genuinely incremental. You are not teaching a new contract; you are teaching what moved and what is new.

Terminology: same ideas, plainer words

The most visible change is vocabulary. NEC4 renamed several core terms to be clearer and more inclusive, but the underlying documents and roles do the same job. If you mentally translate the new word back to the old one, nothing about the mechanism changes.

• Works Information becomes Scope — the document that says what the Contractor must do and any constraints on how.
• Employer becomes Client — the party who wants the work done and pays for it.
• Risk Register becomes the Early Warning Register — the shared list of notified matters and the actions agreed against them.
• Risk Reduction Meeting becomes the Early Warning Meeting — the forum where those matters are worked through.
• The early warning obligation itself moved from clause 16 in NEC3 to clause 15 in NEC4.

The renaming is not cosmetic point-scoring. "Scope" and "Client" travel better across sectors and borders, and "Early Warning Register" ties the document explicitly to the early-warning process it serves — which is exactly where teams should be looking when something starts to go wrong.

The change with the sharpest teeth: deemed acceptance

This is the single most important difference for day-to-day administration, and the one most likely to catch out a team migrating from NEC3. NEC4 introduces deemed acceptance — automatic consequences when the Project Manager fails to respond within the contractual period. NEC3 has no equivalent automatic sanction; under NEC3, silence simply meant the matter stayed open.

Two instances matter most:

1. Compensation event quotations. Under NEC4, if the Project Manager does not reply to the Contractor's quotation within the time allowed, the Contractor can notify that fact, and if the Project Manager still does not respond, the Contractor's quotation is treated as accepted (clause 62.6).
2. Programmes. Under NEC4, if the Project Manager does not respond to a submitted programme within the time allowed, the Contractor can notify that, and a continued failure to reply results in the programme being treated as accepted (clause 31.3).

The effect is profound. Under NEC3, a Project Manager who let quotations and programmes pile up created delay and friction, but the Contractor's only remedy was to push. Under NEC4, that same inertia can hand the Contractor an accepted quotation — money — or an accepted programme it drafted on its own terms. The discipline cuts both ways: Contractors must submit clean, complete quotations and programmes worth accepting, and Project Managers must build a watertight diary so a deadline is never missed by accident.

Payment: who makes the first move

NEC3 and NEC4 take genuinely different starting points on payment, even though the build-up of the amount due is the same.

NEC3 — the Project Manager assesses and certifies

Under NEC3 the Project Manager assesses the amount due at each assessment date and certifies payment (clauses 50 and 51). The initiative is the Project Manager's. The Contractor supplies information, but the contractual act of assessment belongs to the Project Manager, with or without a formal application.

NEC4 — the Contractor applies first

NEC4 flips the default. The Contractor submits an application for payment on or before each assessment date (clause 50.2). The Project Manager then assesses the amount due (clause 50.4) and certifies within one week of the assessment date (clause 51.1). The sting is in the tail: where the Contractor has made an application and no certificate is issued when one is due, the applied amount can become the amount due. Silence has a price here too.

Compensation events: refined, not rewritten

Compensation events sit in section 6 (clauses 60 to 66) in both editions and the process is largely the same. NEC4's refinements are practical rather than philosophical:

• A structured process for finalising Defined Cost on the cost-based main Options, so the actual cost of a compensation event is settled within set periods rather than drifting to the final account.
• Tightened time-related provisions around notification and assessment, reinforced by the deemed-acceptance sanction described above.

If you know how to notify, quote and assess a compensation event under NEC3, you know how to do it under NEC4 — you simply work to firmer deadlines and a clearer cost-finalisation route.

What NEC4 adds

Beyond the renamed terms and the rebalanced mechanisms, NEC4 brings genuinely new capability.

New contracts in the suite

The NEC4 suite added two contracts that have no NEC3 equivalent: the Design Build and Operate (DBO) Contract, for projects where a single supplier designs, builds and then operates an asset; and the multi-party Alliance Contract (ALC), which brings the Client and key delivery partners into one integrated commercial arrangement aimed at shared outcomes.

Contractor's design and value engineering

NEC4 lets the Contractor propose changes to the Scope — formal value engineering under clause 16 — giving the Contractor a contractual route to suggest a better, cheaper or faster way of meeting the Client's needs, with a defined way of sharing the benefit. NEC4 also clarified how the Contractor's design is submitted and accepted, reducing the ambiguity that sometimes surrounded design acceptance under NEC3.

BIM, collaboration and dispute avoidance

NEC4 leans into modern delivery. It provides far better support for BIM and the Information Model through secondary Option X10 (Information Management), alongside broader collaboration provisions. It also introduces the Dividing Date concept, which fixes a clear point for assessing certain matters. And on disputes, NEC4 keeps the familiar W1 and W2 procedures but adds Option W3, a Dispute Avoidance Board — a standing panel that helps the parties head off disputes before they harden into formal proceedings.

The differences at a glance

Area	NEC3	NEC4
Scope document	Works Information	Scope
Paying party	Employer	Client
Risk document	Risk Register	Early Warning Register
Risk forum	Risk Reduction Meeting	Early Warning Meeting
Early warning clause	Clause 16	Clause 15
Payment initiative	Project Manager assesses and certifies (cl 50–51)	Contractor applies (cl 50.2); PM assesses (cl 50.4) and certifies within one week (cl 51.1)
Late certification	No automatic sanction	Applied amount can become the amount due
Deemed acceptance	None	CE quotation (cl 62.6) and programme (cl 31.3) treated as accepted on PM silence
Compensation events	Section 6 (cl 60–66)	Section 6 (cl 60–66), plus structured Defined Cost finalisation and tighter timing
Contractor proposals	Limited	Contractor may propose changes to the Scope — value engineering (cl 16)
BIM / information	Limited support	Information Model via secondary Option X10
Dispute resolution	W1 / W2	W1 / W2 plus W3 (Dispute Avoidance Board)
New contract types	—	Design Build and Operate (DBO); Alliance Contract (ALC)

Which to use — and whether to switch

For a new procurement, NEC4 is the natural default. It is the current edition, it is increasingly what South African clients specify, and its refinements — deemed acceptance, the application-driven payment cycle, clearer cost finalisation, W3 and X10 — fix real friction points without disturbing the parts of NEC3 that work. Choosing NEC4 for new work is the path of least resistance and most future-proofing.

Migrating a live or about-to-start programme is a more measured decision. There is no contractual obligation to abandon NEC3, and switching mid-portfolio is rarely worth disrupting contracts that are running cleanly. The cost of moving to NEC4 is mostly internal rather than legal:

• Retraining commercial, planning and project-management staff on the new terms and the rebalanced payment and acceptance mechanisms.
• Rebuilding templates — applications, quotations, registers, programme submissions — around the NEC4 wording and clause numbers.
• Updating procedures so the new deemed-acceptance deadlines are never missed: a single overlooked quotation or programme response now has a contractual, financial consequence.

Be honest about that last point. The biggest practical risk in moving to NEC4 is not the contract — it is administration. The edition rewards organised teams and punishes those who let deadlines slip, because under NEC4 a missed response can cost money or hand over an accepted programme. Decide on the edition with eyes open, and put the discipline in place before the first assessment date.