What does a clause 32 programme revision need to show?

Three things in addition to all the clause 31.2 requirements: actual progress on each operation and its effect on remaining work, how the contractor plans to deal with delays and correct notified defects, and any other changes the contractor proposes to make to the accepted programme. All three must be visible in the revision for it to be compliant.

How often must programme revisions be submitted under NEC?

At intervals no longer than those stated in the contract data, which is typically four weeks. The contractor must also submit a revision when the project manager instructs one (within the period for reply), and the contractor can submit more frequently whenever they choose. The contractual interval is the minimum, not the standard.

Can the project manager reject a programme revision?

Yes, using the same four grounds as for the first programme under clause 31.3: the plans are not practicable, the required information is not shown, the programme does not represent the contractor's plans realistically, or the programme does not comply with the scope. Non-acceptance on any other ground is itself a compensation event under clause 60.1(9). The project manager must give reasons for non-acceptance.

What happens if the project manager does not respond to a programme revision?

Under NEC4, the same deemed acceptance mechanism applies as for the first programme. If the project manager does not respond within two weeks, the contractor may notify the failure to respond. If the project manager then fails to respond within a further one week, the programme is deemed accepted. The contractor must issue the notification of failure. Deemed acceptance does not happen automatically. The article on NEC clause 31 programme acceptance covers the deemed acceptance mechanism in detail.

Should non-implemented compensation events be shown on revised programmes?

Yes. NEC4 removed the NEC3 wording about "implemented compensation events" precisely because it was being misinterpreted as excluding non-implemented events. A revised programme should reflect all compensation events affecting the work, whether implemented or pending. Non-implemented events should be clearly identified so the project manager can distinguish agreed changes from proposed changes, but they should be visible in the programme because they represent the reality of the remaining work.

Is a programme narrative required under clause 32?

The exact words of clause 32 do not require a narrative. However, a revision submitted without a narrative explaining what changed, why, and what the contractor plans to do about any delays is much harder for the project manager to review and far more likely to be rejected or ignored. A short narrative covering progress, compensation events, methodology changes, and the current critical path is the single most effective tool for securing acceptance.

What is the difference between a clause 32 revision and a compensation event quotation programme?

A clause 32 revision is a complete updated programme submitted for acceptance showing the current state of all works. A compensation event quotation programme under clause 62.2 shows the specific changes to the accepted programme caused by one compensation event. They serve different purposes and are submitted through different contractual routes, but they should be consistent with each other. The revised programme should reflect implemented compensation events, while the CE quotation programme shows the effect of a specific event against the accepted programme at the dividing date.

What a clause 32 programme revision actually needs to show under NEC

May 4

20 min read

Updated: Oct 30