The legal anatomy of a construction variation

Most disputes in UK construction — at any project size — are not about quality of work. They are about scope. Specifically, they are about whether something the client asked for was inside the original contract or outside it.

The mechanism for handling "outside it" is the variation. And the failure to handle variations correctly is, by some margin, the most expensive operational mistake builders make.

This article walks through what a variation legally is, what makes one robust, and why the way most builders handle them is a slow-motion contract failure.

What a variation actually is

Under standard JCT and similar UK construction contracts, a variation is any change to the works described in the contract documents. It can be additive (the client wants underfloor heating in the en-suite, not originally specified), subtractive (the client decides against the second en-suite), or substitutive (Quooker tap instead of Franke).

The crucial point is that a variation is a contractual amendment. It modifies the agreed scope, the agreed price, and often the agreed completion date. It carries the same legal weight as the original contract itself.

This means:

• It must be agreed in writing.
• It must specify the change to the scope.
• It must specify the change to the price.
• It must specify the change to the completion date (if any).
• Both parties must demonstrably consent.

If any of these are missing, the variation is legally ambiguous — and ambiguity is what funds dispute lawyers.

Where it goes wrong in practice

In day-to-day client-facing work — from a £15k bathroom to a £400k extension — the typical variation conversation goes like this:

Client (in passing, on site, on a Tuesday): "Actually we'd love a Quooker rather than the Franke. Can you do that?"

Builder: "Yeah, that'll be a bit more, around £1,200. I'll add it."

Client: "Great, thanks!"

Six months later, the final invoice shows a £1,290 line for the Quooker variation. The client, looking at it cold, says: "I don't remember agreeing to that price." A dispute is born.

What went wrong? Nothing was written. No specific price was confirmed. No completion-date impact was assessed. No signature was captured. The conversation happened, the work happened, but the contract documentation didn't keep up.

What a legally robust variation looks like

A defensible variation has six elements:

1. A unique reference

Variation V001, V002, V003 etc. So you can refer to it, both parties can refer to it, and it appears as a discrete line on the final account.

2. A title

"Substitute Quooker Fusion for originally-specified Franke tap" — not "kitchen tap." Specific enough that a third party reading it cold knows exactly what changed.

3. A description

What's changing and, ideally, why. "Client requested boiling-water functionality; includes tank, hot-water unit and reconfigured plumbing under sink." This protects you if the change cascades into other works.

4. A monetary delta

A specific pound figure. "+£1,290 inclusive of supply, installation and tank cost." Not "around £1,200." Not "see invoice." A number.

5. A programme delta

"+0 days" if it has no impact. "+2 days" if you need extra time. The omission of this is one of the most common sources of dispute — clients often expect variations to be cost-only, and resent any timeline impact unless flagged at the moment of agreement.

6. Demonstrable acceptance

A signature, an email approval with full quotation of the variation document, or — in a digital portal — a tap-to-accept with a logged user, timestamp and immutable record.

Why "I said it on WhatsApp" doesn't count

A WhatsApp message from a builder saying "Quooker variation £1,200" followed by a thumbs-up emoji from the client is, technically, evidence of an agreement. In practice, it is hopelessly weak:

• WhatsApp messages can be deleted by either party.
• The thumbs-up doesn't quote what was agreed — it could refer to the preceding eight messages.
• There's no record of the specific scope ("Quooker Fusion" vs "Quooker Classic").
• There's no record of the programme impact.
• If the client claims the thumbs-up was a misclick, you have very little to fall back on.

In a small claims dispute, this evidence might just about hold. In a £20k variation dispute heading to the TCC, it absolutely won't.

The bare minimum standard for UK variations

If you take nothing else from this article, take this:

Every variation, regardless of size, should be a written record that includes: title, description, cost, programme impact, and an explicit confirmation of acceptance by the client.

Builders Ready, as a piece of software, exists primarily because most builders find this admin friction too high to maintain by hand. A purpose-built tool collapses it to: type the variation, tap propose, client gets a notification, client signs with their finger, done. The audit trail is automatic.

But the principle holds whether you use Builders Ready, a Word template, or a paper form. Document every variation as if it were going to be read out in court, because occasionally one will be.

One last thing — the cumulative effect

The biggest source of "final account shock" isn't a single variation. It's the cumulative effect of fifteen small variations totalling £18k that the client never tracked. By the time they see the final number, they feel ambushed — even when every individual variation was technically agreed.

This is why a live finance dashboard matters as much as the variations themselves. If your client can see the running total — original quote £285k + variations to date £8,400 = current contracted value £293,400 — there's no shock at handover. The number was visible the whole time.

Transparency removes ambushes. Documentation prevents disputes. Both are far cheaper than litigation.