NEC4 compensation events: how to get quotations agreed and what makes them acceptable to the project manager
- Feb 10
- 17 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 question that contractors ask their planning teams hundreds of times across the life of an NEC project: how do we get this compensation event quotation agreed? The question is asked with the same urgency every time, often when a quotation has already been rejected once or twice, and the commercial team is searching for the additional element that will finally produce acceptance. The answer is usually framed as a list: include more cost detail, expand the time impact assessment, add more supporting evidence, write a fuller narrative.
This framing is wrong. The question itself is wrong.
The strongest contractors do not ask how to get a quotation agreed. They ask what makes a quotation acceptable to a project manager who wants to accept it and what makes a quotation rejectable by a project manager who is looking for reasons to reject. These are different questions, and they produce different answers. The first question optimises for completeness. The second question optimises for acceptability. The two are not the same, and the difference between them is the difference between a quotation that lands on the project manager's desk and gets accepted in fifteen minutes and one that lands on the same desk and produces two weeks of revision cycles.
Most NEC4 commentary on compensation event quotations focuses on the contractor's submission: what should be included, how it should be structured, what timeframes apply. This is necessary but insufficient. The acceptance decision is made by the project manager, not by the contractor. The submission is the input. The acceptance is the output. The contractor who designs their quotation around the contractor's desire to recover entitlement produces submissions that are technically complete but acceptance-resistant. The contractor who designs their quotation around the project manager's review experience produces submissions that the project manager can accept directly, often within the first review cycle.
This article explains what makes an NEC4 compensation event quotation genuinely acceptable to the project manager, why most quotations fail not on substance but on structure, and how contractors who reframe their submissions from completeness to acceptability transform their compensation event recovery rates over the life of a project.
What the project manager is actually doing when reviewing a quotation
A project manager reviewing a contractor's compensation event quotation is performing a specific contractual function with limited time. They are typically reviewing five to ten quotations simultaneously across multiple projects. Each quotation arrives as a package that must be evaluated against clauses 63.1 to 63.10 within the contractual response period under clause 62.3. The project manager's options under clause 62 are constrained: accept the quotation, instruct a revised quotation, notify that the proposed event is not a compensation event, or notify that they will make their own assessment under clause 64.
The project manager's strong default preference is acceptance. Acceptance is procedurally efficient. It moves the project forward. It avoids the workload of either instructing revisions (which produces another review cycle) or making their own assessment (which transfers significant additional work to the project manager). Acceptance is also the lowest-risk option for the project manager institutionally, because it confirms the contractor's analysis rather than substituting the project manager's view.
What prevents acceptance is rarely a substantive disagreement with the contractor's conclusion. It is the inability to verify the conclusion within the time available. A project manager who cannot trace the contractor's analysis from the dividing date through the schedule logic to the cost calculation in the time available will not accept the quotation, because acceptance creates exposure they cannot contain. The default in those cases is to instruct a revised quotation with comments, kicking the package back to the contractor and resetting the review clock.
This is the structural insight that most contractors miss. The project manager is not an adversary trying to find reasons to reject. The project manager is a busy practitioner trying to find a path to acceptance and being prevented from doing so by quotations that do not give them that path. The contractor who designs the quotation as a path to acceptance, with each element placed to allow the project manager to verify it efficiently, transforms the dynamic. Acceptance becomes the easy choice. Rejection requires positive effort.
Why most NEC4 compensation event quotations are acceptance-resistant
The majority of compensation event quotations submitted on UK NEC projects are constructed in a way that makes acceptance harder than it should be. Five specific structural failures recur across thousands of submissions, and each has the same effect: it forces the project manager to do work the contractor should have done, and the response is rejection or instruction to revise rather than acceptance.
Failure one: the dividing date is not stated explicitly. The project manager has to work out from the cover correspondence and the supporting documents which date the contractor is using as the reference point for the assessment. Where the dividing date is ambiguous or unsupported by clear contractual reference, the project manager has procedural grounds to reject before engaging with the substance.
Failure two: the accepted programme used is not identified. Clause 63.5 requires the assessment to use the accepted programme current at the dividing date. Many quotations do not specify which version of the accepted programme is being used, leaving the project manager to infer it from context. This is grounds for rejection on its own under clause 64.1's "not correctly assessed" trigger, even before the substance is examined.
Failure three: the time impact and cost impact are not internally consistent. The time impact assessment shows six weeks of additional site activity. The cost assessment shows preliminaries for four weeks. The two halves of the same quotation tell different stories. A project manager spotting this inconsistency cannot accept the quotation as submitted, because acceptance would mean accepting both numbers despite their inconsistency.
Failure four: assumptions are buried rather than declared. The contractor's assessment depends on assumptions about resource availability, programme sequence, weather, subcontractor mobilisation, and many other variables. These assumptions exist whether or not they are stated. When they are buried inside spreadsheets or implied by activity logic, the project manager cannot evaluate them. When they are declared explicitly at the front of the quotation, the project manager can evaluate each one and accept or challenge it specifically. Acceptance is much easier when assumptions are visible than when they are hidden.
Failure five: the supporting evidence is unindexed. The quotation references an instruction, an RFI, a meeting minute, a site record. The project manager has to find each of these in their own files or wait for the contractor to provide them. Where the supporting evidence is indexed in the quotation with clear references and ideally provided as appendices, the project manager can verify each evidential point in seconds. Where it is not indexed, verification becomes its own project.
These five failures account for the majority of quotation rejections. None of them is a substantive disagreement about the underlying analysis. All of them are procedural failures that prevent the project manager from accepting a quotation they would otherwise accept. The article on how to structure a time impact assessment under NEC4 covers the structural elements that prevent the time-side failures. The cost-side failures follow the same pattern: declare the basis explicitly, anchor it to verifiable evidence, present it in a form the project manager can review efficiently.
What an acceptance-optimised quotation looks like
An NEC4 compensation event quotation designed for acceptance has a recognisable structure. It contains the same information as a conventional quotation, organised in a way that allows the project manager to verify each element in the order they will look at it.
The structure has six elements.
Element one: the cover page. The cover identifies the compensation event with the CE reference number, the clause 60.1 ground, the dividing date with explicit justification, the accepted programme version being used (with acceptance date), the headline figures (time impact and cost impact), and the decision the project manager is being asked to make. This page should fit on a single sheet and be readable in thirty seconds. The project manager who reads only the cover page should know what the event is, what the contractor is claiming, and what is being asked of them.
Element two: the assumptions register. Five to ten assumptions, each tied to a specific element of the assessment. Each assumption should be testable: the project manager can either agree with it or identify why they disagree. Assumptions about resource availability, weather, subcontractor mobilisation, sequence of activities, lead times, and method should be declared explicitly. The assumptions register protects the contractor by making the basis of the assessment visible. It protects the project manager by giving them a finite list to evaluate.
Element three: the time impact assessment. Built using the structural elements covered in detail in how to structure a time impact assessment under NEC4. The dividing date and accepted programme are stated explicitly. The fragnet shows the event's specific impact in isolation. The impacted programme shows the calculation of the time impact. The narrative explains the cause and effect chain in prose the project manager can follow without opening the programme files.
Element four: the cost build-up. Constructed using the schedule of cost components for the relevant option. Anchored to the time impact: if the time impact shows six weeks of additional activity, the cost build-up shows the cost of those six weeks. Anchored to evidence: each cost line traceable to a quote, a rate, a record. Anchored to the assumptions register: if a cost line depends on a stated assumption, the cost line references the assumption.
Element five: the supporting evidence index. A numbered list of every piece of evidence cited in the quotation, with a clear reference and ideally a copy provided as an appendix. The project manager wanting to verify any specific point can find it in seconds rather than minutes.
Element six: the decision request. A short statement of what is being asked of the project manager: accept the quotation as submitted, accept with stated comments, or instruct revisions on a specific basis. This is not a procedural nicety. It is a focusing element that tells the project manager what response is appropriate, which guides them toward the acceptance path rather than the revision path.
These six elements are the same content most contractors already include in quotations. The difference is the placement and the explicit framing. An acceptance-optimised quotation gives the project manager every element they need to verify the assessment in the order they will look at them, with no element buried, no element implied, and no element requiring the project manager to do work that should have been done by the contractor.
The relationship between quotation acceptability and clause 64
The acceptability of compensation event quotations connects directly to the project manager's clause 64 power. Under clause 64.1, the project manager makes their own assessment of a compensation event in four circumstances. The second of those circumstances is when the project manager decides that the contractor has not assessed the compensation event correctly, and the project manager does not instruct a revised quotation.
This trigger is meaningfully different from the others. It does not require the contractor to have failed to submit anything. It activates when the contractor has submitted a quotation that the project manager judges has not been correctly assessed. The judgement is the project manager's, and the standard is whether the assessment complies with clauses 63.1 to 63.10.
A quotation with the five structural failures described above is genuinely vulnerable to clause 64 activation under the second trigger. The project manager can credibly argue that the assessment has not been correctly produced because the dividing date is ambiguous, the accepted programme reference is missing, the time and cost elements are inconsistent, the assumptions are not visible, or the evidence is not indexed. Each of these procedural failures can be characterised as a failure to comply with the assessment rules, even if the underlying analysis is sound.
The contractor whose quotations are acceptance-optimised removes this risk entirely. There is no procedural ground for the project manager to characterise the assessment as not correctly produced. The dividing date is stated. The accepted programme is identified. The time and cost elements are consistent. The assumptions are explicit. The evidence is indexed. The project manager who wants to invoke clause 64 has to do so on substantive grounds, which are much harder to sustain. The article on NEC4 clause 64 covers the switching mechanism in detail.
This is the practical link between quotation structure and commercial control. Acceptance-optimised quotations preserve the contractor's control of valuation. Acceptance-resistant quotations create the conditions for that control to switch to the project manager. The structural difference between the two approaches is small. The commercial difference compounds across every event in the project.
The CE clock as an acceptance discipline, not an administrative discipline
Most contractors run a CE clock as an administrative discipline: a tracker that records what has been notified, what has been quoted, when each event was implemented. This is necessary but insufficient. The CE clock that produces acceptance is run as a forward-looking discipline that drives quotation quality, not just a backward-looking record of activity.
The acceptance-driven CE clock tracks the same dates as the administrative clock: awareness, notification, quotation due, quotation submitted, project manager response due, project manager response, implementation. But it adds three operational disciplines that change how quotations are produced.
The first is forecast quotation production. As soon as a compensation event is notified, the planning and commercial teams produce a draft quotation, even if formal pricing is not yet possible. The draft establishes the dividing date, identifies the accepted programme, builds the fragnet, drafts the assumptions register, and identifies the evidence required. The forecast quotation is not for submission. It is for internal review, to identify where the assessment needs further work before formal submission.
The second is the pre-submission acceptance test. Before the quotation is submitted, a senior commercial reviewer applies the project manager's review test to the quotation. They read the cover page in thirty seconds. They check the dividing date and accepted programme references. They verify the time-cost consistency. They evaluate whether the assumptions are clear and the evidence indexed. If the quotation cannot pass this internal acceptance test, it is not submitted. It is revised first.
The third is the response monitoring discipline. Once the quotation is submitted, the project manager's response is tracked daily. If the project manager does not respond within the period for reply, the contractor invokes the failure-to-reply mechanism under clause 62.6, which under NEC4 produces deemed acceptance after a further two weeks. If the project manager responds with revision instructions, the contractor analyses the comments and prepares a revised quotation that addresses each comment specifically. If the project manager responds with acceptance, the implementation is processed promptly to lock in the position.
These three disciplines transform the CE clock from a tracker of past activity into a system that produces quotation acceptance as its primary output. Contractors who run the clock this way report that compensation event acceptance rates increase by 30 to 50 percent within the first three months of implementation, and the time from notification to implementation typically halves.
Recovery when quotations are routinely being rejected
Some contractors find themselves in a pattern where quotations are routinely rejected on first submission, often with vague reasons that do not point to specific actionable changes. The pattern is corrosive: each rejection produces revision work, the second submission addresses some issues but introduces others, and the cycle continues across multiple events simultaneously.
Recovery from this pattern is structural rather than tactical. Resolving individual rejections is necessary but insufficient. The contractor needs to address the underlying conditions that produce rejections in the first place.
The first step is a quotation audit. Take the most recent five rejected quotations and analyse the rejection reasons. The pattern of rejection reasons reveals which of the five structural failures is dominant. If most rejections cite "not adequately supported," the failure is in the evidence index. If most rejections cite "the methodology is unclear," the failure is in the assumptions register or the time impact structure. If most rejections cite "inconsistencies between cost and programme," the failure is in the consistency check between the two halves.
The second step is template restructuring. Once the dominant failure is identified, the contractor's quotation template is rebuilt to address it specifically. This is not just a formatting change. It is a structural change to how quotations are produced internally, with new sections, new mandatory checks, and new pre-submission review steps.
The third step is selective resubmission of historical events. Where compensation events are still open and the recovery is commercially significant, revised quotations using the new template can be submitted as updated submissions. The project manager who has been rejecting quotations under the old format often accepts the same underlying claims when presented in the new format, because the procedural grounds for rejection have been removed.
The fourth step is sustained discipline. Recovery from a rejection pattern takes three to six months of consistent execution. During that period, every quotation goes through the full pre-submission review. Acceptance rates improve gradually rather than dramatically. By month four or five, the contractor is operating in a different regime: most quotations are accepted on first or second submission, and the commercial position on the project has stabilised.
For contractors with multiple projects in this state simultaneously, specialist NEC programme support provides the systematic intervention that breaks the rejection pattern across the portfolio. The cost of the intervention is small compared to the cost of allowing rejection patterns to continue across the duration of multi-year programmes.
What good looks like across the project lifecycle
A contractor running compensation event quotations well across an NEC4 project shows a recognisable pattern.
In the first three months, the CE register fills with notified events that have moved through quotation to implementation cleanly. Acceptance rates on first submission run at 60 to 70 percent. Where revisions are instructed, the project manager's comments are specific and addressable, and revised quotations are accepted. The accepted programme is current and the dividing date discipline is consistently applied.
By month six, the CE register shows roughly fifteen to twenty events depending on project size, the majority implemented with agreed valuations rather than project manager assessments under clause 64. The cumulative agreed value reflects what the contractor expected the events to be worth. Disputes are rare and where they arise, the contractor's procedural position is strong because the quotation packages have been consistently structured.
By project completion, the CE register shows a complete record of every event with traceable assessments, agreed valuations, and clear evidence trails. The end-of-project commercial position reflects the sum of properly handled events rather than a forensic reconstruction. The project's commercial outturn is predictable rather than discovered.
This pattern is achievable on any NEC4 project. The disciplines that produce it are not technically demanding. They require consistent execution: every quotation built to the acceptance-optimised structure, every CE clock dating maintained, every pre-submission test applied, every project manager response tracked.
The disciplines that prevent it are also recognisable: quotations submitted as cost spreadsheets with attached narratives, dividing dates implied rather than stated, accepted programmes assumed rather than identified, assumptions buried rather than declared. These are the patterns that produce rejection cycles, clause 64 activations, and end-of-project commercial discoveries that nobody anticipated.
The structural difference between the two patterns is small. The compounding effect across the life of an NEC4 project is substantial.
The argument in short
The question contractors usually ask about NEC4 compensation event quotations is the wrong question. They ask how to get a specific quotation agreed. The right question is what makes a quotation acceptable to a project manager who wants to accept it and what makes a quotation rejectable by a project manager looking for reasons to reject. The first question optimises for completeness. The second question optimises for acceptability.
The project manager's default preference is acceptance. Acceptance is procedurally efficient, moves the project forward, and avoids the additional workload of revision instructions or own-assessment under clause 64. What prevents acceptance is rarely substantive disagreement. It is the inability to verify the contractor's analysis within the time available. The contractor who designs the quotation around the project manager's review experience transforms the dynamic. Acceptance becomes the easy choice. Rejection requires positive effort.
The five structural failures that make most quotations acceptance-resistant are: dividing date not stated explicitly, accepted programme version not identified, time and cost elements inconsistent, assumptions buried rather than declared, supporting evidence unindexed. None of these is a substantive failing. All are procedural failings that prevent acceptance. All are eliminable through structural changes to how quotations are produced.
An acceptance-optimised quotation has six elements: a cover page that summarises the event and the request, an assumptions register declaring the basis, a time impact assessment built to verifiable structural standards, a cost build-up internally consistent with the time impact, a supporting evidence index, and an explicit decision request. The same content most contractors already include, organised to allow the project manager to verify it efficiently and accept it directly.
Contractors who run the CE clock as an acceptance discipline rather than an administrative discipline produce quotations the project manager can accept on first submission. Acceptance rates of 60 to 70 percent on first submission are achievable. Time from notification to implementation typically halves compared to administrative-only CE clocks. Commercial control of valuation stays with the contractor by default, and the structural conditions for clause 64 activation rarely arise.
For contractors operating in a rejection pattern, recovery is possible but requires structural intervention rather than tactical fixes. A quotation audit identifies the dominant procedural failure. Template restructuring addresses it. Selective resubmission of historical events recovers what is recoverable. Sustained discipline over three to six months produces the new regime. The cost is modest. The commercial benefit compounds across every event in the remaining project.
NEC4 compensation event quotations work as the contract intended when contractors design them around acceptance rather than around their own desire to recover entitlement. The two are not in conflict. Acceptance is the route to entitlement recovery. Quotations that protect entitlement most reliably are the ones the project manager can accept.
FAQ
Why do NEC4 compensation event quotations get rejected?
Most rejections are procedural rather than substantive. The five structural failures that account for the majority of rejections are: dividing date not stated explicitly, accepted programme version not identified, time and cost elements internally inconsistent, assumptions buried rather than declared, and supporting evidence unindexed. None of these requires the project manager to disagree with the contractor's underlying analysis. All prevent the project manager from verifying the analysis within the time available, which forces them toward revision or own-assessment rather than acceptance.
What is the project manager's preference when reviewing a quotation?
Acceptance. Acceptance is procedurally efficient, moves the project forward, and avoids the workload of either instructing revisions or making their own assessment under clause 64. Project managers reach for rejection or revision when they cannot verify the contractor's analysis efficiently within the time available. A quotation designed to make verification efficient produces acceptance as the default response.
What is the structure of an acceptance-optimised NEC4 compensation event quotation?
Six elements: a cover page summarising the event and the request, an assumptions register declaring the basis, a time impact assessment built to verifiable structural standards (dividing date, accepted programme, fragnet, impacted programme, narrative), a cost build-up internally consistent with the time impact, a supporting evidence index, and an explicit decision request. The article on how to structure a time impact assessment under NEC4 covers the time-side structure in detail.
How does quotation structure connect to clause 64?
Clause 64.1 second trigger activates when the project manager decides the contractor has not assessed the compensation event correctly. A quotation with the five structural failures is genuinely vulnerable to this trigger because each failure can be characterised as a failure to comply with the assessment rules in clauses 63.1 to 63.10. An acceptance-optimised quotation removes these procedural grounds, leaving the project manager to disagree on substance rather than form, which is much harder to sustain.
What is a CE clock and how does it produce acceptance?
A CE clock is an integrated tracker of every compensation event from notification through to implementation. The acceptance-driven CE clock adds three disciplines to administrative tracking: forecast quotation production from notification, pre-submission acceptance testing before formal submission, and active response monitoring including invocation of the failure-to-reply mechanism under clause 62.6 when the project manager does not respond within the period for reply. Contractors who run the clock as an acceptance discipline typically report acceptance rates 30 to 50 percent higher than those running administrative-only tracking.
What does deemed acceptance under NEC4 clause 62.6 do?
If the project manager fails to reply to a quotation within the period for reply, the contractor can issue a notification of the failure. If the project manager fails to reply within two weeks of the notification, the quotation is treated as accepted and is implemented. This mechanism did 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.
How long does it take to recover from a rejection pattern?
Three to six months of sustained discipline. Recovery requires a quotation audit to identify the dominant procedural failure, template restructuring to address it, selective resubmission of historical events where commercially significant, and consistent execution on every new submission. Acceptance rates improve gradually rather than dramatically. By month four or five, the contractor is operating in a different regime where most quotations are accepted on first or second submission.
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.
The disciplines that produce quotation acceptance are operational, not legal.
NEC Planning Solutions builds CE clocks, restructures quotation templates, and embeds the pre-submission acceptance discipline that transforms compensation event recovery rates across the project lifecycle.
