A builder's variations register: recording changes before they cost you

Take a renovation that runs fourteen weeks and picks up nine changes along the way: a moved doorway, an upgraded cooktop circuit, two extra downlights in each bedroom, a skylight, and five smaller ones. Four are priced and agreed in writing. Three are mentioned on site and absorbed. Two are argued about at the final invoice.

The four written ones are paid in full. Say the other five come to $11,000, part in work never billed and the rest in a discount given to end the argument. A variations register is the cheapest insurance a builder carries, and this article is about keeping one that actually gets kept.

Why registers fail

Every builder agrees variations should be documented. Registers still fail, for predictable reasons.

The form is too heavy. If recording a variation means a formal document with signatures, small changes skip it. The $600 change is exactly the one that gets absorbed, and a job can have nine of them.

It lives somewhere else. A register kept in a folder beside the job gets updated in batches, from memory, which is to say wrongly. The register has to be a list on the job itself.

"We'll sort it at the end." The end is when the client's memory of agreeing has faded and the money is largest. A variation is easiest to price and agree in the 48 hours after it comes up, and nearly impossible fourteen weeks later.

Home building contracts often have formal variation requirements of their own: writing, signatures, sometimes set wording. Where yours does, the register supplements the contract paperwork rather than replacing it. Check your standard-form contract and your local rules for what a binding variation needs. The register below is the working layer that makes sure the formal step actually happens.

What each entry records

Five fields. Any more and it will not get filled in on site.

• Date raised, and who raised it: the client, the builder, or the site, such as a wall that turns out to be load-bearing.
• What changed, in one or two sentences of nouns.
• Price difference, plus or minus, with the tax treatment noted. Credits go in too: a register with credits in it is one a client trusts.
• Time impact in days, even if zero. Time claims argued at the end without records made at the time lose.
• Status: proposed, priced, agreed (with the date and how), done, invoiced. An entry left at "proposed" for a week is a decision being made by default, on your money.

The screen and the routine

The register earns its keep through one widget on the job's dashboard: variations not yet agreed, oldest first. The routine is weekly. Every Friday, anything at "proposed" gets a price and goes to the client, and anything priced for more than a week gets a call.

On the money side, give each entry an agreed amount, filled in once the client agrees, and give the job a total of its agreed amounts. "What is this job worth now?" becomes a number, not a reconciliation. The quoting habits upstream of all this, scope in nouns and exclusions written before the job, are covered in quoting for trade jobs.

The client conversation

The register changes the tone of variations from confrontation to bookkeeping. "I'll add it to the variations list and send you the price tonight" keeps the relationship because it is procedural. Clients rarely leave over changes costing money. They leave over surprises. A client who sees the list grow as the job goes, credits included, signs the final invoice without the meeting. The wider setup is in job tracking for a trade business.

Running it in Diract

At sign up, pick Something else and type builder as your trade, which starts you on a builder's workspace with jobs, their lines and what is owed. Name the register in What does your business do?: "residential builder, renovations and extensions, fixed-price contracts with progress claims and client-selected PC items, and a variations register on every job." The plan under Our suggestions then carries the register as a table connected to the job, with the five fields above.

If the workspace is already built, add it through Build your process. Confirm the plan part by part before building, as walked through in build a business app without coding. Signed variation documents can stay in the Drive folder the job already uses, linked from the entry.

Conclusion

Nine changes a job, five fields an entry, one Friday routine. A variations register does not slow a build down. It turns the changes a build was always going to have from end-of-job arguments into line items agreed while everyone still remembers agreeing.

Build your app free at diract.io. Every plan starts with a 7 day free trial, and no card is charged until it ends.

Questions

Does a register entry replace the contract's variation paperwork?

No. Where your contract or the law requires a signed variation document, the register is what makes sure that document exists. An entry should not reach "agreed" without it.

Should credits and nil-cost changes go in?

Yes. They cost a line each, and they make the register credible to the client and to anyone who later has to rely on it.

What about variations on cost-plus jobs?

Record them anyway, with the estimated impact. Cost-plus removes the argument about price, not the argument about scope.

This article is general information, not legal or financial advice. Current as at 19 September 2026. The product changes often, so check the screen before relying on a detail here.