NEC4 Multiple Compensation Events: Best Practice for Quotations, Dividing Dates and Accepted Programmes
- 2 days ago
- 7 min read
Why Multiple Compensation Events Become Difficult Under NEC4
Managing multiple compensation events under NEC4 is not difficult simply because several changes have arisen on the same job. It becomes difficult when the team stops separating cause, timing and programme effect. On a live project, several instructions may affect the same work areas, the same interfaces, or the same route to planned Completion. Once those effects are blended into one broad programme narrative, the contractor often loses the ability to show what changed, when it changed, and what time or cost effect belongs to which event. NEC guidance points towards separate, prospective assessment of each event rather than a vague cumulative story.
The Accepted Programme and the Dividing Date
The contractual anchor for time assessment is the Accepted Programme current at the dividing date. NEC guidance under clause 63.5 is aimed at identifying the effect due only to the compensation event, rather than mixing it with other matters. NEC’s FAQ makes the practical consequence clear. If a later programme was issued after the dividing date, that later programme is irrelevant to the assessment of that earlier compensation event. The baseline is fixed by the contract, not by whichever programme update happens to be available when the parties start arguing about the quotation.
That is one of the most important controls on a project with several live changes. If the wrong programme revision is used, the assessment becomes easier to challenge because it is no longer tied to the accepted baseline current at the dividing date. NEC also notes that the closer the Accepted Programme is to the dividing date, the easier it is for the contractor to quote and for the Project Manager to review and accept the quotation properly.
Should Each Compensation Event Be Assessed Separately under NEC4?
Under NEC4, multiple compensation events should usually be assessed sequentially, separately and prospectively, with each event tested against the Accepted Programme current at its own dividing date. In practice, that usually supports separate programme extracts or fragnets for each CE, rather than one blended impact programme, unless the events arose close together and the parties agree to consider them together.
That is the clearest operational reading of NEC4 ECC Practice Note 1.1. The note says that if multiple compensation events arise, the assessments should be carried out sequentially, separately and prospectively. It also says the impact of other compensation events existing before the dividing date should be recognised before making the new assessment. So the contract does not ask the parties to ignore earlier events, but it does point away from one merged time-impact exercise that tries to prove several distinct events in one movement.
NEC’s own materials also show that the practical task is to decide which activities on the Accepted Programme each compensation event affects and what the delay impact is to those activities. If helpful, users may produce a version of the programme specifically for the purpose of the compensation event assessment, but that programme is not itself a programme submitted for acceptance. That supports focused event-specific programme evidence rather than one blended impact model covering several unrelated changes at once.
The Limited Circumstances Where Events May Be Considered Together
There is a qualification in the NEC guidance, but it is narrow. Practice Note 1.1 says that where a number of events arise over a short period of time, it may be sensible, by agreement, to consider them together. The key words are “over a short period of time” and “by agreement”. This is not the main rule. It is a limited exception to the normal NEC approach of separate, sequential and prospective assessment.
That is why this point has to be framed carefully. If written too broadly, it sounds as though combining multiple compensation events into one impact exercise is standard NEC practice. It is not. The safer and more defensible position is that separate assessment is the default, and combined consideration is only sensible where the timing is genuinely close, the interaction is real, and both parties are content that clarity will not be lost.eption to the normal NEC approach of separate, sequential and prospective assessment.
Why One Blended Impact Programme Can Be Risky
A single impact programme covering several compensation events often looks efficient, but it can create more problems than it solves. Once several events are blended into one revised sequence, it becomes harder to show which delay belongs to which instruction, which assumptions apply to which quotation, and whether the Accepted Programme at the correct dividing date has really been used for each event. NEC guidance is built around identifying which activities on the Accepted Programme each compensation event affects and then assessing the delay effect to those activities. That logic is easier to preserve when the assessment remains event-specific.
This is a common contractor mistake on live projects. Three compensation events arise, and the team then produces one impacted programme with all three folded into it, expecting that one file to do the work of three assessments. Even where the planning logic is sound, the contractual clarity is weaker. It becomes harder for the Project Manager to test each event cleanly, and easier for the discussion to drift into overlap arguments, causation disputes, and questions about what the programme position really was at the time. For a deeper contractor-side method, see how contractors should assess delay impacts.
What the Case Law Really Tells Us
The most useful public precedent here is not a case saying that three compensation events require three separate impact programmes. There is no strong public authority that goes that far. The more useful lesson comes from Northern Ireland Housing Executive v Healthy Buildings (Ireland) Ltd [2017] NIQB 43, an NEC3 PSC case rather than an NEC4 ECC case, which NEC itself discusses in its commentary on retrospective assessment. The value of that case here is narrower but still relevant. It shows what can happen when compensation event management drifts away from live prospective administration and into a later dispute after the work has already been carried out.
The practical lesson for contractors is straightforward. If multiple compensation events are not kept moving through the contract while the assessment is still live, the parties are more likely to end up arguing from hindsight. That does not prove that every CE must have a standalone full programme submission, but it does support disciplined, separate and timely assessment rather than a loose blended approach that only becomes intelligible at the end of the job.
A Practical Contractor Approach
The strongest way to run multiple compensation events under NEC4 is to treat each one as its own decision package while still recognising earlier compensation events existing before the dividing date before assessing the next. In practice, that means stating the event clearly, fixing the dividing date, identifying the Accepted Programme revision used, showing the relevant programme extract or fragnet, and explaining the direct and wider effect on the remaining work. NEC guidance expressly allows a version of the programme to be produced for the purpose of the compensation event assessment, provided it is understood that this is not itself a programme submitted for acceptance. If the programme basis cannot be agreed, the risk increases that the Project Manager will assess the event under clause 64 instead.
That approach is also the best way to avoid the familiar contractor error of producing one merged impact programme that tries to prove three separate compensation events in one document. The merged version may look tidy, but it usually weakens traceability. A clean separate assessment keeps the time effect reviewable, protects the commercial narrative, and makes it easier for the Project Manager to assess the quotation while the position is still live. This is exactly the kind of issue our NEC3/NEC4 compensation events support service is designed to help with.
FAQ
What makes multiple compensation events difficult under NEC4?
Multiple compensation events become difficult when several changes affect the same activities, interfaces or planned Completion path and the contractor stops separating cause, timing and programme effect. NEC guidance points towards assessing the effect of each event against the Accepted Programme, rather than letting several events collapse into one broad cumulative narrative.
Why does the Accepted Programme matter so much when assessing multiple compensation events?
Under NEC4, the Accepted Programme current at the dividing date is the contractual basis for assessing the time effect of a compensation event. A later programme issued after that dividing date is not the correct basis for assessing that earlier event. That is why poor programme discipline makes multiple CEs much harder to value and agree properly.
Should each compensation event be assessed separately under NEC4?
Usually, yes. NEC4 ECC Practice Note 1.1 says that where multiple compensation events arise, the assessments should be carried out sequentially, separately and prospectively. In practice, that usually supports separate programme extracts or fragnets for each CE, with earlier compensation events existing before the dividing date recognised before the next event is assessed.
Can multiple compensation events ever be considered together?
Sometimes, but only in limited circumstances. NEC4 ECC Practice Note 1.1 says that where a number of events arise over a short period of time, it may be sensible, by agreement, to consider them together. That is a narrow qualification to the main rule, not the normal approach.
Why can one blended impact programme be risky?
One merged impact programme may look efficient, but it can make it harder to show which activities each compensation event affects, which assumptions apply to which quotation, and whether the correct Accepted Programme at the dividing date has been used for each event. NEC guidance allows a programme version to be produced to support a CE assessment, but that support programme is used for explanation and assessment, not as a replacement accepted programme.
Need firmer control of compensation events on a live project?
If quotations are drifting, the programme basis is unclear, or change is becoming harder to value and defend, early contract-aligned support can make the position easier to manage.
References
Comments