Variation approvals rarely go missing because of paperwork alone
When extra work is done without approval, or approved work never makes it to invoice, the problem is usually blamed on paperwork.
The form was not completed. The photos were not attached. The customer never signed. The office did not follow up.
Those things matter, but they are usually symptoms rather than the underlying issue.
In most trade, service and construction businesses, variations go missing because the approval path is broken across multiple handovers:
- someone on site identifies the extra work
- someone in the office prices it
- someone sends it to the customer
- someone waits for approval
- someone tells the team to proceed
- someone later tries to invoice it
If that chain depends on memory, emails, phone calls and scattered attachments, approvals will go missing. Not because nobody cares, but because ownership becomes unclear and the workflow has no reliable state.
The fix is not just “better paperwork”. It is a structured variation workflow that controls how a variation moves from identification to pricing, approval and invoicing.
The real problem is usually handover failure
A variation can be captured properly and still go wrong.
A technician might take good photos and note the extra work clearly. A supervisor might send the information through. The estimator might even price it quickly. But if there is no defined handover between those stages, the variation can still stall or disappear.
Common failure points look like this:
- site sends evidence, but nobody owns the next action
- office prices it, but the customer never receives a formal approval request
- customer approves by text or phone, but that approval is not tied back to the variation record
- work proceeds urgently on site, but commercial approval is never regularised
- approved variations are not visible to invoicing, so chargeable work is missed
- pending variations sit in inboxes with no follow-up trigger
That is why it helps to separate two different ideas:
Variation capture
This is the act of recording that extra work exists.
For example:
- a supervisor notices the original scope is no longer accurate
- a technician records additional labour, materials or access issues
- site photos show unforeseen conditions
- a note is made that the customer requested extra work
Capture matters, but capture alone does not protect revenue.
Variation workflow control
This is the system that determines what happens next.
It defines:
- who reviews the variation
- what evidence is required before pricing
- who can send it for approval
- what counts as customer approval
- whether work can proceed before approval
- how pending items are followed up
- when the approved amount becomes available for invoicing
Many businesses capture variations reasonably well but still lose money because they never built the control layer.
Start by defining who identifies, prices and approves variations
A reliable variation process needs explicit ownership at each stage.
If those roles are vague, staff will fill the gaps inconsistently. One project manager will be strict, another will wave things through, and someone in accounts will later be left trying to reconstruct what happened.
At a minimum, define these responsibilities.
Who identifies the variation
This is usually someone on site:
- technician
- installer
- site supervisor
- project manager
Their job is not to produce a perfect commercial document. Their job is to identify that the work falls outside the agreed scope and trigger the process early enough to control it.
That trigger matters. If site teams only raise a variation after the work is already complete, the business is immediately in a weaker position.
Who prices the variation
This may sit with:
- estimator
- project manager
- operations manager
- office administrator with pricing authority
The key is that pricing should happen from a complete pack of information, not from fragments delivered across calls, texts and emails.
If the pricing person has to chase photos, interpret unclear notes and confirm what was actually requested, delays are predictable.
Who approves the variation internally
Many businesses skip this step and go straight from site to customer.
That often causes problems because the variation goes out before the business has checked:
- whether the work is genuinely out of scope
- whether the description is clear
- whether the pricing is complete
- whether enough evidence exists
- whether the customer contact is correct
An internal approval step does not need to be bureaucratic, but someone should confirm that the variation is ready to leave the business.
Who obtains customer approval
This should not be ambiguous.
If site assumes the office is sending it, and the office assumes the project manager already handled it, the variation sits in limbo.
One role should own customer submission and follow-up, even if different people contribute to the content.
Define the minimum evidence required before approval
A common cause of disputes is that the business seeks approval without enough evidence, or completes the work without being able to justify the change later.
The variation record should require enough information for someone not on site to understand three things:
- what changed
- why it changed
- what the customer is being asked to approve
That usually means some combination of:
- a clear description of the extra work
- photos
- marked-up plans or site sketches where relevant
- quantity or scope detail
- notes about what triggered the variation
- labour and material basis for pricing
- timing impact, if relevant
This does not mean turning every variation into a legal brief. It means defining the minimum evidence standard that makes approval defensible.
For example, “additional trenching required” is weak.
A better record would explain that the original route was obstructed by unforeseen ground conditions, include site photos, identify the revised trench length and note the added labour and materials required.
That level of clarity helps the customer approve more confidently and gives the office something usable for invoicing if questions arise later.
Customer sign-off needs to be deliberate, not implied
One of the biggest risks in variation approval is treating vague customer communication as formal approval.
Comments like these are where trouble starts:
- “They seemed fine with it on site.”
- “They said to just keep moving.”
- “I’m pretty sure the client contact agreed over the phone.”
- “We got an email saying go ahead, but it did not mention the amount.”
For a variation workflow to hold up operationally, the business should define what counts as customer sign-off.
That might include:
- signed variation form
- approval by email against a clearly described variation and amount
- approval through a customer portal or job record
- SMS approval only if the variation reference, scope and amount are clearly tied together
The exact method matters less than consistency.
What matters is that the approval:
- is linked to a specific variation
- identifies the work being approved
- includes the commercial amount or pricing basis
- can be retrieved later
- is visible to the people who need to act on it
If approval comes in through one channel and the variation record lives somewhere else, the process needs a deliberate step to connect them. Otherwise the business ends up with evidence scattered across inboxes and phones.
Use statuses to control the workflow, not just record the variation
A variation list without meaningful status control becomes a backlog of unresolved items.
The point of status is not reporting for its own sake. It is to make the next action visible.
A practical variation approval workflow might include statuses such as:
- identified
- evidence required
- ready for pricing
- priced
- sent to customer
- awaiting customer approval
- approved
- rejected
- approved and ready for invoicing
- invoiced
The exact labels are less important than the logic behind them.
Each status should answer two questions:
- what condition has been met
- who owns the next action
For example:
- if a variation is “evidence required”, site owns the next step
- if it is “ready for pricing”, office or estimating owns it
- if it is “sent to customer”, someone should own follow-up by a defined date
- if it is “approved”, operations and invoicing should be able to act from that state confidently
Without status discipline, variations drift because nobody knows whether the issue is missing information, missing pricing, missing customer response or missing invoice action.
Build triggers so pending variations do not rely on memory
A variation approval process breaks down when follow-up depends on someone remembering to chase it.
That is especially common when site is moving quickly and office staff are juggling multiple jobs.
A better approach is to define triggers tied to variation state.
Examples:
- when a variation is marked “identified”, the record cannot progress without required evidence
- when evidence is complete, pricing is assigned automatically or manually to the responsible person
- when sent to customer, a follow-up date is created
- if no response is received by that date, the variation is flagged for action
- when approved, the record becomes visible to scheduling or delivery if work is waiting on authorisation
- when completed, the approved value is made available to invoicing
The principle is simple: the workflow should create the reminder, not the person.
That does not mean every step needs heavy automation. Even a modest system can support this if statuses, owners and due dates are defined properly.
Urgent on-site work needs an exception path
Not every variation can wait for a neat approval cycle.
Sometimes work has to proceed immediately because of safety, access, damage prevention, compliance or the practical reality of having a crew already on site.
This is where many businesses either lose revenue or create conflict, because they treat urgency as a reason to skip the process entirely.
A better model is to define an exception path.
That path should answer:
- who can authorise urgent work internally
- what conditions justify proceeding before customer sign-off
- what minimum evidence must still be captured on site
- how the customer is notified
- how the variation is regularised commercially after the fact
For example, the process might allow a project manager to authorise urgent remedial work up to a certain threshold where delaying would create a bigger operational problem. But the workflow would still require:
- photos
- site notes
- reason for urgency
- record of who authorised proceeding
- formal customer approval request issued as soon as possible
The exception should be controlled, not informal.
If “urgent” becomes the default excuse for bypassing approval, the business has not created an exception process. It has created a leak.
Approved variations must hand over cleanly to invoicing
Approval is not the end of the process.
A surprisingly common failure is that the variation gets approved properly, the work gets done, and invoicing still misses it because the commercial handover is weak.
This usually happens when the invoice team cannot easily see:
- which variations are approved
- which have been completed
- what amount should be billed
- whether the approved amount has already been partially claimed
- which customer or job record the charge belongs to
If invoicing relies on someone emailing accounts at the end of the month with a list of extras, work will be missed.
The cleanest approach is to ensure that an approved variation carries forward the information invoicing needs, including:
- variation reference
- linked job or project
- approved amount
- scope description
- approval evidence
- billing status
That does not mean accounts needs every site photo. It means the commercial record must be complete enough that invoicing is not reconstructing the story from scratch.
A variation should move into invoice readiness through the workflow itself, not through a separate memory-based handover.
What a reliable approval flow looks like in practice
A good variation approval workflow is usually simple to describe, even if the implementation needs care.
A practical sequence looks like this:
Site identifies extra work The person on site records the issue as soon as it is known to be outside scope.
Required evidence is captured Photos, notes, quantities and any supporting detail are attached before pricing begins.
Internal review confirms it is ready Someone checks that the variation is legitimate, clear and commercially usable.
Pricing is prepared The business calculates the amount or pricing basis from complete information.
Customer approval request is issued The request clearly states the variation scope, amount and any relevant timing impact.
Approval status is tracked The variation remains visible as pending until the customer response is received.
Work proceeds under the correct rule Either approval has been received, or an authorised urgent-work exception applies.
Approved variation becomes invoice-ready Once completed, the approved amount and supporting reference are available to invoicing.
Invoice status is updated The variation is marked billed so it does not sit in a grey area indefinitely.
That is the operational model. Software may support it, but software is not the model.
Common fixes that do not actually solve the problem
When variation approvals go missing, businesses often try to patch the issue with one isolated improvement.
Examples include:
- introducing a new form
- asking staff to email the office more consistently
- creating a shared spreadsheet
- telling project managers to follow up harder
- adding another chat group
Those changes can help temporarily, but they usually fail because they do not solve the handover logic.
A form does not define ownership. An email does not create workflow state. A spreadsheet does not enforce evidence requirements. A chat message does not create invoice readiness.
If the process still relies on individuals to manually bridge the gap between site, office, customer and accounts, the failure mode remains.
Good variation control protects both revenue and relationships
A structured approval process is not just about extracting more charges.
It also helps reduce disputes because the customer sees:
- what changed
- why it changed
- what evidence supports it
- what they are approving
- when the work was authorised
That clarity matters commercially. It is easier to have a straightforward conversation about a variation before the work is buried inside a final invoice.
Internally, it also reduces the friction between teams.
Site is not blamed for failing to “tell the office”. Office is not blamed for failing to “chase the client”. Accounts is not blamed for “missing extras”.
Instead, the process makes the handovers visible.
The goal is control, not paperwork for its own sake
If variation approvals are going missing between site, office and customer, the answer is usually not more admin. It is better workflow control.
That means being clear about:
- who identifies the variation
- what evidence is required
- who prices it
- who sends it for approval
- what counts as customer sign-off
- how pending items are tracked
- how urgent exceptions are handled
- how approved variations reach invoicing
When those rules are explicit, fewer chargeable items disappear into the gaps between teams and systems.
Where a variation process already spans multiple people, inboxes and job records, mapping the approval path properly before adding automation is usually the right starting point. That is the kind of workflow design 5M Consulting helps businesses sort out when revenue is leaking through operational handovers.