The work grows, the invoice doesn't
A tech is on a routine job and finds the real problem — a corroded line, a part that's failing, a second issue the customer didn't mention because they didn't know it was there. The right move is obvious: fix it while you're standing there, because a second truck roll for the same site is pure waste. So the tech fixes it. And then one of two bad things happens. Either the extra work never makes it onto the invoice — the tech meant to note it, got busy, and you ate the labor and the part for free. Or it lands on the invoice and the customer, who never agreed to it, disputes the whole bill: "I never approved that — I'm not paying for work I didn't ask for."
Both outcomes come from the same gap: the scope grew on-site and nothing captured the growth at the moment it happened. The work expanded; the agreement didn't. A change order is the discipline that closes that gap — a recorded, approved adjustment to the job's scope and price, captured the instant the scope changes, while the tech and customer are still face to face. Get it right and the extra work is extra revenue. Get it wrong and it's either a write-off or a war.
Why uncaptured scope creep bleeds you both ways
When you trace change-order failures, they fall into two piles, and most operations suffer from both at once:
- Silent give-aways. The tech does the extra work and forgets to bill it. The labor, the part, the drive — all delivered free because the line item was never added while the job was open. Across a year this is one of the quietest margin leaks in the trade: real work, real cost, zero revenue.
- Surprise-bill disputes. The tech does the extra work, bills it, and the customer balks because they never said yes. Now you're discounting to keep the peace or chasing an invoice the customer feels ambushed by — the exact surprise-bill dispute that sinks your reviews and your cash flow.
Notice both come from doing the work before the agreement and the record catch up. The fix isn't "remember to bill it" or "always call the office first" — it's making the approval and the line item part of the same on-site moment as the work itself.
Get the yes before the wrench turns
The single rule that prevents both failure modes: no added scope without an approval, captured before the work is done. When a tech finds something beyond the original job, the sequence is fixed — surface it, price it, get the customer's yes, then do it. Not "do it and explain later."
This is far easier when the tech is equipped to quote on the spot, the same way a good on-site estimate works. A tech with a price book in hand can show the customer a firm number for the additional work in seconds — "while I'm in here, this line is failing; it's $180 to replace it now and saves you a second visit." The customer sees a specific price against a specific problem, decides, and the decision is on the record. A vague "there's some other stuff I should probably do" invites a vague answer and a later dispute; a priced, itemized change invites a clean yes or no.
Capture the change as a line item, not a memory
The approval only sticks if it's attached to the job immediately. The moment the customer says yes, the added work becomes a line item on the open job — at the price quoted — so the billing detail grows exactly as the scope grows. There's no second step where the tech has to remember to tell the office, which is precisely where uncaptured work disappears.
In Hosting Field, a job carries line items for labor, parts, and expenses with live totals, and those items can be added and edited right on the job while it's open — then they lock once the job is invoiced. So when scope grows mid-visit, the tech adds the approved work as it happens and the job total recomputes instantly; by the time the job hits its completed state, the expanded scope is already in the billable detail, not in someone's head. The on-job time tracking captures the extra labor the change required the same way — clocked on the job, rolled into a billable line at the tech's rate — so the additional time doesn't vanish either. The change order isn't a separate document to chase; it's the job's own line items growing as the work does.
Make the approval provable
A verbal yes at the door is better than nothing, but it's still memory — and memory is exactly what disputes are made of. The stronger the record of the approval, the less ground a customer has to stand on later. Two disciplines make the change defensible:
- Itemize what changed. The added work shows on the job as its own clearly described line, separate from the original scope, so the invoice tells the story: here's what you booked, here's what we found, here's what you approved. Transparency pre-empts the dispute.
- Tie it to the completion sign-off. When the customer reviews the finished work — including the added scope — and gives an on-site sign-off, that acknowledgment now covers the change too. They saw the expanded line items and signed against them. Framed honestly for what it is — proof of completion, not a legal e-signature — it turns "I never approved that" into a closed conversation, because the record shows they reviewed it at the door.
Don't let change orders become a slush fund
A caution that protects the relationship as much as the margin: change orders are for genuine scope growth — a real problem found, a real addition the customer chose — not a habit of low-balling the original quote and padding it on-site. Customers learn fast. A shop whose every job mysteriously grows 40% once the tech is inside earns a reputation for bait-and-switch, and that reputation costs more than the padding earns. Quote the original job honestly, surface real additions transparently, and let the customer genuinely choose. The change-order discipline exists to capture work that legitimately appeared, not to manufacture it.
It also has to stay fast. If approving a change means the tech calls the office, waits on hold, and stalls in the customer's hallway, the discipline dies and the tech goes back to "fix it and sort it out later." The whole point is that the price, the yes, and the line item all happen in the same on-site minute. Equip the tech to do it there, or it won't happen at all.
What to measure
- Change-order capture rate — added work that got an approval and a line item versus work that got done off the books. If techs are doing extras you can't find on invoices, you're giving away labor and parts.
- Average change-order value per job — extra revenue captured per job that grew. A healthy number means real additional work is being billed; a suspiciously high one means you might be padding, so watch it honestly.
- Dispute rate on jobs with change orders — if jobs that grew get disputed more, your approval isn't being captured well enough at the door. Tighten the on-site yes and the sign-off.
The extra work a tech finds on-site is some of the best work you'll do — it's already-dispatched, already-trusted, and it saves a second trip. But it only helps if the agreement grows with it. Surface the change, price it, get the yes, and let the line items grow as the scope does — and the work that used to either vanish or detonate becomes clean, approved, billable revenue every time.