Customer Says "The Last Guy Broke It" Translation Decision Tree

Why this matters

"The last guy broke it" is a loaded report that mixes a diagnostic clue with a liability minefield. Sometimes the prior tech genuinely caused the fault, and the customer's instinct is a valuable lead worth investigating first. Sometimes the prior work is coincidental and the customer is assigning blame to the most recent person who touched the system. How you translate this phrase determines both your diagnosis and your professional standing, because the customer is watching how you talk about another contractor's work, and a careless accusation can pull you into a dispute that is not yours. This article gives a way to use the clue without taking the bait, across any trade.

Symptom presentation

The customer reports a fault and attributes it to recent work by another contractor or a prior visit from your own company. The attribution may be precise ("it stopped the day after he left") or vague ("it's never been right since"). The phrase carries an emotional charge: frustration, distrust, sometimes an expectation that you will confirm wrongdoing.

Two things are tangled in the report. There is a diagnostic signal (a fault that began near recent work is often caused by that work) and a relational signal (the customer wants validation or a culprit). Separate them. Use the first; manage the second carefully.

Quick checks at intake

Pin the timeline. Did the fault begin immediately after the prior work, or sometime later? Immediate onset strengthens the work-caused hypothesis; a gap weakens it. Ask specifically what the prior work involved and where.

Stay neutral in language. Gather facts without endorsing or dismissing blame. "Let me see what was done and what's happening now" keeps you diagnostic, not adversarial. Avoid agreeing that someone broke it before you have evidence.

Look at what the prior work physically touched. Disturbed wiring, a reconnected line, a replaced part, a changed setting. The most likely work-caused faults are in whatever the prior tech handled, so that is where you look first.

Isolation tree

Branch A: fault began immediately after prior work, and the prior work touched the now-failing area. Investigate the prior work first. A loose connection, a reversed part, a wrong component, a kinked line, a changed setting, or debris left behind is the high-probability cause. This is the case where the customer's instinct is likely correct, and finding it is fast.

Branch B: fault is in the same system but a different area than the prior work touched. Possible the prior work disturbed something adjacent (bumped a wire, knocked a sensor, dropped debris) or possible it is coincidental. Check the adjacent-disturbance candidates, then proceed to normal diagnosis if those clear.

Branch C: fault is unrelated to what the prior work touched. The attribution is likely coincidental timing. Diagnose the symptom on its own merits without reference to the prior contractor, and be ready to explain to the customer, factually, that the fault is in a different area than the recent work.

Branch D: the prior work was incomplete or substandard but did not directly cause this fault. Document the workmanship issue factually for the customer's record, but keep it separate from the diagnosis of the presenting symptom. Two different problems should not be merged into one accusation.

Branch E: the fault is normal wear or end of life, and the prior work is being blamed because it is the most recent event. Educate the customer on the actual failure mode. The translation here is "this would have failed regardless of who was last here," delivered without dismissing their concern.

Branch F: you genuinely cannot tell whether the prior work caused the fault. Document what you found objectively (state of connections, parts, settings) without assigning blame you cannot prove. Let the facts stand; do not speculate about another contractor's competence on the record.

Confirming diagnosis

Confirm the cause by evidence, not by the customer's theory. If correcting the prior work resolves the fault, the work-caused hypothesis is confirmed and you can state that factually. If the fault traces elsewhere, the prior work was not the cause regardless of timing, and you say so plainly.

Document objectively. Record what you observed (a loose terminal, a wrong part, a normal worn component) in neutral, factual terms. Avoid characterizing intent or competence; a work order that says "neutral found loose at the device" is defensible, one that says "previous tech was careless" is not.

Tell the customer what you found in factual terms, and let them draw conclusions. Your job is the diagnosis and the fix, not adjudicating a dispute with another contractor.

Next steps

When the prior work caused the fault, correct it, document factually, and let the customer decide how to handle the other contractor. When it did not, diagnose and repair the actual cause and explain the timeline neutrally.

If the customer wants you to formally assess another contractor's work for a dispute or claim, that is a separate, paid scope; clarify that your service visit diagnoses and fixes, and a formal assessment is its own engagement. Keep your documentation factual either way, because it may end up in a dispute you did not start.

References

• ISO 13379-1 (Condition monitoring and diagnostics of machines; failure cause attribution).
• OSHA 29 CFR 1910 (general industry safety; hazard correction regardless of origin).
• NARI (National Association of the Remodeling Industry) standards of practice and professional conduct.
• PHCC (Plumbing-Heating-Cooling Contractors Association) code of ethics and workmanship guidance.