Who has to give an NEC early warning: contractor, Project Manager, others
Who owes an early warning under NEC, who keeps the register and calls meetings, and how knowledge on site reaches the person who sends notices.
On this page
Two parties owe the duty, and each owes it to the other: you, as Contractor, and the Project Manager (the person the Client appoints to run the contract day to day). If someone has told you early warnings are the contractor's job alone, they have misread clause 15.1 in NEC4 (16.1 in NEC3).
In plain English
Whoever hears about a problem first must say so. The Project Manager runs the paperwork, but neither of you has to wait to be asked.
Who does what
Both of you must warn of anything that could add to the Prices, make Completion later, put a Key Date at risk or hurt how the works perform in use. Either of you can instruct the other to attend a meeting after the first one, and either can bring extra people along if the other agrees. A contractor instructing a Project Manager is unusual in a contract, but it means an urgent problem does not have to wait for the diary.
Only the Project Manager keeps the early warning register (the shared list of risks), issues the first one in NEC4, calls the first meeting, and issues the revised register after each meeting along with any instruction to change the Scope.
Only you have the option to warn about something that could raise your own total cost without touching the four items above. It is a choice, not an obligation.
What to expect from the Project Manager
The Project Manager often knows things you cannot. Look for warnings about:
- a possible change of heart by the Client, the end user or the funder;
- slippage in things the Client provides: access, free-issue items, information;
- third-party approvals that the Client controls;
- neighbouring contractors whose delays could reach you.
A warning from that side can save the Client more than a compensation event would cost later.
What you are expected to raise
You see the work first: buying, ground and existing structures, subcontractor capacity, design development. The warning should come from whoever finds the problem, or reach the person who sends notices fast. Whatever any member of your team knows is treated as your organisation's knowledge. If a junior engineer knew weeks before your commercial manager, you cannot easily say you were unaware, and the measure when a compensation event is reduced is what an experienced contractor could have warned about.
Everyone else
| Role | Named in the clause? | What to do |
|---|---|---|
| Client | No; the Project Manager acts | Tell the Project Manager early |
| Supervisor | No | Pass on anything with a listed effect and attend if asked |
| Designers | No direct duty | Report through whoever appointed them |
| Subcontractors | Duty runs to the Contractor, not the Project Manager | See the subcontractor guide |
Forms differ. On short contracts there is no Project Manager, so warnings pass between you and the Employer (NEC3) or Client (NEC4). Professional service contracts use their own role titles.
Delegation
The Project Manager can hand actions to a colleague once you have been told. Ask who is authorised to send notices and the register.
When the Project Manager stays silent
The express price consequence in 61.5 and 63.7 targets a missing warning from the Contractor only. A silent Project Manager still falls short of 15.1 and of mutual trust and co-operation under 10.2. Whether anything further follows turns on the facts, so get advice on a specific case.
Related guides
- Running an early warning meeting
- The NEC Project Manager
- Client ignored my early warning
- Early warnings for subcontractors
This guide is general information, not legal advice. Check it against your contract.
