Why change requests need a guardrail
A small scope change can silently change price, parts, crew time, access, permit needs, warranty language, and schedule availability. If the team answers from memory or lets AI draft from incomplete notes, customers can receive a promise the estimator, dispatcher, or owner cannot honor.
STOP AUTOMATION: do not quote, approve, schedule, or send a revised estimate from AI output alone. A human owner must verify the original estimate, requested change, price impact, material availability, schedule impact, and any warranty/permit/policy limits.
Change-request intake card
| Field | What to capture | Human review rule |
|---|---|---|
| Original estimate | Estimate number, date, scope summary, price, expiration, estimator/owner. | Use the source estimate, not a recalled summary or AI-generated rewrite. |
| Requested change | What the customer wants added, removed, swapped, expedited, or clarified. | Separate confirmed customer words from internal assumptions. |
| Evidence/source | Photos, measurements, site notes, part/model numbers, tenant/owner approvals, or vendor notes. | Flag missing proof before repricing or promising feasibility. |
| Price/schedule impact | Possible added cost, credit, deposit, crew time, access window, materials, and availability. | Only the approved estimator/owner can confirm price or timing. |
| Customer-safe reply | Acknowledge the change, explain the review step, and set a realistic next update time. | Do not imply approval, discount, warranty, emergency priority, or same-day scheduling unless verified. |
| CRM closeout | Label, owner, due time, revised estimate link, customer reply status, and next follow-up. | Keep old and revised scope connected so teams do not work from the wrong version. |
Copy/paste customer replies
Hi [Name] — thanks for the update. I have your requested change as: [customer words]. I am going to compare it against estimate [#] and confirm any price, material, or schedule impact before we revise anything. I will update you by [time/date].Quick note: I do not want to guess on the revised price or timing. [Owner/estimator] needs to review [photo/measurement/part/access detail] first. Once verified, we can send the revised estimate or next-step options.CRM note: change request for estimate [#]. Customer requested: [change]. Proof needed: [photos/measurements/approval]. Owner: [person]. Due: [date/time]. Do not schedule or promise revised pricing until owner review is complete.AI review prompt
Act as a cautious local-service estimate change-request reviewer. Use only the verified facts below. Do not invent price, diagnosis, availability, warranty coverage, permit/legal requirements, discount, approval, timeline, or customer consent. Return: 1) missing intake fields, 2) risky promises in the draft response, 3) customer-safe acknowledgement wording, 4) owner/estimator questions, and 5) a STOP AUTOMATION decision if the change request is not ready.
Verified facts:
- Original estimate number/date/scope:
- Customer requested change:
- Source proof available:
- Price/schedule/material impact known? [yes/no/source]
- Owner/estimator reviewer:
- Customer update deadline:
- Stop rules:Fast QA before sending
- Compare the requested change against the original estimate and any revised estimate draft.
- Confirm whether the change affects deposit, parts, labor, access, permits, warranty, or schedule.
- Use a review-status reply if the answer is not ready; do not let AI fill unknowns.
- Attach the revised estimate or scope note in the CRM before a dispatcher, technician, or property manager acts on it.
Related free assets: Quote Scope Comparison Checklist, Change Order Text Templates, and Estimate Approval Follow-Up Templates.
Disclosure: Horizon Flow is Andrew Burton's digital product catalog. This worksheet is useful without purchase; product links are labeled and UTM-tagged.