# NEC4 Risk Register and Early Warning: A Practical Walkthrough

**TL;DR**

The Risk Register (clause 15) and Early Warning (clause 16) are not optional paperwork—they are your primary tools for controlling cost and programme on NEC4 ECC contracts.

A well-maintained Risk Register turns uncertainty into action items; a neglected one leads to disputes over compensation events.

The Early Warning process compels proactive collaboration—failure to notify risks in time can lose you entitlement to time and money.

---

Why These Two Clauses Matter More Than You Think

If you manage NEC4 ECC contracts daily, you already know that clauses 15 (Risk Register) and 16 (Early Warning) are the engine room of risk management. But in practice, too many project teams treat them as a bureaucratic tick-box. The result? Avoidable compensation events, delayed programmes, and strained relationships.

Let’s walk through how to make them work for you—not against you.

---

The Risk Register (Clause 15): Your Contract’s Radar

What It Is (and Isn’t)

The Risk Register is a living document that records risks identified during the contract, along with:

Description of the risk

Likelihood and impact (usually scored)

Proposed mitigation actions

Owner (who is responsible for managing it)

It is **not** a static list from the tender stage. Clause 15.1 requires the Project Manager to maintain it and issue it to the Contractor for comment. Both parties must keep it updated throughout the project.

Practical Example: Ground Conditions

**Scenario:** You’re the Contractor’s Project Manager on a £5m NEC4 ECC Option A (priced contract with activity schedule) for a new drainage scheme. During excavation, you encounter unexpected groundwater.

**What should happen:**

The Risk Register already lists “unforeseen groundwater” with a medium likelihood and high impact.

You issue an early warning (see next section) and update the register to reflect actual conditions.

The mitigation action changes from “dewatering plan” to “additional pumping and temporary works design”.

The register now shows the risk is “live” and being actively managed.

**What often goes wrong:**

The risk is not in the register because it was never formally identified.

The Contractor starts dewatering without notifying the Project Manager.

When the compensation event arises for additional pumping costs, the Project Manager argues it was foreseeable—and the Contractor loses entitlement.

**Lesson:** If it’s not on the register, it’s not managed. Update it weekly, not monthly.

How to Keep It Useful

**Use a simple scoring system** (e.g., 1-5 for likelihood and impact) to prioritise actions.

**Assign owners**—every risk must have a named person responsible for monitoring it.

**Link to early warnings**—every early warning should generate a new or updated risk entry.

**Review at every progress meeting**—clause 15.3 says the Project Manager reviews it with the Contractor “at each risk reduction meeting”. Make this a standing agenda item.

---

Early Warning (Clause 16): Your Early Detection System

The Obligation

Clause 16.1 states: “The Contractor and the Project Manager give an early warning by notifying the other as soon as either becomes aware of any matter that could increase the total of the Prices, delay Completion, or impair the performance of the works.”

Notice the trigger: “as soon as either becomes aware”. This is not “when you’re sure” or “when you’ve had time to assess”. It’s immediate.

Practical Example: Subcontractor Delay

**Scenario:** You’re the Contractor’s Quantity Surveyor. Your steelwork subcontractor tells you informally that their fabrication is running two weeks late due to a raw material shortage.

**What should happen:**

You notify the Project Manager immediately (same day) via the early warning procedure.

The Project Manager calls an early warning meeting (clause 16.3) within two weeks.

At the meeting, you discuss mitigation: resequencing, accelerating other trades, or sourcing from an alternative supplier.

The Risk Register is updated to reflect the new risk and agreed actions.

**What often goes wrong:**

You wait until the next progress meeting to mention it—by then, the delay is locked in.

The Project Manager argues you failed to notify in time, so any compensation event for acceleration or resequencing is not accepted.

**Lesson:** Notify early, even if you don’t have all the details. The meeting will sort out the details.

The Early Warning Meeting

Clause 16.3 requires the Project Manager to instruct the Contractor to attend an early warning meeting within two weeks of notification. Both parties must co-operate in “making and considering proposals” and “seeking solutions”.

**Tips for productive meetings:**

Keep them short—30 minutes max.

Focus on solutions, not blame.

Record decisions in the Risk Register, not separate minutes.

If the risk is resolved, close it out formally.

Common Pitfall: The “No News” Trap

Some teams avoid issuing early warnings because they fear it will trigger compensation events or damage relationships. The opposite is true. A timely early warning protects both parties:

The Contractor shows proactive management.

The Project Manager can plan mitigation without panic.

The compensation event, if it occurs, is based on agreed facts, not hindsight.

---

How the Two Clauses Work Together

Think of early warning as the **trigger** and the Risk Register as the **record**.

| Step | Action | Clause |

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

| 1 | Someone becomes aware of a potential issue | 16.1 |

| 2 | They notify the other party immediately | 16.1 |

| 3 | Project Manager calls early warning meeting | 16.3 |

| 4 | Meeting identifies mitigation actions | 16.3 |

| 5 | Risk Register updated with new risk and actions | 15.1 |

| 6 | Actions are monitored at subsequent meetings | 15.3 |

If you skip step 2, step 5 becomes a retrospective excuse. If you skip step 5, step 2 becomes a forgotten conversation.

---

Real-World Example: A Success Story

I worked on a £12m NEC4 ECC Option C (target cost) road improvement scheme. Early in the works, the Contractor’s site engineer noticed that a utility diversion was taking longer than anticipated. They issued an early warning within hours.

The early warning meeting agreed to:

Accelerate the utility works (at cost).

Resequence the pavement construction to start from the opposite end.

Update the Risk Register with a new entry: “Utility delay risk—now managed via acceleration”.

The result? The project finished on programme, and the compensation event for acceleration was agreed without dispute. The risk register remained a trusted reference throughout.

---

Key Takeaways

**Treat the Risk Register as a live tool, not a filing exercise.** Update it after every early warning meeting and progress review.

**Notify early warnings immediately, even without full details.** Clause 16.1 requires “as soon as” awareness—delaying can lose you entitlement.

**Link early warnings to the Risk Register every time.** Each notification should generate a new or updated risk entry with an owner and mitigation action.

**Use the early warning meeting to solve problems, not assign blame.** The NEC4 ethos is collaboration—and these meetings are where it happens.

**Category:** Risk Management