Why NEC programmes are not accepted
The four grounds a Project Manager can use to refuse a programme under clause 31.3, and the practical mistakes behind each one.
On this page
Under clause 31.3 the Project Manager either accepts a submitted programme or notifies the Contractor of the reasons for not accepting it. The reasons are limited. A Project Manager can only refuse for one of four grounds, so a rejection letter that does not fit one of them is open to challenge: withholding acceptance for a reason outside the contract can be a compensation event under 60.1(9), while a valid reason is not one (13.8). The Project Manager has two weeks to reply (three under the NEC4 ECS). Check the exact wording in your contract.
The four grounds
1. The Contractor's plans are not practicable. The logic or durations do not hold together in the real world. Typical causes: durations far shorter than the work needs, resources overloaded, work sequenced in an order that cannot be built, or conflicts with access and possessions.
2. It does not show the information the contract requires. This is the clause 31.2 content test. See our clause 31 checklist. Missing Key Dates, missing time risk allowances, no Client or third-party activities and no stated access dates are the most common.
3. It does not represent the Contractor's plans realistically. The programme looks acceptable on paper but is not what the site team intends to do. Warning signs: lots of hard constraints forcing dates, float that appears from nowhere, activities that finished before they started, or a critical path that does not run through the actual critical work.
4. It does not comply with the Scope (the Works Information in NEC3). For example, a required sequence, working-hours restriction, possession window or, under NEC4, the form the Scope requires for the programme has been ignored.
Mistakes that trigger a rejection
- Poor logic. Activities with no predecessor or successor, many lags and leads, and many relationships that are not finish-to-start make the programme hard to trust. These are DCMA schedule quality measures, covered in our P6 health check guide.
- Hard constraints that force the programme to show the answer the Contractor wants.
- Negative float left in the submission with no explanation. The programme is telling the Project Manager the Contractor will be late.
- Data not updated. Actuals missing, or forecast dates earlier than the data date.
- Changes not explained. Logic or durations changed since the last revision with no schedule of changes.
- Implemented compensation events not reflected in the revised programme.
How to reduce the risk
- Run a schedule quality check before every submission.
- Send a short programme narrative with each revision explaining what changed and why.
- Include a schedule of changes listing logic, duration and date changes.
- Do not submit with unexplained negative float.
- If you receive reasons for non-acceptance, respond to each one specifically and resubmit promptly.
Deemed acceptance
Under NEC4 ECC, if the Project Manager misses the two-week reply, the Contractor can notify that failure, and if there is still no answer one further week later the programme is treated as accepted (31.3). Under the NEC4 ECS the periods are three weeks and two further weeks. NEC3 has no such rule: silence there is only a compensation event under 60.1(6) and the programme stays unaccepted. Whether a programme missing required information can be treated as accepted is not settled, so send a complete one. Check your Contract Data and Z clauses, as periods can be amended, and diarise the Project Manager's reply period every time you submit.
While a programme stays unaccepted
If the latest programme is not accepted for one of the four reasons, the Project Manager can assess compensation events itself, using its own view of the remaining work (64.1, 64.2). Separately, if the Contract Data names no programme, a quarter of the Price for Work Done to Date is held back in each assessment until you submit a first programme that shows the required information (clause 50.5 in NEC4, 50.3 in NEC3). A later revision that is rejected does not trigger that holdback.
This guide is general information, not legal advice. Check it against your contract.
