The compensation event mistakes that cost contractors money

The common NEC compensation event errors made by contractors and Project Managers, what each costs and the habit that prevents it.

Compensation events and change3 min read

On this page
  1. In plain English
  2. The costliest slips
  3. Contractor mistakes
  4. What to expect from the Project Manager
  5. Slips on both sides
  6. A one-minute test
  7. Related guides

Few compensation event losses come from legal arguments. They come from missed dates, the wrong programme and quotations that price the wrong thing. A compensation event is an event the Client carries the risk for, so your price and dates get reassessed. This guide assumes NEC4 ECC unless it says otherwise. The Project Manager is the person the Client appoints to run the contract day to day.

In plain English

Notify on the day, price forward from the right date, keep your programme current, and diarise every reply deadline.

The costliest slips

Slip What it costs Habit that stops it
Notifying outside the time limit The event itself, unless an instruction or similar caused it Notify the moment anyone says "that is not ours"
An instruction with no notification Later arguments while cost goes unassessed Decide the compensation event question before issuing
Using the wrong programme Delay figures you cannot defend Identify which Accepted Programme stood at the dividing date
Counting delay from the Completion Date Time over- or under-claimed Count how far the event shifts planned Completion
Pricing actuals for future work A quotation sent back or reassessed Divide the work at the dividing date
A reply period slipping An outcome nobody chose Diary each period on day one

Contractor mistakes

Waiting to know the number. A notice only has to identify the event, and cost comes later in the quotation. The eight weeks in clause 61.3 start when you knew it had occurred, not when you finished the sums.

Leading with the fallback. Citing Client breach or prevention when a specific entry fits undermines the notice. Work through the specific entries and name the one you rely on.

Pricing as if you were helpless. Clause 63.9 assumes prompt, competent reaction. Keeping a crew standing for three weeks when they could have been redeployed invites a revision or the Project Manager's own figure.

Omitting risk allowances. Clause 63.8 allows for risks with a significant chance of arising that are not compensation events. Once the event is implemented, a wrong forecast is not revisited (66.3), so an absent allowance means you carry the risk for nothing.

Never warning. If an experienced contractor could have flagged it, the event can be assessed as if a warning existed (61.5 and 63.7). A warning is cheap.

What to expect from the Project Manager

  • Instruction now, commercial detail later. Under 61.1 the notification should accompany the instruction. Splitting them muddies the dividing date and the actual versus forecast split.
  • "Not a compensation event" without a ground. Clause 61.4 gives a closed list of grounds. A shortage of budget is not one.
  • Revised quotations as pressure. They need reasons. When more rounds are pointless, the contract provides their own assessment.
  • Rejecting programmes, then assessing without one. Slow or unfounded replies leave nothing to measure the next event against.

Slips on both sides

  • Settling the money but not the time, leaving the Completion Date open until delay damages loom.
  • Waiting months and then pricing everything as actual cost, which is not what clause 63.1 describes.
  • Trying to reopen an implemented event because a forecast proved wrong. Only a corrected stated assumption does that.
  • Holding the status in one person's head. A compensation event register reviewed weekly fixes most lapses.
  • Skipping the Z clauses, which often amend time bars, reply periods and the event list.

A one-minute test

Choose one open event. Can your team name who acts next, by when and under which clause? If not, repair the process before the next event arrives.

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

Was this useful?