Early warning mistakes that cost NEC contractors money
The most common errors in giving, writing and following up NEC early warnings, from silence to over-warning, with a simple fix for each.
On this page
Teams get early warnings wrong in two opposite ways. Some say too little, usually from worry about how it looks. Others warn about everything to protect themselves. Both leave the genuine risks unmanaged until it is too late. Clause numbers below are NEC4 Engineering and Construction Contract (ECC).
In plain English
Warn early, warn specifically, and treat the warning as the start of a conversation, not a claim and not a confession.
Mistakes in deciding whether to warn
- Waiting until you know the cost and delay. By then the cheap options have gone and the 61.5 risk (a reduced compensation event because you should have warned) is building. Warn on "could" and write "not yet known" where you cannot size it.
- Fearing it admits fault. A warning says nothing about blame. Silence about your own problem usually costs more.
- Staying quiet for the sake of the relationship. The later surprise does more harm. Ring them, and put the notice in writing that day.
- Knowledge stuck on site. If foremen and engineers have no easy way to pass concerns on, the people who send notices hear too late.
- The Project Manager never warning. The Project Manager (the person the Client appoints to run the contract day to day) holds information you do not. Ask each week what they know that you do not.
Mistakes from warning too much
Long lists of warnings go unread, meetings overrun and the items needing a decision get lost.
- A blanket letter listing every possible hazard is not a warning about anything.
- Using warnings to stack up a claim file. It shows, and the meeting becomes a negotiation.
- Warning about trivia. If a matter cannot affect the Prices, dates or performance, a chat is enough.
- Several matters in one notice. Split them so each can be closed on its own.
Mistakes about what a warning is
- Assuming a warning doubles as an event notice. It does not, and this error is the expensive one: the 61.3 period for notifying an event keeps running. Compare each open warning with the list of compensation events and send a separate notice where one fits.
- Rejecting a warning. The contract offers no such reply. The matter is logged and discussed. Answering "rejected, no entitlement" treats a warning like a claim, and the next one may never come.
- Reading a register entry as agreement to pay. It shows the matter is being managed, nothing more.
- Planning around a reply. NEC sets no reply period for a warning. If it is urgent, instruct a meeting.
Paperwork slips
- Burying it in a progress report or minutes. Notifications go as separate communications (13.7).
- Quoting the wrong clause. Clause 16 covers early warning in NEC3 but, in NEC4, deals with Contractor's proposals. Update your templates.
- A late register. Under NEC4 the revised register is due a week after each meeting (15.4); once it slips, actions lose their owners.
- Vague actions. "Keep an eye on it" is not an action. Give it a person, a task and a date.
- Closing items too soon. An entry comes off only when a meeting decides, and you should record when and why.
Mistakes in meetings
- Missing the first one. NEC4 puts it inside two weeks of the starting date (15.2), but mobilisation tends to swallow it. See the kick-off meeting guide.
- Agreeing a Scope change in the minutes. A change needs the Project Manager's instruction (15.4). Working on a minute puts payment at risk.
- Arguing who pays. Ask what the best way to deal with it is; the other clauses settle the money.
- Sending people who cannot commit. Decisions then wait another week.
A monthly check
Compare your own internal risk list with the shared register. Any item on yours with a possible effect on cost, dates or performance that is missing from the register is a warning you owe, or a gap you will have to explain.
Related guides
- What should be an early warning
- Early warning register template
- Early warning admits liability?
- Running an early warning meeting
This guide is general information, not legal advice. Check it against your contract.
