The scope changed. Did your price?

The renovation is moving. Then a revised plan arrives, the customer asks for different cabinetry and the site supervisor records an extra electrical point. Each change is visible somewhere, but the approved quote still describes yesterday’s job.

That is a commercial handover problem, not simply an admin problem. If changed work begins before the scope, price, timing and approval path are clear, the business is carrying uncertainty on site.

A useful building variation workflow brings the original agreement and the proposed change together before extra work proceeds. It prepares the evidence and the draft. The builder keeps the judgement.

Why scope changes escape the price

Scope changes rarely arrive through one neat channel. They can appear in revised drawings, customer messages, meeting notes, supplier advice, photos or a conversation on site. Each source may be reasonable on its own. The risk appears when nobody can see the complete change against the approved quote.

The usual manual response is fragile. Someone remembers the conversation, forwards a screenshot, marks a plan and intends to update the quote later. Meanwhile the crew needs an answer, the program keeps moving and the old price remains the easiest number to find.

This is different from keeping a general price list current. One approved price change should reach every quote, but a variation also needs job-specific context: what was agreed, what is changing, why it changed and who must approve the commercial effect.

1. Define the sources that count

Start by listing the approved sources for one kind of scope change. For a residential builder, that might include the signed quote, current drawings, customer email, site diary and approved selections.

Do not ask an automated workflow to treat every message as an instruction. Instead, define what makes an item a proposed change. Useful fields include:

• the job and customer
• the original scope reference
• the proposed addition, removal or substitution
• the source and time of the request
• photos, drawings or notes that support it
• the person responsible for review

The aim is not to collect more information. It is to stop the commercial decision from depending on somebody remembering which message mattered.

2. Compare the change with the approved job

The workflow should place the current approved scope beside the proposed change. It can highlight a revised drawing, a changed selection or a new site note, then prepare a short change list linked to the source material.

This comparison is where software can remove searching without pretending to understand the whole job. It can show that a skylight was added to a revised plan or that the customer requested a different finish. It should not decide whether the request is included, buildable, compliant or chargeable.

If the source is unclear, contradictory or incomplete, route it to the responsible person. An exception is useful information. Hiding uncertainty inside an automatic update is not.

3. Prepare a reviewable variation

Once a proposed change is identified, prepare a draft variation with the details the business normally needs. This may include the original scope reference, description of the change, supporting documents, estimated cost and time effect, exclusions and the required approval step.

Use the business’s approved estimating rules and pricebook. Do not let a model invent a price from generic market data. The draft can assemble known labour, material and subcontractor inputs, but the builder or estimator should confirm quantities, margin, tax treatment, timing and contract requirements.

The Australian Government’s current guidance on preparing quotes recommends clear written quotes that include variations and revisions discussed. Its contract guidance also explains that variation terms can affect cost and timing, and recommends recording agreed contract changes in writing.

4. Stop changed work at the right gate

A good workflow does not stop the entire site every time a note changes. It creates a clear gate for work that could affect scope, price, program, safety, compliance or the customer promise.

The gate should answer four questions:

1. What changed from the approved job?
2. What evidence supports the change?
3. Who has authority to set the commercial response?
4. What approval is required before the changed work begins?

For NSW residential building work, check the current contract and applicable rules. NSW Fair Trading’s contract variations guidance says variations must be documented and explains the information to provide before varied work starts. This article is operational guidance, not legal advice. Obtain appropriate professional advice for the job and contract.

5. Make approval visible to the site

After the owner or authorised estimator approves the commercial response and the customer completes the required approval, update the job record the site team actually uses.

The site should see the current approved scope, any changed drawings, the variation status and the next permitted action. Avoid sending complete customer or contract records through loosely controlled chats. Link people back to the controlled source where possible.

Acknowledgement matters. A variation can be approved in the office but still fail operationally if the supervisor works from an earlier plan. Make the current version and approval status obvious at the point of use.

6. Test with recent changes

Choose three recent variations: one straightforward addition, one ambiguous request and one change discovered on site. Trace each from first evidence to quote or contract, approval and site instruction.

Look for the point where someone had to search several systems, retype the same description or rely on memory. That is usually the first connection worth fixing.

Test reversals and late changes too. The workflow should preserve which version was current, who approved it and what the crew was told. It should never silently erase the original agreement.

What stays under human judgement

People decide whether a request changes the agreed scope, whether it is safe and buildable, how it affects price and program, what the contract requires and how to explain the decision to the customer. They handle negotiation, uncertainty and exceptions.

Automation can gather approved evidence, compare versions, prepare a draft variation, route it for review and update the controlled job record after approval. It should not accept work, set an invented price or commit the business to a customer promise.

Trace one scope change before it becomes extra work

Book an on-site automation review and bring one recent revised plan, customer request or site note. For suitable Sydney building and renovation businesses, the first review is $0.

We will trace the change against the approved quote, identify where the commercial handover broke and show the first practical connection to test. Scope, price and customer approval stay with your team.