NEC programme acceleration and mitigation: the practical contractor guide
- 3 days ago
- 16 min read
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
There is a conversation that happens on almost every NEC project that falls behind programme. The project manager calls a meeting. The programme shows delay. The completion date is at risk. The project manager asks the contractor to take action to recover the position.
At that moment, two entirely different contractual mechanisms are in play, and most contractors do not recognise which one they are being asked to engage.
If the project manager is asking the contractor to reorganise the remaining work to reduce the effect of delay without incurring additional cost, that is mitigation. The contractor is obliged to do it. Clause 63.8 assumes the contractor reacts competently and promptly to any compensation event, and compensation event assessments are made on that basis whether or not the contractor actually mitigated. Mitigation is not optional under NEC. It is built into the assessment mechanism.
If the project manager is asking the contractor to spend money, add resources, work longer hours, or take on additional risk to bring forward the completion date beyond what mitigation alone can achieve, that is acceleration. The contractor is not obliged to do it. Clause 36 provides a voluntary mechanism for agreeing acceleration, and the contract specifically prevents the project manager from imposing it.
The distinction between these two concepts is the most commercially significant boundary in NEC time management, and it is the one that contractors most often get wrong. Contractors who mitigate when they should be quoting for acceleration give away recovery work that the contract entitles them to be paid for. Contractors who refuse to mitigate on the grounds that it constitutes acceleration lose entitlement because the assessment assumes they would have mitigated anyway. Both mistakes are expensive. Both are avoidable.
This article explains how NEC programme acceleration and mitigation work in practice. It covers what the contractor is obliged to do, what the contractor can choose to do, where the line sits between the two, and how to protect the commercial position in each situation.
The obligation to mitigate: what clause 63.8 actually requires
Clause 63.8 of NEC4 (clause 63.6 in NEC3) states that assessments of compensation events are made on the assumption that the contractor reacts competently and promptly to the event, that the accepted programme can be changed, and that additional cost reasonably incurred will be included. This clause is short. Its commercial weight is substantial.
The critical phrase is "reacts competently and promptly." This does not mean the contractor must do everything possible to eliminate delay. It means the contractor must do what a competent contractor would reasonably do in the circumstances to reduce the time effect of the event, without being disadvantaged commercially.
In practice, this translates to three obligations. First, the contractor should consider whether the remaining work can be re-sequenced to reduce the delay. Moving non-critical activities ahead of delayed critical activities, changing the order of work within a section, or bringing forward procurement that would otherwise have waited. Second, the contractor should consider whether parallel working is possible where the original plan was sequential. Third, the contractor should consider whether resource allocation can be adjusted to prioritise the affected work.
These are planning decisions, not financial commitments. They involve rearranging the programme to optimise the remaining sequence in light of the event that has occurred. They should not involve the contractor spending more money than it would have spent under the original programme, working longer hours than the original programme assumed, or taking on additional risk that the original programme did not include.
If the contractor fails to take reasonable mitigation steps, the compensation event assessment will be reduced to reflect the mitigation that should have occurred. The assessment assumes competent mitigation happened, whether or not it actually did. A contractor who submits a quotation showing full delay without any mitigation analysis is inviting the project manager to reduce the assessment on the grounds that the contractor should have done more.
This is why every compensation event quotation should include a mitigation statement. The statement should describe what mitigation was considered, what was implemented, and what residual delay remains after mitigation. If mitigation was not possible, the statement should explain why. This protects the quotation against reduction and demonstrates to the project manager that the contractor has applied the competent and prompt standard the contract expects. The article on NEC delay analysis and extension of time covers the clause 63.8 assessment mechanism in detail.
The voluntary mechanism: what clause 36 provides
Clause 36 is the NEC contract's acceleration mechanism, and it is designed around a principle that contractors should understand clearly: acceleration cannot be imposed.
Under NEC4, either party may propose acceleration to achieve completion before the completion date. If both parties are willing to consider it, the project manager instructs the contractor to submit a quotation for the acceleration. The contractor has three weeks to provide the quotation. The quotation must include proposed changes to the prices and a revised programme showing the earlier completion date.
Under NEC3, only the project manager could instruct a quotation for acceleration. NEC4 opened the proposal to either party, but the mechanism remains fundamentally voluntary. The contractor can decline to provide a quotation, or can provide a quotation that the project manager may choose not to accept. The project manager cannot make their own assessment of the acceleration quotation. This is a deliberate and significant design choice. Unlike compensation event quotations, where the project manager can assess the event themselves under clause 64 if they are not satisfied with the contractor's quotation, acceleration quotations are either accepted or rejected. The PM has no power to impose a lower price or a different programme for acceleration.
The reason for this design is practical. Acceleration involves the contractor taking on additional risk and cost: overtime working, additional plant, compressed sequences, double shifts, weekend work, out-of-sequence procurement. The contractor is the only party who can genuinely assess the cost and risk of these measures, and the contract recognises this by giving the contractor pricing control. A project manager who imposes acceleration costs based on their own view of what is reasonable is almost always wrong about the risk, which is why the contract does not allow it.
If the quotation is accepted, the revised programme becomes the accepted programme, the completion date is brought forward, and the prices are adjusted. The contractor is then contractually obliged to achieve the new earlier completion date.
Where the line sits: mitigation versus acceleration
The commercial significance of NEC programme acceleration and mitigation comes down to one question: is the contractor being asked to recover time at no additional cost (mitigation), or is the contractor being asked to recover time at additional cost (acceleration)?
Mitigation involves rearranging the programme to reduce delay using the existing resources, sequences, and working patterns available to the contractor. It costs the contractor nothing additional. It is an obligation, not a favour. It is built into every compensation event assessment.
Acceleration involves spending money, adding resources, or taking on risk that the contractor would not have incurred under the original programme. It is always at additional cost. It is never an obligation. It is always subject to agreement and separate payment.
The difficulty is that on a live project, the line between the two is rarely clean. A project manager who asks the contractor to "recover the programme" may genuinely not know whether they are asking for mitigation or acceleration. The contractor who responds without understanding the distinction may end up doing acceleration work at mitigation prices, which means doing it for free.
Three practical tests help determine which side of the line a request falls on.
First, does the recovery involve additional cost? If the contractor can recover the programme by re-sequencing work within the existing resource and budget, that is mitigation. If the contractor needs to add labour, extend working hours, or bring in additional plant, that is acceleration.
Second, does the recovery involve additional risk? If the contractor is being asked to compress a sequence that was originally planned with reasonable contingency, and the compression creates risk of quality problems, rework, or further delay, that is acceleration. Mitigation should not expose the contractor to additional risk.
Third, would a competent contractor do this without being asked? If the re-sequencing is the kind of thing any reasonable planner would do in response to the event, it is mitigation. If it requires a deliberate commercial decision to spend money or accept risk, it is acceleration.
These tests are not absolute. They will not resolve every borderline case. But they provide a framework for thinking about the distinction that most contractors lack, and they protect against the two most common mistakes: treating acceleration as mitigation and treating mitigation as acceleration.
The trap: giving away acceleration as mitigation
The most common commercial mistake on delayed NEC projects is the contractor who accelerates without realising they are entitled to a separate quotation.
The pattern is familiar. The project is behind programme. The project manager applies pressure. The contractor responds by adding resources, working weekends, compressing testing and commissioning. The programme recovers. The project manager is satisfied. The contractor absorbs the cost as overhead because nobody identified the recovery measures as acceleration.
This happens because the conversation about recovery is almost always framed as an obligation. The project manager says "you need to get back on programme." The contractor hears "I am required to do this." The contractor does not distinguish between re-sequencing the work (mitigation, which is an obligation) and adding a Saturday shift (acceleration, which is compensable).
The remedy is to separate the two conversations at the point they arise. When the project manager requests recovery, the contractor should respond with two things. First, a revised programme showing what mitigation is possible through re-sequencing and reprioritisation alone. This is the contractor's obligatory response. Second, if the mitigation alone is not sufficient to recover the programme, a statement that further recovery requires acceleration measures, and an offer to provide a quotation under clause 36.
This separation protects the contractor in two ways. The mitigation programme demonstrates that the contractor has met the clause 63.8 standard, which protects compensation event assessments. The clause 36 offer demonstrates that the contractor understands the boundary and is not willing to accelerate for free. If the project manager wants the additional recovery, they can instruct the quotation. If they do not, the contractor's position is clear: mitigation has been done, the residual delay is a consequence of the compensation event, and the contractor is entitled to the corresponding extension of time.
The other trap: refusing to mitigate
The second most common mistake is the contractor who refuses to re-sequence work on the grounds that it constitutes acceleration, when it is actually reasonable mitigation that the contract requires.
This usually happens when the contractor has been burned before, giving away recovery measures without payment, and has overcorrected by treating every request for programme adjustment as an acceleration demand. The project manager asks the contractor to move a non-critical activity ahead of a delayed critical activity. The contractor says "that is acceleration and we want a quotation." The project manager says "that is basic programme management and you are obliged to do it." Neither party is entirely wrong, but the contractor has picked the wrong battle.
Re-sequencing work within the existing resource envelope, without additional cost or risk, is mitigation. The contractor is obliged to do it under the clause 63.8 assumption, and refusing to do it does not protect the contractor's position. It weakens it. The compensation event assessment will assume the mitigation happened regardless, which means the contractor gets a lower entitlement and still has to do the work.
The correct approach is to do the mitigation, record it in the programme, and explain it in the compensation event quotation as part of the mitigation statement. The quotation then shows: here is the compensation event, here is the mitigation we implemented, and here is the residual delay after mitigation. The contractor gets credit for mitigating and retains entitlement for the delay that remains.
The contractor who refuses to mitigate gets the worst of both worlds: a reduced assessment (because the assessment assumes mitigation anyway) and a damaged relationship with the project manager (because the contractor appears uncooperative).
How to present acceleration in the programme
When acceleration is agreed under clause 36, it must be shown in a revised programme that becomes the new accepted programme. This programme needs to be credible, achievable, and honest about the risk the contractor is taking on.
A common mistake is to produce an acceleration programme that simply compresses durations without showing how the compression will be achieved. An acceleration programme that shows a twelve-week activity reduced to eight weeks without explaining the additional resources, the extended working hours, or the parallel sequences that make the reduction possible is not credible. The project manager may reject it, or worse, accept it and then hold the contractor to dates that were never achievable.
A good acceleration programme shows three things. First, the baseline position: what the programme would look like without acceleration, based on mitigation alone. Second, the acceleration measures: the specific changes in resource, sequence, working patterns, or methodology that produce the earlier completion. Third, the risk: what could go wrong with the accelerated programme and what contingency the contractor has carried.
This structure protects the contractor because it creates a clear record of what was agreed, what was assumed, and what the contractor was paid to achieve. If the acceleration fails because of a subsequent compensation event, the contractor can point to the baseline position and demonstrate that the event, not the acceleration failure, caused the delay. Without this structure, the causes become entangled and the contractor's position is harder to defend.
The acceleration programme should also be consistent with the pricing. If the quotation includes costs for an additional crane, the programme should show activities that require the crane. If the quotation includes weekend working, the programme should show a six- or seven-day calendar on the affected activities. Inconsistency between programme and pricing is one of the fastest ways to lose credibility with the project manager and, if challenged later, with an adjudicator.
The early warning connection
Early warnings under clause 15 (clause 16 in NEC3) are not a separate mechanism from mitigation and acceleration. They are the mechanism by which mitigation and acceleration conversations should begin.
Clause 15.1 requires both parties to notify events that could affect time, cost, or quality. When a compensation event occurs and the contractor identifies a time risk, the early warning should be the first notification, before the formal compensation event notification under clause 61.3. The early warning triggers a risk reduction meeting under clause 15.2, where both parties discuss how to mitigate the effect.
This matters for the acceleration and mitigation distinction because the risk reduction meeting is the right place to separate the two. The contractor presents the event, the likely impact, and the mitigation options. If mitigation alone is insufficient, the contractor states that further recovery would require acceleration and offers to provide a quotation under clause 36. The conversation happens early, before positions harden, and before the project manager has started to treat the delay as the contractor's problem to fix at the contractor's cost.
Contractors who skip early warnings and go straight to compensation event notification miss this opportunity. By the time the formal CE process is underway, the conversation about mitigation and acceleration has become adversarial. The project manager wants the contractor to recover the programme. The contractor wants to protect its entitlement. Neither party has had the collaborative discussion that might have identified a practical solution.
If the contractor notifies an early warning and the PM fails to call a risk reduction meeting, that failure is itself recorded. If the PM later argues that the contractor should have mitigated more aggressively, the contractor can point to the early warning and the absence of a risk reduction meeting as evidence that the PM did not engage with the mitigation discussion when it was offered.
Clause 63.7 of NEC4 (clause 63.5 in NEC3) reinforces this by allowing the PM to assess a compensation event as if an early warning had been given, if the contractor failed to give one. This means the PM can reduce the assessment on the basis that earlier notification would have enabled earlier mitigation. The contractor who gives early warnings consistently removes this risk entirely.
What happens when the PM calls mitigation "acceleration" and vice versa
Mischaracterisation in both directions is common, and both directions cost the contractor money.
When the project manager describes acceleration as mitigation, the PM is asking the contractor to spend money without payment. The contractor's response should be clear: "we have mitigated by re-sequencing the programme. The remaining recovery requires acceleration measures, and we would be happy to provide a quotation under clause 36." This is not confrontational. It is contractually precise. It identifies the boundary and invites the PM to proceed through the correct route.
When the project manager describes mitigation as acceleration, the PM is offering to pay for something the contractor is obliged to do for free. This sounds like a gift, but it is a trap. If the contractor accepts payment for mitigation under a clause 36 arrangement, the contractor has accepted a revised completion date that is earlier than the one mitigation alone would have achieved. The contractor is then obliged to meet that earlier date. If a subsequent compensation event occurs, the contractor's entitlement is measured from the accelerated programme, not the mitigated one. The contractor has inadvertently reduced its own future entitlement by agreeing to acceleration terms for work that was already required.
The correct response is to distinguish the two explicitly. Mitigation is done as part of the compensation event process and does not change the completion date beyond what the event and the mitigation together produce. Acceleration is a separate agreement that changes the completion date by a further amount, at additional cost. Keeping the two separate in the programme, in the quotation, and in the contractual record is essential for protecting entitlement through the rest of the project.
Programme records that protect the position
Whether the contractor is mitigating or accelerating, the commercial position is only as strong as the records that support it.
For mitigation, the programme revision should show the re-sequenced work as visible changes to the accepted programme. The narrative should explain what mitigation was considered, what was implemented, and what residual delay remains. The compensation event quotation should include the mitigation statement, the residual impact programme, and the remaining duration to planned completion after mitigation. The article on clause 32 programme revision covers the revision discipline that supports this.
For acceleration, the records should include the clause 36 quotation with the proposed changes to prices, the revised programme showing the acceleration measures and the earlier completion date, the project manager's acceptance, and the programme update that implements the accepted acceleration. All of these should be filed as a single package so that the acceleration agreement is traceable if a subsequent event affects the accelerated programme.
The most important record in both cases is the baseline programme immediately before the event occurred. This is the snapshot that shows what the programme would have looked like without the compensation event, without the mitigation, and without the acceleration. Every subsequent analysis of entitlement depends on this snapshot. The article on NEC delay analysis and extension of time explains why the accepted programme at the dividing date determines the quality of the contractor's time entitlement.
NEC programme acceleration and mitigation: the argument in short"
NEC programme acceleration and mitigation are not the same thing, and treating them as interchangeable is one of the most expensive mistakes a contractor can make on an NEC project.
Mitigation is an obligation. It involves re-sequencing work to reduce delay within the existing resource and budget. It costs the contractor nothing additional. It is built into every compensation event assessment under clause 63.8. Refusing to mitigate does not protect the contractor's position. It weakens it.
Acceleration is voluntary. It involves spending money, adding resources, or taking on risk to recover time beyond what mitigation alone can achieve. It is always at additional cost. It cannot be imposed. It is subject to agreement and payment under clause 36.
The contractors who manage NEC projects well separate the two at the point they arise. They mitigate as part of every compensation event response, record the mitigation in the programme and the quotation, and present the residual delay honestly. When recovery beyond mitigation is needed, they offer a clause 36 quotation rather than absorbing acceleration costs as overhead. They use early warnings to start the conversation before positions harden. And they keep the programme records that protect both the mitigation and the acceleration as traceable, defensible commercial events.
The discipline is not complicated. The boundary between the two concepts is not always sharp. But understanding where it sits, and acting accordingly, is the difference between recovering what the contract provides and giving it away through confusion.
FAQ
What is the difference between mitigation and acceleration under NEC?
Mitigation is re-sequencing or reprioritising work to reduce delay within the existing resource and budget. It costs the contractor nothing additional and is an obligation under clause 63.8: compensation event assessments assume the contractor mitigated competently whether or not they actually did. Acceleration involves additional cost, such as overtime, extra plant, weekend working, or compressed sequences, to recover time beyond what mitigation alone can achieve. Acceleration is voluntary and is agreed under clause 36, with the contractor providing a quotation that the project manager can accept or reject but cannot assess themselves.
Can the project manager force acceleration under NEC?
No. Clause 36 is a voluntary mechanism. Under NEC4, either party may propose acceleration, but the contractor can decline to provide a quotation. The project manager cannot make their own assessment of an acceleration quotation, unlike compensation event quotations. This design protects the contractor from having acceleration costs imposed at the PM's estimate rather than the contractor's own assessment of cost and risk.
What does "reacts competently and promptly" mean under clause 63.8?
It means the compensation event assessment assumes the contractor took reasonable steps to reduce the time effect of the event through re-sequencing, reprioritisation, or resource reallocation within the existing programme. If the contractor could have reduced the delay through reasonable mitigation but did not, the assessment is reduced to reflect the mitigation that should have occurred. The standard is competent, not exceptional: the contractor is expected to do what a reasonable contractor would do, not what a heroic contractor might do.
Should the contractor include mitigation in compensation event quotations?
Yes. Every quotation should include a mitigation statement describing what mitigation was considered, what was implemented, and what residual delay remains after mitigation. If mitigation was not possible, the quotation should explain why. This protects the quotation against reduction by the project manager on the basis that the contractor should have mitigated more.
What changed between NEC3 and NEC4 on acceleration?
Under NEC3, only the project manager could instruct a quotation for acceleration. Under NEC4, either party may propose acceleration, but both parties must be willing to consider it before the quotation process begins. The timescales are now defined: three weeks for the contractor to provide the quotation, three weeks for the project manager to respond. The fundamental principle remains: acceleration is voluntary and cannot be imposed.
How should acceleration measures be shown in the programme?
The acceleration programme submitted under clause 36 should show three things: the baseline position without acceleration (what mitigation alone achieves), the acceleration measures themselves (additional resources, extended hours, compressed sequences), and the risk the contractor has carried. The programme should be consistent with the pricing: if the quotation includes costs for weekend working, the programme should show a six- or seven-day calendar on the affected activities. Inconsistency between programme and pricing weakens the contractor's position.
What is the role of early warnings in mitigation and acceleration?
Early warnings under clause 15 are the mechanism by which mitigation and acceleration conversations should begin. The early warning notifies the risk. The risk reduction meeting under clause 15.2 is the place to discuss mitigation options and, if mitigation is insufficient, to identify that further recovery requires acceleration under clause 36. Contractors who give early warnings consistently also protect themselves against clause 63.7, which allows the PM to reduce an assessment on the basis that earlier notification would have enabled earlier mitigation.
What happens if the contractor accelerates without a clause 36 agreement?
The contractor absorbs the cost. Without a formal clause 36 quotation and acceptance, the acceleration measures are treated as the contractor's own choice. The contractor has no contractual entitlement to recover the additional cost, and the programme showing the earlier completion may become the baseline against which future compensation events are assessed, potentially reducing the contractor's future entitlement. This is why informal acceleration without a clause 36 agreement is commercially dangerous.
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.
Need support with programme recovery or acceleration quotations?
If the programme is behind, mitigation options need to be identified, or an acceleration quotation needs to be produced under clause 36, specialist NEC programme support provides the analysis and the programme evidence to protect the contractor's commercial position.
