NEC4 Early Warning vs Compensation Event: Know the Difference or Lose Money

**TL;DR**

Early Warnings are about notifying potential issues *before* they happen; Compensation Events are about notifying actual cost/time impacts *after* they occur.

Failing to issue a timely Early Warning can reduce your entitlement to a Compensation Event by up to 75% (clause 63.5).

Mixing them up leads to lost money, delayed programmes, and strained relationships—know which one to use, and when.

---

The Confusion That Costs You

You’re on site. The ground conditions are worse than the Site Information suggested. The Contractor has already hit waterlogged silt two metres below formation level. The Project Manager is waiting for a notification. What do you send? An Early Warning? A Compensation Event quotation? Both?

Get it wrong, and you might lose thousands. Worse, you could lose the chance to recover cost at all.

The NEC4 Engineering and Construction Contract (ECC) is built on two distinct mechanisms: **Early Warnings** and **Compensation Events**. They are not interchangeable. They serve different purposes, trigger different obligations, and carry different consequences. Yet in practice, I see engineers and contract managers treat them as the same thing. That mistake is expensive.

---

What Is an Early Warning? (Clause 15)

An Early Warning is a **proactive** notification. You issue it when you become aware of something that could:

Increase the total of the Prices,

Delay Completion,

Delay a Key Date, or

Impair the performance of the Works.

The key word is *could*. You do not need certainty. You do not need a fully priced quotation. You just need a reasonable suspicion that a risk is emerging.

**Clause 15.1** says:

> "The Contractor and the Project Manager shall give an early warning by notifying the other as soon as either becomes aware of any matter that could affect..."

Notice the word *shall*. This is a mandatory obligation. If you know about a risk and do not notify, you are in breach of contract.

**Real example:**

You are the Contractor’s site engineer. The piling rig breaks down. It will take 10 days to get a replacement. You know this will delay the substructure works. You must issue an Early Warning immediately—even if you don’t yet know the full cost or programme impact. Do not wait until the repair quote arrives. Do not wait until the delay is certain. Do it now.

---

What Is a Compensation Event? (Clause 60)

A Compensation Event is a **reactive** entitlement. It is an event listed in clause 60.1 (or the Contract Data) that entitles the Contractor to:

Additional payment (changes to the Prices), and/or

More time (changes to the Completion Date or Key Dates).

Common examples include:

A change to the Scope (clause 60.1(1))

Physical conditions that could not have been foreseen (clause 60.1(12))

A Project Manager instruction (clause 60.1(4))

A delay caused by the Employer or Project Manager (clause 60.1(5))

**Crucially**, a Compensation Event is only valid if it is **notified properly** and within the time limits in clause 61.3.

**Real example:**

The same piling rig breakdown? That is *not* a Compensation Event under clause 60.1 unless the breakdown was caused by the Employer, or the contract specifically lists it (e.g., in the Contract Data). So you cannot submit a Compensation Event for it. But you *must* issue an Early Warning.

---

The Critical Link: Clause 63.5

Here is where the money gets lost.

**Clause 63.5** says that if a Compensation Event arises from a matter that the Contractor *should have* early-warned, the Project Manager may assess the Compensation Event as if the Contractor had given the warning. In practice, that means:

> The Project Manager can reduce the assessed time and cost by the amount that could have been avoided if the Early Warning had been given.

That is a **reduction of up to 75%** in some assessments. I have seen it happen. A Contractor fails to warn the Project Manager that a design change will clash with a service duct. The clash is discovered late. The Project Manager assesses the Compensation Event using clause 63.5 and awards only 25% of the actual cost because the Contractor should have warned earlier.

**The lesson:** Do not skip the Early Warning just because you think it’s not yet a Compensation Event. If you delay, you risk losing your entitlement.

---

When to Use Each (A Practical Decision Guide)

| Situation | What to do | Why |

|-----------|------------|-----|

| You spot a risk (e.g., weather data suggests a storm is coming) | **Early Warning** | No cost or time impact yet, but it *could* affect the programme |

| The Project Manager issues a revised drawing | **Compensation Event** | This is a change to the Scope (clause 60.1(1)) |

| You find unexpected rock during excavation | **Both** | Early Warning immediately (risk of delay/cost), then Compensation Event under clause 60.1(12) |

| Your own subcontractor is late | **Early Warning only** | Not a Compensation Event unless the contract says so, but the delay could affect others |

| The Employer fails to give access on time | **Compensation Event** | Clause 60.1(5) – no Early Warning needed, but still good practice to notify |

---

Three Common Mistakes (And How to Avoid Them)

1. Sending a Compensation Event Instead of an Early Warning

You send a quotation for a potential issue that hasn’t happened yet. The Project Manager rejects it because there is no entitlement. Meanwhile, you have not formally warned anyone of the risk. The issue escalates. You lose the chance to mitigate.

**Fix:** If you are unsure, issue an Early Warning first. You can always follow up with a Compensation Event later when the impact is certain.

2. Issuing an Early Warning but Never Following Up

You warn the Project Manager about a risk. The risk materialises. But you do not submit a Compensation Event notification within the required period (usually 8 weeks under clause 61.3). You lose entitlement.

**Fix:** Treat the Early Warning as the start of a process, not the end. Set a reminder to assess whether the risk has become a Compensation Event.

3. Assuming Every Early Warning Becomes a Compensation Event

Not all risks lead to compensation. Some are the Contractor’s own risks (e.g., poor productivity, subcontractor failure). If you automatically submit a Compensation Event for every Early Warning, you waste time and damage credibility.

**Fix:** Only submit a Compensation Event if the event is listed in clause 60.1 and the risk has actually caused cost or delay.

---

Best Practice for Site Teams

**Use a single register** for Early Warnings and Compensation Events. Track them together so you can see the link.

**Always issue Early Warnings in writing** (email or NEC4’s formal notification form). Verbal warnings are not enough.

**Don’t be afraid to warn early** – even if the risk seems small. Better to over-warn than under-warn.

**Review clause 63.5** with your team. Make sure everyone understands the financial consequence of late warnings.

---

Key Takeaways

**Early Warnings** are for *potential* issues; **Compensation Events** are for *actual* cost/time impacts. Do not confuse them.

**Clause 63.5** means a missed Early Warning can reduce your Compensation Event entitlement by up to 75%. That is real money.

**Always warn first, then assess.** Issue an Early Warning as soon as you spot a risk. Follow up with a Compensation Event only if the risk materialises and is listed in clause 60.1.

**Use a joint register** to track both. It will save you time, disputes, and lost claims.

---

*This post is part of the Early Warning category on nec4engine.com. For more practical NEC4 guidance, explore our other articles.*