Scope: Practical commentary on NEC4 ECC. Check the edition, selected options, Contract Data and amendments used on your project.
Recognise when a warning is required
Clause 15.1 sets the mandatory triggers for the Contractor and Project Manager. Check the selected options and amendments for additional requirements. The process also allows matters to be raised beyond the mandatory threats.
Give the required warning promptly. Do not wait for a complete financial assessment where the notification trigger has already been met.
Make the register useful
NEC4 uses the Early Warning Register and early warning meetings. Identify the matter, potential effect, proposed response, agreed action and action owner. Keep the status connected to current project evidence.
Use concise factual descriptions. Separate what has been observed from what might happen next. An early warning should help the recipient understand what needs attention.
Use meetings to decide and follow through
Bring the people who can explain the issue or act on the response. Consider proposals and the effect on the whole project. Record decisions, responsibilities and follow-up dates, then check whether the actions were completed.
A meeting record is evidence of the discussion. It does not automatically replace a separately required instruction, acceptance or compensation event notification.
Keep the processes separate
An early warning and a compensation event notification perform different functions. Review the clause 61 requirements independently. The ECC time bar depends on awareness of the event and the applicable notification responsibility, not simply the date someone opened an early warning entry.
Under clauses 61.5 and 63.7, a failure to give an early warning an experienced contractor could have given can affect assessment. Apply the contractual process and assess the effect of earlier warning; do not impose an invented fixed penalty.
Use records to support judgement
- Link the matter to location, activity and programme information.
- Retain the formal warning and delivery evidence.
- Record mitigation proposals and the reasons for decisions.
- Keep the register current after the meeting.
- Review any separate cost implications under the applicable main option.
Site records help the team identify and explain a risk. They do not guarantee that a warning has been served correctly or that a later compensation event will be accepted.
Sources and further reading
- NEC101: Early warnings
- NEC: Purposes of notifications
- GMH Planning/CECA: A positive approach to early warnings (practical commentary; check the applicable contract and amendments).
Related GMH guidance and discussion
These are practical commentary and discussion. Check the NEC edition and project amendments; older posts may use earlier clause numbering.
.webp)
