Revised programme submission timeline cheat sheet

When the Contractor must submit programmes under clause 31 and 32, how long the Project Manager has to reply, and what to diarise.

Programmes and time3 min read

On this page
  1. The timeline
  2. Why the interval matters
  3. What a revised programme must show
  4. Planning your monthly cycle
  5. Diarise these dates every time
  6. Common slips

Programme timing is where NEC contracts catch people out. Fail to submit a first programme and payment is affected. Submit something that gets rejected and the review clock starts again. This cheat sheet summarises the standard ECC timings. Your Contract Data sets the actual periods, so use this as a prompt, not a substitute.

The timeline

Step Who When Clause
First programme Contractor Within the period stated in the Contract Data (or with the tender, where the contract says so) 31.1
Accept or give reasons for not accepting Project Manager Within two weeks of submission (three weeks for a Contractor replying to a Subcontractor under the NEC4 ECS) 31.3
Notify a failure to reply (NEC4 only) Contractor Any time after the two weeks; the programme is treated as accepted if there is still no reply one further week later (two further weeks under the NEC4 ECS) 31.3
Revised programme, when instructed Contractor Within the period for reply after the Project Manager's instruction 32.2
Revised programme, regular Contractor At intervals no longer than the interval in the Contract Data, from the starting date until Completion 32.2
Revised programme, with a quotation Contractor As part of a compensation event quotation where the remaining plans change 62.2
Revised programme, voluntary Contractor Whenever the Contractor chooses 32.2

Why the interval matters

The regular revision interval in the Contract Data is a minimum frequency, not a target. If it says every four weeks, a programme that is five weeks old is late. The duty starts at the starting date and lasts until Completion of the whole of the works, and it is not suspended while you wait for a reply to the last revision. The quarter holdback of the Price for Work Done to Date (clause 50.5 in NEC4, 50.3 in NEC3) applies only while no first programme showing the required information has been submitted and the Contract Data names none. If a required revision has not been sent, the Project Manager can assess a compensation event itself (64.1), using its own programme for the remaining work (64.2).

What a revised programme must show

Under clause 32.1 each revised programme shows:

  • The actual progress achieved on each operation and its effect on the timing of the remaining work
  • (NEC3 only) The effects of implemented compensation events. NEC4 32.1 no longer lists this, but a realistic revision should still show the effect of events on the remaining work
  • How the Contractor plans to deal with any delays and to correct notified Defects
  • Any other changes the Contractor proposes to make to the Accepted Programme

Planning your monthly cycle

A simple monthly rhythm avoids last-minute rushes.

  1. Week 1: Update actuals and remaining durations to the data date.
  2. Week 1: Reflect implemented compensation events.
  3. Week 2: Run schedule quality checks and fix what you find.
  4. Week 2: Write the narrative and schedule of changes.
  5. Week 2: Internal review, then submit.
  6. Weeks 3 to 4: Diarise the Project Manager's reply date and chase if nothing arrives.

Figure 1. A four-week revision cycle for a Contract Data interval of four weeks. Week 1 updates actuals and implemented compensation events from the data date, week 2 runs the quality checks, writes the narrative and submits, and weeks 3 and 4 are the Project Manager's two-week reply period, with the reply due on the next data date.
Figure 1. A four-week revision cycle for a Contract Data interval of four weeks. Week 1 updates actuals and implemented compensation events from the data date, week 2 runs the quality checks, writes the narrative and submits, and weeks 3 and 4 are the Project Manager's two-week reply period, with the reply due on the next data date. Open full size

Diarise these dates every time

  • The submission date
  • The end of the Project Manager's reply period
  • Under NEC4 ECC, the date from which you can notify a failure to reply, and the date one week after that notification, when the programme is treated as accepted if there is still no answer (NEC3 has no such rule). Check your Contract Data and Z clauses, as periods can be amended
  • The next regular revision date

Common slips

  • Treating the interval as optional
  • Submitting a revised programme that does not reflect implemented compensation events
  • Not recording when the programme was actually sent
  • Resubmitting after a rejection without answering each reason given

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

Was this useful?