7 ways contractors lose entitlement on NEC4 compensation events
Updated: Oct 15
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
Contractors lose entitlement on NEC4 compensation events through process, not merit. The seven ways are notifying outside the eight weeks in clause 61.3, thin notices, quoting against the wrong Accepted Programme, quotations with no programme logic, early warnings run as paperwork, cost build-ups that look backwards, and an audit trail nobody can rebuild.
Every contractor running an NEC4 contract loses some compensation event entitlement that the contract would otherwise have delivered. The amount lost is not random. It is the predictable consequence of seven specific failure modes that recur across contractor types, contract sizes, and sectors. Each failure mode produces a recognisable pattern. Each is preventable through operational discipline that does not require unusual technical capability. And the cumulative effect across a multi-year contract is the difference between the project margin the contractor priced into the bid and the project margin the contractor actually realises.
Experienced commercial directors recognise the pattern but rarely articulate it. The lost entitlement is not driven by adversarial project managers or technically demanding contracts. It is driven by how the contractor's own organisation handles the compensation event mechanism day-to-day. The seven failure modes that follow each represent a specific operational decision point where contractor behaviour either preserves entitlement or quietly forfeits it.
The market context makes the discipline more important than it was three years ago. King's College London and the Adjudication Society's third construction adjudication report identified inadequate contract administration and lack of competence as leading causes of dispute referrals, with referral volumes reaching record levels. Compensation events sit precisely at the intersection of contract administration and commercial competence. They are where weak administration produces the largest measurable entitlement loss, and where strong administration produces the most defensible commercial position.
How NEC4 compensation events work
A compensation event is an event listed in the contract, mostly in clause 60.1, that entitles the Contractor to a change in the Prices, the Completion Date or the Key Dates where it affects cost or time and is not the Contractor's fault. The most familiar is an instruction changing the Scope. Each then follows the same sequence.
Step | NEC4 clause | Who acts | Time limit |
Notify an event arising from the Project Manager's or Supervisor's own communication | 61.1 | Project Manager | At the time of the instruction, notification, certificate or changed decision |
Notify any other event | 61.3 | Contractor | Within eight weeks of becoming aware it has happened, or the Prices and dates do not change |
Decide whether it is a compensation event | 61.4 | Project Manager | One week from the Contractor's notification, or longer if the Contractor agrees |
Submit the quotation | 62.3 | Contractor | Three weeks from the instruction to submit quotations |
Reply to the quotation | 62.3 | Project Manager | Two weeks from submission |
Assess the change to the Prices and any delay | 63 (dividing date 63.1, delay 63.5) | Contractor, in its quotation | Within the time allowed for the quotation |
Assess the event itself where clause 64.1 applies | 64 | Project Manager | The time allowed for the quotation, counted from when the need becomes apparent |
Notify a missed deadline | 61.4, 62.6, 64.4 | Contractor | Two more weeks of silence after the notice count as acceptance, but an unanswered quotation for a proposed instruction or changed decision is not accepted (65) |
Implement the event | 66 | Project Manager | On accepting a quotation or notifying an assessment, or when a quotation is treated as accepted |
Table 1: the NEC4 compensation event procedure, with the clause and the time limit for each step
Notification comes first. Where the event comes from the Project Manager's or Supervisor's own instruction, notification, certificate or changed decision, clause 61.1 makes the Project Manager notify it at the time. The Contractor notifies any other event under clause 61.3, within eight weeks of becoming aware it has happened, or the Prices and dates do not change. The Project Manager then has a week under clause 61.4 to say whether it is a compensation event.
Quotations follow under clause 62.3, with three weeks to submit and two to reply. Assessment under clause 63 turns on the dividing date in 63.1: the date of the communication that gave rise to the event or, for any other event, the date it was notified. Work done by then is priced at actual Defined Cost and the rest at forecast. Delay is measured under 63.5 against the Accepted Programme current at that date.
Clause 64 makes the Project Manager assess the event itself where the quotation is late, where it decides the quotation is wrongly assessed and does not ask for a revision, or where a required programme is missing or not accepted for a reason the contract gives. Clause 66 then implements the event, and the assessment is not revised except as the contract allows. Under clauses 61.4, 62.6 and 64.4, if the Project Manager misses its deadline and the Contractor notifies the failure, two more weeks of silence count as acceptance. Quotations for a proposed instruction or a proposed changed decision are the exception: under clause 65, if the Project Manager does not reply in time, the quotation is not accepted.
Failure mode 1: missing the clause 61.3 notification window
The most expensive single failure mode in NEC4 compensation event administration is the one most contractors recognise least as a failure mode. Clause 61.3 establishes that if the contractor does not notify a compensation event within eight weeks of becoming aware that the event has happened, the Prices, the Completion Date or a Key Date are not changed. The clause does not soften this with conditions. Its only exception is an event that arises from the project manager's or supervisor's own instruction, notification, certificate or changed decision, which clause 61.1 makes the project manager notify. The time bar is operational regardless of the merits of the underlying entitlement.
What this looks like on site is unremarkable. The contractor's team becomes aware of an event that may produce a compensation event. The team waits to understand the impact before notifying. The team waits to see if the event resolves itself. The team waits because the QS function is overloaded. The team waits because the project manager has not formally instructed a quotation. Eight weeks pass. The notification is made. The project manager responds with the eight-week point. The entitlement is lost.
The detail that catches contractors out is the wording of the awareness test. The eight-week clock runs from awareness of the underlying event, not from realising that the event constitutes a compensation event under one of the clause 60.1 categories. A contractor who hits unexpected ground conditions on day one and only realises in week ten that they amount to a compensation event under clause 60.1(12) has missed the window. The mental categorisation of the event as a CE is not the trigger. The awareness of the event itself is.
The discipline that prevents this is operational rather than technical. The CE trigger log treats compensation event notification as a planning control rather than a commercial control. Every event that may produce a compensation event is logged on the date the team first becomes aware of it, with a target notification date set immediately. A weekly fifteen-minute CE triage reviews the log, confirms which events need notifications this week, which need quotations, and which are awaiting project manager response. The lookahead programme reflects the same triggers. Compensation events are not left to the QS function alone; the planning function owns the notification timeline because the contractual clock runs on the planning function's awareness.
The article on the NEC4 compensation event time bar covers the eight-week mechanism in full detail. The article on acceleration and mitigation under NEC4 covers the related clause 63.9 expectation that the contractor reacts competently and promptly to compensation events.
Failure mode 2: notifications that are not decision-grade
Even where notification happens within the time window, many notifications do not contain enough information for the project manager to respond properly. The notification states that an event has occurred without anchoring the event to a specific clause, specifying the date the contractor became aware, identifying the affected programme interfaces, or quantifying the initial mitigation actions taken. The project manager receives a notification that requires further information before assessment can begin. The eight-week clock has been stopped but the process has not started.
What this looks like is a notification that reads "delay due to access" or "late information" with no hard dates, no clause hook, and no link to the impacted programme logic. The project manager responds asking for clarification. The contractor provides incremental information across multiple exchanges. Three weeks pass before the project manager has enough information to instruct a quotation under clause 61.4. The instruction reflects the project manager's reading of the event, which may not match what the contractor actually intended to claim.
The cost is harder to measure than the time bar failure mode because it does not produce immediate entitlement loss. It produces something more insidious: a compensation event process that runs slowly, drifts in scope, and reaches agreement at lower values than a tight initial notification would have produced. Across twenty compensation events on a multi-year contract, the cumulative effect shows up clearly in the final account.
The discipline that prevents this is the one-page notification format. Every compensation event notification carries five specific elements: a summary of the event in one paragraph; the dates (event occurred, awareness date, notification date); the clause hook identifying the specific clause 60.1 item or referencing the instruction that triggered the event; the impacted interfaces showing what the contractor was waiting for and where it hits the programme logic; and the immediate mitigation actions taken within the first forty-eight hours. The format does not require sophisticated documents. It requires the planning function and the commercial function to agree on the standard and apply it consistently.
The article on what NEC compensation event notifications need to contain covers the procedural mechanics in detail.
Failure mode 3: the wrong accepted programme at the dividing date
The third failure mode produces the largest single category of project manager rejection on submitted quotations, and the cause is almost always a misunderstanding of what the contract requires.
Under clause 63.5, a compensation event is assessed against the accepted programme current at the dividing date. Clause 63.1 fixes the dividing date: the date of the instruction or other communication that gave rise to the event or, for any other event, the date it was notified. The accepted programme at that date is the reference programme against which the time impact is calculated. A programme accepted after the dividing date is not the relevant programme for the assessment. A programme that was current operationally at the time but had not been formally accepted is also not the relevant programme.
What this looks like is a contractor quotation that uses a later revised programme or a current planning "what-if" rather than the accepted programme that was actually in force on the dividing date. The project manager rejects the quotation. The contractor revises and resubmits. The cycle consumes weeks of commercial attention and produces an eventual agreement at lower value than the original quotation would have warranted.
The cost compounds with the next failure mode, because the operational consequences of getting the dividing date programme wrong include weakening the contractor's broader position on programme acceptance discipline. A contractor who cannot demonstrate which programme was accepted on which date is implicitly admitting that the programme acceptance regime has not been administered tightly.
The discipline is operational. Every compensation event quotation states the dividing date on the cover sheet. The quotation uses an extract from the accepted programme current at that date, with the impacted chain shown as it existed in that programme. Where the accepted programme is badly out of date or where there is genuine disagreement about which programme applies, the contractor proposes a specific programme to use for the assessment, or accepts the project manager's instruction on which programme applies. NEC's own practice notes specifically contemplate producing a programme to support a compensation event assessment, used for assessment rather than for general acceptance. This is the contract working as designed, not a deviation from it.
The articles on clause 31 programme acceptance and clause 32 programme revision cover the programme acceptance regime that this failure mode depends on. The judgement calls that decide how much of that delay you actually recover are set out in assessing NEC4 compensation events.
The point was tested in court in June 2026. In Premier Modular v Maidstone and Tunbridge Wells NHS Trust, an adjudicator awarded a contractor £1.65m for a late permanent water supply, and the Technology and Construction Court then refused to enforce it. Both parties had agreed the only Accepted Programme was the original attached to the contract, and that programme contained no date for the supply at all. The adjudicator closed the gap himself by treating a later contractor-issued programme as the Accepted Programme, a basis neither side had argued, and the award did not survive. NEC's own guidance says the same thing without the litigation: a programme issued after the dividing date is irrelevant to the assessment of that event. If the date you are claiming against is not in the baseline current at the dividing date, the entitlement has nothing underneath it.
Failure mode 4: quotations submitted without a programme story
The fourth failure mode produces the slowest agreement cycles and consequently the largest cashflow impact. A contractor submits a quotation containing a cost build-up and a narrative explanation, but no programme demonstration of the time impact. The time consequence is asserted in prose but not shown in logic. The project manager cannot validate the time element through the same calculation the contractor used to produce it, so the quotation cycles through revise-and-resubmit until either the contractor produces a programme-based demonstration or the project manager invokes clause 64 to assess the event themselves.
What this looks like operationally is a quotation document where the cost build-up is detailed, the narrative is articulate, and the programme section is either absent or replaced with a summary table of dates. The project manager has no way to test the contractor's logic. The quotation reads as a claim rather than as a prospective assessment, which is the opposite of what NEC4 was designed to produce.
The cost is delayed agreement, lower agreed values when agreement is reached, and increased exposure to clause 64 project manager assessments. In practice a clause 64 assessment tends to come in well below what a properly prepared quotation would have produced, for reasons covered in the article on clause 64 project manager assessments.
The discipline is the CE Decision Pack. Every compensation event quotation contains a consistent set of elements: a cover sheet stating the decision needed and the dividing date; a programme extract showing the impacted chain and interfaces as they existed in the accepted programme at the dividing date; an assumptions register listing five to ten key assumptions on which the quotation depends; a structured cost build-up that distinguishes direct cost of change from time-related cost; and an evidence index pointing to the supporting records held in the project's controlled storage. The pack does not need to be a long document. It needs to be a consistent one, produced to the same format on every event. The standardisation is what makes the process work at speed.
Pack element | What it carries |
Cover sheet | The decision needed and the dividing date |
Programme extract | The impacted chain and interfaces as they stood in the accepted programme at the dividing date |
Assumptions register | Five to ten key assumptions the quotation depends on |
Cost build-up | Direct cost of change kept separate from time-related cost |
Evidence index | Where each supporting record sits in the project's controlled storage |
The article on structuring time impact assessment under NEC4 covers the programme extract and time impact demonstration in detail.
Failure mode 5: early warnings treated as paperwork
The fifth failure mode produces a specific commercial consequence that catches contractors out because the mechanism is not always obvious until it is invoked.
Under clause 15.1, the contractor and the project manager must each give early warning of any matter that could increase the total of the Prices, delay Completion, delay meeting a Key Date or impair the performance of the works in use. The early warning regime is collaborative rather than adversarial; both parties are expected to manage risk reduction together through early warning meetings and risk reduction actions. Most contractors recognise this in principle.
The commercial consequence becomes operational under clause 61.5 and clause 63.7. If the contractor failed to give an early warning that an experienced contractor could have given, the project manager may state this when instructing a compensation event quotation. The compensation event is then assessed under clause 63.7 as if the early warning had been given. In practice, this strips out whatever cost and delay an early warning would have avoided, because the assessment assumes the parties had time to consider risk reduction actions that did not actually happen.
What this looks like on site is an early warning regime that operates as a parallel paperwork stream rather than as a live risk management tool. EWNs are issued when convenient. EWN meetings happen when scheduled but do not always produce specific risk reduction actions. Issued EWNs are not linked to subsequent compensation events through the contractor's commercial register. Six months into the contract, several events have produced compensation event entitlement, but the contractor cannot demonstrate the early warning trail that would have prevented clause 63.7 assessments.
The cost is direct entitlement reduction. The fix is to treat the early warning regime as a connected operational discipline, not as a procedural overhead. EWNs are linked to subsequent CEs in the contractor's register. EWN meetings produce dated risk reduction actions assigned to named owners. Mitigation actions reflected in the contractor's programme even when provisional. The article on acceleration and mitigation under NEC4 covers the relationship between mitigation expectations and CE assessment in detail.
Failure mode 6: cost build-ups that are not forecast-led
The sixth failure mode sits in the commercial mechanics of the quotation itself. NEC4 expects compensation event quotations to be forecasts of cost and time impact, built prospectively from the dividing date forward. Many contractor quotations are structured as retrospective claims, built from actual cost data accumulated since the event occurred. The two structures produce different outcomes and the contractual mechanism rewards one and penalises the other.
What this looks like on site is a quotation cost build-up based on the resources actually deployed against the event, presented as a "total cost incurred" figure, with risk allowance either absent or buried as a percentage uplift. The project manager challenges the build-up because the assumptions are not visible, the time-related costs are not separated from direct costs, and the risk allowance is not justified against specific contingencies. The challenge consumes weeks of commercial attention. The eventual agreed value is lower than a properly structured forecast would have produced.
The cost is direct. A properly structured quotation tends to be agreed close to the value submitted. A poorly structured one gets cut, or ends as the project manager's own assessment under clause 64. The difference compounds across the project life.
The discipline is structural. Every CE cost build-up uses a consistent four-section structure: defined cost forecast by resource and work package; time-related cost tied to the specific change in planned completion or key dates; risk allowance with rationale aligned to the competent and prompt mitigation that NEC practice notes expect; and direct cost of change separated cleanly from time consequence cost. The separation matters because if the time impact is not accepted, the contractor still preserves the direct cost element intact. The article on the relationship between NEC4 cashflow and the programme structure covers the broader cost discipline in detail.
How that build-up is actually assessed, from Defined Cost and the Fee under clause 63.1 rather than from your tendered rates, is set out in full in the NEC compensation event quotation guide.
Failure mode 7: an audit trail that cannot be reconstructed
The seventh failure mode is the one that decides outcomes when compensation events go to dispute. Most NEC contracts produce some events that the parties cannot resolve through normal commercial dialogue. These events escalate to senior representatives under W1, to adjudication, or in rare cases to arbitration. At each escalation, the party with the cleaner contemporaneous record has the stronger position.
What weak audit trail looks like is recognisable. Evidence sits in inboxes rather than in controlled storage. Programme files are overwritten rather than versioned. Photographs and site diaries are not time-stamped or are not linked to specific CE references. The team that produced the original quotation has moved on by the time the dispute crystallises. The contractor cannot reconstruct the basis on which the quotation was prepared, and the dispute is resolved on the project manager's evidence rather than on the contractor's evidence.
The cost is concentrated rather than distributed. Most compensation events do not go to dispute. The ones that do tend to be the larger ones, and the contractor's exposure on a single disputed event can exceed the cumulative cost of all the other failure modes combined.
The discipline is straightforward operationally but requires sustained organisational commitment. Every compensation event has a dedicated folder in the project's controlled storage. Every document in that folder follows a strict naming standard with revision control. Every programme version that touches the compensation event is captured in a programme version register that can prove what was accepted and when. The evidence index in the CE Decision Pack points to the supporting records, which means anybody asked to reconstruct the basis of the quotation can do so in minutes rather than reconstructing fragments of evidence under pressure weeks or months later.
This discipline pays back at two specific moments. First, when the project manager challenges a quotation during normal administration and the contractor can produce the supporting evidence rapidly. Second, when the dispute resolution mechanism is invoked and the contractor's evidence base is substantively stronger than the project manager's. Both moments produce outcomes that justify the operational discipline several times over.
How the seven failure modes connect
The seven failure modes are not independent. They interact. A contractor who misses the eight-week window on a particular event has fewer options when the quotation is challenged. A contractor whose notifications are not decision-grade gets slower responses and softer initial positions from the project manager. A contractor who quotes against the wrong programme cannot defend the quotation when it is challenged. A contractor whose quotations lack a programme story cannot prevent clause 64 assessments. A contractor who treats early warnings as paperwork accepts clause 63.7 reductions. A contractor whose cost build-ups are not forecast-led accepts retrospective challenge to the build-up. A contractor whose audit trail cannot be reconstructed under pressure accepts unfavourable resolution at every escalation point.
The compounding effect across a multi-year contract is what makes the discipline strategic rather than tactical. A contractor running tight discipline across all seven recovers entitlement that is predictable, defensible, and on the timeline the contract was designed to deliver. A contractor running loose discipline across two or three loses entitlement that compounds across every compensation event on the contract. The gap between the two does not look dramatic event by event. It looks decisive in the final account.
The article on NEC4 programme compliance and the three commercial exposures covers the broader exposures that connect to these specific failure modes.
How to protect entitlement on NEC4 compensation events
What the seven failure modes share is that the prevention is operational rather than technical. None requires unusual scheduling software. None requires unusual contractual sophistication. All require the contractor's organisation to handle the compensation event mechanism as a connected operational discipline rather than as a series of procedural events handled by separate functions.
The disciplines that work consistently across contractors who recover entitlement well are recognisable. The planning function and the commercial function meet weekly on the compensation event log, not monthly. The CE trigger log is maintained in real time, not retrospectively. The one-page notification format is used consistently, not occasionally. The CE Decision Pack format is the same on every event, not reinvented each time. The early warning regime is a live risk management tool, not a parallel paperwork stream. The cost build-ups are forecast-led, not actual-led. The audit trail is built during the project, not reconstructed after the dispute crystallises.
The contractors who commit to this discipline are not necessarily the largest or the most technically sophisticated. They are the ones who treat the compensation event mechanism as a structural feature of how they run NEC projects, not as an aspiration the project team will get to when time allows. The contractors who do not commit produce the seven failure modes repeatedly across every project, and the cumulative cost shows up in the final account rather than in any single event the team can point to as the cause.
Download the Compensation Event Trail Checklist
The procedural trail that decides whether a compensation event survives: the clause 61.3 clock, what makes a notification decision-grade, the early warning limb, the reply deadlines in both directions, and the records that rebuild the position two years later. Direct download, no sign-up.
FAQ
What is a compensation event under NEC4?
A compensation event is an event listed in the contract, mostly in clause 60.1, that entitles the Contractor to a change in the Prices, the Completion Date or the Key Dates where it affects cost or time and is not the Contractor's fault. Common examples are an instruction changing the Scope, the Client not providing something by the date shown on the Accepted Programme, and physical conditions an experienced contractor would have judged too unlikely to allow for. Each event is notified under clause 61, quoted for under clause 62, assessed under clause 63, or by the Project Manager under clause 64, and implemented under clause 66.
What is the eight-week time bar under clause 61.3?
Clause 61.3 gives the Contractor eight weeks from becoming aware that an event has happened to notify it. Miss that and the Prices, the Completion Date and the Key Dates do not change, unless the event arose from the Project Manager's or Supervisor's own instruction, notification, certificate or changed decision. The clock runs from awareness of the event, not from recognising it as a compensation event.
What makes a compensation event quotation decision-grade?
Five elements consistently distinguish quotations that get agreed at submission value from quotations that cycle through revise-and-resubmit. A cover sheet stating the dividing date and decision needed. A programme extract showing the impacted chain as it existed in the accepted programme at the dividing date. An assumptions register naming the key assumptions on which the quotation depends. A structured cost build-up separating direct cost from time-related cost. An evidence index pointing to the supporting records. The standardisation across all CE quotations is what makes the process work at speed.
What is the project manager assessment under clause 64?
Where the contractor fails to submit a compliant quotation on time, or where the project manager judges a quotation incorrectly assessed, the project manager assesses the event themselves under clause 64. In practice a clause 64 assessment tends to come in well below what a properly prepared quotation would have produced. The mechanism is covered in detail in the article on clause 64 project manager assessments.
How does the early warning regime affect compensation event assessment?
Under clauses 61.5 and 63.7, if the contractor failed to give an early warning that an experienced contractor could have given, the project manager can state this when instructing a quotation. The compensation event is then assessed as if the early warning had been given, which strips out whatever cost and delay a timely early warning would have avoided. The mechanism makes the early warning regime a live commercial discipline rather than a procedural overhead.
Does this apply to small contractors and specialist subcontractors?
Yes. The contract mechanisms apply equally regardless of contract size. The detail and the planning resource scale, but the seven failure modes appear consistently across contractor types. Small contractors and specialist subcontractors are often more exposed because the absence of a full in-house planning function means the compensation event discipline depends on individual commercial leaders rather than on institutional process.
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 BEng 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.
Arrange a consultation
Compensation events slipping through on your job? We will find where the process is leaking and close it. The first consultation is 30 minutes with Roman Bazelchuk, Director, confidential, with no documents needed in advance. Email info@necplanningsolutions.co.uk or call 0330 223 7709. Our compensation event support is set out here.
