Behind programme on an NEC contract: what to tell the Project Manager
What to say, in what order, when your NEC works are slipping: early warning, revised programme, and keeping any compensation event claim intact.
On this page
Your site team has just told you the job is slipping and you are wondering whether to say so now or try to claw it back first. Under NEC the answer is to say so now, and to say it in the right form.
The short answer
Warn the Project Manager (the person the Client appoints to run the contract day to day) the moment Completion or a Key Date looks threatened. Then send a revised programme showing where you really are. Staying quiet while you try to recover does not protect you: it weakens any compensation event you may need later, and it leaves the Accepted Programme (the programme the Project Manager has accepted as your baseline) out of date as a measuring stick.
What to do, step by step
- Measure the slip. Put actual progress into the programme and read off the new planned Completion and the new position on each Key Date (a date in the Contract Data by which a stated piece of work must be done).
- Send the early warning. This is clause 15.1 in NEC4 (16.1 in NEC3). It is a duty, not a favour, and it starts when you become aware of the risk. Keep it factual.
- Work out why you are behind. The reason decides what you say next (see the table below).
- Notify any compensation event separately. The time limit for notifying an event is eight weeks from becoming aware of it under clause 61.3, so older items may already be tight. Under the NEC4 subcontract the period is seven weeks.
- Submit a revised programme. Clause 32.1 says it must show actual progress, the effect on the remaining work and how you intend to deal with delays. Clause 32.2 covers timing: when the Project Manager instructs it, whenever you choose, and at least at the interval in your Contract Data.
- Size your exposure. If Completion is at risk and Option X7 applies, delay damages are in play. If a Key Date is at risk, clause 25.3 is the one to read.
| Why you are behind | What to say | What it affects |
|---|---|---|
| Your own or your suppliers' performance | Warn, with a recovery plan. No claim | Float goes first, then delay damages |
| A listed event, such as late access | Notify it as a compensation event and quote | Completion Date moves only if planned Completion is pushed back |
| Both | Warn, notify the event on its own, show the two separately | Arguments over cause are likely |
| Unclear | Warn now, name no cause | Keeps your options open |
What to record
- When each cause first became known to anyone on your team.
- Any extra labour or plant you add at your own cost to recover, with timesheets and hire records.
- Every warning, notice and programme submission, with proof of delivery.
What not to do
- Do not stay silent until Completion is close.
- Do not leave the Accepted Programme untouched for months. A stale baseline makes later events harder to assess.
- Do not assume the Project Manager can order you to speed up. They can ask for a revised programme and can decline one that is not realistic (31.3), but a contract requirement to finish earlier needs the acceleration route in clause 36.
- Do not worry that a warning admits fault. It does not: it only puts the matter on the table.
When to get help
Bring in your commercial manager as soon as you have both your own delay and a possible compensation event on the same activities. A planner can rebuild the programme if its logic no longer matches the site. Take legal advice if delay damages or a Key Date charge look large.
Example
A drainage subcontractor's package has a Completion Date in week 40 and planned Completion in week 37. By week 20 the crew is three weeks behind through a late plant delivery, and then access to the northern run is withheld for two weeks. The planner issues the warning in week 20, notifies the access event separately, and submits a revised programme with the two causes shown as distinct bars. The three weeks of terminal float (the gap between planned Completion and the Completion Date) absorb the first slip. The access event is assessed on its own merits.
Related guides
- Programme shows we will finish late
- Terminal float in NEC
- Revised programme submission timeline
- Acceleration under NEC
This guide is general information, not legal advice. Check it against your contract.
