The NEC Accepted Programme: the one programme that counts

What the NEC Accepted Programme is, why it is the baseline for delay and compensation events, and how to stop it drifting out of date.

NEC basics for newcomers3 min read

On this page
  1. Why it affects your money and time
  2. How it drifts
  3. Example: a pumping station refurbishment
  4. Habits that prevent trouble
  5. Misunderstandings
  6. Related guides

Your site team may be working to revision 9 of the programme, but the contract may only recognise revision 4. That gap is the heart of this topic. The Accepted Programme is the single programme the contract treats as the real one: either the version listed in Contract Data, or the most recent version the Project Manager (the person the Client appoints to run the contract day to day) has accepted. Anything newer that has not been accepted is just information. The term is defined in clause 11.2 and the procedure is in clause 31.

Why it affects your money and time

It is the measuring stick for a number of contract tests:

  • Late access (60.1(2)). Access must be later than the access date and also later than the date your programme shows.
  • Client-supplied items (60.1(3)). Lateness is judged against the programme.
  • Work by the Client or Others (60.1(5)). Their timings on the programme are part of the test.
  • Delay assessment (63.5, or 63.3 in NEC3). Delay means how far planned Completion moves compared with the programme.
  • First programme (50.5, or 50.3 in NEC3). Where Contract Data names no programme, a quarter of the assessed Price for Work Done to Date is held back until a compliant first programme goes in.

Acceptance is not an instruction. It does not make the Project Manager responsible for your works (14.1) and it does not shift the Completion Date.

How it drifts

You send revision after revision. Some get queried, some get no reply. Site keeps planning from your latest file, so everybody believes they know "the programme". Months later the last accepted version is stale.

NEC4 has a safety net. If the Project Manager says nothing, you can notify that failure, and if there is still no answer within the time allowed, the programme counts as accepted (31.3). NEC3 has nothing similar. There, silence is dealt with through the failure-to-reply compensation event while the earlier accepted programme stays in force.

Example: a pumping station refurbishment

Suppose the accepted version (revision 2, from February) shows Completion on 20 September. Your later revision 5, sent in June and never answered, shows 11 October because your own pipework fabrication slipped. In July the Project Manager instructs a larger access hatch that adds two weeks on the critical path.

Strictly, revision 2 is the baseline. Measuring two weeks from it ignores the three weeks you had already lost, and a fair assessment has to separate your delay from the hatch delay. You will need to show the effect from your true position. Had revision 5 been answered promptly, none of this would be arguable.

You can also put changes to the programme inside a compensation event quotation (62.2), which helps but is not a replacement for regular acceptance.

Habits that prevent trouble

  1. Keep a revision log with date sent, reply due, reply given and status.
  2. Chase answers, and if the Project Manager does not accept, expect reasons in writing.
  3. Before preparing any delay assessment, confirm which revision was in force at the relevant date.
  4. In letters, name the revision number and say whether it is accepted.

Misunderstandings

  • Comments on a programme are not acceptance, and site working to it is not acceptance either.
  • Clause 31.3 lists the allowed grounds for not accepting. Refusing on any other ground can be a compensation event itself (60.1(9)).
  • Acceptance does not prove your logic works, and it does not turn dates shown for the Client into new duties beyond the contract.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?