What is a programme under NEC4?

The Accepted Programme is the programme identified in the Contract Data or the latest programme accepted by the Project Manager. Keep a clear register of submissions, responses and accepted versions. A file labelled “baseline” is not necessarily the Accepted Programme.

Use clause 31.2 and the Scope as the submission checklist. The programme needs the relevant dates, operations, interfaces, resources and information requirements, alongside float and time risk allowances. This is a summary, not a substitute for the complete clause.

Before submitting, reconcile the programme with site progress. Check that access, design, procurement and work by Others are visible where they affect delivery. Explain material changes in a short narrative, with references to supporting records.

The Project Manager has two weeks to respond under clause 31.3. Non-acceptance must be based on the stated grounds: impracticable plans, missing required information, unrealistic representation of the Contractor’s plans, or non-compliance with the Scope.

If no response is notified within the allowed period, the Contractor may notify that failure. Continued failure for a further week after that notice results in the programme being treated as accepted. The initial two-week silence alone is insufficient.

Terminal float is the gap between planned Completion and the Completion Date. Under NEC4 ECC, the time assessment under clause 63.5 protects that gap for the Contractor. It is incorrect to say that a compensation event must first use up terminal float before the Completion Date can move.

Time risk allowances address risks within the Contractor’s plan; activity float concerns flexibility within the programme logic. Keep these concepts separate when explaining a delay assessment.

Clause 32 governs programme revisions. Maintain the update cycle, record actual progress and show the changes required by the contract. Where clause 64 applies, the Project Manager may need to assess the programme for remaining work for a compensation event assessment.

• Retain the submitted programme, narrative and transmission evidence.
• Record the response date and reasons for any non-acceptance.
• Link progress entries to locations and activities so the planner can check them.
• Keep original records and later corrections distinguishable.

Gather can support the site-recording part of this process. Programme preparation, acceptance and contractual notifications still need the responsible people to act.

• NEC: Why an up-to-date accepted programme is essential
• NEC: Reasonable time risk allowances
• GMH Planning/CECA: Importance of the Accepted Programme (practical commentary; check the applicable contract and amendments).
• GMH webinar: getting the programme right (practical commentary; check the applicable edition and amendments).

Explore Gather’s NEC4 articles and webinars.