BHD Commercial · Practical guidance
NEC4 Site User Guide — Operating NEC4 in Practice
A plain-English field guide to the weekly habits that connect site activity, notices, risk, programme, records and commercial control under NEC4.
1. What good NEC4 administration looks like
NEC4 works best when the project team deals with events as they arise, makes information visible and gives people enough time to act. The site team does not need to become a team of lawyers. It does need a reliable routine: communicate clearly, record the facts, raise risk early, preserve the programme and route commercial consequences to the right owner.
Every important matter should answer five questions: What happened? When did it happen? Who knows? What could it affect? What needs to happen next?
2. The weekly operating rhythm
| Routine | Purpose | Minimum output |
|---|---|---|
| Daily site record | Capture labour, plant, progress, access, conditions, instructions and disruption while facts are fresh. | Signed or controlled daily record with linked evidence. |
| Weekly risk review | Review early warnings and agree actions that reduce cost, delay or performance risk. | Updated early warning register, owners and dates. |
| Weekly commercial review | Review potential and notified compensation events, payment, forecast and records. | Updated CE register and clear next actions. |
| Programme review | Compare actual progress with the Accepted Programme and identify emerging effects. | Progress narrative, logic and record of assumptions. |
| Communication check | Confirm that instructions, notices, RFIs and decisions are issued through the approved route. | Clean communication log and filed attachments. |
3. Early warnings and risk reduction
Raise an early warning when a matter could increase the total of the Prices, delay Completion or a Key Date, or impair performance. The useful early warning is specific enough for the team to act on: describe the matter, the possible effect, the owner and the action that could reduce the risk.
- Open or update the early warning register as soon as the matter is identified.
- Notify through the contractual communications system and keep the reference.
- Bring the matter to the next risk reduction meeting, or arrange one sooner where urgency requires.
- Record the options considered, the agreed action and who owns it.
- Close the warning only when the reason for closure is clear and recorded.
4. Instructions and communications
An instruction, a request for information, a meeting action and a commercial notice are not interchangeable. Keep the original communication, identify the sender and recipient, record the relevant revision or drawing and note any action or possible effect on cost and time.
If a communication changes the work or reveals a possible compensation event, flag it to the commercial lead immediately. Do not rely on a conversation, marked-up drawing or meeting minute as the only record where the contract requires a formal communication.
5. Compensation events
When an event may change the Prices, Completion Date or a Key Date, open a record promptly and identify the contractual route. Record when the team became aware, when it was notified, the relevant event basis, the response and the next assessment deadline. Keep the quotation, programme impact, assumptions, mitigation and supporting records connected.
Before submitting or accepting an assessment, check that the cost story, programme story and site records agree. Make clear which information is actual, which is forecast, what dividing date or programme basis has been used and what assumptions remain open. Escalate any approaching deadline rather than leaving it in “under review”.
6. Programme and records
The programme is a live management tool as well as a contractual record. Record progress honestly, explain departures from plan, identify the cause and show the effect on remaining work. Retain the programme revision, progress evidence, logic changes, mitigation and assumptions used for any assessment.
Useful supporting records can include site diaries, photographs, delivery tickets, labour and plant returns, inspection records, RFIs, drawings, instructions, meeting minutes, correspondence and subcontractor records. File them by reference so another person can follow the story without reconstructing it from email.
7. Roles and escalation
| Role | Owns | Escalate when |
|---|---|---|
| Site manager | Facts, progress, access, daily records and immediate operational action. | An instruction, disruption or condition may affect time, cost or safety. |
| Commercial lead | Notices, registers, quotations, payment, forecast and entitlement record. | A deadline is approaching, evidence conflicts or the event basis is unclear. |
| Planner | Programme status, logic, critical path and time impact narrative. | Progress or an event may change Completion or a Key Date. |
| Project Manager / client team | Decisions, instructions, responses and risk-reduction participation. | Information is missing, options need a decision or risk cannot be reduced. |
8. A practical end-of-week check
- Are all new risks and potential events on a named register?
- Are every open action and deadline owned by a person?
- Do the latest site records, programme and commercial forecast tell the same story?
- Are formal notices issued and filed through the required communication route?
- Can the team explain what changed, what it may affect and what happens next?
Further reading
These links are starting points for wider reading. They do not replace the executed contract or advice on a live project.