Customer Disputes What Was Taken - The Response Standard

Purpose

This SOP guarantees that when a customer disputes what a completed job included, an item taken they say should have stayed, or an item left they say should have gone, the shop answers from a documented record and a consistent resolution rule, not from whoever happens to remember the job. A scope dispute handled by memory turns into a credibility fight the shop usually loses, because the customer is certain and the crew is guessing, and a guess that turns out wrong costs more in trust than the disputed item was ever worth. Handled against the walkthrough record, the same dispute becomes a two-minute comparison with a defensible answer either way, and a defensible answer is what keeps a single disputed toolbox from becoming a public review dispute.

Scope

Covers a scope dispute raised any time from job completion through the shop's stated claim window, on a job where a confirmed scope was captured at walkthrough. It does not cover the live, on-arrival decision about a scope change discovered before or during loading (see the rebid-vs-honor decision trees, which own that in-the-moment call), it does not cover producing the scope record itself (see the in-home walkthrough and item confirmation standard, this SOP is downstream of that record and depends on it existing), and it does not cover a dispute over what a taken item was worth rather than whether it should have been taken at all (see the item-value dispute response, a separate claim with a separate resolution path).

Roles and the handoff between them

The procedure

1. Log the dispute verbatim and pull the confirmed-scope record before responding to anything. Write down exactly what the customer says, item by item, then open the walkthrough record for that job. Acceptance: the disputed item is named in writing and the record is open before any answer is given. Wrong looks like reassuring the customer "we'll look into it" and improvising a response from memory the next day. Stop rule: if the job's confirmed-scope record cannot be located, say that plainly to the customer rather than guessing, and escalate to the office manager immediately, since the shop is now answering without its own evidence. Hazard: none, this is a records step.

2. Compare the disputed item against the record and classify it. Check whether the item appears on the walkthrough's item list or photos, and whether authorization was captured for it specifically or only as part of a bulk description. Acceptance: the item is marked confirmed-in-scope, confirmed-excluded, or a genuine gap, the record simply does not address it. Wrong looks like reading a vague or bulk-described record as decisive proof either way when it does not actually cover the specific item in dispute. Stop rule: where the record is silent on the specific item, that counts as unresolved, not decided in the shop's favor by default, and it carries forward to the resolution step rather than being closed here. Hazard: none.

3. Check the item's disposition before promising anything about recovering it. If the claim is that something was wrongly taken, confirm where it actually is: still on the truck, at the shop, already routed to a donation partner, already scrapped or landfilled per the routing standard. Acceptance: a status is established, recoverable-intact, recoverable-but-processed, or unrecoverable, before the customer is told anything definite. Wrong looks like telling the customer "we'll get it back for you" on the first call, before anyone has actually checked where the item went. Stop rule: if disposition cannot be confirmed the same business day, tell the customer that directly and give a concrete follow-up time rather than leaving the promise open-ended. Hazard: if recovery would require entering an active transfer-station tip floor or a landfill working face, the crew does not walk out onto it; recovery in that setting is coordinated through the facility's own staff, never attempted solo to make good on a promise already made.

4. Resolve according to the record and the disposition, in writing. A confirmed-in-scope claim is declined with the record shown to the customer. A confirmed-excluded claim or a genuine record gap triggers the shop's stated remedy: return the item if it is still recoverable, or apply the compensation policy if it is not. A bulk description like "garage general contents" is real authorization for the pile as a whole, but it is weak evidence for a dispute over one specific item inside that pile, and the resolution should reflect that weakness rather than treat a bulk photo as equal to an itemized sign-off. Acceptance: the customer receives the classification, the evidence behind it, and the resolution, in writing, not only over the phone. Wrong looks like resolving verbally with nothing sent afterward, which leaves no record if the customer disputes the resolution itself next. Stop rule: if the customer rejects a resolution built on a genuine gap rather than a clear record, escalate to the shop's formal complaint path rather than closing the file unilaterally, and if that escalation does not happen within the stated window, the file stays open rather than getting marked resolved by default. Hazard: none.

5. Close the file, and where the dispute exposed a real documentation gap, feed that back separately from the customer resolution. A gap found in step 2, an item genuinely never captured by name, is a process signal, not just a one-time inconvenience. Acceptance: the file closes with a final classification and resolution, and any identified gap is logged as a coaching item distinct from the customer's own case. Wrong looks like closing the ticket and treating the underlying gap as fixed just because this one customer was satisfied. Stop rule: where disputes repeatedly trace to the same crew lead or the same walkthrough habit, that pattern is flagged to office as a training issue rather than logged as another isolated coincidence. Hazard: none.

The record this produces

• The dispute, verbatim: what the customer claims, item by item.
• The comparison result: confirmed-in-scope, confirmed-excluded, or gap, with the record evidence cited.
• Disposition: where the disputed item actually was when the claim was checked.
• Resolution: what was offered, in writing, and any claim or compensation reference.
• Process signal: any documentation gap logged separately, for coaching rather than for this one file.

One run of this standard, filled in

A residential garage cleanout. Two days after completion, the customer calls: a red metal toolbox with hand tools was taken, and they say they thought it was staying.

• Step 1: the office logs the claim verbatim, pulls the job's walkthrough record before saying anything else. Pass.
• Step 2: the item list reads "garage general contents, per photo," no toolbox named individually. The walkthrough photos do show a red toolbox sitting in the pile the customer walked and signed off on. Classified: a genuine gap, present and photographed within the confirmed bulk scope, but never itemized or authorized by name. Pass.
• Step 3: the office, wanting to be helpful, tells the customer on the first call "we'll get it back for you," before checking anything. Fail against the step's own acceptance, a status was promised with nothing confirmed. Stop rule taken: the office manager catches it before the callback and checks the shop's load log, the metal and appliance run that included the toolbox went out on scrap pickup two days earlier. Status: unrecoverable. The office calls the customer back the same day with the accurate status rather than letting the false promise stand unaddressed.
• Step 4: because the item was present in a confirmed but non-itemized bulk pile, the gap benefits neither side outright. The office applies its stated remedy for an unresolved scope gap on an unrecoverable item, sends the photo evidence and the resolution in writing the same day. Pass.
• Step 5: the office logs a process signal: a bulk description like "garage general contents" does not protect against a dispute over one specific item inside it. Coaching note goes to the crew lead: call out anything that reads as an individual tool set, box, or higher-visibility item by name during the walkthrough, even inside a pile that is otherwise handled in bulk. Pass.

The step that mattered was 3, not 2. The record gap was real but defensible either way; the false promise on the first call was not defensible at all, and fixing it same-day is what kept a genuine gap from becoming a broken commitment on top of it.

References

• See related: the in-home walkthrough and item confirmation standard, which produces the scope record this SOP compares every dispute against.
• See related: the customer-adds-items rebid-vs-honor decision trees, which own the live, on-arrival scope-change decision rather than a post-completion dispute.
• See related: the on-site sort, donate, recycle, dump routing standard, which determines whether a disputed item's disposition is actually recoverable.
• See related: the item-turns-out-to-have-value dispute response, which owns a dispute over an item's worth rather than whether it should have been taken.