NEC Clause 31 programme checklist
A practical checklist of what clause 31.2 says your NEC programme must show, so it is not sent back at the first review.
Clause 31 of the NEC Engineering and Construction Contract (ECC) tells the Contractor what a programme must contain. Project Managers use it as their test, so a programme that misses an item is the easiest kind to reject. This checklist follows clause 31.2 in plain English. The list is the same in NEC3 and NEC4, except that NEC4 also says the programme must be in the form the Scope states (software, file type and so on). Terms differ too: Works Information in NEC3 becomes Scope in NEC4. Always read the clause in your own contract, the Scope and the Contract Data.
The checklist
Tick each item against your programme before you submit it.
Dates
- The starting date is shown.
- The access dates are shown: the dates the Client gives the Contractor access to each part of the Working Areas.
- Every Key Date is shown, with the date the Contractor plans to meet each Key Date's Condition.
- The Completion Date for the whole of the works is shown.
- Planned Completion is shown, so the Project Manager can see how it compares to the Completion Date.
Logic and time
- The order and timing of the operations the Contractor plans to carry out to Provide the Works is shown.
- Provisions for float are visible, so a reader can see what spare time exists and where.
- Provisions for time risk allowances are identified and set out, not buried inside activity durations.
Other parties
- The order and timing of the work of the Client and Others is shown.
- The dates by which the Contractor needs acceptances, information and access are shown.
Supporting information
- Each operation has a statement of how the work will be done, including the principal Equipment and other resources.
- Health and safety requirements and the procedures set out in the contract (for example review periods) are reflected.
- Any other information the Scope requires the programme to show is included, and under NEC4 the programme is in the form the Scope states.
How to make the items easy to find
A Project Manager reading the programme should not have to hunt. A few habits help.
- Name the activities clearly. Use "Key Date 1: Site establishment", not "KD1 stuff". Name Client and third-party activities so they are obvious, for example "Utility diversion (by others)".
- Show time risk allowance as its own activity, or a clearly labelled item, before the date it protects.
- Use milestones for access dates and Key Dates, and keep them in a clearly named section of the work breakdown structure.
- Show float honestly. Do not hide it with constraints or by padding durations.
- Keep the logic continuous from the data date to Planned Completion so the critical path can be traced. Clause 31.2 does not list the critical path by name, but a broken network is easy to fault as unrealistic.
Common slips
- The Completion Date is missing, so the programme cannot be compared to the contract.
- Key Dates appear in the Contract Data but not in the programme.
- Client and third-party activities are not shown, or are shown with no dates for when the Contractor needs them.
- Time risk allowance is not identified.
After you submit
The Project Manager has two weeks to accept the programme or give reasons for not accepting it (three weeks for a Contractor's reply to a Subcontractor's programme under the NEC4 ECS). Missing required information is one of the four reasons clause 31.3 allows. If your Contract Data names no programme, a quarter of the Price for Work Done to Date is held back in each assessment until you have submitted a first programme that shows the information the contract requires (clause 50.5 in NEC4, 50.3 in NEC3). Check your Contract Data and Z clauses, as periods can be amended. See our guide to why NEC programmes are not accepted and the revised programme timeline.
This guide is general information, not legal advice. Check it against your contract.
