When an Accepted Programme Stops Protecting a Specialist Contractor Under NEC
Updated: Sep 29
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
An accepted programme stops protecting a specialist contractor when it falls out of date but is still the one on record. Under NEC4, delay from a compensation event is measured against planned Completion on the Accepted Programme current at the dividing date, so a stale programme measures change against a job that no longer exists.
For the purposes of this article, specialist contractors include firms delivering mechanical, electrical, civil, groundworks and fit-out packages, along with other trade or package contractors who are running live sections of work under NEC without a large in-house planning function.
Many of these businesses are substantial operators in their own right, so size is not the issue. What matters is whether the accepted programme is still close enough to the live job to do the work NEC expects it to do. NEC’s own guidance is clear that the contract is not administered as intended without an accepted programme in place.
A specialist contractor usually discovers the real value of the accepted programme at the moment it stops protecting them. Until then, it can feel procedural. It is something to submit, update and move on from while the team gets on with delivery. Once change, disruption or delay lands on a programme that no longer reflects the live package, the accepted programme stops being background administration and starts becoming the contract’s last agreed picture of events. Under NEC, that matters because compensation event assessment is meant to deal with the effects of change as soon as they arise, while the works are still live.
The accepted programme is the contract’s live baseline
The clearest way to understand the accepted programme is to treat it as the contract’s live baseline. It is the agreed picture of sequence, timing and progress from which later movement can be judged. If that picture is current, both sides have a workable basis for understanding what changed, when it changed, and what effect it had. If that picture is stale, the contract still has a baseline, but it is no longer a reliable one. That is usually the point at which the commercial position begins to weaken, not because the project has necessarily gone badly wrong, but because the contractual record is beginning to lag behind the job. NEC says the contractor can protect itself by producing a revised programme as soon as it becomes aware that the previous one is out of date.
That sounds straightforward, but on specialist packages the drift often happens quietly. The team may still understand the work perfectly well. The site manager knows where access changed. The commercial lead knows what has been notified. The planner or package lead may have a working file that reflects reality much better than the last accepted submission. The difficulty is that NEC does not operate on informal understanding alone. It operates through an accepted programme that remains usable when time has to be assessed properly.
Programme problems usually begin with drift, not collapse
Most accepted programmes do not fail in one dramatic moment. They drift out of step with the works.
A revised programme goes in late. Another goes in but is not accepted. The team carries on using internal updates, marked up PDFs or meeting records that are closer to the truth than the formal accepted version. For a while, that can seem manageable. The package still moves. Decisions still get made. But the contract is starting to rely on an earlier version of the job. NEC’s own FAQ makes clear that the Project Manager can instruct a revised programme as soon as the previous one is out of date, and equally that the contractor can produce a new one as soon as it becomes aware of the same. That is NEC’s way of saying that the accepted position is supposed to stay close enough to the job to remain useful.
That is also the point at which the argument begins to change shape. Instead of asking what the programme showed at the time, the parties start trying to reconstruct what the job must have looked like later on. If that process has already started, the next difficulty is often what happens without an accepted programme. By then, the problem is no longer just keeping the programme current. It is recovering a credible contractual position after the accepted one has already drifted away.
What is lost when the accepted programme goes out of date
The real loss is not tidiness. It is control.
When the accepted programme falls behind, the contractor is not just losing a cleaner record. It is losing the contract’s preferred route for explaining the effect of change while the project is still moving. That is the turning point. Up to then, a weak programme may look like an administrative irritation. After that, it becomes a commercial problem.
The loss has a precise shape. A programme stays the Accepted Programme until a revised one is accepted, however far the job has moved on. Under NEC4 clause 63.5, the delay a compensation event causes is measured against planned Completion on the Accepted Programme current at the dividing date. Float the site has already used can still appear on paper, and a sequence that has since changed is still treated as the plan.
Clause 64.2 goes further. Where the contractor has not submitted a revised programme for acceptance as the contract requires, the Project Manager assesses the compensation event using its own assessment of the programme for the remaining work. Keeping the baseline current is what each clause 32 programme revision is for, and it costs far less than recovering the position afterwards.
Why hindsight is usually a bad sign
One of the more interesting things about NEC is that its logic is forward looking, but many disputes end up being argued backwards.
The contract is designed around prospective assessment. In practice, once programme discipline weakens, parties often fall back on hindsight and reconstruction. That shift matters because it usually means the live machinery of the contract has already started to slip. The further the parties move away from contemporaneous programme and quotation discipline, the more actual records and hindsight begin to dominate.
That is one reason Northern Ireland Housing Executive v Healthy Buildings (Ireland) Ltd still gets mentioned in NEC commentary. It was an NEC3 Professional Services Contract case, not an NEC4 subcontract dispute, so it should not be stretched beyond its facts. But it remains useful because it exposed the practical difficulty of assessing compensation events once the process has moved away from live quotation and into retrospective argument. The wider lesson is a simple one. Once the accepted programme stops keeping pace with the job, the contract becomes less capable of dealing with change in real time and more likely to invite argument later.
The warning signs specialist contractors miss
This issue often shows up earlier than many specialist contractors expect, not because the job is failing, but because the accepted programme has quietly stopped keeping pace with the live works.
The early signs are usually easy to miss. Design information arrives later than planned. Access changes. Interfaces with others move. A change is being discussed before it is fully instructed. The team understands what has happened and what is likely to happen next, but that understanding is still sitting in conversations, marked up files and working assumptions rather than in a revised accepted programme.
That is where the risk begins. From the contractor’s point of view, the job may still feel under control because the people running it understand the sequence, the constraints and the likely impact of events. The difficulty is that the contract is starting to rely on an older picture of the works. Once that happens, the accepted programme becomes less useful as a record of cause and effect and harder to rely on when time has to be explained properly.
The warning sign to watch for is a gap between the team’s live understanding of the job and the accepted contractual position, whether or not the package is in trouble. A better internal file may help the contractor manage the works day to day, but it is not the same thing as having a current accepted programme that can still carry the time story when it matters.
The working file against the Accepted Programme
Compared on | The team’s working file | The Accepted Programme |
Who relies on it | The site team, day to day | Both parties, whenever a compensation event is assessed |
What it shows | The job as it is running now | The job as it stood at the last acceptance |
Standing under the contract | None unless it is submitted and accepted | The baseline for delay under clause 63.5 |
When it changes | Whenever the team updates it | Only when a revised programme is accepted |
When the two diverge | The real story, with no contractual weight | The contractual weight, telling an old story |
A stronger position usually comes from rhythm
For most specialist contractors the answer is a steadier rhythm and clearer ownership, rather than a larger planning department.
What the contract needs is a programme that shows the job as it is, and a routine that gets each new event into it while it can still be accepted and used. That takes no extra overhead, only somebody whose job it is to keep the contract’s version of the job close to the site’s.
That is why programme support becomes valuable well before a formal dispute appears. The warning signs are familiar by then: updates going in late, and quotations built from memory rather than from a current baseline.
For teams that need help at that point, specialist contractor planning support is really about restoring a credible and current programme position before the commercial record becomes harder to defend.
Protection is usually lost gradually: the accepted programme stops being trusted, first by the other side and then, quietly, by the contractor itself. That is usually the point to deal with it, while it can still do the job NEC expects it to do.
FAQ
Is an out-of-date programme still the Accepted Programme?
Yes. The latest programme the Project Manager has accepted remains the Accepted Programme until a revised programme is accepted in its place, however far the job has moved on. That is what makes drift dangerous: under NEC4 clause 63.5, delay from a compensation event is still measured against planned Completion on the Accepted Programme current at the dividing date.
Why does the accepted programme matter if the site team already knows what is happening?
Because NEC does not rely on site knowledge alone. It relies on an accepted and current programme as part of the contractual basis for dealing with time and compensation events. Internal understanding helps, but it is not a substitute for a programme position the contract can actually recognise.
Can a specialist contractor rely on a better internal programme that was never accepted?
It may help the team run the works, but that is not the same as having a programme the contract will treat as the accepted baseline. A later internal file may be more accurate operationally, yet still carry far less weight contractually.
What usually happens once the accepted programme falls behind the job?
Compensation event assessment becomes harder to manage in real time. The discussion starts to move away from live programme evidence and towards later reconstruction. That usually means less control for the contractor over how time is framed and explained.
About the author
Roman Bazelchuk is the Founder of NEC Planning Solutions Ltd, a UK project planning and controls consultancy supporting contractors with NEC programme compliance, compensation event assessments and live project controls. He is an NEC Accredited Project Manager and holds the APMG Project Planning and Control qualification, with a BEng in Mechanical Engineering and postgraduate training in Planning and Control.
NEC Planning Solutions provides contract-aware planning support through a QA-governed delivery model, helping project teams keep programmes accepted, current and commercially useful from tender through to live delivery.
Need stronger programme control on a live NEC project?
If the accepted programme is slipping behind the job, or change is becoming harder to explain, early support can help restore a credible programme position before the commercial record becomes harder to defend.
