The NEC mistakes that cost contractors money, and a weekly self-check
The most common procedural errors on NEC jobs, what each costs you, how to avoid it, and a five-question check you can run on Monday.
On this page
Most NEC problems are about procedure, not law: notifying late, letting the programme go stale, not chasing replies, quoting without working and keeping thin records. A simple routine fixes nearly all of them, and they cost more than any dispute over interpretation. The list below uses the NEC4 Engineering and Construction Contract (ECC), roughly in order of damage.
Your side of the table
| Mistake | What it costs | The fix |
|---|---|---|
| Notifying a compensation event later than eight weeks from becoming aware | You may lose the change to Prices and dates (61.3) | Site reports anything unusual the same day; diaries get checked weekly |
| Staying quiet about a risk | Any related event is assessed as though you had warned (61.5, 63.7) | Raise it at once and add detail afterwards |
| No accepted programme | A quarter of the Price for Work Done to Date can be held back where none was identified (50.5), and your delay evidence is weaker | Submit a complete programme on time against a checklist |
| Letting a late reply slide | Treated acceptance only works if you send the second notification | Put the date in the diary and send it |
| Quotations with no working | The Project Manager may assess instead (64.1) | Show a clear build-up |
| Patchy records for cost-based Options C, D and E | Costs ruled out as Disallowed Cost | Build the records system before work starts |
What to expect from the Project Manager and Client
Knowing their usual errors helps you protect yourself.
- Late or missing replies. That can be a compensation event (60.1(6)) or lead to treated acceptance of a quotation nobody reviewed. Share a list of reply dates and ask who covers leave.
- Instructing without notifying the event. The event stays open with no eight-week bar on you. Expect the notification to come with the instruction (61.1).
- Refusing a programme on grounds the contract does not list. That may itself be a compensation event (60.1(9)). Only the 31.3 reasons count.
- Assessing to a budget. Weak assessments can be overturned. Ask for visible working (64).
- Client instructing directly. Agree a single channel at kick-off.
- Late Client-provided items. These fall under 60.1(3), often with knock-on delay.
Mistakes both sides make
- Two separate registers. They drift apart and the argument becomes about the list. Agree a single numbering scheme and compare lists every month.
- Treating a warning as a claim. If people fear a warning means admitting fault, they stop raising them and the mechanism fails.
- Agreeing things only in meetings. A communication has to be recordable in writing (13.1), and minutes do not replace a notice.
- Leaving compensation events until the end. The system is designed around forecasting soon after the event, so a pile-up at Completion forces everyone to reconstruct history.
- Ignoring Z clauses. A heavily amended contract is not standard NEC.
- Using the wrong edition's language. NEC3 says Employer, Works Information and Risk Register. NEC4 says Client, Scope and Early Warning Register. A wrong clause number invites a technical objection.
- Treating acceptance as approval. Under 14.1, acceptance leaves your responsibility intact. A poor design does not become someone else's problem.
How small slips pile up
A footbridge job. A steel delivery from a Client-chosen source slips, and you do not warn. The Project Manager is on leave and never replies to your programme. In a meeting the team agrees a re-sequence by word of mouth. Four months later you notify a compensation event. The Project Manager says it is out of time, and with no Accepted Programme there is nothing to measure against. Neither side looks good.
Any one of these alone would have been survivable. A warning, a chaser or a written instruction would each have stopped the chain.
Monday morning self-check
- Which replies fall due in the next two weeks?
- Has our latest programme been accepted, and how long ago was it submitted?
- Which compensation events are past eight weeks and still not implemented?
- Do both sides hold the same register?
- When did we last raise an early warning, and if it was long ago, why?
Related guides
- Common compensation event mistakes
- Common early warning mistakes
- Common NEC payment mistakes
- A weekly NEC routine
This guide is general information, not legal advice. Check it against your contract.
