Contracts · Variations
Variation management software,
judged on what moves after approval.
A buyer's page rather than an explainer. Six evaluation criteria for the category, the questions worth asking a provider, a twenty-minute demo script most products fail somewhere in the middle of, and the honest limits of what any variation tool can do. What a variation is and how to run one is covered separately, and linked throughout.
01 / The direct answer
What variation management software does
Variation management software prices a change to the contracted scope, produces the client-facing version of it, captures the agreement as a dated record, moves the contract sum and the job budget when that agreement lands, and makes the approved variation available on the next progress claim. Change order software and variation control software describe the same category.
The buying insight is in that sentence and it is easy to miss. Only the first two of those five things happen inside the variation itself. The other three are connections to the budget, the claim and the programme, which means this category is judged almost entirely on what it touches rather than on what it contains. A product that produces an immaculate variation document and moves nothing has solved the visible half of the problem and left the expensive half alone.
This page is about evaluating the software. What a variation actually is, including the contract formalities that decide whether one is recoverable at all, is in variations. The working routine for running them on a live job is the managing variations guide. The related discipline of stopping scope leaking before it ever becomes a variation is scope creep and variation control. Those are separate questions and worth keeping separate from the product decision.
02 / Before you buy
Six criteria for the category
Ranked by what they cost you when they are missing. The second is the one almost nobody evaluates, and the fourth and fifth are the reason to buy anything at all.
Two layers on one variation
A variation has an internal cost build and a client-facing summary, and they are different documents for different readers. Software that offers only one forces a choice between exposing your margin line by line and maintaining the client version by hand in Word. Ask which layers exist and whether cost visibility can be switched per variation.
A reconciliation rule between those layers
The criterion almost nobody evaluates and the one that decides whether the two layers stay honest. If the client summary is composed separately from the cost build, something has to stop them disagreeing. Ask whether the system will refuse to send a variation whose client-facing total does not match its internal total, or whether it will cheerfully send both.
Approval that produces a record, not an email
What you need months later is a dated artefact showing what was described, what it cost and that the client agreed. Ask what the client actually receives, how they approve it, whether a decline captures a reason, and what the record looks like when it is produced in a dispute rather than on a screen.
A running total anyone can query without rebuilding it
Not a report someone assembles, a figure that is simply true at any moment, including variations pending. Ask to see it on a job with eight variations in mixed states, then ask what a site supervisor can see. A total only the contract administrator can produce is a total nobody asks for at the moment it matters.
The first two criteria are worth treating as a single test, because a variation has two audiences and they want opposite things. Internally it is a cost build, priced line by line from real rates, because that is how you know the change makes money. Externally it is a summary a homeowner can read and agree to, because a line-by-line cost breakdown handed to a client is an invitation to negotiate each line and to discover your margin. Almost every product lets you produce both. The question that separates them is what stops the two versions disagreeing once someone edits one of them, and a product with no answer to that has handed you a manual reconciliation dressed up as flexibility.
03 / The conversation
Questions worth asking a provider
Six questions with specific answers. Any of them met with a reassurance rather than a demonstration on your own job is worth pressing on until you get one.
- 01
Where does a variation line come from
Typed fresh, or drawn from the same price book and rates that built the estimate. This decides whether variation pricing is consistent with the original job or a separate act of memory. If it is typed fresh every time, expect variation margins to drift from contract margins in a direction nobody is monitoring.
- 02
Can I hide my cost breakdown without maintaining a second document
Press on this one. A tool that meets the requirement by letting you export to Word and edit it has met nothing, because the second the client version is hand-edited the reconciliation is gone. You want the two layers generated from one record, with visibility as a setting rather than a rewrite.
- 03
Does a selection above its allowance become a variation, and how
Prime cost and provisional sum overruns are the most common source of a variation on a residential job. Ask whether the system connects selections to variations, whether the connection is automatic or prompted, and what the client sees. Products vary enormously here and many do not connect them at all.
- 04
What happens on the day a variation is approved
Ask for the complete list of what moves, and be suspicious of a short answer. Contract sum, job budget, forecast final cost, claim availability, programme dates if an extension of time was part of it. Anything that does not move automatically is something a person will move, sometimes.
- 05
What is the record if this ends up in a dispute
Ask to see a variation produced as a document, months after the fact, including who approved it, when, from what device or link, and what they were shown at the time. A screen that displays an approval status is not the same as an artefact you can hand to a lawyer or an insurer.
- 06
What leaves if I stop paying
Variation history is one of the records you are most likely to need after a subscription ends, because defects periods and disputes run for years. Ask what exports, in what format, whether the client-facing documents come out as well as the data, and run the export during the trial rather than being told it exists.
04 / The test
A demo you can run in twenty minutes
Run one variation from end to end and do not let the demonstration skip ahead. Use your own numbers, and use a change you have actually had to price, ideally an awkward one.
- Price it from the price book. Build the variation from rates rather than typing a total, and check the rates are the ones your estimate would have used. If variation pricing draws on a different source from estimating, your variation margins will drift from your contract margin.
- Hide the cost breakdown. Compose the client-facing version and confirm you can present a summary without exposing line-by-line costs, without exporting to Word and editing it by hand. Hand-editing is the point at which every downstream guarantee stops applying.
- Try to break it deliberately. Change the client-facing total so it no longer matches the internal cost build, then attempt to send it. This is the single most revealing thirty seconds in the whole evaluation. A product that stops you has a reconciliation rule. A product that sends it does not.
- Approve it as the client. Go through the actual client experience, on a phone, and then decline one and check whether a reason is captured. Look at the resulting record and ask yourself whether you would be comfortable producing it in a dispute two years from now.
- Check what moved without you. Immediately after approval, look at the contract sum and the job budget. Both should have changed. If either needs a person to update it, that person will forget, and the budget will quietly stop describing the job you are actually building.
- Raise a claim two stages later. Not the next one, two along. The approved variation should be offered for inclusion, with you choosing whether it goes on. This is the test that most directly protects money, because agreed work that never reaches a claim is the largest and least visible leak in residential claiming.
Most products fail somewhere between step three and step six, and the failures are informative rather than disqualifying. A product that stops at step four is a good documentation tool and you should price it as one. A product that clears step six is doing something structurally different, and the difference is usually that variations are not a standalone module in it.
05 / Honest limits
What variation software cannot do
Three limits, and the first is the one that catches builders who assume the software has covered them.
It cannot make an unsigned variation recoverable. Australian residential building contracts, and the legislation sitting behind them in each state, generally require a variation to be documented and agreed in a particular way before the work proceeds. Software can hold your own sequence and refuse to let you skip a step in it. It cannot supply a contractual entitlement you did not obtain, and a meticulously recorded variation that was never signed remains a conversation about goodwill. The formalities themselves are covered in variations, and a specific dispute belongs with a lawyer.
It cannot price the work. What a change genuinely costs, including the disruption to sequencing and the time it consumes, is a judgement, and a system that offers to generate a variation price from a description is offering you a number with no provenance. And it cannot classify. Whether a request is a variation, an adjustment to a prime cost or provisional sum allowance, or your own estimating error, is decided by comparing the request against the priced documents at the priced revision, which is a human act with commercial consequences either way. That distinction is set out in scope creep and variation control, and getting it wrong in either direction costs money.
One category caveat worth stating. Almost everything above assumes residential contracting, where a variation is a discrete priced change to a fixed-price contract with a homeowner. Variation and claim administration on commercial and civil work runs differently, commonly through a superintendent or contract administrator with formal notice requirements and time bars attached. If that is your work, treat the criteria on this page as a starting point and test the notice and assessment workflow specifically.
06 / How VIABUILD does it
Variations as one module, not a standalone tool
Variations in VIABUILD are one module of the Construction Operating System for residential builders, on the same data model as the estimate, the budget and the claims, which is what allows the last three criteria above to be met without an integration for each.
A variation carries two layers. The internal cost build is priced from the same rates and price book that built the estimate. The client-facing rows are composed separately, with a toggle deciding whether the client sees pricing at all, and a reconciliation rule between the two that refuses to send the variation if the client-facing rows do not agree with the internal total. It goes out as a branded PDF and a link. The client signs on the link, or declines with a reason, and both outcomes leave a dated record of what they were shown.
On approval the contract sum and the job budget move, so cost tracking reflects the job as it now is, and the variation is waiting on the next progress claim for you to include. Client selections that land above their allowance feed the same mechanism, which is where a large share of residential variations actually originate.
What we do not claim. VIABUILD does not decide whether a change is a variation, an allowance adjustment or an estimating error. It does not price the disruption for you. It does not give you a contractual entitlement you did not obtain, and it does not assess your position under any state's legislation. The full feature detail is on variations, and if you want to tighten the process before changing any software, the managing variations guide is usable today on whatever you currently run.
07 / FAQ
Common questions.
Variation management software is the tool a builder uses to price a change to the contracted scope, get it agreed in writing before the work starts, and carry the consequences of that agreement through the rest of the job. In practice it does five things. It builds the variation, ideally from the same rates and price book that built the original estimate. It produces the client-facing version, which is a different document from the internal cost build. It captures the approval as a dated record rather than an email thread. It moves the contract sum and the job budget when approval lands. And it makes the approved variation available on the next relevant progress claim so agreed work is actually billed. Change order software and variation control software describe the same category under different names.
A register records that a variation exists. Software in this category is judged on what happens after it exists, which is a much harder problem and the reason a spreadsheet eventually stops being enough. A register will tell you there are eight variations totalling a number. It will not stop the client-facing summary drifting from the priced cost build, it will not move the contract sum and the budget on approval, it will not make the approved variation available on the claim two stages later, and it cannot produce a defensible artefact showing what the client was shown when they agreed. Those four behaviours are the entire buying case. If a product you are evaluating is essentially a register with better formatting, it will leave the expensive problems exactly where they are.
Run one variation end to end and refuse to let the demonstration skip. Price it from the price book and check the rates are the ones your estimate used. Compose the client-facing version and confirm the cost breakdown can be hidden without hand-editing a second document. Deliberately break the two layers so the client total no longer matches the internal total, and see whether the system stops you sending it. Approve it as the client, then look at what the record contains. Then check three things moved without you touching them, the contract sum, the job budget and the availability of that variation on the next claim. Finally raise a claim two stages later and confirm it is genuinely offered. Twenty minutes, and most products fail somewhere in the middle of it.
Some do, some do not, and it is worth asking explicitly rather than assuming, because the two are commercially entangled and often administratively separate. A variation frequently carries time as well as cost, and unclaimed time is as real a loss as unclaimed money, particularly where liquidated damages apply. What to establish is whether time can be priced and agreed on the same instrument as the cost, whether an approved extension moves the programme dates, and whether the contractual notice requirements for claiming time are prompted or left to you. Be careful with any product implying it manages your entitlement to an extension of time, because that is a contract question rather than a software one. The mechanics of liquidated damages are covered separately in the knowledge library.
Three things, and the first is the one that catches builders out. It cannot make an unsigned variation recoverable. Most Australian residential building contracts and the legislation around them require variations to be documented and agreed in a particular way, and a beautifully recorded variation that was never signed is still a conversation about goodwill. Software can enforce your own sequence, it cannot supply a contractual entitlement you did not obtain. It cannot price the work for you, because the judgement about what a change genuinely costs including disruption and time remains yours. And it cannot decide whether something is a variation at all, as opposed to an allowance adjustment or your own estimating error, which is a classification question requiring a person to compare the request against the priced documents at the priced revision.
Rarely, and it is worth understanding why, because it is the structural point behind the whole category. Every criterion on this page except the first two is about a connection to something outside variations. The price book that supplies the rates, the selections that generate the overruns, the budget that has to move, the claim that has to carry it, the programme that absorbs the time. A standalone tool can produce a beautiful variation document and cannot do any of that without an integration for each, which is a lot of seams for a small module. This is one of the few categories where the argument for a connected system is not a marketing preference but the actual mechanics of the problem, and it is worth deciding that question before you compare products.
Variations are one module of VIABUILD, the Construction Operating System for residential builders, on the same data model as the estimate, the budget and the claims. A variation is built as an internal cost breakdown and a separately composed client-facing summary, with a reconciliation rule between them that refuses to send the variation if the client rows do not match the internal total, and a toggle deciding whether the client sees your pricing. It goes out as a branded PDF and a link, the client signs on the link or declines with a reason, and both leave a dated record. On approval the contract sum and the budget move, and the variation is waiting on the next progress claim. Selections that land above their allowance feed into the same mechanism. Full detail is on the variations feature page.
08 / Keep reading
Keep reading on variations and scope
The reference behind the mechanism, the discipline that stops scope leaking, the working guide, the product pages, and the checklist to use against every vendor.
Approve it, and watch three things move.
The category is judged on what happens after approval. In VIABUILD the contract sum moves, the budget moves, and the variation is already waiting on the next progress claim. One module of the operating system, on the same data as the estimate.