Guide
Change Orders: Keep Trust When the Scope Changes Mid-Job
Stop and explain before doing extra work: describe what you found, that it wasn't in the original scope, and what it would cost to fix. Get approval in writing (text or email) with amount and work; take a photo of the issue; update the invoice right away, not at the end. One line in the note: 'Customer approved $X for [work] on [date].' When you're ready for software, look for job notes that capture scope changes with photos and approval workflows that attach to the job so original scope vs. changes is clear.
For teams dealing with 'while you're here' requests and unexpected issues who want to keep trust and avoid 'I didn't agree to that.'
Next: Use the stop-explain-approve-photo-update flow on the next 5 scope changes; store the approval with the job and see if disputes drop.
The situation
You're on a job and the customer asks for extra work, or you find something that needs fixing that wasn't in the original scope. You need to get approval and update the price without looking like you're trying to upsell, and you need a clear record so there's no dispute later.
What usually causes it
- No clear process for handling scope changes so each job is ad hoc and something gets missed.
- Waiting until the end to mention extra costs so the customer feels ambushed.
- Not documenting what was agreed vs. what's new so later you can't prove what was approved.
- Being vague about why the change is needed so it feels like an upsell instead of a fix.
Quick fixes you can try this week
- Stop and explain before doing extra work: 'I found [issue]. This wasn't in the original scope. Here's what it would cost to fix.'
- Get approval in writing (text or email): 'Customer approved $X for [work] on [date].' and store with the job.
- Take a photo of the issue before fixing it so you have proof of why the change was needed.
- Update the invoice immediately, not at the end, so the total isn't a surprise.
- Be clear about why: 'The original quote was for [X]. This [new issue] requires [Y].' so it's transparent.
If you're ready: what to look for
- Job notes that capture scope changes with photos so the record is attached to the job.
- Approval workflows that get customer sign-off before extra work so you're never doing unapproved work.
- Change order templates that make it easy to document additions without writing from scratch.
- Invoicing that shows original scope vs. changes clearly so the customer sees the breakdown.
Mistakes to avoid
- Doing extra work without approval; that's when 'I didn't agree to that' happens.
- Waiting until the end to mention extra costs; it feels like a bait-and-switch.
- Not documenting why the change was needed; you need proof if there's a dispute.
- Being pushy about upsells instead of explaining the need; trust drops when it feels salesy.
Take the FSM quick check
Quick checkSee if Field Service Management tools are right for your team.
Take the FSM quick checkRelated templates
Copy-paste scripts and checklists for this pain: