The Accepted Programme in NEC4: Why It's the Baseline for Everything

The Accepted Programme is one of the most important control documents under the NEC4 Engineering and Construction Contract (ECC). It establishes the Contractor’s plan for Providing the Works, records the timing of Client and Contractor obligations, and provides the baseline against which the effects of compensation events are assessed.

It is not simply a planning document. It is a contract document with direct consequences for entitlement, payment, delay assessment, forecasting and project governance.

This is the fifth instalment in the NEC4 series, following guidance on Early Warnings, Compensation Events, Payment and Defined Cost, and Disallowed Cost.

What is the Accepted Programme?

Under NEC4 ECC, the Accepted Programme is the programme identified in the Contract Data or the latest programme accepted by the Project Manager. The defined term is set out in clause 11.2(1), while clauses 31 and 32 establish the submission, acceptance and revision processes.

The distinction between an ordinary programme and an Accepted Programme matters. A Contractor may have several working programmes, recovery programmes or internal forecasts. However, the programme which carries contractual significance is the one identified in the Contract Data or accepted through the NEC4 process.

The Accepted Programme provides the common reference point for:

• The Contractor’s planned method and sequence of Providing the Works.
• The timing of access, information and other Client obligations.
• Progress monitoring and delay analysis.
• Compensation event assessments.
• Forecast Completion and Key Dates.
• Commercial reporting and entitlement management.

A programme can therefore be technically detailed yet commercially weak if it is not submitted, maintained and accepted in accordance with the contract.

What must the programme show?

Clause 31.2 requires the programme to show the Contractor’s plan for Providing the Works in a form that can be understood. The programme must include the information required by the contract, including:

• The Starting Date.
• The Completion Date and Key Dates.
• The float.
• The order and timing of operations.
• The planned delivery of Plant, Materials and Contractor’s Equipment.
• The dates when the Contractor requires access to and use of the Site.
• The dates when the Contractor requires access to anything the Client is to provide.
• Any other information stated in the Scope or Contract Data.

The programme should explain how the work will be delivered, not merely show a series of dates. Its logic, sequencing and planned resources should be sufficiently clear for the Project Manager and wider project team to understand the proposed method.

Where the Scope requires specific programme information, that requirement must be included. Where the Scope does not specify the information required, the Contract Data governs the relevant requirements and submission intervals.

A useful test is whether an independent reviewer could identify:

1. What the Contractor plans to do.
2. When each operation is planned.
3. What must be provided by the Client or Others.
4. Where float exists.
5. What activities drive Completion and Key Dates.
6. How current progress affects the remaining work.

How is a programme accepted?

The Contractor submits the programme to the Project Manager for acceptance. Under clause 31.3, the Project Manager must respond within two weeks by either accepting the programme or notifying the Contractor of the reasons for non-acceptance.

The reasons for rejection are limited. The Project Manager may reject the programme where:

• The Contractor’s plans are not practicable.
• The programme does not contain the information required by the contract.
• It is not a realistic programme.
• It does not comply with the Scope.

The Project Manager is not entitled to reject a programme simply because it does not reflect a preferred sequence or because the Project Manager would have planned the work differently. Any reasons for non-acceptance should be stated with sufficient detail for the Contractor to correct the identified issue.

If the Project Manager does not respond within the two-week period, the Contractor may give notice of that failure. If the Project Manager still does not respond within one further week, the programme is treated as accepted.

This deemed acceptance route is important, but it must be administered precisely. The Contractor should retain evidence of:

• The date the programme was submitted.
• The fact that it was submitted for acceptance.
• The contractual response deadline.
• The notice of failure to respond.
• The expiry of the further one-week period.

A programme should not be assumed to be accepted merely because no objection has been raised informally.

When must the programme be revised?

Clause 32 requires the Contractor to submit a revised programme:

• When instructed by the Project Manager.
• When the Contractor’s programme or plan for Providing the Works changes.
• At the intervals stated in the Contract Data, commonly every four weeks.

A revised programme should show actual progress achieved, the effect of progress on remaining work, how the Contractor plans to deal with delays and Defects, and any other proposed changes.

It should also reflect implemented compensation events and other changes affecting the plan. If the programme does not show what is actually happening on site, it becomes increasingly difficult to use it as a reliable baseline for assessment.

Programme timescales

Stage	Responsible party	Standard period	Commercial control
Submit programme or revised programme	Contractor	As required by Contract Data, instruction or change to plan	Mark the submission clearly as being for acceptance.
Accept or reject	Project Manager	Within 2 weeks	Any rejection must rely on a permitted reason.
Notice of failure	Contractor	After the two-week period expires	Give formal notice if no response has been received.
Deemed acceptance	Contractual process	After a further 1 week without response	The programme is treated as accepted.
Routine revision	Contractor	Commonly every 4 weeks	Keep progress, remaining work and changes current.

Why the Accepted Programme matters commercially

The Accepted Programme is the baseline against which compensation events are assessed.

Clause 63.5 compares the effect of a compensation event with the Accepted Programme current at the dividing date. For example, where a compensation event affects planned Completion, the assessment considers whether planned Completion is later as a result of the event than it was on the relevant Accepted Programme.

That comparison requires a credible baseline. The programme must show the planned sequence, float, access requirements, affected operations and the position of the work at the dividing date.

The Accepted Programme also identifies the obligations of both parties. It records when the Contractor requires access to the Site, information, Plant, Materials or other items the Client is to provide. It therefore supports the analysis of whether a delay arises from a compensation event, a Contractor risk, an interface issue or another cause.

It also underpins:

• Delay analysis.
• The time element of compensation event quotations.
• Forecast Completion and Key Date reporting.
• Assessment of mitigation and recovery.
• The connection between time-related cost and programme effect.
• Evidence supporting contractual entitlement.

Without a current Accepted Programme, the Project Manager may have to assess a compensation event using assumptions or an outdated baseline. That usually weakens the Contractor’s position because the planned effect of the event is harder to demonstrate. It also increases the risk that the parties will disagree about what work was critical, what float was available and whether the event actually delayed Completion.

The clause 50.3 cash-flow risk

Clause 50.3 provides a direct financial incentive to maintain a compliant Accepted Programme. Where the Contractor has not submitted a programme which the Project Manager has accepted and which contains the required information, the Project Manager may withhold 25% of the Price for Work Done to Date until the position is corrected.

This is not a technical administration point. On a high-value programme, withholding 25% of the Price for Work Done to Date can create a material cash-flow exposure, affect supply chain payments and distort the commercial forecast.

The practical control is straightforward: programme submissions should be treated as hard commercial deadlines, with ownership, review and escalation built into the monthly reporting cycle.

The programme cycle

The programme cycle should operate as a controlled process:

1. The Contractor submits a revised programme.
2. The Project Manager accepts or rejects it within two weeks.
3. If rejected, the Contractor amends and resubmits it.
4. If there is no response, the Contractor gives notice of the failure.
5. If there is still no response within one further week, the programme is treated as accepted.
6. The Accepted Programme becomes the assessment baseline.

This cycle should be visible in the project records and programme register. It should not depend on informal agreement at a progress meeting.

Practical controls for project teams

A reliable programme process requires more than producing a revised file each month.

Keep the programme realistic

The programme should reflect actual progress, current access, procurement status, available resources and known constraints. An optimistic programme may appear positive in the short term but will weaken forecast integrity when the planned dates cannot be substantiated.

Maintain defensible logic and float

Logic links should demonstrate how activities drive Completion and Key Dates. Float should be identifiable and consistently managed. Unexplained float movements or excessive constraints make later delay analysis more difficult.

Link time and cost controls

The Accepted Programme, commercial forecast, Early Warning Register, compensation event register and risk register should tell one consistent story. If a risk appears in the forecast but not in the programme, or a programme delay has no corresponding commercial review, governance is incomplete.

Review at every progress cycle

Do not wait for a Project Manager instruction before reviewing the programme. Each progress cycle should test:

• Actual progress against the Accepted Programme.
• Changes to remaining work.
• The effect of early warnings.
• Implemented and potential compensation events.
• Access and information requirements.
• Recovery or mitigation measures.
• Forecast Completion and Key Dates.

Conclusion

The Accepted Programme is the contractual baseline for how the works are planned, delivered and assessed. It gives the parties a shared reference for obligations, progress, compensation events, delay and forecast completion.

For the Contractor, maintaining a current Accepted Programme protects entitlement and reduces the risk of assessment against an outdated position. For the Project Manager, it provides the evidence needed to administer change and monitor delivery. For senior stakeholders, it connects programme status, risk exposure and commercial forecast into one controlled view.

The essential discipline is to submit a realistic programme, secure acceptance, revise it at the required intervals and ensure that cost and time remain aligned.

Sources and references

• NEC: Why an up-to-date Accepted Programme is essential for success
• NEC4 Engineering and Construction Contract
• NEC4 ECC clauses 31 and 32: programme submission, acceptance and revision.
• NEC4 ECC clause 50.3: payment consequences where the required programme has not been accepted.
• NEC4 ECC clause 63.5: assessment of compensation events against the Accepted Programme current at the dividing date.
• NEC guidance on Accepted Programmes and programme management.

Social-sharing summary

The Accepted Programme under NEC4 ECC is a contract document, not simply a planning artefact. This practical guide explains clause 31, programme content, the two-week acceptance period, deemed acceptance, clause 32 revisions, the 25% payment withholding risk and why the Accepted Programme is central to compensation event assessment and commercial entitlement.

---

About the Author

Nick Garvey is a chartered construction professional (MCIOB, FCaSA, FQSi) with more than 25 years of experience in commercial leadership and project controls across defence infrastructure, government estates, highways, facilities management and public-sector programmes. He leads cost, schedule, risk and performance reporting on major defence infrastructure programmes, chairs risk reviews at senior governance level, and writes about earned value management, quantitative risk analysis, NEC4 contracts and forecast integrity.

All views my own, shared in a personal capacity.