How to use it
- Enter the programme reference and the date it was received: the Project Manager has two weeks to respond (clause 31.3).
- Work through each line and record whether the programme shows it, with a short comment.
- Anything marked 'No' becomes a reason for not accepting. Group them under the four reasons in clause 31.3.
- Keep the completed checklist with the programme submission as your record of the review.
Clause 31.2: what each programme must show
| Clause | Requirement | What to look for |
|---|---|---|
| 31.2 | The starting date, access dates, Key Dates and Completion Date | Dates match the Contract Data; any later date is explained. |
| 31.2 | Planned Completion | A clear completion milestone; if later than the Completion Date, the reason is stated. |
| 31.2 | The order and timing of the operations the Contractor plans to do | Logic-linked activities; few open ends; no loops; sensible lags. |
| 31.2 | The order and timing of the work of the Client and Others | Client works, utilities, statutory bodies and other contractors are shown as agreed or as in the Scope. |
| 31.2 | The dates when the Contractor plans to meet each Condition for the Key Dates | Each Key Date condition has its own milestone. |
| 31.2 | Provisions for float and time risk allowances | Float is visible; time risk allowances are identified, not hidden in durations. |
| 31.2 | Provisions for health and safety requirements and contract procedures | Durations allow for safety requirements and for the response periods in the contract. |
| 31.2 | Dates when the Contractor needs access, acceptances, Plant and Materials and other things from the Client, and information from Others | Information-required and access-required dates are shown and are realistic. |
| 31.2 | For each operation, how the Contractor plans to do the work, with principal Equipment and resources | A method statement or narrative is included with the submission. |
| 31.2 | Other information which the Scope requires | Check the Scope for format, level of detail and any specific requirements. |
Clause 32.1: what each revised programme must also show
| Clause | Requirement | What to look for |
|---|---|---|
| 32.1 | Actual progress achieved on each operation and its effect on the remaining work | A data date; progress recorded; no incomplete work left in the past. |
| 32.1 | The effects of implemented compensation events | Each implemented event is reflected and traceable. |
| 32.1 | How the Contractor plans to deal with any delays and to correct notified Defects | Slippage since the last accepted programme is explained, with recovery measures. |
| 32.1 | Any other changes the Contractor proposes to make to the Accepted Programme | Changes in sequence, method or durations are identified. |
Clauses 32.2 and 31.3: timing and response
| Clause | Requirement | What to look for |
|---|---|---|
| 32.2 | Revised programme submitted within the interval stated in the Contract Data | Compare the data dates of successive programmes. |
| 31.3 | Response within two weeks of submission | Acceptance, or the reasons for not accepting. |
| 31.3 | Reasons limited to those in the contract | Not practicable; does not show the required information; does not represent the plans realistically; does not comply with the Scope. |
NEC4 Engineering and Construction Contract (June 2017, with amendments). Clause references are to the unamended edition named above. Contracts are often amended: check every reference against your own contract. This template is a starting point for your review, not legal advice.