A revised programme under NEC4 clause 32 has to do two jobs at once, and most of the ones that get rejected only do one. Clause 32.1 says what it must show: actual progress and its effect on the remaining work, how you're dealing with delays and correcting notified Defects, and any other changes you're proposing to the Accepted Programme. Clause 32.2 says when you have to submit one: at the interval stated in Contract Data Part One (four weeks is typical), whenever the Project Manager instructs it, or whenever you choose to submit one yourself.

Notice what's not in that second list: a compensation event isn't itself a clause 32.2 trigger. It reaches your programme through a different door, clause 62.2, which requires your CE quotation to include the programme alterations if the event changes the plan for remaining work. Treat the two as the same obligation and you'll either miss a clause 32 interval while waiting for a CE to "count," or submit a CE-driven revision that never gets tied back to the quotation it was meant to support. This piece walks through both, and the one step in between that most planners skip.

What Clause 32.1 Actually Requires You to Show

Every revised programme needs three things, on top of everything clause 31.2 already requires of the first programme (starting date, Key Dates, Completion Date, planned Completion, order and timing of operations, float and time risk allowances, the critical path, health and safety requirements, terminal float).

Actual progress and its effect on remaining work. Not a percentage typed into a field. The remaining logic and durations need to reflect what the progress actually means for the rest of the schedule, including where an activity ran long enough to eat into the float ahead of it.

How you're dealing with delays and correcting notified Defects. If something's running late, the revision needs to show the recovery or mitigation plan, not just a pushed-out date. If a Defect has been notified, the correction needs its own visible activity.

Any other changes you're proposing to the Accepted Programme. New activities, deleted ones, resequencing, a changed method. This is also where a compensation event's effect on remaining work lands once you've decided how to model it, whether or not that CE has been formally implemented yet.

Step 1: Work Out Which Clause Actually Applies

Before you touch P6, decide why you're revising. If it's the routine interval, or the Project Manager has instructed one, that's a straightforward clause 32.2 submission. If it's driven by a compensation event you're still quoting for, you're really building two related documents: the clause 32 revision itself, and the programme alterations that clause 62.2 requires inside your CE quotation. Keep track of which one you're producing, because they have different deadlines and different audiences even when the underlying schedule change is identical.

Step 2: Snapshot the Accepted Programme Before You Change Anything

This is the step that gets skipped, and it's the one that actually protects your CE assessment. Clause 63.5 assesses a compensation event's time effect against the accepted programme current at the dividing date, the date the event was notified. If you go straight into revising that programme to reflect the CE before you've locked a copy of it as it stood at the dividing date, you've overwritten the one artefact your own quotation depends on.

In P6, save the current Accepted Programme as a baseline (Project ▸ Maintain Baselines) before you make a single change, and name it something that ties it to the date, not just "Baseline 3." Assign it as the Project Baseline (Project ▸ Assign Baselines) so every later comparison runs against it automatically. Only once that's done should you start editing the live schedule.

Step 3: Update Actual Progress First

Status the schedule against real dates: actual starts, actual finishes, remaining durations based on genuine forecast productivity, not the original duration minus percent complete. Keep logic intact rather than forcing dates with constraints to make the picture look tidier than it is. This is the "actual progress and its effect on remaining work" half of clause 32.1, and a Project Manager checking it against site records will spot a schedule that's been forced far faster than one that's been honestly updated.

Step 4: Model the Compensation Event as Its Own, Traceable Change

Where the revision is carrying a CE's effect on the programme, don't fold the new or altered activities anonymously into the existing logic. Tag every activity the event touches with a distinct Activity Code or user-defined field carrying a generic CE reference (your own numbering, not the client's), so anyone reviewing the revision, or the quotation it's attached to, can filter straight to exactly what changed and why. This does double duty: it satisfies clause 32.1's "other changes" requirement with something a Project Manager can actually verify, and it's the same alteration set clause 62.2 needs inside your quotation, built once instead of reconstructed twice.

Step 5: Show the Recovery Plan for Anything Running Late

Where progress has eaten into float or pushed planned Completion out, add the recovery activities explicitly: resequenced work, added shifts, a changed method, whatever you're actually proposing. A revision that shows a later finish date with no visible plan to address it reads as an admission you've stopped trying to hold the programme, and it invites the Project Manager to reject on the same "not practicable" ground that governs the first programme.

Step 6: Run a Schedule-Quality Check Before You Resubmit

A revised programme fails for exactly the same reasons a first one does. Negative float, broken logic and hard constraints propping up sequencing you haven't actually worked out are all grounds for a "not practicable" rejection under the same test clause 31.3 applies to every programme submission, first or revised. Run it through a DCMA-style check before it goes anywhere near the Project Manager. Run the free schedule check against the revised .xer or .xml; nothing is uploaded, stored or shared. If you want the walkthrough for reading what comes back, we've covered that separately: how to read a DCMA-style result in P6.

Step 7: Submit for Acceptance on the Same Terms as the First Programme

A revised programme is accepted or rejected under the same clause 31.3 test as the first one: not practicable, doesn't show the required information, doesn't represent your plans realistically, or doesn't comply with the Scope. Nothing else counts, and lateness on its own isn't one of the four, whatever an older piece of NEC guidance you might read elsewhere says. The Project Manager has the period for reply, two weeks by default, to accept or notify non-acceptance with reasons. If that period passes with nothing back, notify the Project Manager of the failure; if a further week passes with still nothing, the programme is treated as accepted. We've written the step-by-step version of that first submission in our clause 31 programme acceptance walkthrough, and the reference version in our NEC4 programme requirements guide.

Step 8: Attach the Same Alteration Set to Your Clause 62.2 Quotation

If this revision exists because of a compensation event, the programme alterations you've just built are the ones clause 62.2 requires inside your quotation, the same CE-tagged activities from Step 4. Don't let the two documents drift: a quotation that shows one version of the schedule impact while your clause 32 submission shows another gives the Project Manager grounds to send the quotation back for revision under clause 62.3, and it undermines your own evidence if the event ends up disputed later. One alteration set, referenced from both.

Where Revisions Actually Go Wrong

The single most common failure is sequencing: contractors revise the programme to reflect a compensation event's impact, submit that as their clause 32 revision, and only afterwards pull together the clause 62.2 quotation, using whatever the programme looks like by then. By that point the schedule has usually moved on again, updated with more progress or a second change, and the "programme current at the dividing date" that clause 63.5 actually wants no longer exists anywhere. Locking a baseline before you touch anything, Step 2 above, is the entire fix, and it costs about two minutes in P6.

The second failure is treating "other changes" as a free pass to bundle unrelated resequencing into a CE-driven revision without separating it out. If a Project Manager can't tell which activities changed because of the compensation event and which changed because you decided to resequence something else entirely, they can't verify either, and a revision they can't verify is a revision they're entitled to query rather than accept.

When to Get a Second Opinion

If a revision keeps coming back, or a compensation event's programme impact is contested enough that you want it checked before the Project Manager sees it, that's the point for an independent read. Planned's NEC4 Programme Acceptance Review tests a programme, first submission or revision, against clauses 31.2 and 31.3 before it goes in, with a written recommendation delivered inside the reply period.

Book a Free Consultation to have a revision looked at before you submit it, or run the free schedule check first to catch the basic quality issues yourself.

Frequently Asked Questions

Does a compensation event automatically trigger a clause 32 revised programme?

Not directly. Clause 32.2's own triggers are the stated interval, a Project Manager instruction, or the Contractor's own choice. A compensation event reaches the programme through clause 62.2, which requires the Contractor's quotation to include the programme alterations where the event changes the plan for remaining work. In practice the two often happen close together, but they're separate obligations with separate deadlines.

What must a clause 32.1 revised programme show?

Actual progress achieved on each operation and its effect on the timing of remaining work, how the Contractor plans to deal with any delays and correct notified Defects, and any other changes the Contractor proposes to make to the Accepted Programme, on top of everything clause 31.2 already requires of the first programme.

Can a revised programme be rejected just for being submitted late?

No. A revised programme is accepted or rejected under the same clause 31.3 test as the first one: not practicable, missing required information, not a realistic representation of plans, or non-compliant with the Scope. Late submission on its own isn't one of the four.

What is the dividing date and why does it matter for a revision?

The dividing date is the date a compensation event is notified. Under clause 63.5, the event's time effect is assessed against the accepted programme current at that date. If you revise the programme to reflect the event before locking a copy of it as it stood at the dividing date, you lose the baseline your own assessment needs.

How often does a revised programme have to be submitted?

At intervals no longer than the period stated in Contract Data Part One, commonly four weeks, in addition to whenever the Project Manager instructs one or the Contractor chooses to submit one.

About Planned Ltd

Planned Ltd is a project planning and controls consultancy for construction and infrastructure: planning and scheduling, project controls, delay and claims, schedule assurance, and Primavera systems and training.

Written by our planning team and reviewed by the Director.