Early warnings under NEC: the cheapest insurance on the project

If the compensation event is how NEC pays for change, the early warning is how NEC tries to stop change from hurting in the first place. It is the contract's signature forward-looking tool — a cheap, fast, low-drama mechanism for getting a problem onto the table while there is still time to do something about it. On a South African project where margins are thin and programmes are tight, it is the closest thing to free insurance you will find.

The mechanism lives in clause 16 in NEC3 and was renumbered to clause 15 in NEC4. The numbering changed; the philosophy did not. Both editions impose a mutual duty to speak up early, both funnel the warning into a shared register, both bring the parties together to work the problem, and both carry a quiet but sharp sanction for the Contractor who stays silent. This article walks through all of it — the duty, the register, the meeting, the sanction — and is careful to flag exactly where NEC4 differs from NEC3, because on a live contract those differences matter.

The duty to warn — and it runs both ways

The first thing to understand is that the duty is mutual. This is not a contractor's obligation that the Client can sit back and police. Both the Contractor and the Project Manager must notify the other as soon as either becomes aware of any matter which could:

• increase the total of the Prices — make the job cost more;
• delay Completion — push out the date the works are finished;
• delay meeting a Key Date — push out one of the interim milestones the contract has fixed; or
• impair the performance of the works in use — affect how the finished asset performs once it is operating.

The trigger is awareness, and the timing word is as soon as. You do not wait until the matter is certain, costed or confirmed. The duty bites the moment a matter could have one of those effects. A late delivery the supplier has hinted at, a design query that has not come back, a sub-surface condition that looks unexpected, a third party who has not signed off in time — all of these are early-warning territory long before anyone knows whether they will actually cost money or time.

What NEC4 added

NEC4 kept all four triggers above and bolted on a fifth. Under NEC4, a matter must also be notified if it could increase the Contractor's total Defined Cost — that is, increase what the work actually costs the Contractor, even if it would not change the Prices.

That distinction is deliberate and, on target-cost and cost-reimbursable contracts, important. On an Option C target-cost job the Contractor carries a share of any overspend through the pain/gain mechanism. A matter might push up the Contractor's own cost without changing the Prices at all — and under NEC3 there was an argument that it therefore did not need to be warned. NEC4 closes that gap: if it hurts the Contractor's Defined Cost, it gets notified. This pulls the Client and Project Manager into helping manage costs that the Contractor partly bears, which is exactly the collaborative behaviour NEC is trying to engineer.

The register: where warnings live

A notified matter does not float around in emails and corridor conversations — it is captured in a single shared document. In NEC3 this is the Risk Register. In NEC4 it was renamed the Early Warning Register, which is the more honest name because the document is fundamentally a log of early-warning matters and the decisions taken about them.

The register records each matter that has been notified, together with a description of the risk and the actions decided for avoiding or reducing it. It is a living document: matters go on as they arise and come off as they are resolved. Keeping it current and visible to both parties is the whole point — it is the agenda for the meeting, the audit trail of who decided what, and the running picture of where the project's exposure sits. A neglected register is a contract running blind.

The meeting: co-operating to solve the problem

Notifying a warning is only the start. Either party may instruct the other to attend a meeting to work the risk — called a risk reduction meeting in NEC3 and renamed an early warning meeting in NEC4. Again, the label changed and the substance did not.

What happens at that meeting is the heart of NEC's collaborative DNA. Those who attend co-operate to:

1. make and consider proposals for how the effect of each registered risk can be avoided or reduced;
2. seek solutions that give best value to those who will be affected — not the solution that suits one party, but the one that is best overall;
3. decide on the actions to be taken and, crucially, who will carry each one out under the contract; and
4. decide which risks can now be removed from the register because they have been dealt with.

Note who can be in the room. Because the goal is best value to all who are affected, the right specialists, designers and subcontractors can be brought in — the meeting is a problem-solving forum, not a contractual stand-off. The mindset is the opposite of the adversarial posture that dominates traditional South African contracting, where parties often hoard information about looming problems hoping to convert them into a claim later.

The cheapest day to deal with a risk is the day you first see it. Every day you wait, the options narrow, the cost climbs, and the warning that could have saved the project quietly turns into the claim that fights over it.

The sanction: warn, or be paid as if you had

So what makes anyone actually do this? The duty to warn would be toothless without a consequence, and NEC provides a precise one — aimed squarely at the Contractor.

If the Contractor did not give an early warning of a matter which an experienced contractor could have given, then when that matter later becomes a compensation event, the event is assessed as if the Contractor had given the early warning. This is clause 63.5 in NEC3 and clause 63.7 in NEC4.

Read that carefully, because it is subtler than a penalty. The Contractor is not fined and the entitlement is not struck out. Instead, the assessor builds the compensation event on a hypothetical: it asks what the time and cost effect would have been if the warning had been given early enough for the parties to act on it at the meeting. Any extra cost or delay that flowed from the silence — the bit that timely co-operation could have avoided or reduced — is simply not the Client's to bear. The Contractor recovers less, sometimes substantially less.

The test is objective: not what this contractor knew, but what an experienced contractor in the same position could have spotted and flagged. You cannot escape it by pleading inexperience. Two further points keep the sanction fair and contained:

• It applies only where the Contractor could have given the warning. A matter that no experienced contractor could have foreseen does not attract the reduction.
• It only bites if the Project Manager invokes it through the proper procedure — under NEC4 (clause 63.7) by stating in the instruction to submit quotations that the Contractor failed to give an early warning an experienced contractor could have given, and under NEC3 (clause 63.5) by notifying that decision. If the Project Manager does not raise it at that point, the event is assessed in the ordinary way.

The practical lesson for South African contractors is blunt: silence is expensive. Sitting on a problem in the hope of a richer claim later is precisely the behaviour clause 63.5/63.7 is designed to defeat. Warn early, get it in the register, and you protect both the project and your own assessment.

NEC3 versus NEC4 — the differences that matter

If your organisation runs both editions, as many provincial departments, municipalities and state-owned entities do during the transition, keep these distinctions straight:

• Clause number. The early warning mechanism is clause 16 in NEC3 and clause 15 in NEC4.
• Extra trigger. NEC4 added a fifth trigger: a matter that could increase the Contractor's total Defined Cost, even if it would not change the Prices.
• The register. The Risk Register (NEC3) was renamed the Early Warning Register (NEC4).
• The meeting. The risk reduction meeting (NEC3) was renamed the early warning meeting (NEC4).
• The sanction clause. The "assessed as if warned" rule is clause 63.5 in NEC3 and clause 63.7 in NEC4 — same principle, different number.

Getting the terminology right is not pedantry. A notification that cites the wrong clause or names the wrong document invites argument, and argument is exactly what the early warning exists to prevent.

Bringing it together

The early warning is the least glamorous clause in the contract and arguably the most valuable. It costs almost nothing to give, it pulls problems forward while solutions are still cheap and plentiful, and it carries a sanction sharp enough to make silence the worse choice. Used properly, it keeps the register current, the meetings focused on best value, and the compensation events smaller than they would otherwise have been. Used poorly — or ignored — it becomes the reason a Contractor recovers less than it expected. Warn early, warn often, and keep the two processes clear in your head: the early warning manages the risk, the compensation event handles the time and money, and they are not the same thing.