Change Orders 101: How to Handle Scope Creep Without Losing the Client
"While you're here, could you also..." is one of the most common sentences in field service, and one of the most dangerous to handle badly. Say yes without adjusting the price and scope, and you've quietly agreed to do more work for the same money. Say no bluntly, and you risk the relationship over what might be a completely reasonable request. A change order process is the difference between the two.
What a change order actually is
A change order is simply a written update to the original, approved scope — what's being added or changed, what it costs, and a new approval from the client before that new work happens. It doesn't need to be complicated or feel like a legal document. It needs to exist, in writing, before the extra work starts — not as an afterthought added to the final invoice.
Why "I'll just take care of it" backfires
Quietly absorbing small additions feels generous in the moment, but it trains a client — often without either side realizing it — that the original estimate was never really the final word. On a longer job, that pattern compounds: several small unbilled additions can add up to real, uncompensated hours, and by the time it's noticed, it's awkward to suddenly start charging for something that's been free the whole project.
Catching scope creep before it's a dispute
The moment to flag a change is the moment the request happens, not the moment the invoice is written. A simple habit — "happy to add that, let me get you a quick price for it before I start" — normalizes change orders as routine rather than confrontational. Most clients respond well to it, because it's honest and transparent, not because they're being difficult about paying for extra work.
When the change reveals a problem, not a request
Sometimes scope changes because of what's found once work starts — rot behind a wall, wiring that doesn't meet current code, a pipe in worse shape than expected. This is exactly why the original estimate's list of exclusions matters (see: the anatomy of a winning estimate) — a clear "this estimate assumes X; if we find Y, that's a separate change order" note turns a potentially awkward surprise into something the client was already prepared for.
Keep the process short, not bureaucratic
None of this needs to slow a job down. A short, clear description, a price, and a quick approval — even a text message confirmation for a small change — is enough to protect both sides. The goal isn't paperwork for its own sake; it's making sure "what we agreed to" is never just two different memories of the same conversation.