- Why Variations Go Wrong
- The Financial Stakes
- What a Good Variation Management Process Looks Like
- How Variation Management Connects to the Rest of the Contract
- What Effective Variation Management Requires From Your Platform
- Common Mistakes to Avoid
- FAQs
Variations are a fact of life on any construction project. A client changes their mind about a partition wall. An unexpected ground condition forces a redesign. The architect issues a revised drawing mid-programme. None of this is unusual. What is unusual — and genuinely damaging — is when those changes aren't tracked, priced, and agreed in time to protect your margin.
Poor variation management is one of the most common reasons UK contractors finish a project in the red despite doing solid work. The build goes well, the client is happy, and then the final account tells a completely different story.
This article covers why variation management breaks down, what it costs when it does, and how to run a tighter process from instruction to agreement.
Why Variations Go Wrong
Most contractors understand how a variation should work in principle. You get an instruction, price it, submit it, get it agreed. Straightforward on paper.
In practice, the process falls apart at several predictable points.
Instructions arrive without formal authorisation
Work starts on a verbal instruction or an email that was never formally issued as a contract instruction. By the time you raise the variation, the client disputes whether the instruction was ever given — or argues the scope was already included in the contract sum.
Under a JCT contract, the architect or contract administrator has specific authority to issue instructions. Work carried out without a proper instruction is at risk. Your team needs to know this, and your process needs to enforce it.
Pricing gets delayed until it becomes a dispute
The instruction lands, the work gets done, and the variation sits in a spreadsheet waiting to be priced. Weeks pass. By the time you submit a figure, the client has moved on and the number feels like a surprise. What should have been a straightforward commercial conversation becomes a negotiation — or worse, a formal dispute.
Variations priced and submitted promptly are far more likely to be agreed without argument. Delay creates doubt.
The budget impact stays invisible until it’s too late
On a live project with multiple concurrent variations, it's easy to lose sight of the cumulative effect on the contract sum and your forecast margin. One variation is manageable. Ten variations — some agreed, some pending, with sub-contractor costs attached to several — creates a financial picture that's genuinely difficult to hold in a spreadsheet.
By the time it becomes clear, you've already committed costs you can't recover.
Sub-contractor costs aren’t captured in time
Your sub-contractor carries out the varied work. They submit their claim weeks later — sometimes after your own submission to the client has already been agreed at a lower figure. You end up absorbing the difference.
Getting sub-contractor costs into your variation claim before you submit to the client is a discipline that many teams struggle to maintain under programme pressure.
The Financial Stakes
Variations aren't just an administrative headache. They directly affect your contract profit.
Consider a £10 million contract. If 8% of the contract value passes through variations — which is not unusual on a complex project — that's £800,000 of work that needs to be correctly identified, priced, submitted, and agreed. If your process recovers only 85% of that value due to late submissions, disputed instructions, or unagreed claims, you've left £120,000 on the table. On a project where your margin sits at 4–6%, that's a significant portion of your profit.
Multiply that across three or four concurrent contracts and the numbers become serious.
The problem usually isn't that contractors are doing the wrong work. It's that the commercial process around that work isn't tight enough to recover the full value.
What a Good Variation Management Process Looks Like
Strong variation management isn't complicated. It's consistent. Here's what it requires.
A clear instruction before work starts
Every variation should begin with a written instruction from the contract administrator. If work is instructed verbally, follow it up immediately in writing — confirm what was instructed, when, and by whom. Don't wait for the formal instruction to arrive before you document the conversation.
This protects you. It also keeps the client and design team honest about what they've asked for.
Prompt pricing and submission
Price the variation as soon as the scope is clear. Don't wait until the end of the month or until you have a batch to submit together. Each variation should be priced, submitted, and chased for agreement as a standalone item.
If the scope isn't yet clear, submit a preliminary notice that a variation is pending and an estimate will follow. This keeps the client informed and prevents the "we didn't know this was coming" response when the final figure arrives.
Sub-contractor costs captured early
If the varied work involves sub-contractors, get their costs before you submit to the client. Build this into your process as a standard step, not an afterthought. A variation claim that doesn't include sub-contractor costs is incomplete — and puts your margin at risk.
Tracking against the contract budget
Every variation — instructed, submitted, and agreed — should be visible against the original contract sum. Your commercial team needs to see the running total at all times: what's been agreed, what's pending, what's in dispute, and what the cumulative effect is on forecast margin.
This is where most spreadsheet-based processes break down. The data exists, but it's spread across multiple files, inboxes, and individuals. Nobody has the full picture until someone manually compiles it.
A formal agreement process
A variation isn't complete until it's agreed in writing. Submitted is not the same as agreed. Your process should track every variation from instruction through to final agreement, with clear ownership and follow-up actions at each stage.
Unagreed variations sitting in the final account are a liability. The client's QS will scrutinise them, challenge them, and reduce them where they can. Your best protection is a clean paper trail and a prompt agreement process throughout the project — not a scramble at the end.
How Variation Management Connects to the Rest of the Contract
Variations don't exist in isolation. They connect directly to programme, design, quality, and sub-contractor management.
A variation that requires a design change needs an RFI raised and answered before work can proceed. If that RFI is delayed, the programme slips. If the programme slips, your preliminaries increase. If the design change affects a sub-contractor's scope, their programme and costs shift too.
This is why variation management can't be handled as a standalone commercial task. It has to be connected to everything else happening on the project.
When your team is managing variations in a spreadsheet while the programme lives in a separate tool, the design team is communicating by email, and sub-contractor costs are sitting in someone else's inbox — the connections break. Things fall through the gaps. Costs accumulate without anyone noticing until it's too late to act.
What Effective Variation Management Requires From Your Platform
If you're managing variations on a mid-sized contract — say £5 million to £50 million — you need a system that does more than store data. You need one that keeps your team on top of the process.
That means:
- Every variation tracked from instruction to agreement, with status visible across the whole commercial team
- Budget impact updated automatically as variations are added, so your forecast margin is always current
- Sub-contractor costs attached to the relevant variation, not held separately
- Alerts when a variation has been submitted but not agreed within a reasonable timeframe
- Documentation generated automatically, so your team spends time managing the process rather than writing it up
Elevate Software is built around exactly this kind of process-led approach. Variation management tracks every contract change — cost, quality impact, and budget implications — and the colour-coded guidance system tells your team what needs attention next. Nothing sits unactioned because the platform surfaces it automatically.
The result is a commercial team that's always current, always informed, and never blindsided by a final account that doesn't reflect the work actually done.
Common Mistakes to Avoid
A few patterns come up repeatedly on contracts where variation management has gone wrong.
Starting work without a written instruction. This is the single biggest risk. No instruction, no entitlement. Make it a rule that no varied work starts without something in writing.
Treating the variation log as a filing system rather than a live management tool. A log updated once a month isn't a management tool — it's a record of what happened. You need live visibility, not a retrospective.
Letting the final account become the first time variations are properly reconciled. By that point, memories have faded, documents are harder to find, and the client's QS has had months to build a counter-argument. Agree variations as you go.
Failing to connect variation costs to sub-contractor payments. If a variation increases a sub-contractor's scope, their payment should reflect that. If it reduces their scope, that needs tracking too. Disconnected sub-contractor management creates financial exposure at both ends.
Assuming the client understands the scope of a variation. Write it out clearly. Include what's in scope, what's excluded, what assumptions you've made, and what the programme impact is. Ambiguity in a variation submission is an invitation to dispute.
FAQs
What is construction variation management?
Construction variation management is the process of identifying, pricing, submitting, and agreeing changes to the original contract scope. It covers all instructions that alter the works — whether they add, omit, or change something from the original contract documents.
Why do variations cause cost overruns on construction projects?
Usually because changes aren't priced promptly, sub-contractor costs aren't captured before submission to the client, or variations aren't formally agreed during the project and become disputed at final account. Poor tracking means the cumulative budget impact stays invisible until it's too late to manage.
What is the correct process for issuing a variation under a JCT contract?
Under a JCT contract, variations must be instructed in writing by the contract administrator. The contractor is entitled to value the variation and submit it for agreement. If an instruction is given verbally, confirm it in writing immediately and request formal confirmation. Work carried out without a proper instruction may not be recoverable.
How should sub-contractor variation costs be managed?
Sub-contractor costs should be captured before the main contractor submits the variation to the client — as part of your own pricing process, not as a separate exercise after submission. Failing to do this risks absorbing the difference if the agreed client figure comes in lower than the sub-contractor's eventual claim.
What is the difference between a submitted and an agreed variation?
A submitted variation is one you've priced and sent to the client or contract administrator for agreement. An agreed variation is one where the value and scope have been formally accepted in writing. Submitted variations are not guaranteed income. They remain at risk until formally agreed.
How many variations are typical on a UK construction project?
There's no fixed number. Complex commercial or fit-out projects routinely see dozens over a contract period. Volume matters less than process. A project with fifty well-managed variations will outperform one with ten that are poorly tracked and disputed at final account.
How does variation management connect to programme management?
Variations that require design changes or additional procurement affect the programme. If a variation isn't processed quickly — including the associated RFI and sub-contractor instruction — the programme slips and preliminary costs increase. Variation management and programme management need to be connected, not handled in separate systems.
Variation management isn't glamorous. But it's where contract profit is won or lost. A tight process, applied consistently from the first instruction to the final account, is the difference between a project that delivers the margin you priced and one that doesn't.
If your team is managing variations across multiple contracts and finding the process fragmented, slow, or invisible to the people who need to act on it, it's worth seeing how a purpose-built platform can change that.
Download the Elevate brochure at elevate-software.co.uk.