Notifying a compensation event when you never gave an early warning

Yes, you can notify a compensation event without an early warning under NEC. Learn what it may cost you and how to run both notices together.

Compensation events and change3 min read

On this page
  1. In plain English
  2. Side by side
  3. Three situations
  4. What not to do
  5. Doing both at once
  6. Related guides

Yes, you can. Under both NEC3 and NEC4, a warning is not a precondition for notifying a compensation event, which is an event the Client carries the risk for, so your price and dates get reassessed. The catch is on the money side: where an experienced contractor would have raised a warning, the event can be priced as if one had been raised.

In plain English

An early warning is a heads-up about a risk. A compensation event notice formally starts a change to price and time. They often concern the same problem, but each stands alone.

Side by side

Early warning Compensation event notice
Purpose Let both sides avoid or shrink a risk Start the change to Prices and dates
Given by You or the Project Manager Whoever the cause points to
Triggered by Awareness of a possible effect on cost, time or quality A listed event
NEC4 / NEC3 clause 15 / 16 61.1 and 61.3 in both
Deadline As soon as you know Eight weeks from your awareness, when it is yours to give
Consequence Nothing is admitted An entitlement the Project Manager must answer

The Project Manager is the person the Client appoints to run the contract day to day.

Three situations

  1. Warning first, event later. This is the tidy order. The warning sits on the register, options get discussed, and if the matter turns into a compensation event you notify it in a separate document. The warning does not pause the eight weeks. Anything agreed at the meeting should feed into the pricing.
  2. No chance to warn. A freak storm or sudden structural failure leaves no opening. You just notify, and since the Project Manager has nothing to base a 61.5 statement on, pricing is untouched.
  3. Warning possible, none given. You can still notify. If the Project Manager concludes an experienced contractor would have warned, they record that in the instruction to quote, and the assessment proceeds as if you had. The pricing rule is 63.7 in NEC4 and 63.5 in NEC3. See what a missing warning costs.

What not to do

  • Do not hold a notice back because no warning went out. A late notice under 61.3 can lose the event outright. A 61.5 statement merely adjusts the price.
  • Do not produce a warning afterwards as cover. Sending one after the event, with no explanation, helps nobody and looks poor on the record. If you knew earlier, be honest about it.
  • Do not put both messages in one document. They do different jobs, and clause 13 wants notifications kept apart. Two on the same day is perfectly fine.
  • Do not rely on the Project Manager already knowing. It may help in practice, but the clause asks what you could have done.

Doing both at once

Suppose you hear on a Tuesday that the Client's fabricated steel for a substation will land three weeks after the date shown on the Accepted Programme. Nothing has gone wrong yet.

  1. Send an early warning that day.
  2. Ask for it to be logged and for a meeting on options.
  3. Notify the event under 60.1(3). You are allowed to, because the clause also catches an event you expect.
  4. When instructed, prepare the quotation, reflecting the options discussed.

In NEC4 the eight weeks run from awareness that the event has happened, so notifying now is early. That is harmless and gets people talking.

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

Was this useful?