Seven worked compensation event examples for contractors

Seven invented NEC4 examples showing which clause applies, who notifies and how the result is worked out, including two events that fail.

Compensation events and change4 min read

On this page
  1. At a glance
  2. 1. A door is added
  3. 2. Late access
  4. 3. An unexpected obstruction
  5. 4. A very wet month
  6. 5. A late reply
  7. 6. A search that finds nothing
  8. 7. Two that fail
  9. What to take from them
  10. Related guides

These examples use NEC4 ECC. A compensation event is an event the Client carries the risk for, so your Prices and dates can change. Every project and figure below is invented. Real results depend on your contract, Z clauses and Accepted Programme (the programme the Project Manager has accepted). The Project Manager is the person the Client appoints to run the contract day to day.

At a glance

# Situation Clause Notifies Outcome
1 Client wants a door added 60.1(1) Project Manager Money, no time
2 Plot handed over late 60.1(2) You Money and time
3 Old culvert dug up 60.1(12) You Depends on the Site Information
4 Very wet month 60.1(13) You Only the excess
5 Design reply late 60.1(6) You Small money, a little time
6 Drain search finds nothing 60.1(10) Either Cost of the search
7 Two that fail none You No change

1. A door is added

On a school refurbishment, the Project Manager instructs an extra door in a corridor wall and notifies the event with the instruction (61.1). You assess £5,000 of forecast Defined Cost and add an illustrative 10% Fee, so £5,500. The work fits into a non-critical activity with float, so planned Completion stays put. The Prices rise and the Completion Date does not.

2. Late access

The Accepted Programme gives you a compound area on 1 June, matching the contractual access date. The Client's previous contractor leaves on 15 June. Access came after both dates, so 60.1(2) applies. Nothing the Project Manager did caused it, so you notify. The critical path crosses that area, so planned Completion and the Completion Date move two weeks. Standing time, extended preliminaries and resequencing are priced as Defined Cost with the Fee.

3. An unexpected obstruction

Digging a trench, you hit an old brick culvert missing from the Site Information. The test for 60.1(12) looks forward from the Contract Date: would an experienced contractor have thought it so unlikely that allowing for it was unreasonable? Clause 60.2 says you are taken to have considered the Site Information, public information it refers to, a visual inspection and what could reasonably be obtained otherwise. If old maps in the Site Information show a culvert there, your case weakens. If there is no hint anywhere, it strengthens. Only the gap between what you found and a reasonable allowance counts. Notify promptly, because the time limit applies.

4. A very wet month

Rainfall at the Contract Data location is 210mm in one month. The weather data says anything above 160mm in that month happens less than once in ten years. That triggers 60.1(13), but you are assessed only on the extra 50mm, not the whole 210. You need records of what you could have achieved at 160mm as well as what you did at 210, and in practice that is the hard bit.

5. A late reply

You submit a design for acceptance and the Project Manager does not reply within the period for reply. Work waiting on it stops for three days. That falls under 60.1(6). It is a small event, worth a few days of idle resources. Many teams skip two-day delays with no effect, which is fine, because the test needs an effect on cost, Completion or a Key Date.

6. A search that finds nothing

The Supervisor suspects a Defect in a buried duct and orders you to uncover it. It is sound. That is 60.1(10), unless the search was needed only because you gave too little notice of work covering a test. You are paid for opening up and reinstating, plus any knock-on delay. Had a Defect been found, you would have paid to fix it with no event.

7. Two that fail

  • A supplier collapses. The replacement costs time and money, but it is not on the list, not a Client act and a typical Contractor risk.
  • A damp week. Rain stops earthworks for seven days, yet the monthly total never reaches the once-in-ten-years level. No 60.1(13) event, and 60.1(19) cannot rescue it because you could have allowed for it.

What to take from them

Outcomes keep turning on documents: the Accepted Programme dates in example 2, the Site Information in example 3 and the weather data in example 4. Get those right before an event, and you have already won much of the argument.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?