The Project Manager has not accepted my programme: what now?

What to do when your NEC programme is not accepted: check the reply, fix the stated reasons, resubmit and protect your position on time.

Programmes and timeScenario4 min read

On this page
  1. The short answer
  2. What to do, step by step
  3. What to record
  4. What not to do
  5. When to get help
  6. Example
  7. Related guides

You submitted a programme under an NEC contract and the Project Manager has come back saying it is not accepted. This guide is written from the Contractor's side. A Subcontractor submitting to the Contractor should apply the same steps but check the subcontract, which may have different wording and periods.

The short answer

Read the Project Manager's reply and find the stated reasons. Under clause 31.3 the Project Manager must either accept the programme or give reasons for not accepting it, and this should happen within two weeks of your submission (three weeks for a Contractor replying to a Subcontractor under the NEC4 ECS). Only four reasons are allowed: the plans shown cannot practicably be carried out, required information is missing, the programme does not realistically represent your plans, or it does not comply with the Scope (Works Information in NEC3). Your job is to answer those reasons, in writing, and resubmit quickly. The reasons are your list of work.

What to do, step by step

  1. Confirm the reply is valid. Check it came through the communication system in your contract (clause 13), is in writing, and actually gives reasons. A bare "not accepted" is not the same as reasons. If the reason is not one of the four, withholding acceptance can be a compensation event under 60.1(9), and you should say so in writing. A reason that is one of the four is not a compensation event (13.8).
  2. Note the dates. Record the date you submitted, the date the reply arrived, and whether it was inside the two weeks. Do this on day one.
  3. List each reason separately. Turn each stated reason into a line in a table: reason, your view (agree, partly agree, disagree), and the change needed.
  4. Fix what you agree with. Common genuine issues are missing logic, no float or time risk allowance shown, missing Key Dates, or work that is not in the Scope. Use the clause 31 programme checklist to test the whole programme, not just the reasons given. A later planned Completion than the Completion Date is not, by itself, one of the four reasons, so do not hide an honest forecast.
  5. Challenge what you disagree with, politely and in writing. Quote the clause, say how the programme meets it, and offer a short meeting. Clause 10.2 (mutual trust and co-operation) supports a constructive approach.
  6. Resubmit with a short cover note. Say which reasons you have addressed and how. Keep the programme narrative short and specific. See writing a programme narrative.
  7. Keep working to your own latest plan. Keep updating the programme internally so that, when accepted, it reflects the true position.
  8. Check your time position. If an event has changed your plan, check whether you need to notify a compensation event. The clock on notification does not stop because the programme is stuck. While your latest programme stands unaccepted for one of the four reasons, the Project Manager can assess compensation events itself, using its own programme for the remaining work (64.1, 64.2), so resubmitting quickly protects you. The last Accepted Programme stays the baseline in the meantime. See missed the eight-week deadline.

What to record

  • Submission date, method and the exact file version sent.
  • The Project Manager's reply, with date received and who sent it.
  • Your response to each reason and the date you sent it.
  • Meeting notes and agreed actions.
  • Any instruction you received that relied on the unaccepted programme.

What not to do

  • Do not ignore the reply and resubmit the same programme unchanged.
  • Do not argue in general terms. Answer each reason in turn.
  • Do not stop updating the programme because the last one was refused.
  • Do not assume the Project Manager's silence on a later submission means acceptance. Under NEC4 ECC a programme is treated as accepted only if you notify the failure to reply and a further week passes with no answer. NEC3 has no such rule. Check your Z clauses too.
  • Do not use the reasons as an excuse to rewrite everything. Change what is needed.

When to get help

Get a planner involved if the reasons are about logic, float or the critical path and your team cannot resolve them quickly, or if you are on a second or third refusal. Get a commercial manager involved if the lack of an accepted programme is affecting assessment of compensation events. Take legal advice if you are considering formal dispute steps, for example under the dispute resolution Option in your contract. See also why NEC programmes are not accepted.

Example

A Contractor submits a revised programme on a Monday. Eleven days later the Project Manager replies that it is not accepted because the programme does not show a Key Date and the logic around a road closure looks unrealistic. The Contractor adds the Key Date, rewrites the logic with a short note explaining the closure sequence, and sends both with a cover note within three days. It records that the reply arrived inside the two weeks and keeps the exchange on file.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?