Why this matters
Change orders are a lead-response problem, not just a billing problem
A scope change can become a good customer experience when the team confirms what changed, why it matters, what it costs, and how the schedule is affected. It becomes a dispute when the work happens before the customer sees the difference between the original estimate and the extra request.
The templates below are intentionally plain. Edit the bracketed fields, verify the facts against the approved estimate, and keep a copy in the CRM or job notes.
Copy/paste change order text templates
1. Customer requested extra work
Hi [Name] — we can add [extra work requested]. That was not part of the original approved scope for [job/project]. The added price is [amount] and the schedule impact is [same day / adds X hours / moves completion to date]. Reply APPROVE if you want us to add it, or SKIP if you want us to finish the original scope only.
2. Technician found a new issue
Hi [Name] — while working on [original job], our tech found [new issue]. This is separate from the original scope because [reason]. Recommended next step: [repair/diagnosis/quote]. Added cost: [amount or quote needed]. Would you like us to approve this change before proceeding?
3. Photos/details needed before pricing
Hi [Name] — before we price the extra [requested work], can you send [photos/measurements/access details]? Once we confirm the scope, we’ll send a clear change-order price for approval before any extra work is started.
4. Schedule impact confirmation
Quick update: adding [extra work] changes the schedule from [original timing] to [new timing]. The approved price would be [amount]. Please confirm whether you want the added work included, or if we should keep today’s job to the original scope.
5. Not recommended / not safe to add today
Hi [Name] — we do not recommend adding [request] during today’s visit because [safety/access/material/scope reason]. We can either finish the original approved scope today or schedule a separate quote/visit for [next step].
6. Approval receipt
Thanks — we have your approval for the change order: [added scope], [price], [schedule impact]. We’ll add this to the job notes and proceed based on that approval.
CRM labels for change-order follow-up
- change-order-requested — customer or tech raised extra scope.
- change-order-priced — added scope and price have been written clearly.
- approval-needed — do not proceed until customer/owner approval is captured.
- schedule-impact — extra work changes arrival, completion, or return-visit timing.
- scope-declined — customer chose original scope only.
AI prompt to draft a safe change-order message
You are helping a local service business draft a change-order message. Use only the facts I provide. Do not invent price, timeline, warranty, diagnosis, discounts, financing, or safety claims. Original approved scope: [paste] Requested or discovered change: [paste] Approved added price or pricing status: [paste] Schedule impact: [paste] Photos/access/materials needed: [paste] Customer tone/context: [paste] Draft: 1. A short customer text confirming what changed. 2. A clearer email version if the change needs more detail. 3. CRM labels to apply. 4. Stop rules: list anything that requires owner/manager approval before sending.
Human review checklist
- Confirm the original estimate/scope before saying something is “extra.”
- Use only approved price, deposit, fee, warranty, and schedule language.
- Do not start extra work until the customer’s written approval is captured.
- Escalate safety, insurance, permit, legal, financing, hardship, or dispute situations to the owner/manager.
- Store the change-order message, approval, and final scope in the CRM/job notes.
Where this fits in the Local Lead Rescue System
This page is a free public resource. The paid Local Lead Rescue System expands lead response into missed-call scripts, quote follow-up, stale-lead reactivation, appointment confirmation, CRM labels, and review rules.
For an ungated starter workflow, use the free AI lead response quickstart.