Compensation events in plain English: what counts under clause 60.1
A plain-English walk through the clause 60.1 list of NEC compensation events, grouped by category, so you can spot a valid event early.
On this page
If you work on an NEC contract you will hear "that's a compensation event" said about everything from a late drawing to a flooded trench. Some of those calls are right and some are not. The list in clause 60.1 is the only thing that decides, and it is more specific than most people remember.
This guide groups the list by theme so you can recognise events quickly. It deliberately does not quote item numbers, because the numbering and the wording differ between NEC3 and NEC4 and between contracts that have been amended. Always check the list in your own contract, including any Z clauses.
What a compensation event actually is
A compensation event is something that happens which is not the Contractor's risk under the contract. If it does, the Contractor may be entitled to a change in the Prices, a later Completion Date or Key Date, or both. It is the contract's way of re-balancing time and money when the Client's side changes things or carries a risk.
Two points catch people out:
- The event must be on the list, or be an event the contract says is one. "It wasn't our fault" is not enough.
- The event must have an effect on cost or time. An event with no effect on either is still notified, but it produces no change.
The main groups on the list
Instructions and changes. The Project Manager or Supervisor instructs a change to the Scope (Works Information in NEC3), or gives an instruction that changes the Accepted Programme or the way the work is done. Instructions to stop or not start work, and instructions to uncover or test work that turns out to be fine, also sit in this group.
Access and information. A part of the Site is not available to the Contractor by the later of its access date in the Contract Data and the access date on the Accepted Programme. The Client or its people do not provide something the contract says they will provide, such as materials, plant or information, by the date in the programme.
Failure to act on time. The Project Manager or Supervisor does not reply to a Contractor's communication within the time the contract requires. A late reply to a programme or other submission can fall here.
Wrong or changed information. The Project Manager or Supervisor goes back on a decision already given, or the Project Manager corrects an assumption it stated earlier when assessing a compensation event. The Project Manager also withholds an acceptance for a reason the contract does not give.
Other parties and external events. The Client or Others working outside the times on the Accepted Programme or the conditions in the Scope, or doing Site work the Scope does not mention, can be an event. So can one of the Client's liabilities stated in the contract, the Client failing to supply materials, facilities or samples for tests, a rare event neither side could prevent that stops completion, and events added in the Contract Data or by secondary Options (for example a change in the law under Option X2). Early take over of part of the works before Completion is another.
Physical conditions. Physical conditions within the Site, not including weather, that an experienced contractor would have judged to have such a small chance of occurring that it would have been unreasonable to allow for them. Only the excess over a reasonable allowance is assessed. This is a high bar, and it depends on the Site Information and what an experienced contractor could reasonably have found out. See unforeseen ground conditions.
Weather. Weather is an event only where a calendar month's measurement, recorded at the place named in the Contract Data before the Completion Date, is shown by the weather data to occur on average less often than once in ten years. Only the excess over that level is assessed, and each measurement is tested on its own. Ordinary bad weather is a Contractor risk. Check the Contract Data for the weather criteria in your contract.
Defects and testing. In some situations the Client's side carries the cost of searching for or testing a Defect that is not found. Check the Defects clauses (about clauses 40 to 46) in your contract.
Contractual breaches by the Client side. A breach of contract by the Client that is not on the list for another reason can also be a compensation event.
How to use the list
- Find the event in your contract's list, not in a summary.
- Note the exact words that apply and what has to be true.
- Check the Contract Data for any value, station or period the event relies on.
- Notify in time. The Contractor must notify an event within eight weeks of becoming aware that it has happened (seven weeks under the NEC4 subcontract). If it does not, the Project Manager can say the Prices and dates will not change. The bar does not apply to events arising from an instruction, notification, certificate or changed decision of the Project Manager or Supervisor, which the Project Manager notifies itself. See missed the eight-week deadline.
Things that are not compensation events
- Your own late delivery, poor productivity or resourcing problems.
- Ordinary weather.
- A cost increase you simply did not allow for.
- A Subcontractor's failure, unless it flows from a Client-side event.
Related guides
- Compensation event notification checklist
- Early warning: do I give one?
- How to prepare a CE quotation
This guide is general information, not legal advice. Check it against your contract.
