Construction variations: how a contract price grows from signing to completion

A variation is a change to the scope, materials, or method agreed in your building contract. If it differs from what the contract and plans describe, it is a variation, and it almost always changes the price, the timeline, or both.

Variations come from every direction. The builder hits a problem on site and proposes a fix. You decide on stone benchtops instead of laminate. A surveyor or certifier requires extra work. A provisional sum allowance for an item that was only estimated at signing turns out to cost more once the real quote arrives. Each of these is a separate change to the original deal.

Under most Australian residential building contracts, a variation should be in writing and agreed before the work happens. The detail of what is required differs by state, and your state building authority and fair trading or consumer affairs office publish the rules. The practical point holds everywhere: a variation is a new agreement on top of the old one, and it should be recorded as such, not handled with a verbal yes on site.

Variations are different from defects. A defect is work that does not meet the agreed standard, and the builder fixes it at their cost. A variation is a deliberate change to the agreed scope, and someone pays for it. Keeping the two separate matters, because owners sometimes get billed as a variation for what is really rectification work.

No single variation breaks a budget. The pile does. Here is why the pile grows on almost every job.

None of this is the builder acting in bad faith. The current system rarely gives either side a single live view of the contract sum plus approved variations, so the total only becomes clear when the final claim arrives.

The surprise at completion is almost always a visibility problem, not a single shock variation. Changes get agreed in scattered places: an email, a text, a conversation on site, a line buried in a progress claim. There is no one ledger that says here is your original price, here are the changes you approved, here is the new total.

Because the changes are scattered, the running total lives in the builder's head and their accounting system, not in front of the owner. The builder is not hiding it. They are carrying the financing of the job out of their own pocket inside a structure that was never built to give the owner a live view. When the final invoice arrives and reconciles every change at once, it can look like a sudden jump even though each step was reasonable.

This is also where disputes start. An owner who never clearly approved a change disputes the charge. A builder who did the work in good faith on a verbal instruction cannot prove the approval. Both are now arguing about money that should have been settled before the work happened. Tribunals like VCAT in Victoria, and equivalents in other states, hear a steady stream of these.

The fix is not complicated in principle. Record every variation in writing, get clear approval from both parties before the work happens, and keep a live running total of the contract sum plus approved variations. The hard part is doing it consistently across dozens of small changes over many months. That is where a structured, recorded process earns its keep.

The single most useful control on variations is dual approval: a change does not alter the contract sum until both the builder and the owner have explicitly agreed to it. Either side can propose a variation order, but the price does not move on one signature.

Dual approval does two things at once. It protects the owner from charges they never agreed to, because nothing changes the total without their yes. It protects the builder too, because once the owner approves in a recorded way, there is no later argument about whether the change was authorised. The work and the money are settled before a tool is picked up.

This is deliberately the only place dual approval applies. Ordinary progress payments do not need both parties to sign off twice, because they are claims against work already agreed in the contract. Variations are different: they change the deal itself, so they get the extra gate. Adding the same friction to every routine payment would just slow honest payments down.

On BuildFair, both builder and owner variations require dual approval before they change the contract sum, and the person who submitted a variation cannot be the one who approves it. When a variation is approved, the system recalculates the project's total approved variations and updates the live contract figure, so the running total is always current for both sides. Every step is written to a tamper-evident audit trail, so there is a permanent record of who proposed what, who approved it, and when.

Variations do not only change what the owner pays. They also change how much the people doing the work can be paid. Each subcontractor on a job has a payment cap equal to their contract value plus their approved variations. Amounts claimed above that cap are withheld, not paid, until a variation lifts the ceiling.

This matters because it cuts both ways. A subcontractor who does genuine extra work needs an approved variation to be paid for it, which is fair. A subcontractor who tries to over-invoice beyond the agreed scope hits the cap, and the extra is held back rather than quietly paid out. Approved variations expand the cap, but they do not magically create headroom beyond the real scope of the job.

There is an important limit here. An approved variation lifts the cap by the approved amount, not by whatever a later invoice happens to claim. The cap is contract value plus approved variations, full stop. If you want the mechanics of how money moves down the chain, see the subcontractor payment chain and why subcontractors do not get paid.

Materials a builder buys on a subcontractor's behalf are set off against that subcontractor's payable pool, so the same dollars are not paid twice. Retention-style withheld amounts release after completion once any open defects are resolved, which is covered in retention and how much to hold.

Whether you use a platform or a spreadsheet, the same habits keep the contract sum honest from signing to completion.

Done consistently, these habits turn the end-of-build surprise into a number you have watched grow the whole way.

BuildFair gates every variation through dual approval and tracks the approved total against the contract sum, so the running figure is visible to both the builder and the owner as it grows. The submitter cannot approve their own change, and each approval, rejection, and submission is written to a double-entry, hash-chained ledger that records every step permanently.

Underneath the records, the money is handled separately. Owner deposits and progress payments are held in regulated custody with BuildFair banking partner Kobble (Kobble operates under AFSL 545391, Yondr Money Pty Ltd), separate from the builder operating account, and released only on verified conditions. BuildFair itself does not hold your funds. Subcontractor and supplier payments are released on a fixed 7-day clock from invoice approval, so an approved variation flows into a payment cap that is enforced, not just noted.

If you want to see how progress payments and variations sit together across a build, read what is a progress claim and how the payment schedule works. To understand how the contract terms shape all of this before you sign, see negotiating your building contract.

This guide is general information, not legal or financial advice. For a specific dispute over a variation, speak to a lawyer, your state tribunal such as VCAT or its equivalent, or Legal Aid, and check the variation rules published by your state building authority.