Scope: Practical commentary on NEC4 ECC. Check the edition, selected options, Contract Data and amendments used on your project.
Use the contract as the submission checklist
Identify the Accepted Programme and check the full clause 31.2 requirements alongside the Scope. Record operations, interfaces and required inputs in enough detail to show a realistic plan. Keep the programme’s data date, version and assumptions clear.
Before submission, reconcile actual progress with site records and explain important changes in the narrative. A polished chart does not compensate for missing logic or unsupported status information.
Track acceptance and non-acceptance
Under clause 31.3 the Project Manager responds within two weeks. The grounds for non-acceptance concern practicability, required information, realistic representation of the Contractor’s plans and compliance with the Scope.
If no response is notified within the allowed period, the Contractor may notify the failure. Continued failure for a further week after that notice results in the programme being treated as accepted. The initial missed deadline alone is insufficient.
Explain float without mixing concepts
Show and explain the provisions for float and time risk allowances. Terminal float, between planned Completion and the Completion Date, is protected for the Contractor in the NEC4 ECC time-assessment mechanism. It is distinct from float within the activity network.
Keep allowances credible and visible. Avoid shifting them merely to produce a preferred commercial answer; the programme still needs to represent the intended plan realistically.
Use the relevant assessment provisions
A compensation event assessment needs the programme relevant to the dividing date and the applicable assessment rules. Where the conditions in clause 64 apply, the Project Manager makes the relevant assessment, including assessment of the programme for remaining work.
Clause 63.1 concerns the cost assessment and dividing date; it is not a general authority for the Project Manager to invent programme assumptions whenever a submission is overdue.
Make updates a repeatable routine
- Confirm the required update interval and other submission triggers.
- Collect progress information from the people responsible for each work area.
- Retain the original evidence behind status changes.
- Explain delays, proposed responses and changes to remaining work.
- Record submission, response and reminder dates.
A planner, QS and delivery manager should be able to follow the same chronology. Gather supports the underlying site-recording process; it does not replace programme acceptance or the people responsible for contractual action.
Sources and further reading
- NEC: Accepted programmes
- NEC: Time risk allowances and terminal float
- GMH Planning/CECA: Importance of the Accepted Programme (practical commentary; check the applicable contract and amendments).
Related GMH guidance and discussion
- GMH guidance: revising the programme
- GMH blog: the programme baseline
- GMH webinar: getting the programme right
These are practical commentary and discussion. Check the NEC edition and project amendments; older posts may use earlier clause numbering.
.webp)
