Variations in Construction Contracts (UK): How to Price, Evidence, and Get Paid

If variation work is not tracked clearly, it often gets done but not paid in full.

For many subcontractors, the issue is not effort on site. The issue is weak commercial control: unclear instructions, missing records, and valuation lines that mix original scope and changed scope.

This guide explains a practical UK process for managing variations so they can move from instruction to agreement, then into your payment application with less friction.

What is a variation in construction contracts?

A variation is a change to the agreed scope, quality, sequence, or quantity of work under the contract.

In practice, it can include:

• additional work that was not in the original scope
• omitted work
• changed specification or materials
• changed sequence or access constraints that alter cost
• remeasurement outcomes where quantities differ from assumptions

The exact definition and entitlement rules depend on your contract form and amendments. That is why your commercial team should treat each variation as a traceable commercial item, not a note in an email chain.

Why variation control affects cash flow

Variation value is often real margin. If those lines slip, your monthly cash position drops fast.

Typical failure pattern:

1. Site receives instruction.
2. Work proceeds immediately.
3. Quotation and evidence are assembled late.
4. Variation value is reduced or delayed in certification.
5. Cash flow pressure grows, even though work is complete.

Strong variation control reduces this gap by linking instruction, evidence, and valuation timing from day one.

A simple variation workflow that works on real projects

You do not need heavy process. You need consistent process.

1) Log the instruction immediately

Create one variation record per change. Include:

• variation reference code
• instruction date
• who instructed it
• contract/project reference
• short description of changed scope
• status (draft, quoted, agreed, disputed, valued)

If instruction is verbal, confirm in writing the same day.

2) Define commercial basis before work runs too far

Set the pricing route early:

• contract rates
• new star rates
• daywork basis
• agreed lump sum

Even if final value is pending, make the intended route explicit. Ambiguity at this stage becomes argument at valuation stage.

3) Keep evidence in one place

Attach evidence to the same variation record:

• marked drawings
• site photos
• labour and plant records
• material backup
• correspondence and meeting notes

A good commercial file allows an independent reviewer to understand what changed and why the value is fair.

4) Link each variation to a payment cycle

Do not wait for final account to recover every change. Track variation value against the current interim cycle where contractually appropriate, with clear status labels such as:

• pending quote
• submitted not agreed
• agreed not yet certified
• certified this cycle

This is where most spreadsheet systems break. Lines are duplicated, overwritten, or left off the application entirely.

Worked example in GBP

Below is a practical example for one project cycle.

Project baseline:

• Original subcontract value: £240,000
• Retention: 5%
• Previous certified total (before this cycle): £96,000

Variation items this cycle:

• V-014 additional drainage run: £8,400 (submitted)
• V-015 changed slab edge detail: £4,750 (agreed)
• V-016 omitted duct route: minus £1,200 (agreed omission)

Variation position:

• Gross variation movement this cycle: £11,950

Current gross valuation to date including variations:

• Prior gross valuation baseline: £120,000
• Plus current cycle baseline progress: £28,000
• Plus net variation movement: £11,950
• Gross valuation to date: £159,950

Retention calculation:

• 5% of £159,950 = £7,997.50

Net valuation to date:

• £159,950 minus £7,997.50 = £151,952.50

Less previous certified:

• £151,952.50 minus £96,000 = £55,952.50 this application

The commercial point is simple. If V-014 and V-015 were missing or delayed, this cycle would be materially under-claimed.

How to stop variation disputes before they start

Disputes are harder to avoid when records are thin. You can reduce risk with four controls.

Control 1: Separate original scope and variation lines

Keep variation lines separate from original bill or schedule lines. Mixing them hides trend, muddies audit trail, and makes agreement harder.

Control 2: Time-stamp commercial events

Track key dates for each variation:

• instruction date
• quote submitted date
• response date
• agreement date
• first valuation inclusion date

You cannot manage ageing without dates.

Control 3: Keep a reason code

Use simple reason categories, for example:

• client instruction
• design development
• access/sequence change
• quantity change
• omission

This helps during review meetings and final account negotiation.

Control 4: Reconcile monthly

At each application cycle, reconcile three totals:

• total variations instructed
• total variations agreed
• total variations certified to date

If those numbers diverge for too long, margin and cash both suffer.

Payment notices and variations: what matters in practice

Variation entitlement sits in contract mechanics, but payment and withholding still sit inside statutory notice frameworks.

Your practical checklist each cycle:

• ensure the application clearly identifies the sum applied for, including variation components
• keep supporting breakdown available for review
• monitor notice dates and final date for payment under your contract
• if less is certified or paid, compare against notice mechanics and your submitted basis

This is process discipline, not legal theatre. Most delayed recovery starts with poor application clarity or poor date control.

Common variation mistakes subcontractors can avoid

1) Waiting for full agreement before recording value

Even when value is not fully agreed, record status and current assessment. Otherwise backlog grows and visibility disappears.

2) No owner for variation administration

If no one owns the register, everyone assumes someone else has done it.

3) Evidence stored across personal inboxes

If proof is spread across devices and inboxes, response quality drops under pressure.

4) Not linking variations to programme impact

Where relevant, changed sequence and disruption should be documented in parallel with cost impact. Separate records can weaken commercial position.

5) Treating omissions casually

Negative variations are still variations. If omissions are not tracked formally, totals become unreliable and trust in the register collapses.

Variation register fields you should standardise

If different people log variations in different formats, reporting quality drops quickly. Use one structure across all projects:

• variation reference
• short title
• instruction source
• date instructed
• pricing basis
• quoted value
• agreed value
• valued to date
• certified to date
• ageing bucket
• next action owner

This format gives commercial, site, and finance teams one shared language. It also makes handover between estimators, QS, and operations much easier when projects are busy.

How BuildQS helps with variations

BuildQS is designed for valuation workflows where scope changes are normal.

Practical benefits:

• variation tasks are flagged separately from original tasks
• this-application versus previous value stays explicit
• cumulative valuation and retention remain consistent as lines change
• project teams can keep one shared commercial record instead of parallel spreadsheets

Useful pages:

• How to Create a Payment Application in BuildQS (/blog/how-to-create-a-payment-application-in-buildqs)
• Payment Application Discounts in Construction Explained (/blog/payment-application-discounts)
• Construction Act Payment Terms: JCT, NEC and Default Timescales (/blog/construction-act-payment-terms)
• Automatic Calculations Feature (/features/automatic-calculations)
• BuildQS vs Excel Comparison (/compare/excel)
• Pricing (/pricing)

Frequently asked questions

Are variations only payable once fully agreed in writing?

Contract terms control this, but commercially you should still track and submit variation positions with clear status. Waiting for full agreement on every item can delay legitimate recovery.

Should omissions be in the same register as additions?

Yes. One register should hold additions and omissions so the net movement is clear and auditable.

How often should I review variation ageing?

At least once per application cycle. A monthly ageing view is the minimum for most subcontractors.

Is this legal advice?

No. This is a practical commercial workflow guide for subcontractors. Contract interpretation and dispute strategy should be reviewed with qualified legal advisers.

Want tighter control of variation value each month? Use BuildQS to track scope changes, valuation status, retention, and net due in one workflow. Start Free Trial (/pricing)

Sources

• UK legislation, Housing Grants, Construction and Regeneration Act 1996, Section 110A (payment notices): https://www.legislation.gov.uk/ukpga/1996/53/section/110A
• UK legislation, Housing Grants, Construction and Regeneration Act 1996, Section 111 (pay less and payment framework): https://www.legislation.gov.uk/ukpga/1996/53/section/111
• The Scheme for Construction Contracts (England and Wales) Regulations 1998, Part II (payment provisions): https://www.legislation.gov.uk/uksi/1998/649/schedule/part/II
• JCT, contract product overview and current contract family references: https://www.jctltd.co.uk/product
• NEC Contracts, NEC4 Engineering and Construction Contract product information: https://www.neccontract.com/products/nec4/engineering-and-construction-contract