Customer changed the scope after approval? A small-job change-order workflow

First decide what actually changed

Ask one practical question: “Could a person who only saw the accepted estimate know we were going to do this?” If not, stop treating the change as an invisible note. Safety or emergency conditions need their own appropriate response; this workflow is not permission to continue unsafe work.

Why an Approved label is not enough

Jobber documents an important distinction. Certain edits to an approved quote, including line items or totals, remove the visible signature while a signed PDF of the earlier version is retained in an internal note. The quote can nevertheless remain Approved. To collect a fresh signature, its guidance describes returning the quote to Awaiting Response and resending it. That is documented product behavior, not a bug we discovered or a new test result. Jobber quote approvals.

Housecall Pro distinguishes the actor. Its documentation separates customer approval from a manual office action, which produces Pro Approved or Pro Declined. An internal status change and a customer-signed agreement are different evidence. Open the agreement or decision history instead of relying on the label alone. Housecall Pro approvals and signatures.

For any software, check the same four things: who made the decision, which version they saw, when they decided, and where the record is preserved. Do not manually mark a new version accepted merely to make the dashboard look tidy.

The one-page change record

You do not need a complicated approval system to make the difference visible. Start with a record linked to the correct customer and job, then use the acceptance method required for your work.

1. Original reference: estimate number, accepted version, date, and the unchanged base scope.
2. Change reference: a unique number, version, issue date, and who requested it.
3. Scope difference: additions, removals, substitutions, exclusions, and unresolved assumptions.
4. Money difference: additions and credits separately, the revised subtotal, and how applicable taxes or fees will be handled.
5. Timing difference: extra duration and dependencies such as materials, access, permits, or a separate visit. Do not invent a confirmed slot.
6. Decision evidence: authorized decision-maker, acceptance method, timestamp, and a retained copy of the exact version.
7. Operational handoff: who updates the work instructions, checks materials, and reconciles the invoice.

Preserve the original estimate even when your system creates a replacement version. If the price changes twice, keep the earlier proposal as superseded rather than deleting the trail. Stop old reminders and links from presenting that earlier proposal as current.

A message you can adapt before requesting acceptance

Hi [name], you asked us to change [specific item] on job [reference]. The attached change [number and version] shows what is added or removed compared with estimate [original reference and version].

The proposed adjustment is [addition] less [credit], with a revised [subtotal/total and tax treatment] of [amount]. The effect on timing is [verified impact or dependency]. The remaining agreed scope is unchanged.

Please review that version and use [the appropriate acceptance method] if you want to proceed, or contact us with questions. We will not start the proposed extra work while its acceptance is unresolved. We will confirm any revised booking separately.

Replace every placeholder and attach or link the right document. This message introduces the change; it does not replace required contract wording, cancellation information, signatures, or other local obligations. Never translate silence, an opened email, or “please explain the price” into acceptance.

Handle all four outcomes, not just yes

• Accepted: retain the decision, update instructions, and reconfirm capacity before promising a date.
• Declined: do not perform the rejected extra. Confirm whether the original work remains feasible and agreed.
• Pending: keep the proposed extra out of accepted work and invoice calculations. Send a proportionate clarification through the agreed channel if needed.
• Superseded: identify the replacement and stop treating the old change request as open. Do not count both versions in the total.

If a customer disputes the scope or authority of an approval, pause the affected commercial step and resolve that issue before sending routine collection reminders. A workflow status cannot settle a disagreement.

Reconcile additions, credits, and pending options

Fictional small repair job, in one chosen currency, before tax or fees. These numbers illustrate recordkeeping; they are not a price recommendation.

The invoice should explain those accepted changes without adding the pending 90 or forgetting the 40 credit. Check completed versus billable work, payment terms, taxes, fees, deposits, previous invoices, and payments separately. An accepted subtotal is not automatically the amount currently due.

Your five-minute end-of-job check

Open the accepted base estimate, each change decision, the worker’s completion record, and the draft invoice together. Can you trace every added or removed invoice item back to a decision? Can the customer see what changed? Are rejected, pending, and superseded items excluded from accepted extras? Resolve any mismatch before sending.

For work not yet quoted, start with our quote-request form comparison and pre-send estimate checklist. For an estimate still awaiting its first decision, use the estimate follow-up message templates. Those earlier stages should not be confused with a change to work the customer already accepted.

Need a software starting point? The solo operator hub connects the tools without assuming a one-person business needs a full dispatch platform.