A Recent Repair May Have Caused the New Fault (Decision Tree)
Why this matters
A repair goes in, and days later a new symptom shows up that was not there before. Maybe it was your work, maybe another shop's. Either way the question is loaded: did the repair cause this, or did something else just happen to break next? Answer it wrong and you either eat a callback that was a coincidence, or you dodge a collateral fault you actually created and lose the customer's trust when it surfaces. The honest, systematic way through is to test causation instead of assuming it in either direction. This tree keeps you fair to the customer and to the work.
Start here: safety before the credibility conversation
If the new symptom is a hazard (arcing, a gas or CO concern, a leak under pressure, a tripping protective device), handle the hazard first, regardless of who caused it. De-energize and verify, relieve pressure, or shut off and confirm control before you sort out blame. A dangerous new fault after a repair is a safety response, not a warranty debate.
First, confirm the symptom is genuinely new
Before you connect it to the repair, make sure it did not exist before, quietly.
- Ask what specifically is different now versus before the repair, in the customer's words.
- Rule out the same fault resurfacing. A repair that did not fully fix the original problem can look like a new symptom when it is really the old one coming back. That is a different article on a patch masking a fault, but check it here.
- Check whether the new symptom was simply hidden by the original fault and only became noticeable once the first problem was fixed.
If it is truly new and truly post-repair, continue.
The adjacency test: did the repair touch it
Collateral damage almost always lands close to what the tech's hands were on. Map the new fault against what the repair physically involved.
- Same component, system, or area the repair worked on: adjacency is high, causation is a live suspect.
- A connection, fastener, line, or setting the repair had to disturb to get access, even if it was not the target: classic collateral. Access work knocks things loose.
- A different system entirely, untouched and not shared with the repair: adjacency is low, coincidence rises.
Low adjacency does not clear the repair automatically, but high adjacency is where you look first.
Collateral patterns to check
Repairs introduce faults in a handful of repeatable ways. Inspect for these on anything the work touched or disturbed.
| Pattern | What to look for |
|---|---|
| A connection left loose or over-tight | A terminal, fitting, or fastener disturbed for access and not properly remade |
| Wrong torque or seating | A part installed too loose or too tight, a gasket or seal not seated |
| A wrong or missing consumable | The wrong lubricant, sealant, filter, or fluid; one left out entirely |
| Air, debris, or contamination introduced | A line opened and not purged or cleaned, leaving an airlock or fouling |
| A setting or protective device bumped | A valve, damper, breaker, dip switch, or control setpoint changed by hand or by accident |
| Something moved out of alignment | A part shifted, a linkage disturbed, a clearance closed up |
The reversibility check
Where it is safe and practical, the cleanest proof is reversibility.
- Inspect and correct the specific collateral item you found (remake the connection, reset the setting, purge the line).
- Retest. If the new symptom clears, the repair caused it and you have both the confirmation and the fix.
- If undoing or correcting the suspect item changes nothing, the repair is less likely the cause, and you widen the search.
When it is coincidence
Sometimes a part simply reached the end of its life the same week the repair happened. If the new fault has low adjacency, no collateral pattern checks out, and it is a normal wear failure, do not force a causal story onto the timing. Say so plainly, show the customer what actually failed, and treat it as the separate job it is. Forcing causation to please a customer is as dishonest as dodging it to protect the work.
Owning your own work
If it was your repair and the evidence points to collateral, own it directly and make it right. The customer already suspects the timing; a straight answer backed by what you found protects the relationship better than a defensive one. If it was another shop's repair, describe the finding as a finding, not an attack, and let the facts carry it.
Recap
- Handle any hazardous new symptom before assigning cause.
- Confirm the symptom is genuinely new, not the old fault resurfacing or newly visible.
- Score adjacency: how close is the new fault to what the repair touched or disturbed.
- Check the collateral patterns, use a reversibility test to confirm, and call true coincidence honestly rather than forcing causation either way.
References
- Trade-standard practice on post-repair verification and workmanship inspection
- Manufacturer documentation on correct torque, consumables, and reassembly procedures
- See related: A Prior Patch Is Masking the Symptom; The Fault Started After Another Trade Did Work