Programme is the contract: why your NEC Accepted Programme decides every claim

Most contractors I work with treat the Accepted Programme as a planning department artefact. The planners draw it up. The PM sees it. Site uses it as a wall chart. Nobody on the commercial team reads it carefully, and the resubmission discipline drifts about a fortnight after contract signature.

On any NEC project, this is the single most expensive blind spot you can have. The Accepted Programme is not a project-management document. It is a contract document, and the absence of a current one will quietly destroy your ability to recover on every compensation event that follows, however strong the underlying merit. It will also expose a quarter of your monthly PWDD to retention under clause 50.3. Two of the worst commercial outcomes on any NEC project trace back to the same root cause.

What an Accepted Programme actually is

Clause 31 requires the Contractor to submit a programme to the Project Manager within the period stated in the Contract Data. The contents are prescribed at clause 31.2: starting and completion dates, planned Completion, order and timing of operations, dates for access and information, float, time risk allowances, health and safety requirements, the Contractor’s plan for the works, and so on (the list runs from (a) to about (l) depending on edition). The Project Manager then has the period stated in the Contract Data (typically two weeks) to accept it or reject it with reasons.

Once accepted, that submission becomes the Accepted Programme. It is referenced throughout the contract: as the basis for time-impact assessment on compensation events (clause 63 in NEC3, clause 63.5 in NEC4), as the trigger for early warnings, as the document the Project Manager certifies against, and as the operating reality of how the works are planned to be carried out.

Clause 32 then requires the Contractor to revise the programme: at intervals stated in the Contract Data (typically four weeks), when the Project Manager instructs a revision, and when there has been a change to the planned Completion, Key Dates, or actual progress. Every revision must be resubmitted for acceptance. A programme that was accepted in March and never revisited by July is not an Accepted Programme. It is a historical document.

Why no current programme means no credible CE assessment

This is the part that catches contractors out commercially, every single project.

When a compensation event occurs, clause 63 requires the Contractor’s quotation to include an assessment of the effect on planned Completion and on any Key Dates. That assessment is by definition a comparison: where the planned activities sat before the event, and where they sit after. That comparison is built on the Accepted Programme. If your Accepted Programme is six weeks out of date when the CE occurs, your time impact analysis is sitting on a foundation the Project Manager can pull apart in a paragraph.

Two outcomes usually follow. Either the Project Manager rejects your quotation on the basis that the programme is not current and the impact cannot be properly assessed, and instructs you to resubmit. Or the Project Manager invokes clause 64 and makes their own assessment, which (as covered in the five NEC compensation event traps) tends not to be generous.

Either way, you end up arguing about the programme rather than the entitlement. And the longer you spend arguing about the programme, the more your CE pipeline backs up, the more risk you carry on cash flow, and the more your commercial team loses control of the cumulative position.

The clause 50.3 retention threat

Clause 50.3 in NEC3 (and clause 50.5 in NEC4) gives the Project Manager a sharp tool. If the Contractor has not submitted a first programme for acceptance, or has not submitted a revised programme as required by clause 32, the Project Manager may retain one quarter of the Price for Work Done to Date from the next certified payment.

On any project of meaningful scale, one quarter of monthly PWDD is a serious number. On a £30m project running at £2m a month, that is £500k a month sitting in the Employer’s account rather than yours, often when you need it most because the very event that is straining the programme is also straining the cost base.

In practice the retention is rarely deployed punitively from day one. It is deployed as leverage. A Project Manager with the 50.3 (or 50.5) lever sits across a negotiating table differently than one without it. Settlements get shaped accordingly. The cleanest defence is to never give them the lever in the first place.

Where programmes fail acceptance in practice

I see the same five reasons for rejection across most projects.

1. Missing 31.2 contents. The programme does not show one or more of the prescribed contents. Float is collapsed into total programme duration with no separate line. Time risk allowances are missing entirely. Resources are not shown against operations. Access dates are not flagged.

2. Bar chart instead of properly logic-linked CPM. A Gantt that looks like a programme is not a programme. NEC requires the critical path to be demonstrable, and a programme without proper logic links cannot show one. Project Managers reject these on sight, and they are right to.

3. Float allocation that the Project Manager will not accept. The Contractor places float at the end of the programme, ahead of planned Completion, where it benefits the Contractor in any subsequent CE assessment. Project Managers increasingly reject this and instruct that float is shown where it actually exists in the logic. This is a fight, and it is worth understanding the Project Manager’s view before the first submission.

4. The programme is out of date on the day of submission. Common when the planning function works on a monthly cycle but submissions slip a week. By the time the Project Manager reviews, the programme no longer matches site actuals. Rejected.

5. The programme is not consistent with the method statement, the BoQ activities, or the resource plan. Internal inconsistencies the Contractor has not picked up before submission. Project Manager spots them. Rejected.

Any of these is rejectable. Once rejected, the clock under clause 31.3 restarts, and any compensation event that occurs while there is no current Accepted Programme is being assessed against nothing. You are in the position the clause 50.3 retention was designed to address.

Making programme submission a commercial discipline

The fix is structural. Programme submission has to live with the commercial team, not the planning team.

That does not mean the commercial lead draws the programme. It means the commercial lead owns the acceptance status, owns the resubmission calendar, signs off every submission for 31.2 compliance before it goes out, and tracks the Project Manager’s acceptance/rejection turnaround. If the Project Manager has gone past their period without responding, the commercial team chases. If a CE occurs and the latest programme is stale, the commercial team blocks the quotation submission until a revised programme is in.

Practically, that looks like four habits on a project:

• A standing monthly programme revision date, written into the project commercial calendar, that does not move.
• A pre-submission compliance checklist covering every 31.2 contents item, signed off by the commercial lead.
• A live register of acceptance status, with the Project Manager’s last response date and any open queries.
• A rule that no CE quotation goes out unless the latest revised programme has been submitted and is either accepted or sitting inside the Project Manager’s response window.

None of this is hard work. It is administrative discipline. But the contractors that do it recover a meaningfully larger share of their CE pipeline than the contractors that do not, and they almost never see a 50.3 deduction.

The same logic applies to FIDIC. The 28-day Notice of Claim under Sub-Clause 20.1 is the FIDIC equivalent of an unforgiving procedural lever that destroys substantively strong claims if the contractor’s commercial discipline does not match.

The bottom line

If you remember one thing from this piece, make it this: under NEC, an Accepted Programme that is not current is not an Accepted Programme. It is the base case for nothing, the defence for nothing, and the exposure to a quarter-of-PWDD retention is real.

Treat clause 31 and clause 32 submissions as a monthly commercial discipline, owned by the commercial lead. The cost of the discipline is a few hours of admin a month. The cost of skipping it shows up in every CE quotation you submit and every settlement you negotiate from a weaker position.