NEC programme submission covering note and checklist you can copy

A plain covering note and checklist for submitting a first or revised NEC4 programme so the Project Manager finds it easy to accept.

Tendering and starting a contract3 min read

On this page
  1. In plain English
  2. Sample covering note
  3. Checklist to attach
  4. Example "what changed" section
  5. Heading off a refusal
  6. Related guides

A programme that arrives with a clear covering note gets answered faster and challenged less. The Project Manager (the person the Client appoints to run the contract) has a short time to reply and a short list of reasons for refusing, so your note should show at a glance what changed, why, and what you need from them.

This works for a first programme under clause 31.1 and a revised programme under 32.2 of the NEC4 Engineering and Construction Contract (ECC). The wording below is a sample of ours, not NEC text.

In plain English

Send the programme with a one-page note saying what moved and why, and a checklist showing where each required item can be found. Make it hard for the Project Manager to say anything is missing.

Sample covering note

Copy this layout and fill in the brackets.

  • Submission: programme for acceptance under clause [31.1 or 32.2], contract [name and number].
  • Revision: [number], following [the previous Accepted Programme].
  • Data date: [the date progress is recorded up to].
  • Reply due: [date], by our reading of clause 31.3.
  • Files: [native programme file and PDF, in the format the Scope asks for].
  • Dates: planned Completion [date, and change since last time]; Completion Date [date]; terminal float [period and change]; each Key Date forecast [dates].
  • What changed: [implemented compensation events, delays, method or sequence changes].
  • What we need from you: [Client or Others items required in the coming period, with dates].
  • Reservation: this submission is not a notification of any compensation event. Any event arising from it will be notified separately.

Checklist to attach

Tick against the full lists in clauses 31.2 and, for a revision, 32.1 of your own contract. This is the short form.

  1. Planned Completion.
  2. Completion Date, Key Dates, starting date and access dates.
  3. Order and timing of your work and the work of others.
  4. When each Key Date's Condition will be met.
  5. Float and time risk allowances.
  6. Health and safety requirements.
  7. When you need access, acceptances, items to be provided, and information.
  8. How each operation will be done.
  9. Anything else the Scope asks to be shown.
  10. For a revision: actual progress and its effect on the work still to do.
  11. For a revision: how you plan to deal with delays and notified Defects.
  12. For a revision: any other changes you want to make.

Add a column saying where in the programme each item appears. Under NEC3, a revision also had to show the effect of compensation events; keep doing so under NEC4, as good practice.

Example "what changed" section

A water main job, Revision 6, invented figures.

  • Two extra valve chambers instructed under CE-014 are now included. Planned Completion and the Completion Date each move 5 days.
  • Section 3 is two weeks behind because our own pipe delivery slipped. A second gang from week 22 recovers 8 days.
  • Sections 4 and 5 swap order to suit the road closure we were granted. No effect on planned Completion.
  • Time risk allowance on testing drops from 5 to 3 days. Terminal float rises from 7 to 9 days.
  • Client-supplied valves are now needed by 14 May. Please confirm this suits your supplier.

Writing that takes minutes and can save a week of questions.

Heading off a refusal

Under clause 31.3 the Project Manager can refuse a programme for four reasons: the plans are not practicable, required information is missing, it does not realistically represent your plans, or it breaks the Scope. Write your note to answer each.

  • Send on time, even if imperfect. A real revision beats a perfect one a month late.
  • Do not hide entitlement in the programme. Showing an event's effect is not notifying it.
  • Chase the reply. Under NEC4, if two weeks pass without an answer you can notify the failure, and a further week of silence means the programme is treated as accepted. NEC3 has no such rule, although a late reply that causes harm can be an event under 60.1(6).
  • Keep logic live. Unlinked bars are hard to accept and useless for assessing delay.

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

Was this useful?