NEC4 Clause 31: What a Compliant Programme Contains and Why Acceptance Is Worth Fighting For

Why the Programme Is a Commercial Document

Under most traditional contracts the programme is a management tool with fuzzy contractual status. NEC turned that on its head: the Accepted Programme is the baseline against which compensation events are assessed. When a CE lands, its time effect is measured by its impact on planned Completion as shown on the Accepted Programme, and its cost effect flows from the change to the forecast. No current Accepted Programme means every CE assessment starts with an argument about what the baseline even was — an argument the Project Manager is empowered to settle by making their own assessment. Contractors who treat clause 31 as planning-department admin are handing away the instrument that protects their entitlement; clients who let programmes drift unaccepted lose their honest picture of the job. Both sides need this clause to work.

What Clause 31.2 Actually Requires

A programme submitted for acceptance is far more than a bar chart. Clause 31.2 requires it to show, among other things: the starting date, access dates, Key Dates and Completion Date; planned Completion; the order and timing of the operations the Contractor plans to carry out; the order and timing of the work of the Client and Others as last agreed or as stated in the Scope; provisions for float, time risk allowances, health and safety requirements and the procedures set out in the contract; the dates when the Contractor plans to complete work needed to allow the Client and Others to do their work; and for each operation, a statement of how the Contractor plans to do it with the principal Equipment and other resources. In short: logic, resources, method and interfaces — a programme someone could actually interrogate.

The distinction the clause forces into the open is between time risk allowance — the Contractor's owned contingency inside activity durations or as explicit buffers, there because risk is real and priced — and float. Terminal float, the gap between planned Completion and the Completion Date, belongs to the Contractor: a CE that pushes planned Completion pushes the Completion Date with it, preserving that gap. Free float between activities is, in effect, shared — a CE that only eats float without moving planned Completion moves nothing. Showing these honestly is not generosity; it is what makes your CE assessments stick later.

The Acceptance Process

The Contractor submits a first programme either with the tender (if the Contract Data asks for it) or within the period stated in the Contract Data, and revised programmes at the intervals stated and when instructed or when the Contractor chooses. The Project Manager responds within two weeks, and may only withhold acceptance for the reasons in clause 31.3: the plans it shows are not practicable; it does not show the information the contract requires; it does not represent the Contractor's plans realistically; or it does not comply with the Scope. Not accepting for any other reason is itself a compensation event. NEC4 added a lever NEC3 lacked: if the Project Manager simply fails to respond, the Contractor can notify, and continued silence can result in the programme being treated as accepted. Use it — politely, in writing, every time.

Silence is the real enemy on live jobs. A programme submitted, unanswered and quietly superseded by the next revision builds a project with no accepted baseline at all. Chase every submission to a conclusion: accepted, or rejected for a 31.3 reason you then fix and resubmit. The correspondence trail is itself protection.

Revisions: The Discipline That Pays

Clause 32 requires revised programmes to show actual progress and its effect on remaining work, the effects of implemented compensation events, and how the Contractor plans to deal with delays and correct notified Defects. This is the drumbeat that keeps the baseline honest — and it is where records earn their keep. A revised programme showing actual progress is only as credible as the site records behind it: allocation sheets, diaries, photos with dates, delivery records. When the CE quotation says the pump chamber slipped three weeks because access was given late, the Accepted Programme shows the entitlement and the site records prove the facts. Either one without the other is half a case.

The Practical Standard

Run clause 31 like this and it becomes an asset rather than a chore. Submit on time, every interval, whether or not anything dramatic changed. Include everything 31.2 lists — the resource statements and interface dates are what get programmes rejected, so do them properly once and maintain them. Show time risk allowance and float explicitly and defend the distinction. Chase acceptance in writing and use the deemed-acceptance mechanism when responses do not come. Impact every CE on the current Accepted Programme, not on a private working file. And keep the site records that make the programme's story provable. None of this is clever; all of it is discipline — and on an NEC job, programme discipline is money.