How to Automate Variations and Extra Work on a Job
The technician gets to site.
The customer asks for something extra.
It might be:
- another outlet,
- an upgraded product,
- additional labour,
- extra materials,
- a return visit,
- or a change to the original scope.
The work gets done.
Then someone says:
“Did we actually charge for that?”
If variations are being tracked through texts, notes and memory, there is a good chance some of that revenue is disappearing.
Capture the Variation While It Happens
The best time to record extra work is while the person is still on site.
A simple variation form might capture:
- what changed,
- why it changed,
- additional labour,
- materials required,
- photos,
- estimated price,
- customer approval,
- and who submitted it.
That information should attach directly to the job.
Nobody should need to reconstruct the variation later.
Give Every Variation a Status
Extra work should move through a clear process.
For example:
- Variation raised.
- Pricing calculated.
- Customer approval requested.
- Variation approved.
- Work completed.
- Final value added to the job.
- Finance receives it for invoicing.
Now everyone can see what is happening.
The variation does not disappear inside a message thread.
Do Not Rely on the Technician to Remember the Price
Field staff should be able to capture what happened.
That does not necessarily mean they should calculate the final charge.
The system can use:
- standard labour rates,
- product pricing,
- markups,
- call-out fees,
- and predefined variation rules.
Or it can simply send the variation to someone in the office for pricing.
The important part is that the extra work is recorded before it gets forgotten.
Keep Approval Attached to the Job
A customer saying:
“Yeah, go ahead.”
can become difficult to prove later.
Where practical, the system should capture approval.
That could be:
- a digital signature,
- an approval button,
- an email confirmation,
- or a recorded status with supporting notes.
Now operations and finance both know the variation was authorised.
Feed Approved Variations Into the Final Invoice
Once approved, the variation should become part of the job value.
For example:
Original quote: $8,000
Approved variation: $750
Final job value: $8,750
Finance should not have to search through messages to work out whether there was additional chargeable work.
The system should carry the approved amount into billing.
Use Rules for Common Variations
Some extras happen repeatedly.
For example:
- additional hours,
- extra site visits,
- product upgrades,
- disposal fees,
- urgent work,
- and additional materials.
If those are predictable, the system can make them easy to select.
That speeds up data entry and keeps pricing more consistent.
Make Unapproved Work Visible
Sometimes extra work has happened but approval is still missing.
That should be obvious.
A manager might see:
Variation pending approval
Work completed, price not confirmed
Customer approval missing
Variation ready to invoice
This gives the business a chance to fix the issue before the job closes.
Start With the Last Variation You Nearly Missed
Think about a recent job where extra work happened.
Ask:
- How was it recorded?
- Who priced it?
- Was the customer approval captured?
- Did finance know about it?
- Did it appear on the final invoice?
If the process relied on several people remembering what happened, there is probably a better way.
At 5M Consulting, we help trade and service businesses connect field work, variations and invoicing so extra work is captured while it happens and carried through to billing.
If your team is doing work that occasionally never makes it onto the invoice, the variation process is probably leaking revenue.