NEC4 Programme Submission Letter (Clause 31)
Written from experience on CTRL, Crossrail and Network Rail
This NEC4 programme submission letter sends your programme to the Project Manager for acceptance, with a checklist of everything clause 31.2 requires it to show. It works for the first programme under clause 31 and revised programmes under clause 32.
See what you get →Completed except the facts only you know
£25 + VAT
£30 inc. VAT
- Fills in: The letter, from the event or matter you describe, with the contract clauses set out.
- Stays [TO CONFIRM]: Contract number, Project Manager, dates and amounts.
- A competent person must review before use.
- Company logo in header
- Delivered in minutes
- Word document (.docx)
Template
£9 + VAT
£10.80 inc. VAT
Blank letter — fill in yourself
- Word document (.docx)
- Guidance notes included
- Instant download
- Use on any project
Prices exclude VAT: UK customers pay 20% VAT; VAT is not charged for customers outside the UK.All documents are drafts. Placeholders marked [TO CONFIRM] must be completed with your details. Check it against your contract before it’s sent.
What it's for
The Accepted Programme is the baseline for assessing delay from compensation events. If there is no Accepted Programme, the Project Manager can use their own assessment of the programme instead of yours. A complete submission gives the Project Manager fewer reasons not to accept it.
When you need it
With the first programme, which is due within the period stated in the Contract Data (clause 31.1), and with every revised programme.
Who signs it
The contractor’s project manager or planner.
What's inside
- Programme reference and revision, and whether this is a first or revised programme
- A clause 31.2 checklist covering the starting date, access dates, Key Dates, Completion Date, planned Completion, the order and timing of work, work of the Client and Others, dates when things are needed from the Client, float, time risk allowances, health and safety requirements, procedures and resources
- Confirmation that it is consistent with the Contract Data and Scope
- The two-week acceptance period and how deemed acceptance works
- The four reasons the Project Manager can give for not accepting it
FAQ
- Is the programme accepted automatically after two weeks?
- No. If the Project Manager does not reply within two weeks, you can notify that failure. If it continues for a further one week, the programme is treated as accepted (clause 31.3).
- What reasons can the Project Manager give for not accepting it?
- That your plans are not practicable, it does not show the information the contract requires, it does not represent your plans realistically, or it does not comply with the Scope.
- Should I send the native file?
- The letter lists the native file and a PDF as attachments, which most Project Managers expect.
- What is [TO CONFIRM]?
- Details only you know: the contract number, the Project Manager’s name, dates and amounts. We never guess these. They appear as highlighted [TO CONFIRM] placeholders, and the letter opens with a list of every one, so you can complete them before it’s sent.
- Can I edit the document?
- Yes. Both options are Word documents you can edit freely.
- Do I still need to review it?
- Yes. A competent person must check every document against the actual site and works before it is used. ClarusDocs gives you a complete first draft, not a substitute for that check.
Related documents
- Completion and Take Over Request LetterAsk for Completion to be certified — and set up take over properly
- Defects Notification LetterNotify a Defect properly — either way round
- Subcontract Compensation Event Notification LetterSubcontractors: notify a CE to the Contractor before the time bar
- CE Notification LetterThe letter that tells the Project Manager about a compensation event — within 8 weeks
- Early Warning NoticeThe notice that flags a problem early, before it costs time or money
- Site Instruction LogLog every instruction now — so you can claim it later