NEC3 vs NEC4: the changes that matter for contractors' programmes and project controls
- Mar 5
- 16 min read
Updated: 5 days ago
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
A planning team is mobilising on two jobs in the same week. One is NEC3. The other is NEC4. The team treats them as fundamentally different contracts. Separate templates. Separate procedures. Separate training material. Separate internal guidance notes circulated to project managers and quantity surveyors. Six months in, the two procedures have diverged in ways that produce more confusion than clarity. Site teams are uncertain which rules apply where. The commercial team has duplicated administrative work. The planning function has built parallel programme review checklists that are 80% identical and 20% subtly different.
Eventually somebody asks the question that would have saved months of duplicated effort: what actually changed?
The answer is less than most contractors think, and more than most contractors who have only read the marketing materials realise.
The NEC3 vs NEC4 transition is not a move to a new contract. The clause structure is recognisable. The compensation event process works the same way. The programme requirements under clause 31.2 are largely identical. The mutual trust and co-operation language at clause 10 is preserved. A contractor walking into an NEC4 project from an NEC3 background does not need to learn a new contract. They need to understand what was changed, why it was changed, and what the change demands of the contractor's behaviour.
This article explains exactly that. It covers the changes that actually affect contractors managing programmes, compensation events, and project controls on a live job. It does not catalogue every clause amendment. It focuses on the changes that have commercial consequence for the people running the works.
The central insight: NEC4 codifies NEC3 workarounds
The single most useful way to understand the NEC3 to NEC4 transition is this: NEC4 is not new mechanics. It is NEC3 with the most common workarounds standardised into formal procedures.
Every significant change in NEC4 maps to a specific NEC3 failure mode. Project managers ignoring programme submissions for months is now addressed by deemed acceptance. Contractors hiding non-implemented compensation events from revised programmes is now closed off by the removal of the "implemented" qualifier. Risk Registers being conflated with corporate risk management is now resolved by renaming the document to match its actual function. Terminal float ownership being argued from inference is now made explicit. End-of-job reckonings on Defined Cost are now broken into progressive reviews. Disputes drifting into formal adjudication without senior intervention are now interrupted by a four-week negotiation window.
Every change is the codification of a behaviour that experienced contractors and project managers had already developed informally. The contractor who ran NEC3 well was already doing what NEC4 now requires. The contractor who treated NEC3 as a tick-box exercise will struggle with NEC4 worse than they struggled with NEC3, because NEC4 has closed more of the loopholes that protected lax administration.
This reframing matters because it changes how a contractor should approach the transition. The question is not "what new procedures do I need." The question is "where did my NEC3 administration rely on the absence of formal mechanisms, and how does NEC4 affect those dependencies."
The sections that follow walk through each significant change with that lens.
Programme acceptance and deemed acceptance
Under NEC3, the project manager had two weeks to accept a submitted programme or notify reasons for non-acceptance. If the project manager did neither, the programme sat unaccepted. The contractor had no formal lever to force resolution. The most common workaround was to keep submitting revisions, file the chain of submissions, and hope that the absence of an accepted programme would be remedied through escalation, contract correspondence, or eventually a compensation event under clause 60.1(9) for failure to respond.
Under NEC4, the same two-week period applies, but a deemed acceptance mechanism backs it up. If the project manager fails to respond within two weeks, the contractor may notify the failure. If the project manager then fails to respond to that notification within a further week, the programme is treated as accepted. The contractor must issue the notification of failure for this to take effect. Deemed acceptance does not happen automatically.
This is the most behaviourally significant change in the entire NEC3 to NEC4 transition. Under NEC3, project manager silence was a safe position. The programme stayed unaccepted, the contractor's compensation event entitlement weakened over time, and the project manager retained the upper hand in any subsequent assessment. Under NEC4, silence is no longer safe. A contractor who follows the procedure correctly can convert non-response into acceptance through a documented two-step notification chain.
The contractor who exploits this mechanism does not need to be confrontational. The procedure is built into the contract. Submitting formally under clause 13, tracking the two-week window, issuing the notification of failure on day fifteen, and confirming deemed acceptance after the further week is administering the contract as it was designed. The article on NEC clause 31 programme acceptance covers the procedural sequence in detail.
Compensation events on the revised programme
NEC3 clause 32.1 required the contractor to show "the effects of implemented compensation events" on revised programmes. Practitioners interpreted this widely, and incorrectly, to mean that only implemented compensation events should appear in the programme. Non-implemented events, those that had been notified but not yet agreed, were excluded from many revisions on the basis that the contract did not require them.
The interpretation was wrong as a matter of substance. A compensation event that has been notified and is affecting the remaining work is part of the contractor's realistic plan whether or not it has been formally implemented. Excluding it produces a programme that does not represent reality, which is grounds for non-acceptance under clause 31.3. But the wording was loose enough to support the misinterpretation, and the dispute about whether non-implemented CEs should appear absorbed disproportionate attention on many projects.
NEC4 removed the "implemented" qualifier entirely. Clause 32.1 now requires the revised programme to show any changes the contractor proposes to make to the accepted programme, full stop. This includes all compensation events affecting the programme: implemented, pending, in quotation, and notified by either party.
The practical consequence is that contractors managing live NEC4 jobs should treat every compensation event as visible in the programme from the point of notification. Implemented events appear as incorporated changes. Pending events appear as proposed changes, clearly identified so the project manager can distinguish them from agreed baseline. The article on NEC clause 32 programme revision covers the revision discipline that supports this.
What changed for the contractor: the programme becomes the single integrated source of truth for the works including all change, not a partial picture that excludes events still in negotiation.
Early Warning Register and the risk reduction meeting
NEC3 used the term "Risk Register" for the document maintained under the early warning clause. The terminology caused persistent confusion. Many organisations already operated corporate risk registers for governance purposes. Many project teams treated the NEC Risk Register as part of that corporate risk machinery rather than as a contractual control cycle. The result, on too many projects, was a document that captured everything from health and safety risks to commercial threats to weather exposure, all blended into a single register that drove no decisions and triggered no actions.
NEC4 renamed the document the Early Warning Register and renamed the meeting the Risk Reduction Meeting. The clause structure is otherwise broadly similar. The contract still requires both parties to notify events that could affect time, cost, or quality. The register still records those notifications. The meeting still produces actions and decisions.
What the renaming changed was the conceptual frame. The register is now named for its function, which is to capture early warnings and drive mitigation, rather than for its content, which had drifted into generic risk management territory. The meeting is named for its purpose, which is to reduce risk through agreed action, rather than as a generic forum for raising concerns.
NEC4 also moved the previously combined "Risk" section into a clearer split: operational risk through early warnings under clause 15, and commercial liabilities and insurance under clauses 80 to 87. The separation helps keep the early warning conversation operational rather than legal.
What changed for the contractor: clearer terminology, clearer separation between operational risk and legal allocation, and a tighter link between the register and the actions the contract expects to follow from it.
Terminal float and clause 63.5
Under NEC3, terminal float, the gap between planned completion and the contractual completion date, was treated as belonging to the contractor by inference rather than by explicit provision. Most experienced practitioners agreed that compensation events should move the completion date by the amount planned completion was delayed, preserving the terminal float that existed before. But the clause language was not unambiguous, and disputes about whether terminal float was a contractor benefit or a shared float persisted on some projects.
NEC4 made the position explicit. Clause 63.5 (now numbered clause 63.5 in NEC4 ECC, previously 63.3 in NEC3) confirms that planned completion and the completion date are assessed separately, and that the completion date moves by the amount of delay caused to planned completion by a compensation event. The terminal float that existed before the event is preserved.
This change does not invent a new contractor entitlement. It removes the argument that NEC3 left open. A contractor on an NEC4 project arguing that terminal float belongs to them is now arguing from explicit clause language rather than inference. A project manager challenging that position is arguing against the clear words of the contract.
The article on time risk allowance and terminal float in NEC covers the practical mechanics in detail.
What changed for the contractor: an entitlement that was always intended is now beyond argument.
Acceleration under clause 36
NEC3 clause 36 allowed the project manager to instruct the contractor to submit a quotation for acceleration. The contractor was not obliged to provide the quotation, and the project manager could not assess the acceleration themselves. This made acceleration a voluntary mechanism, but the procedural initiative sat with the project manager.
NEC4 opened the proposal to either party. Both the contractor and the project manager can now propose acceleration to bring forward the completion date. If both parties are willing to consider it, the project manager instructs the quotation, and the contractor has three weeks to provide it. The project manager has a defined response period. The fundamental principle remains unchanged: acceleration cannot be imposed, only agreed.
The change matters because it allows contractor-initiated acceleration conversations to follow a formal contractual route rather than ad-hoc commercial negotiation. A contractor who sees an opportunity to recover programme through paid acceleration can propose it through clause 36 and receive a structured response. Under NEC3, the same conversation often happened informally and without the procedural protection of the clause.
The article on NEC programme acceleration and mitigation covers the practical distinction between acceleration and mitigation, which remains the most commercially significant boundary in NEC time management.
What changed for the contractor: acceleration can now be contractor-initiated through a formal mechanism, with defined timescales for both parties.
Defined Cost and progressive review
On Options C, D, and E (target cost and cost-reimbursable), NEC3 contractors typically faced an end-of-job reconciliation of Defined Cost. The contractor submitted cost records throughout the project. The project manager reviewed them. Disputes about which costs were properly within Defined Cost accumulated. The reckoning at completion was often a substantial commercial exercise that took months to resolve, sometimes longer than the construction phase of certain elements.
NEC4 introduced a progressive review mechanism. The contractor can notify the project manager that part of the Defined Cost is ready for review. The project manager has 13 weeks to carry out that review. If the project manager does not respond within 13 weeks, the costs are treated as accepted.
The mechanism does several things. It encourages the contractor to bring cost records forward in tranches as work completes, rather than accumulating everything for an end-of-project audit. It creates a deadline that forces the project manager to engage with cost review while evidence is still fresh. And it provides a backstop that protects the contractor against indefinite delay in cost review, similar to the deemed acceptance mechanism for programmes.
The contractor must invoke the mechanism. Notifying that costs are ready for review is the trigger. Without the notification, the 13-week clock does not start. Many contractors on NEC4 jobs do not use this provision, either because they are unfamiliar with it or because they have continued to operate on the NEC3 end-of-job model. Contractors who do invoke it find that cost agreement happens progressively, friction reduces, and the end-of-job reconciliation becomes manageable rather than monumental.
What changed for the contractor: a tool to convert end-of-job cost battles into progressive cost agreement, but only if the contractor uses it.
Dispute resolution and the senior representative negotiation
NEC3 dispute resolution under W1 (adjudication) and W2 (UK Construction Act adjudication) escalated relatively directly. Once a notice of dissatisfaction was given, adjudication was the next step. Senior intervention happened informally if at all, and many disputes that could have been resolved through commercial negotiation drifted into formal proceedings because no structured intervention point existed.
NEC4 inserted a four-week senior representative negotiation period before formal adjudication can proceed. Each party nominates a senior representative. The representatives meet to attempt resolution. Only if the four weeks pass without resolution does the dispute proceed to adjudication. The mechanism is mandatory under W1 and consensual under W2. NEC4 also introduced W3, the Dispute Avoidance Board option, for projects in jurisdictions where the UK Construction Act does not apply.
For contractors, this changes the texture of dispute management. Disputes that previously escalated quickly now go through a structured intervention point. The senior representative meeting is not optional in W1 and not easily skipped in W2. A contractor preparing for adjudication on an NEC4 contract should expect to engage with the senior representative process first, and should prepare for that meeting with the same rigour they would apply to formal proceedings.
The behavioural effect is that more disputes resolve before adjudication. A contractor with a coherent programme narrative, evidence-backed cost positions, and clear contractual analysis is well positioned to use the senior representative meeting effectively. A contractor without those things will find adjudication delayed but not avoided, and may find the senior representative meeting harder than expected because the other side has prepared more thoroughly.
What changed for the contractor: an additional structured opportunity to resolve disputes before formal proceedings, but only useful if the contractor turns up with the same preparation they would bring to adjudication.
NEC3 vs NEC4: the comparison table
The table below summarises the changes that matter for contractors managing programmes and project controls. It is not exhaustive of every NEC4 amendment. It covers the changes that have commercial consequence on a live job.
Topic | NEC3 | NEC4 | What changed for the contractor |
Programme acceptance | Project manager has 2 weeks to respond; no formal default if silent | Same 2-week period plus deemed acceptance if PM fails to respond after a notification of failure | Silence stops being a safe position; contractor has a procedural lever to convert non-response into acceptance |
Compensation events on revised programme | Required to show "implemented compensation events" | Removed; revised programme should reflect all changes including pending CEs | Programme becomes single source of truth; non-implemented CEs cannot be hidden |
Risk Register | Risk Register | Early Warning Register | Document named for its function; risk allocation moved to separate clauses |
Risk reduction meeting | Risk Reduction Meeting | Risk Reduction Meeting (renamed at the document level, mechanism preserved) | Tighter conceptual link between register and action |
Terminal float | Implied by float between planned completion and completion date | Explicit: clause 63.5 confirms terminal float belongs to contractor | Entitlement that was inferred is now beyond argument |
Acceleration (clause 36) | Only PM could instruct quotation | Either party can propose; defined timescales for both sides | Contractor can initiate paid acceleration through formal mechanism |
Defined Cost (Options C/D/E) | Reconciled at completion | Progressive review: PM reviews within 13 weeks of notification or costs are treated as accepted | Tool to convert end-of-job battles into progressive agreement, if contractor invokes it |
Schedules of Cost Components | Separate short schedule for some Options; multiple fee percentages | Single schedule format; single fee percentage | Simpler commercial mechanics; less interpretation argument |
Dispute resolution | Adjudication via W1/W2 | 4-week senior representative negotiation period before formal escalation; W3 (Dispute Avoidance Board) for non-Construction Act jurisdictions | Structured intervention before adjudication; preparation requirements increase, not decrease |
Additional compensation events | Bespoke Z clauses | Can be added via Contract Data without bespoke amendments | Project-specific risk allocation more transparent at tender stage |
Mutual trust | Clause 10.1 | Clause 10.2; commitment retained and reinforced | No substantive change |
Table 1: NEC 3 vs NEC4 comparisson of changes that affect contractors in UK.
What this means for contractors who learned NEC3
The most useful conclusion from the analysis above is also the most uncomfortable for contractors who treated NEC3 as a procedural framework rather than a commercial discipline.
NEC4 has not made the contract easier. It has made it harder to administer badly. Each significant change closes a loophole, codifies a workaround, or creates a procedural mechanism that benefits the contractor who follows it correctly. The contractor who already ran NEC3 well, submitting programmes formally, tracking responses, escalating non-acceptance, showing all compensation events on revised programmes, distinguishing terminal float from contractor risk, and using clause 36 to formalise paid acceleration, finds that NEC4 supports those behaviours with explicit provisions that NEC3 only implied.
The contractor who ran NEC3 informally, submitting programmes by email without formal notification, accepting project manager silence rather than challenging it, hiding non-implemented compensation events to avoid commercial pressure, allowing terminal float to drift, and accelerating without clause 36 quotations, finds that NEC4 has tightened most of the gaps that previously protected this style of administration. The contractor's options are narrower. The procedural levers that benefit the project manager are reduced. The procedural levers that benefit the contractor exist but require the contractor to use them.
The transition therefore demands more from contractors who treated NEC3 as paperwork. NEC4 provides better tools, but the tools require active engagement. Deemed acceptance does not happen unless the contractor notifies the failure. Progressive Defined Cost review does not happen unless the contractor notifies that costs are ready. Contractor-initiated acceleration does not happen unless the contractor proposes it. Visible non-implemented compensation events do not appear unless the contractor includes them.
The pattern is consistent: NEC4 has made the contract more procedurally fair, and the procedural fairness benefits the side that engages with the mechanism.
NEC3 vs NEC4 summary
NEC4 is not a new contract. It is NEC3 with the workarounds codified, the loopholes closed, and the procedural mechanisms made explicit.
The contractor who understood NEC3 well already understands most of NEC4. The behaviours that worked under NEC3 still work under NEC4. The procedural mechanisms have changed in ways that benefit contractors who use them and disadvantage contractors who do not.
The most behaviourally significant change is deemed acceptance, which converts project manager silence from a safe position into a defeasible one. The most commercially significant change is the progressive review of Defined Cost on Options C, D, and E, which can transform end-of-job reckonings into manageable agreement. The clearest substantive change is the explicit treatment of terminal float at clause 63.5, which removes an argument that NEC3 left open.
For contractors managing live NEC4 jobs, the practical lesson is to use the mechanisms the contract provides. Submit programmes formally under clause 13. Track the two-week response window. Issue the notification of failure on day fifteen if no response has been received. Show all compensation events on revised programmes whether implemented or pending. Notify Defined Cost ready for review in tranches. Propose acceleration through clause 36 rather than absorbing recovery costs as overhead. Engage the senior representative process before adjudication with the same rigour as the formal proceedings.
NEC4 rewards the contractor who administers the contract as it was designed to be administered. The contractor who does not is no worse off than under NEC3, but the contractor who does is significantly better protected than NEC3 ever allowed.
FAQ
Is NEC4 a fundamentally different contract from NEC3?
No. The clause structure, the compensation event mechanism, the programme requirements, and the mutual trust language are all preserved. NEC4 codifies workarounds and closes loopholes that NEC3 left open, but the underlying mechanics are recognisable. A contractor moving from NEC3 to NEC4 needs to understand what changed and why, not learn a new contract from scratch.
What is the most important NEC3 to NEC4 change for contractors?
Deemed acceptance of programmes. Under NEC3, project manager silence on a programme submission was a safe position. Under NEC4, if the project manager fails to respond within two weeks and then fails to respond to a notification of failure within a further week, the programme is treated as accepted. The mechanism shifts the procedural balance significantly and protects contractors against the most common cause of accepted programme drift on NEC3 projects.
Should non-implemented compensation events appear on NEC4 revised programmes?
Yes. NEC4 removed the "implemented compensation events" wording from clause 32.1 specifically because it was being misinterpreted as excluding non-implemented events. The revised programme should reflect all compensation events affecting the work, whether implemented or pending, with pending events clearly identified so the project manager can distinguish agreed from proposed changes.
Did NEC4 change terminal float ownership?
Not in substance, but it removed the argument. Terminal float belonged to the contractor under NEC3 by inference from the float treatment in compensation event assessment. NEC4 made the position explicit through clause 63.5, which confirms that planned completion and the completion date are assessed separately and that terminal float is preserved when compensation events occur. Contractors arguing terminal float ownership on NEC4 projects argue from explicit clause language rather than inference.
What is the progressive Defined Cost review under NEC4?
On Options C, D, and E, the contractor can notify the project manager that part of Defined Cost is ready for review. The project manager has 13 weeks to carry out that review. If the project manager does not respond within 13 weeks, the costs are treated as accepted. The mechanism allows contractors to convert end-of-job cost reconciliation into progressive cost agreement, but the contractor must invoke it. Without the notification, the 13-week clock does not start.
What is the senior representative negotiation under NEC4?
Before formal adjudication can proceed, NEC4 W1 mandates and W2 permits a four-week period during which senior representatives of each party meet to attempt resolution. Only after the four weeks pass without resolution does the dispute proceed to adjudication. The mechanism creates a structured intervention point that NEC3 lacked and resolves more disputes before formal proceedings.
Is NEC4 harder to administer than NEC3?
No, but it is harder to administer badly. NEC4 has closed several of the loopholes that protected lax administration under NEC3. Contractors who already ran NEC3 well find NEC4 more supportive of their existing behaviour. Contractors who treated NEC3 as a tick-box exercise find NEC4 less forgiving. The procedural fairness has improved on both sides, which means the side that engages with the mechanism gains an advantage.
Should contractors update their internal NEC procedures when moving to NEC4?
Selectively. The procedures that worked well under NEC3 mostly continue to work under NEC4, with adjustments for the specific changes covered above. The biggest adjustments are in programme submission discipline (to support deemed acceptance), revised programme content (to include all compensation events), and Defined Cost notification rhythm (to invoke progressive review). A wholesale procedure rewrite is rarely necessary. Targeted updates to incorporate the new mechanisms are usually sufficient.
About the author
Roman Bazelchuk is the Founder of NEC Planning Solutions Ltd, a UK project planning and controls consultancy supporting contractors with NEC programme compliance, compensation event assessments and live project controls. He is an NEC Accredited Project Manager and holds the APMG Project Planning and Control qualification, with a BSc in Mechanical Engineering and postgraduate training in Planning and Control.
NEC Planning Solutions provides contract-aware planning support through a QA-governed delivery model, helping project teams keep programmes accepted, current and commercially useful from tender through to live delivery.
Need NEC4 procedures aligned with the contract's procedural mechanisms?
If programme submissions are not formal enough to trigger deemed acceptance, if revised programmes are still excluding non-implemented compensation events, or if Defined Cost is accumulating to an end-of-job reckoning rather than progressive review, specialist NEC programme support brings the contractor's administration into alignment with what the contract actually rewards.
