I gave an early warning and the Client or Project Manager ignored it
What to do when an NEC early warning gets no response: follow up, record the position, mitigate, and protect your rights on time and cost.
On this page
You gave an early warning, and nothing happened. No meeting, no reply, no action. This guide is written from the Contractor's side, where the Client (Employer in NEC3) or the Project Manager has not engaged. A Subcontractor can use the same approach against the Contractor, subject to the subcontract.
The short answer
Follow up in writing and keep the record. The early warning clause (15.1 in NEC4, 16.1 in NEC3) places a duty on both parties, and the Project Manager is the one who enters each warning in the early warning register. The meeting provision (15.2 in NEC4, 16.2 in NEC3) lets either side instruct the other to attend a meeting, so you can call one yourself. An ignored warning does not remove the risk, so keep mitigating while you press for a response. The record you build now may matter later for compensation events and for how the contract treats late warnings.
What to do, step by step
- Check the original warning. Was it in writing, through the communication system (clause 13), to the right person, with a clear description? If not, reissue it properly.
- Send a follow-up. Refer to the date of the original, restate the risk, say what has changed, and ask for a meeting or a decision by a stated date. Keep the tone co-operative, in line with clause 10.2.
- Instruct an early warning meeting. Either side may instruct the other to attend (15.2 in NEC4, 16.2 in NEC3), so you do not need the Project Manager's permission. Name the date, time and the matter to be discussed. Also check whether your warning has been entered in the early warning register.
- Escalate sensibly. If the Project Manager remains silent, copy a more senior contact on the Client side. Keep copies of everything.
- Mitigate. Take reasonable, proportionate steps to reduce the effect, such as resequencing or ordering early. Record the cost and time of doing so.
- Watch for a compensation event. If the risk materialises and fits the compensation event list (clause 60.1), notify within the eight weeks in clause 61.3 (seven weeks under the NEC4 subcontract). A previous early warning does not replace a notice. See missed the eight-week deadline.
- Reflect it in the programme. Show the risk and any mitigation in the next revision and narrative. See writing a programme narrative.
- Keep the register current. Show the warning as open, with every chase and response.
What to record
- The original early warning, with date, method and recipient.
- Every follow-up, call, meeting request and response.
- The state of the risk over time, with photographs or site records.
- Costs and time spent on mitigation.
- Any instructions that would have been avoided had the warning been acted upon.
- The point at which the risk became an event, if it did.
What not to do
- Do not assume that giving the warning has protected you. It records the risk, but it does not by itself give time or money.
- Do not stop mitigating because nobody responds.
- Do not send repeated angry messages. One clear follow-up with a date works better.
- Do not delay notifying a compensation event while waiting for a reply.
- Do not alter the programme to hide the effect of the risk.
When to get help
Ask a planner to show the likely effect on the critical path and Completion if the risk materialises. Ask a commercial manager to review whether a compensation event notification is due. Take legal advice if the risk has caused significant cost or delay, if there is a pattern of ignored warnings, or if you are considering the dispute resolution Option in your contract. The record matters because of clause 61.5: if the Project Manager states, when instructing quotations, that an experienced contractor could have given a warning and the Contractor did not, the event is assessed as if the warning had been given (63.7 in NEC4, 63.5 in NEC3). A dated warning that was ignored answers that point. Check your Z clauses, which can change these rules.
Example
A Contractor warns the Project Manager that unclear drawings for a retaining wall may delay the start of piling. No reply comes. A week later it sends a follow-up with a requested decision date and proposes a meeting. Still no answer. It resequences other work to protect the critical path and logs the cost. When the drawings arrive late, it notifies the compensation event in good time, attaching the earlier warning, the follow-up and the mitigation record.
Related guides
- I have noticed a problem: do I give an early warning?
- Running an early warning meeting
- Keeping records under NEC
This guide is general information, not legal advice. Check it against your contract.
