How to Automatically Detect Jobs With Unapproved Variations Before Invoicing
The technician gets to site.
Something is different from the original scope.
The customer asks:
“Can you just take care of that while you're here?”
The technician does the extra work.
Maybe they use another two hours.
Maybe additional materials are required.
Maybe another component needs replacing.
The job gets completed.
Then accounts invoices the original quoted amount.
The extra work never makes it onto the invoice.
That is not really an invoicing problem.
It is a workflow problem.
Extra Work Needs to Become Visible
Variations often begin informally.
A technician might write:
Additional cable required
or:
Customer requested extra outlet
or:
Existing equipment damaged – replacement completed
That information may live inside:
- technician notes,
- photos,
- a text message,
- an email,
- a phone call,
- or someone's memory.
Unless the workflow turns that information into a defined variation, it is easy for the extra work to disappear.
Create a Variation Record When Extra Work Is Identified
Instead of leaving the information inside notes, create something measurable.
For example:
Variation: Additional electrical work
Labour: 2 hours
Materials: $420
Customer Approval: Pending
Invoice Status: Not Ready
Now the system knows there is unresolved commercial work attached to the job.
Check Variations Before a Job Becomes Invoice-Ready
Your invoicing workflow can include a simple rule:
If:
Job Status = Completed
and:
Variation Exists = Yes
and:
Variation Approval = Pending
then:
Ready to Invoice = No
For example:
Job J-10241
Original Work: Complete
Variation: $1,180
Customer Approval: Pending
Invoice Status:
Blocked – Variation Requires Review
That prevents accounts from invoicing too early.
Separate Recorded Variations From Approved Variations
Recording the extra work is only the first step.
A useful workflow might track:
Variation Identified
↓
Variation Priced
↓
Customer Approval Requested
↓
Approved
↓
Ready to Invoice
Each stage tells you what needs to happen next.
Without those stages, a variation can simply remain buried inside a job record.
Tell the Right Person What Is Missing
If a completed job has an unresolved variation, the system should create a clear action.
For example:
Job J-10241 cannot move to invoicing.
Variation Value: $1,180
Status: Customer approval required
Owner: Project Manager
Now the job does not simply sit in limbo.
Someone knows exactly what needs to happen.
Escalate Old Variations
An unresolved variation becomes more important once the physical work has already been completed.
You could use rules such as:
1 day after completion
Notify variation owner.
3 days after completion
Escalate unresolved approval.
5 days after completion
Add to management exception view.
The longer the approval sits unresolved, the longer the associated revenue remains unbilled.
Create an Unapproved Variations View
Instead of searching through completed jobs, operations or accounts could have one screen showing:
Completed Jobs With Unapproved Variations
For example:
J-10241 – $1,180 – Approval pending
J-10258 – $460 – Pricing required
J-10277 – $2,750 – Customer response pending
J-10291 – $820 – Internal review required
That is a much easier list to manage.
Compare Original Value With Final Job Value
Once variations are structured properly, reporting also improves.
You can compare:
Original Quote: $8,500
Approved Variations: $1,650
Final Job Value: $10,150
That gives you a more accurate picture of revenue.
You can also measure:
Total variation value this month
Average variation value
Variation approval time
and:
Variation value completed but not yet invoiced
Those numbers can become commercially significant very quickly.
Track Where Variations Come From
Variation data can also reveal process problems.
For example:
41 variations this quarter
18 – incomplete quoting
11 – site conditions
7 – customer scope changes
5 – technician recommendations
That may show an opportunity to improve quoting or pre-site inspections.
Not every variation can be prevented.
But repeated patterns can tell you where the original process is missing information.
Make the Technician's Part Simple
Technicians should not need to complete a complicated commercial process on site.
They may only need to record:
Extra Work Required: Yes
Description
Photos
Labour Used
Materials Used
The office can then handle pricing and approval.
The important thing is that the extra work enters a structured workflow instead of disappearing inside free-text notes.
Start With One Check Before Invoicing
Before a completed job moves to accounts, ask:
“Is there any recorded extra work that has not been commercially resolved?”
If yes, hold the job.
Assign the next action.
Then release it for invoicing once the variation has been approved or intentionally closed.
At 5M Consulting, we help trade and service businesses build workflows that connect what happens on site with what eventually gets billed.
Extra work should not become free work simply because nobody caught it before the invoice went out.