NEC3 versus NEC4: what changed for programmes

The differences between NEC3 and NEC4 that matter when you build, submit and manage a programme.

Programmes and time3 min read

On this page
  1. What stayed the same
  2. What changed
  3. What this means for your programme
  4. Early warning and compensation event numbers at a glance

Most of the programme mechanics under the ECC are the same in NEC3 and NEC4. The changes that matter in practice are in terminology, how silence from the Project Manager is treated, the form of the programme, how delay is assessed against the Accepted Programme and the way some clauses are numbered. Always read the version your contract actually uses, plus its Contract Data and any Z clauses, because amendments are common.

What stayed the same

  • The Contractor submits a first programme for acceptance (clause 31.1).
  • The Project Manager accepts it or gives reasons for not accepting (clause 31.3).
  • The Contractor submits revised programmes at intervals and when instructed (clause 32).
  • The programme must show what clause 31.2 lists, including Key Dates, float, time risk allowances and the work of the Client and Others.
  • The Accepted Programme is used to assess delay to the Completion Date.

What changed

Topic NEC3 NEC4
Terminology Employer, Works Information Client, Scope
Early warning Clause 16 Clause 15
Silence from the Project Manager A failure to reply within two weeks is a compensation event under 60.1(6), but the programme stays unaccepted Also a 60.1(6) event, and the Contractor can notify the failure under 31.3; if there is still no reply one further week later, the programme is treated as accepted. Under the NEC4 ECS the periods are three weeks and then two further weeks
Form of the programme Not dealt with in 31.2 31.2 says the programme is in the form the Scope states
Revised programme content Clause 32.1 includes showing implemented compensation events That wording is removed from 32.1
Delay in a compensation event assessment 63.3, against the Accepted Programme 63.5, against the Accepted Programme in force at the dividing date
Holdback when no first programme A quarter of the Price for Work Done to Date, clause 50.3 Same rule, clause 50.5
Reasons a programme can be refused Includes compliance with the Works Information Includes compliance with the Scope
Communications Clause 13 Clause 13, with a named communication system in the Scope taking effect when a message is sent through it (13.2)
Mutual trust and co-operation Clause 10.2 Clause 10.2

What this means for your programme

  1. Check which terms your contract uses. A programme that refers to "Works Information" under an NEC4 contract looks careless.
  2. Check the deemed acceptance rules. Under NEC4 your diary matters more. A programme can be treated as accepted if the Project Manager misses the two-week reply, you notify the failure and a further week passes. The Contractor chooses whether to notify, and nothing happens without it. NEC3 has no such rule. A Project Manager who then replies inside the further week ends the failure.
  3. Re-check clause numbers. If you are moving a team from NEC3 to NEC4, do not rely on remembered clause numbers: early warning moved from 16 to 15, the first-programme holdback from 50.3 to 50.5, and the delay rule from 63.3 to 63.5. Look up the 60.1 item each time.
  4. Read the Z clauses. Many clients amend programme clauses heavily, for example to require specific software formats, submission frequencies or schedule quality metrics.

Early warning and compensation event numbers at a glance

Item NEC3 NEC4
Early warning 16.1 15.1
Early warning meeting 16.2 15.2
Notifying a compensation event, and the eight-week time bar 61.3 61.3 (seven weeks under the NEC4 ECS)
Holdback while no first programme 50.3 50.5
Delay assessed against the Accepted Programme 63.3 63.5

Our notice tool uses the right numbers for the version you select.

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

Was this useful?