NEC4 compensation events without an accepted programme: how contractors protect entitlement when the baseline is missing
- Feb 20
- 16 min read
Updated: May 9
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
There is a category of NEC project that experienced commercial directors recognise within the first three months. The contract started normally. The first programme was submitted. The project manager did not accept it on first submission and asked for revisions. The second submission addressed the comments but not all of them. The third submission addressed the rest but introduced new issues. By month three, the project has run through three or four programme submissions, none of which has been formally accepted. The project is operational, the works are progressing, and a steady stream of compensation events has begun to arrive. The accepted programme, contractually, does not exist.
The standard contractor response to this situation is to wait. The compensation events accumulate in the register, marked "pending acceptance of programme baseline." The project manager is reminded periodically that the programme is awaiting their decision. The commercial team holds the events in suspension on the understanding that they cannot be properly assessed without an accepted programme to assess against. By month six, the accumulated value of pending events is substantial, the project manager's review burden is significant, and neither party has a clean route back to a manageable position.
This pattern is one of the most damaging on NEC projects, and the damage is structural rather than situational. The accepted programme is not a procedural document the contract can do without. It is the shared reference frame against which all compensation events are assessed. When it is missing, every compensation event is assessed in a contractual vacuum, with the contractor and the project manager working from different mental baselines. The longer the vacuum persists, the more entitlement the contractor loses, often without realising the loss is happening.
Most existing commentary on this situation treats it as a procedural problem with a procedural solution: keep submitting programmes, push for acceptance, raise it through correspondence and meetings until the project manager engages. This advice is correct but misses the structural point. The accepted programme is not absent because of administrative friction. It is absent because the contractual mechanism that should produce it has stalled, and the stall itself shifts commercial control of the project. The contractor who understands what is happening underneath the procedural surface protects entitlement actively. The contractor who treats it as an administrative inconvenience surrenders entitlement quietly.
This article explains what the absence of an accepted programme actually means, why it shifts commercial control to the project manager, what contractors can do to preserve entitlement while the situation persists, and how to recover the position before the damage compounds beyond practical repair. It is written for contractors who recognise the pattern and want to understand the structural dynamics that produce it.
Why the accepted programme matters more than contractors usually realise
Under NEC4, the accepted programme performs at least seven distinct contractual functions. It establishes the contractor's planned completion and the terminal float between planned completion and the completion date. It identifies the dates by which the project manager and others must provide information or meet other obligations, with failures to meet those dates becoming compensation events under clause 60.1(3). It records the time risk allowances the contractor has built into the programme, which are preserved when compensation events occur. It establishes the float and the critical path against which delay is measured. It is the baseline against which subsequent revisions are compared. It is the reference programme used for compensation event assessment under clause 63.5. And it is the document the project manager refers to when assessing whether the contractor's actual progress is on track to meet the completion date.
When the accepted programme is missing, all seven functions are compromised. The contractor's planned completion is not formally established. Information dates are not formally fixed. Time risk allowances are not formally recognised. The critical path is not formally agreed. Compensation event assessments cannot be properly anchored to a contractual baseline. The progress measurement reference is informal at best.
The compounding effect is that the contractor's commercial position weakens across multiple dimensions simultaneously. Each individual weakness might be manageable. The accumulation across all seven functions is what produces the structural damage. By the time the contractor recognises that the situation is serious, the damage is usually significant.
Contractors who have run NEC projects without an accepted programme for extended periods report a consistent pattern. Compensation events become harder to assess. Delays become harder to attribute. The relationship with the project manager becomes more transactional and less collaborative. The end-of-project reckoning becomes a forensic exercise rather than a clean settlement. None of this is inevitable, but all of it follows from the absence of the shared reference frame the accepted programme provides.
The article on NEC clause 31 programme acceptance covers what acceptance produces and why establishing it early matters so much.
The structural insight: who controls the reference frame controls the assessment
When an accepted programme exists, both parties operate from the same reference frame. The contractor's quotation for a compensation event uses the accepted programme as its baseline. The project manager's review uses the same accepted programme as the basis for their evaluation. Disagreements about the assessment relate to the specifics of the event's impact, not to the underlying baseline. Both parties can challenge each other's analysis on a shared foundation.
When an accepted programme does not exist, the reference frame is contested. The contractor's quotation has to identify some baseline against which to assess the event. The project manager's review may use a different baseline, or may decline to engage with the contractor's chosen baseline at all. The disagreement is no longer about the specifics of the event's impact. It is about which baseline applies, and that disagreement is structurally harder to resolve than disagreements about analysis on a shared baseline.
This is the structural insight that most discussions of compensation events without an accepted programme miss. The absence of the accepted programme does not just make assessments harder. It moves the contest from the assessment level to the baseline level. The party that controls the baseline in this contest controls the entire assessment, because every analytical step depends on the baseline that anchors it.
In practice, the absence of an accepted programme tends to favour the project manager rather than the contractor. The project manager has the institutional position of the contract's administrator, the discretion of clause 64 to make their own assessment if the contractor's position is unsatisfactory, and the practical advantage that disputes about baseline are usually resolved through dispute mechanisms rather than through prospective agreement. The contractor's strongest commercial position is when the accepted programme exists and the contest is about analysis. The contractor's weakest position is when the accepted programme is missing and the contest is about baseline.
This means the practical priority for contractors operating without an accepted programme is not "how do we work around this." It is "how do we re-establish the accepted programme as quickly as possible." The work-arounds are useful tactically but they do not address the underlying structural disadvantage. Only acceptance of a programme addresses that disadvantage.
What clause 64 does in this situation
Clause 64.1 of NEC4 lists four circumstances in which the project manager makes their own assessment of a compensation event. The fourth circumstance is the one that matters most for NEC4 compensation events without accepted programme: the project manager makes their own assessment if, when the compensation event occurred, the contractor had not submitted the alterations to the accepted programme or other relevant information that the project manager requires.
This trigger is structurally different from the other three. The other three relate to specific failures in the compensation event process: the contractor failed to submit a quotation, the quotation was not correctly assessed, or the contractor failed to submit a revised quotation. These are all faults in the contractor's response to specific events. The fourth trigger relates to the broader programme administration regime under clauses 31 and 32. It activates whenever a compensation event arises while the accepted programme is missing or substantially out of date.
The consequence is that during any period when the accepted programme does not exist, every compensation event arising in that period is potentially subject to project manager assessment under clause 64. The contractor cannot prevent this trigger from activating by being more diligent on the specific event. The trigger relates to a structural condition of the contract administration that pre-exists any individual event. The article on NEC4 clause 64Â covers the broader switching mechanism in detail.
In effect, the absence of an accepted programme creates a permanent latent grounds for clause 64 activation across every compensation event in the affected period. The project manager may choose not to invoke clause 64 in any specific case, but they retain the option, and the option itself shifts the commercial dynamic. The contractor's quotation is not the default position; it is a position that survives only if the project manager declines to exercise their clause 64 option.
This is the precise mechanism by which the absence of an accepted programme transfers commercial control. It is not just that assessments become harder. It is that the contractor's procedural position shifts from "my quotation is the baseline unless the project manager identifies specific issues" to "my quotation is the baseline unless the project manager decides to assess themselves." The shift is significant and the contractor cannot reverse it through tactical excellence on individual events. The reversal requires re-establishing the accepted programme.
NEC4 compensation events without accepted programme: how contractors protect entitlement while the position is being recovered
The structural disadvantage created by the absence of an accepted programme can be reduced but not eliminated. Several specific disciplines protect entitlement during the period when the position is being recovered.
The first discipline is anchoring every compensation event assessment to the most defensible baseline available. If the most recent accepted programme is six months old but exists, that programme is the contractual baseline for events that occurred during the period it represented. The contractor's quotation should explicitly identify it as the baseline used, with the reasoning. If no accepted programme has ever existed, the contractor should identify the most recent submitted programme, explain that it has not been formally accepted, and propose its use for the assessment with explicit assumptions documented. The article on how to structure a time impact assessment under NEC4Â covers the structural elements that support this anchoring.
The second discipline is keeping the dividing date discipline tight. Under clause 63.1, the dividing date determines what is actual cost and what is forecast cost. Even without an accepted programme, the dividing date is fixed by the contract. Every quotation should identify the dividing date precisely and apply the actual-cost / forecast-cost split correctly. This is one of the few elements that does not depend on the accepted programme being in place, and it is one of the strongest procedural defences against subsequent retrospective analysis.
The third discipline is full contemporaneous record-keeping for every event. Without the accepted programme as the contractual reference frame, the records of what happened, when, and how the contractor responded become disproportionately important. Photographs, dated diary entries, RFI responses, internal communications, and resource records all carry more weight than they would in a project with a strong accepted programme baseline. The contractor's records are the alternative reference frame that protects against retrospective reconstruction by either party.
The fourth discipline is parallel programme submission. Even while compensation events are being progressed under the existing baseline, the contractor should be submitting revised programmes under clause 32 in an effort to re-establish acceptance. This serves two purposes. It demonstrates that the contractor is engaging with the contract's procedural mechanisms even though the project manager has not been responsive. It also creates the documented submission trail that supports a deemed acceptance argument under NEC4 if the project manager continues to fail to respond.
The fifth discipline is escalation through formal contractual mechanisms when the situation has persisted long enough. Under W1 of NEC4, the contractor can refer disputes to senior representatives. Under clause 13.4, communications must be replied to within the period for reply. Under clause 60.1(6), the project manager's failure to reply to a communication within the period for reply is itself a compensation event. Each of these mechanisms is available and underused. The contractor who escalates appropriately is signalling to the project manager that the absence of an accepted programme has commercial consequences, which is often the trigger for engagement that more passive correspondence has failed to produce.
These five disciplines together do not solve the structural disadvantage but they reduce it materially. Applied consistently, they preserve a substantial portion of the entitlement the contractor would otherwise lose during the period of programme limbo, and they create the foundation for recovery once acceptance is re-established.
How to re-establish the accepted programme
The work of re-establishing the accepted programme is procedural, not technical. The programme itself is rarely the problem. The problem is the absence of the formal acceptance step that converts the latest submitted programme into the contractual baseline.
The cleanest path to re-establishing acceptance has four elements.
The first is a clean, properly compliant programme submission. The submission should pass all five structural checks the project manager will apply (open ends, logic flow, critical path, constraints, calendars), should contain every clause 31.2 information requirement, should pass the realism test, and should comply with the scope requirements. The article on what the project manager checks when reviewing your NEC programme covers the review sequence the project manager applies. A submission that pre-empts every objection in that review sequence gives the project manager nothing to work with on rejection.
The second is a formal submission notification under clause 13. The two-week acceptance clock starts on formal submission. A programme submitted as an email attachment without a clear submission notice does not start the clock cleanly. A formally submitted programme creates an unambiguous procedural position from which deemed acceptance can be invoked under NEC4 if the project manager fails to respond.
The third is active management of the response period. If the project manager responds within two weeks with reasons for non-acceptance, the contractor addresses the reasons and resubmits promptly. If the project manager does not respond within two weeks, the contractor invokes the deemed acceptance mechanism by issuing a formal notification of failure to respond. If the project manager continues to fail to respond after the additional week, the programme is deemed accepted under NEC4. NEC3 does not contain the deemed acceptance mechanism, which is one of the most significant differences between the two contracts and is covered in the article on NEC3 vs NEC4 changes for contractors.
The fourth is the recovery rhythm once acceptance is established. The newly accepted programme becomes the baseline. Subsequent revisions follow under clause 32 at the contractually specified interval. Compensation events arising after the acceptance can be assessed against the new baseline normally. Compensation events that arose during the period of programme limbo need to be revisited and assessed against the appropriate historical baseline, with the new acceptance giving the contractor a stronger commercial position from which to negotiate the historical events.
This four-element path is straightforward to describe but requires consistent execution. Contractors who have allowed the situation to drift for several months often need external support to re-establish the discipline because the internal team has lost confidence in the process. Specialist NEC programme support provides the systematic intervention that breaks the deadlock and brings the project back to a state where the accepted programme exists, compensation events flow through normal assessment, and commercial control sits where the contract intended it to sit.
When the project manager refuses to engage
A specific subset of cases involves project managers who appear to be deliberately not engaging with programme submissions, either because they have been instructed by the employer to delay acceptance for commercial reasons, or because they personally judge that acceptance would create exposure they prefer to avoid.
The Costain v Bechtel question becomes relevant here. Although the case did not finally determine the question of whether project managers owe a duty of impartiality, the principle that project managers must apply the contract's rules honestly when administering specific functions has emerged from subsequent commentary as the practical standard. A project manager who is deliberately not engaging with programme submissions in order to manipulate the commercial position is operating outside the contract's intended dynamic.
For contractors, the response to this situation is procedural rather than confrontational. Document the submissions and the absence of responses. Use the formal mechanisms available under the contract. Refer the failure to respond as a compensation event under clause 60.1(6). Escalate to senior representatives under W1. If necessary, refer the question of programme acceptance to adjudication. The contractual mechanisms exist to handle exactly this situation, and the contractor's strongest position is one in which they have used those mechanisms in sequence rather than relying on informal persuasion.
The contractor who has documented their submissions, escalated through the proper mechanisms, and pursued formal resolution generally finds that the project manager's engagement improves substantially. The contractor who has relied on informal correspondence and meetings often finds that the same project manager continues to be unresponsive indefinitely. The difference is procedural rigour, not commercial pressure.
What good practice looks like in projects that never lose the accepted programme
The strongest contractors operate in a way that prevents the loss of the accepted programme rather than recovering from its absence. The disciplines are recognisable and they are not technically demanding.
The first discipline is treating the initial programme submission as a deliberate exercise in pre-empting review objections. The contractor's planning team builds the programme to pass the project manager's review sequence cleanly, including the scope compliance and information completeness checks. The first submission is the strongest one, not a placeholder for subsequent revision.
The second discipline is treating clause 32 revisions as a non-negotiable rhythm. Revisions are submitted at the contractually specified interval, formally, under clause 13, with proper narrative and baseline comparisons. Each revision creates a new acceptance opportunity. Even if a particular revision is not accepted, the next one in the sequence creates another opportunity, and the cumulative pressure of consistent submission tends to produce engagement.
The third discipline is using deemed acceptance under NEC4 actively. If the project manager fails to respond, the contractor issues the notification of failure and proceeds to deemed acceptance. This is not a hostile act. It is the contract's intended mechanism for handling project manager non-response. Contractors who use it appropriately find that project managers respond faster on subsequent submissions.
The fourth discipline is integrating compensation event assessment with programme administration. Each quotation references the accepted programme version it uses. Each programme revision incorporates the implemented compensation events. The two processes reinforce each other rather than running in parallel without integration. The article on NEC clause 32 programme revision covers the integration discipline.
These four disciplines together produce projects where the accepted programme exists continuously, compensation events flow through normal assessment, and commercial control sits with the contractor by default. The disciplines are not unusual. They are simply consistent application of what the contract was designed to produce.
Summary
The accepted programme is not a procedural document. It is the shared reference frame that anchors every compensation event assessment, every delay analysis, every dispute about progress, and every commercial conversation about time and cost on an NEC project. When it is missing, the reference frame becomes contested, and the contest favours the party with the stronger procedural position, which is usually the project manager.
The structural consequence of this is that periods without an accepted programme transfer commercial control of the project. The contractor's quotations on compensation events arising in those periods are subject to clause 64 project manager assessment as a permanent latent option. Entitlement is lost not through specific challenges to specific events but through the cumulative effect of operating without the contractual reference frame.
The disciplines that protect entitlement during such periods are useful but partial. Anchoring assessments to the most defensible baseline available, maintaining tight dividing date discipline, keeping detailed contemporaneous records, submitting parallel programme revisions, and escalating through formal contractual mechanisms all reduce the structural disadvantage. None of them eliminates it.
The path back to a functioning accepted programme is procedural rather than technical. A clean compliant submission, formally notified under clause 13, with active management of the response period including invocation of NEC4 deemed acceptance if the project manager does not respond, generally produces acceptance within four to six weeks of consistent execution. The path requires discipline rather than complexity, and it requires the contractor to use the contract's mechanisms in the way the contract was designed to be used.
Contractors who never lose the accepted programme operate in a way that prevents loss rather than recovering from it. Strong first submissions, non-negotiable revision rhythm under clause 32, active use of deemed acceptance under NEC4, and integrated compensation event and programme administration produce projects where the structural problem this article addresses simply does not arise. The disciplines are not unusual. They are consistent application of what the contract was designed to produce.
For contractors who have allowed the situation to drift, recovery is possible but typically requires external intervention to re-establish the discipline. The cost of that intervention is small compared to the cost of allowing the situation to continue across the remainder of the project. The latter compounds. The former resolves.
FAQ
What does it mean when an NEC project has no accepted programme?
It means no programme has been formally accepted by the project manager under clause 31.3, either because no programme has been submitted in compliant form, because submitted programmes have been rejected without a subsequent compliant submission being accepted, or because the project manager has not responded to submissions and deemed acceptance has not been invoked. The absence of an accepted programme is structurally significant because the accepted programme is the contractual reference frame against which compensation events, delay, and progress are assessed.
Can compensation events still be assessed without an accepted programme?
Yes, but the assessment is structurally weaker. The contractor's quotation has to identify some baseline against which to assess the event, and the project manager's review may not engage with the chosen baseline. Under clause 64.1, the absence of an accepted programme is a permanent latent grounds for the project manager to make their own assessment, which usually produces a lower entitlement than the contractor's quotation would have produced.
How does NEC4 deemed acceptance help when the project manager is not responding?
NEC4 introduced a deemed acceptance mechanism under clause 31.3. If the project manager fails to respond to a programme submission within the two-week response period, the contractor can issue a notification of failure. If the project manager fails to respond within a further week, the programme is deemed accepted. This mechanism does not exist in NEC3 and is one of the most useful tools NEC4 added for contractors managing unresponsive project managers. The article on NEC3 vs NEC4 changes covers the deemed acceptance mechanism in detail.
Should contractors stop submitting compensation event quotations until an accepted programme exists?
No. The eight-week time bar under clause 61.3 applies regardless of whether an accepted programme exists. Failing to notify and quote compensation events within their procedural deadlines forfeits entitlement entirely on those events. The correct approach is to submit quotations using the most defensible available baseline, with explicit identification of the baseline and any assumptions, while pursuing acceptance of the programme in parallel. The article on the NEC4 compensation event time bar covers the time bar mechanism.
What is the dividing date and why does it matter without an accepted programme?
The dividing date under clause 63.1 separates work done before the date (assessed using actual cost) from work not yet done at the date (assessed using forecast cost). The dividing date is fixed by the contract regardless of whether an accepted programme exists. Maintaining tight dividing date discipline is one of the strongest procedural defences available when the accepted programme is missing, because it prevents the assessment from drifting into retrospective analysis that the contract is designed to avoid.
How long does it typically take to re-establish an accepted programme?
For contractors who execute the four-element path consistently (clean submission, formal notification, active response management, deemed acceptance if needed), four to six weeks from the next submission is typical. The actual timeframe depends on the responsiveness of the project manager and the complexity of the issues that arose during the period of programme limbo. Contractors who continue submitting programmes with the same structural issues that produced earlier rejections will not achieve acceptance regardless of how persistent the submission rhythm becomes.
What if the project manager appears to be deliberately not accepting programmes?
Document the submissions and the absence of responses. Use the formal mechanisms available under the contract. Refer the failure to respond as a compensation event under clause 60.1(6). Escalate to senior representatives under W1. If necessary, refer the question to adjudication. The contractual mechanisms exist to handle this situation, and the contractor's strongest position is one in which they have used those mechanisms in sequence rather than relying on informal persuasion.
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 BSc 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.
When the accepted programme is missing on a live project, the path back is procedural, not commercial.
NEC Planning Solutions provides the systematic intervention that re-establishes acceptance, recovers the historical compensation event position, and brings commercial control back to the contractor.