NEC4 Programme Management: Why the Accepted Programme Is Your Most Important Document
TL;DR
---
Why the Accepted Programme Is Your Most Important Document
If you work with NEC4 ECC daily, you know the contract places the Programme at the heart of project management. But too many engineers, quantity surveyors, and contract managers treat it as an administrative tick-box – something to update monthly because the contract says so. That is a costly mistake.
The Accepted Programme is not just a schedule. It is the legal baseline for time, the trigger for payment, the mechanism for compensation events, and the evidence for delay damages. Without it, you are flying blind. With it, you can control the project.
Let’s be specific about why this document matters more than any other on your project.
---
The Accepted Programme Defines ‘Time’ – And Time Is Money
Under NEC4 ECC, the Accepted Programme is the only document that defines the contractual completion date and the key dates. Clause 31.2 requires the Contractor to submit a programme for acceptance, and Clause 31.3 sets out what it must show: start dates, finish dates, float, logic links, and the method of assessment.
**Real scenario:** You are a Project Manager on a highway widening scheme. The Contractor’s programme shows completion in Week 52, but they have inserted two weeks of total float at the end. A utility diversion in Week 30 causes a four-week delay. Without the Accepted Programme showing that float, the Contractor can argue the delay is critical and claim a compensation event. But if the programme clearly shows the float belongs to the Contractor, they can use it to absorb the delay – and you have no entitlement to reduce the completion date.
**Actionable point:** Always check that the Accepted Programme clearly identifies who owns the float. NEC4 does not automatically assign float to the Employer. If the programme is silent, the Contractor can argue they own it. State it explicitly in the Scope or in the programme narrative.
---
It Controls Payment – Especially Under Options C, D, and E
For cost-reimbursable options (C, D, E), the Accepted Programme is directly linked to the Defined Cost and the Fee. Clause 63.1 says that a compensation event is assessed based on the effect on the Accepted Programme. If the programme is not up to date, you cannot properly assess the time and cost impact.
**Real scenario:** Under Option C, the Contractor submits a compensation event for a design change. They claim an extra 10 weeks of site overheads. You check the Accepted Programme – it shows the change was on the critical path, but the programme is three months old and does not reflect recent acceleration. You have no basis to challenge the time impact. The Contractor’s claim stands, and you pay for overheads you could have avoided.
**Actionable point:** Reject any programme that is not current. Clause 31.3 says the programme must show “the order and timing of the work”. If it is out of date, it fails that requirement. Use Clause 31.3 to demand a revised programme before accepting any compensation event assessment.
---
It Is Your Only Evidence for Delay Damages
Clause X7 (delay damages) is only enforceable if you have a valid Accepted Programme. The Employer can only deduct delay damages if the Contractor is late against the completion date shown in the Accepted Programme. If the programme is not accepted, or if it has been allowed to lapse, the completion date becomes ambiguous.
**Real scenario:** A building project finishes six weeks late. The Employer wants to deduct delay damages at £10,000 per week. The Contractor argues the Accepted Programme was never formally accepted – the Project Manager sent comments but never issued acceptance under Clause 31.3. Without a formally accepted programme, the Employer has no contractual completion date to measure against. The delay damages clause becomes unenforceable.
**Actionable point:** Never leave a programme in “commented” status. If the Contractor submits a programme, you must either accept it or give reasons for non-acceptance within the period for reply (Clause 13.4). If you do neither, the programme is deemed accepted after that period. Keep a clean audit trail.
---
It Drives Compensation Event Assessment
Compensation events are assessed using the Accepted Programme as the baseline. Clause 63.1 states: “The assessment of the effect of a compensation event is based on the Accepted Programme.” If the programme is missing or out of date, the assessment becomes subjective – and that is where disputes start.
**Real scenario:** A ground condition change triggers a compensation event. The Contractor’s programme shows the affected activity as critical. But you know they have been working inefficiently and could have resequenced. Without a detailed, logic-linked programme, you cannot prove the delay was avoidable. The Contractor gets a time extension and additional cost.
**Actionable point:** Require the Contractor’s programme to show all logic links and dependencies. Use Clause 31.2 to insist on a “method statement” that explains how the programme will be achieved. That statement becomes part of the Accepted Programme and binds the Contractor to their own plan.
---
It Is Your Risk Management Tool
The Accepted Programme is not static. Clause 32.1 requires the Contractor to issue a revised programme every period – typically monthly – showing progress, changes, and forecasts. This is your early warning system. If you review the revised programme properly, you can spot delays, resource shortages, and potential compensation events before they happen.
**Real scenario:** On a water treatment plant project, the monthly revised programme showed that a key subcontractor was falling behind on a non-critical activity. The Project Manager flagged it at the progress meeting, and the Contractor accelerated the work before it became critical. The project finished on time, and no compensation event was needed.
**Actionable point:** Do not just file the revised programme. Use it to update your risk register and to trigger early warnings under Clause 15. If the programme shows a trend towards delay, issue an early warning immediately.
---
Practical Tips for Keeping Your Accepted Programme Robust
1. **Accept only complete programmes.** Reject any submission that lacks logic links, float ownership, or a method statement. Use Clause 31.3 to list your reasons.
2. **Keep a formal acceptance record.** A signed acceptance letter or a note in the project management software. Do not rely on emails.
3. **Review every revised programme against the baseline.** Look for changes to completion dates, key dates, and critical path.
4. **Link programme to compensation events.** When assessing a CE, always start with the Accepted Programme. If the programme is out of date, ask the Contractor to update it first.
5. **Train your team.** Engineers and QSs need to understand that the programme is a contract document, not a planning tool. Treat it with the same rigour as the contract data.
---