Callback Traced to Adjacent System Not My Work Decision Tree

Why this matters

A callback is a verdict before you arrive: the customer believes your last repair failed. Sometimes it did. But often the original repair is sound and a different, adjacent system has now failed in a way that produces the same symptom. If you accept the callback as your fault and redo good work, you eat the cost and still do not fix the real problem. If you wave it off without proof, you damage the relationship and may be wrong. The discipline is to treat a callback as a fresh diagnosis, prove whether your prior work is intact, and isolate whether the new fault is in your scope or an adjacent system that simply mimics it. This applies to HVAC, plumbing, electrical, and appliance service equally.

Symptom presentation

The customer reports "the same problem is back" or "it never really got fixed." On arrival, the symptom may look identical to the original complaint, which is exactly why it gets misattributed. Identical symptoms can come from entirely different causes. The blower that would not run last month and will not run today may be a different failure with the same outward sign.

Resist both reflexes: the defensive "my work is fine" and the guilty "I must have missed something." Diagnose first.

Quick checks

Re-establish the state of your prior repair before anything else:

• Is my repaired component still doing its job? Verify the specific part or fix you performed last time is intact and functioning, in isolation if possible.
• Is the symptom truly identical, or just similar? Pin down differences: timing, conditions, magnitude. Subtle differences point to a new cause.
• What is adjacent and shares the symptom path? Upstream supply, downstream load, shared controls, common drains or circuits, and the structure all can produce the same outward failure.
• What changed since the original visit? New equipment added, weather shift, usage change, or another contractor on site can introduce an adjacent fault.

Isolation tree

1. Is my original repair still good?

   • No, my fix failed or was incomplete: own it. Honor the callback, correct it, and review why it did not hold.
   • Yes, my fix is intact and functioning: proceed; the new symptom has a different source.

2. Does the same symptom now trace to an adjacent system?

   • Verify the new fault location with a measurement. If the cause is clearly in a system you did not touch and was not part of the original scope, this is a new fault, not a callback.

3. Did my work, though sound, contribute to exposing the adjacent fault?

   • Sometimes a correct repair restores load or flow that then exposes a marginal adjacent component. The original work is not defective, but the interaction is real. Name it honestly; it affects how you present the cost.

4. Is the adjacent fault in my scope or another trade's?

   • In my scope: it is new work, presented as such with clear documentation that the original repair is sound.
   • Another trade's: make safe if needed, document, and refer, while showing the customer that the original repair held.

Confirming diagnosis

Confirm the distinction with evidence the customer can see:

• Demonstrate your original repair working in isolation.
• Demonstrate the adjacent system failing independently, with a reading or a reproduction.
• Show that correcting the adjacent fault resolves the current symptom while your prior work continues to function.

If your original repair fails the isolation test, the callback is legitimately yours. Accept it without argument and correct it. The goal is the truth, not a verdict in your favor.

Common traps

Two opposite errors dominate callback handling, and both come from skipping the diagnosis:

• The guilt trap: assuming the callback must be your fault and redoing your repair without verifying it failed. This eats labor on good work and leaves the real adjacent fault untouched, so the symptom returns a third time.
• The defensive trap: dismissing the callback as "not my work" before proving the original repair is sound. If you are wrong, you have insulted the customer and abandoned a genuine warranty obligation.

A third subtler trap is the interaction case: your correct repair restored flow or load that then exposed a marginal adjacent component. This is neither pure fault nor pure innocence. Name it as what it is, an interaction, and present the adjacent work as new while acknowledging the connection honestly.

Next steps

Document the callback as either honored-and-corrected or diagnosed-as-new-adjacent-fault, with the evidence for whichever it is. Where it is a new fault, present the finding and options before doing the work, and make clear on paper that the original repair is intact. Keep a record of repeat-versus-new determinations over time; a pattern of the same adjacent system failing after your repairs may point to an interaction you should design around rather than rediscover each visit. A callback handled with proof either way protects the relationship; the worst outcome is redoing good work or dismissing a real one without evidence.

References

• ISO 14224 on failure attribution, as-found condition recording, and distinguishing repeat failures from new failures.
• ISO 13379-1, Condition monitoring and diagnostics of machines, on reasoning from observable symptoms to distinct causes.
• ACCA and PHCC service and warranty guidance on callback diagnosis and scope determination.
• NFPA 70B on documenting electrical findings during repeat service events.