Compensation Events

Most contractors come to NEC with JCT instincts: claim extensions retrospectively, reconstruct delay at the end, argue from the completion date. NEC works the opposite way. Time entitlement is built prospectively, one compensation event at a time, against planned completion at the dividing date. Get that wrong, and you are fighting uphill for every week. Get it right, and the contract does the heavy lifting. This is the complete contractor guide to NEC delay analysis and exte

On NEC Options C and D, real cost can still become vulnerable when the accepted programme and the cost record stop telling the same story. This article looks at the hidden commercial fracture between planning and QS records, and why that is where Defined Cost recovery often starts to fail.

Where multiple compensation events arise under NEC4, separate assessment is usually the safer route. This guide explains the accepted programme, the dividing date, and why one blended impact programme can weaken traceability.

Clause 64 is not a procedural fallback. It is the contract's switching mechanism for commercial control of valuation. When the contractor submits compliant quotations on time with current programme information, the contractor controls valuation. When the contractor fails to meet any of the four conditions, the contract switches that control to the project manager, with consequences that typically reduce entitlement by thirty to sixty percent.

The NEC4 compensation event time bar is the most asymmetric provision in the entire contract. Almost every other NEC provision creates a spectrum of outcomes through judgement, extension mechanisms, or proportionate consequences. The eight-week time bar creates a cliff: notifications inside the period preserve entitlement, notifications outside it forfeit it entirely. The contractor who understands this asymmetry organises their administration around it.

An accepted programme is not a procedural document. It is the shared reference frame against which every compensation event is assessed, every delay analysed, every progress conversation grounded. When it is missing, the reference frame itself becomes contested, and that contest favours the project manager. This is what the absence of an accepted programme actually means commercially, why it shifts control, and how contractors recover the position before the damage compounds.

Most contractors ask how to get NEC4 compensation event quotations agreed. The question is the wrong one. The strongest contractors ask what makes a quotation acceptable to a project manager who wants to accept it and what makes a quotation rejectable by a project manager looking for reasons to reject. The first optimises for completeness. The second optimises for acceptability. The two are not the same.

Every subcontractor delay on an NEC4 project is two delays at once. The subcontract event runs on its own clock with its own notification requirements, evidence, and commercial outcomes. The head contract event runs on a parallel clock with its own clause 61.3 window, its own assessment, and its own clause 64 vulnerability. Most contractors run one of these processes diligently and the other partially or not at all.

Contractors lose entitlement on NEC4 Compensation Events when the process is loose: missed 8-week time bar, wrong Accepted Programme at the dividing date, weak notices and quotations with no programme story. Here are 7 pitfalls and the controls that fix them.

If you are working under the NEC4 Engineering and Construction Contract (ECC), your entitlement to time on a compensation event is only as good as the way you assess it. Most contractors do not lose time because the event was weak. They lose it because the programme evidence is unclear, the “dividing date” baseline is wrong, or the delay model mixes the compensation event with unrelated project noise. The NEC approach is deliberately prospective. It is meant to keep commerci