What Is a Variation Order in Construction? VO vs CE Explained

<div class="ge-article-wrapper"><nav class="ge-toc" aria-label="Table of contents"><p class="ge-toc-label">In this article</p><ul class="ge-toc-list"><li><a href="#the-definition">The Definition</a></li><li><a href="#the-variation-process-under-traditional-contracts">The Variation Process Under Traditional Contracts</a></li><li><a href="#worked-example-jct-variation-vs-nec4-compensation-event">Worked Example: JCT Variation vs NEC4 Compensation Event</a></li><li><a href="#why-variations-matter-for-evm">Why Variations Matter for EVM</a></li><li><a href="#common-mistakes">Common Mistakes</a></li><li><a href="#frequently-asked-questions">Frequently Asked Questions</a></li></ul></nav><article class="ge-article-body"><p>A variation order (VO) is a formal instruction from the client or contract administrator that changes the scope, cost, or timeline of a construction contract. Under JCT and many traditional contract forms, VOs are the standard mechanism for managing change. Under NEC4, the concept doesn't exist, it's been replaced entirely by the <a href="/en/earned-value/definitions/compensation-event">compensation event</a> mechanism, which works quite differently. If you're running <a href="/en/earned-value">earned value management</a> on your project, understanding how variations feed into your budget baseline is critical, because a VO that isn't reflected in your <a href="/en/earned-value/definitions/budget-at-completion">BAC</a> will corrupt every metric downstream.</p><p>Variation orders are covered in the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For how scope changes affect EVM baselines specifically, see the <a href="/en/earned-value/formulas">earned value formulas page</a>.</p><h2 id="the-definition">The Definition</h2><div class="ge-formula-box ge-anim"><span class="ge-formula-label">Formula</span><code>A variation order is a formal instruction that modifies the original scope of works, resulting in a change to the contract sum and/or the completion date.</code></div><p>On JCT contracts, variations are issued under clause 3.14 (JCT DB 2016) or clause 5.1 (JCT SBC 2016). The architect or contract administrator instructs the variation. The QS values it using the contract rates or, where rates don't apply, fair rates and prices.</p><p>On NEC4 contracts, there's no such thing as a variation order. Stop calling them that. The equivalent is a compensation event, and the process, valuation method, and programme implications are fundamentally different.</p><h2 id="the-variation-process-under-traditional-contracts">The Variation Process Under Traditional Contracts</h2><pre class="ge-ascii-diagram ge-anim">VARIATION ORDER PROCESS FLOW (JCT) ========================================== CLIENT / ARCHITECT CONTRACTOR | | | 1. Instruction issued | | (clause 3.14 JCT DB) | |-----------------------------------&gt;| | | | 2. Contractor prices variation | | using contract rates or | | fair rates and prices | |&lt;-----------------------------------| | | | 3. QS reviews and agrees | | or negotiates valuation | |&lt;=================================&gt;| | | | 4. VO valued and agreed | | Contract sum adjusted | |-----------------------------------&gt;| | | | 5. Work executed | | (may start before valuation | | is agreed) | | | | 6. Included in interim | | application and final account | |&lt;-----------------------------------| NEC4 EQUIVALENT (Compensation Event) ========================================== PROJECT MANAGER CONTRACTOR | | | 1. PM gives instruction or | | Contractor notifies event | | (clause 61.1-61.3) | |&lt;=================================&gt;| | | | 2. PM instructs Contractor to | | submit quotation (clause 61.1) | |-----------------------------------&gt;| | | | 3. Contractor submits quotation | | within 3 WEEKS (clause 62.3) | | Based on FORECAST, not actuals | |&lt;-----------------------------------| | | | 4. PM accepts/rejects within | | 2 WEEKS (clause 62.3) | |-----------------------------------&gt;| | | | 5. CE implemented (clause 65) | | Prices and programme adjusted | | PROSPECTIVELY from dividing | | date | | |</pre><p>The critical differences: NEC4 requires quotation based on forecast costs (not actual costs), has strict time bars, and adjusts both the Prices and the programme in one mechanism. JCT variations are valued retrospectively and don't formally adjust the programme.</p><h2 id="worked-example-jct-variation-vs-nec4-compensation-event">Worked Example: JCT Variation vs NEC4 Compensation Event</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A client instructs additional acoustic treatment to conference rooms on a £10M office fit-out. The additional work is valued at £200K.</p><p><strong>Under JCT Design &amp; Build 2016:</strong></p><ul><li>The Employer's Agent issues an instruction under clause 3.14 on 10 March 2026</li><li>The Contractor prices the variation at £215,000 using measured rates</li><li>The QS reviews and negotiates down to £200,000 (agreed 28 March)</li><li>The Contract Sum adjusts from £10,000,000 to £10,200,000</li><li>The Contractor includes £200K in the next interim valuation</li><li>If the work delays completion, the Contractor applies for an extension of time under clause 2.26</li></ul><p><strong>Under NEC4 Option A:</strong></p><ul><li>The Project Manager gives an instruction changing the Works Information on 10 March 2026. This is a compensation event under clause 60.1(1)</li><li>The PM instructs the Contractor to submit quotations (clause 61.1)</li><li>The Contractor submits a quotation within 3 weeks: £200,000 additional to the Prices, plus 2 weeks' delay to the Completion Date</li><li>The PM accepts the quotation within 2 weeks (clause 62.3)</li><li>The compensation event is implemented (clause 65): the activity schedule is updated, the total of the Prices increases by £200K, and the Completion Date moves by 2 weeks</li></ul><p><strong>EVM Impact (both contract forms):</strong></p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>EVM Metric</th><th>Before Change</th><th>After Change</th></tr></thead><tbody><tr><td>BAC</td><td>£10,000,000</td><td>£10,200,000</td></tr><tr><td><a href="/en/earned-value/definitions/planned-value">Planned Value</a> curve</td><td>Original baseline</td><td>Re-profiled to include new work</td></tr><tr><td>Control account CA-006 budget</td><td>£1,400,000</td><td>£1,600,000</td></tr><tr><td><a href="/en/earned-value/definitions/undistributed-budget">Undistributed Budget</a></td><td>£0</td><td>£200K (until WPs created)</td></tr></tbody></table></div><p>On both contract forms, the £200K must be reflected in the EVM baseline. The difference is timing: on NEC4, the CE mechanism forces the baseline update when the quotation is implemented. On JCT, there's no contractual trigger, the commercial team has to discipline themselves to update BAC, and many don't.</p></div><h2 id="why-variations-matter-for-evm">Why Variations Matter for EVM</h2><p>Every variation or compensation event changes the project's scope, which means the <a href="/en/earned-value/definitions/undistributed-budget">Performance Measurement Baseline</a> must be updated. If it isn't, you get phantom variances, cost that looks like an overrun but is actually approved additional scope.</p><p>I've seen this wreck EVM credibility on a £40M hospital project. The commercial team had processed 34 variations worth £3.1M through the final account but hadn't updated the EVM baseline for any of them. The <a href="/en/earned-value/definitions/cost-performance-index">CPI</a> was showing 0.84, which looked catastrophic. Once the baseline was corrected, CPI was 0.96, a completely different commercial picture. The project director had been making decisions based on wrong data for 6 months.</p><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Calling NEC4 compensation events "variations."</strong> This matters. They're not the same mechanism, and using the wrong term leads to wrong processes. CEs are forecast-based, time-barred, and adjust the Prices. VOs are retrospective, not time-barred (in most JCT forms), and adjust the contract sum. The language matters because the process matters.</li><li><strong>Not updating the EVM baseline after variations.</strong> I've covered this above, but it's worth repeating: every agreed VO or implemented CE must flow into BAC. If your EVM system doesn't have a formal process for this, build one. The <a href="/en/earned-value/common-mistakes">common mistakes</a> page covers this in more detail.</li><li><strong>Proceeding with work before the VO is formalised.</strong> On JCT contracts, verbal instructions happen constantly. "Just crack on, we'll sort the paperwork later." Six months later, nobody can agree on the scope or the valuation. If you start work without a formal instruction, document everything contemporaneously and confirm the instruction in writing within 7 days.</li><li><strong>Valuing variations without considering programme impact.</strong> A £200K variation that adds 4 weeks to the critical path doesn't cost £200K. It costs £200K plus the prelim and overhead costs of the delay. On EVM, the BAC increase should include both the direct work and the time-related costs.</li></ol><div class="ge-product-note ge-anim"><p><strong>How Gather helps.</strong> Gather's AI reads your site diaries daily and maps progress against your cost-loaded programme, giving you accurate earned value data without manual spreadsheet updates. <a href="https://gatherinsights.com/contact">Book a demo</a> to see it working on a live NEC4 project.</p></div><h2 id="frequently-asked-questions">Frequently Asked Questions</h2><h3>Is a variation order the same as a change order?</h3><p>Essentially yes. "Variation order" is the standard UK term (used in JCT and FIDIC contracts). "Change order" is the US and international equivalent (used in AIA contracts and many US government contracts). Both describe a formal instruction to change the scope of works. The mechanics differ by contract form, but the concept is the same.</p><h3>How do variation orders affect the critical path?</h3><p>That depends on the work. A VO for additional finishes to an already-constructed room might have zero impact on the programme. A VO for additional piling before the superstructure can start extends the critical path directly. Under JCT, the Contractor claims an extension of time. Under NEC4, the compensation event quotation must include the delay impact on the <a href="/en/earned-value/definitions/accepted-programme">Accepted Programme</a>, and the Completion Date adjusts when the CE is implemented.</p><h3>What if the contractor disagrees with the valuation?</h3><p>Under JCT, if the QS's valuation and the Contractor's pricing can't be agreed, the matter goes to the dispute resolution mechanism (typically adjudication under the Housing Grants, Construction and Regeneration Act 1996). Under NEC4, if the PM rejects the Contractor's quotation or doesn't respond within 2 weeks, the PM makes their own assessment, which the Contractor can then dispute through the W1 or W2 dispute resolution procedure.</p><h3>Do oral instructions count as variation orders?</h3><p>Under most JCT forms, oral instructions can constitute valid instructions if confirmed in writing within a reasonable time. Under NEC4, all instructions must be in writing (clause 13.1). In practice, oral instructions happen constantly on site. The commercial risk is on the Contractor to confirm them in writing promptly. If you don't, proving the instruction was given becomes very difficult at final account stage.</p></article></div>