The Story Doesn't Match What You Found: Decision Tree

Why this matters

The customer says it started yesterday. The corrosion says it has been leaking for a year. The account and the evidence do not line up, and that gap is not noise, it is a clue pointing straight at a missing fact. Techs who force the evidence to fit the story chase ghosts. Techs who let the mismatch lead them find the detail the customer left out. This tree is how you work a contradiction instead of ignoring it.

Start here: trust the evidence, question the account

Physical evidence has no motive and does not misremember. When hardware and history disagree, the hardware is right and the history is incomplete. That does not make the customer a liar, memory compresses and people summarize, but it means the story is the thing to reopen, not the meter reading.

Safety first: if what you found is an active hazard the story downplayed, a gas odor called "a funny smell," scorching called "a little spark," water at a live panel, stop diagnosing. Make the hazard safe (evacuate for gas, de-energize and verify dead for electrical, relieve pressure, isolate water) before you work the contradiction.

Name the kind of mismatch

• If the timeline does not match, they say new, the wear says old: the fault predates their awareness. Something changed recently that made a long-standing problem finally show. Ask what changed in the last week, not what broke.
• If the cause does not match, they blame one thing, the evidence points elsewhere: they have connected two events that are not connected, or disconnected two that are. Treat their causal theory as a guess, not a finding.
• If the severity does not match, they call it minor, you find major (or the reverse): either they have normalized it, or someone has been managing it quietly. Ask how long, and who has been dealing with it.
• If the location does not match, the symptom they report is not where the fault is: you are looking at a downstream effect. Trace back to the source.

Work the gap, do not paper over it

1. Re-ask the history against the evidence. "This looks like it has been going on a while, does that sound right?" Give them the physical fact and let them place it. People remember more when you anchor them to something concrete.
2. Look for the intervening event. A recent remodel, a storm, a power event, a new appliance, a service visit. The thing that "changed nothing" is usually the change.
3. Check for a prior repair. Non-stock parts, fresh tool marks, mismatched fittings, a bypass. If someone worked on this, the story of "it just failed" is missing a chapter. See related: You Find a Jury-Rigged Repair Hiding the Real Fault.
4. Separate what they observed from what they concluded. "The AC died" is a conclusion. "The air stopped feeling cold" is an observation. Keep the observation, drop the conclusion.

When it still does not reconcile

If the evidence and the account cannot both be true, decide whether the gap is innocent or deliberate. Innocent gaps resolve with better questions. A deliberate gap, where they are steering you away from something, needs a different approach. See related: You Suspect the Customer Is Hiding Something.

Either way, diagnose from what is in front of you. The system cannot lie about its own condition. Document what you found, note where it conflicts with the reported history, and base your recommendation on the evidence.

Recap

1. Handle any hazard the story downplayed before anything else.
2. Trust the evidence; treat the account as incomplete, not false.
3. Name the mismatch: timeline, cause, severity, or location.
4. Re-ask history anchored to the physical evidence.
5. Hunt the intervening event and any prior repair.
6. If it will not reconcile, decide innocent versus deliberate and diagnose from the evidence regardless.

References

• Trade-standard forensic practice: physical evidence over reported history
• OSHA hazard-response basics for gas, electrical, and pressure hazards
• See related: The Customer Who Left Out the Detail That Mattered; A Key Fact Surfaces Mid-Repair (decision tree); Reading Contradicts Complaint (decision tree)