Symptom in My Trade Caused by Another Trade: Own vs Refer Decision Tree

Why this matters

The symptom shows up in your trade, but the cause lives in someone else's. An HVAC unit short-cycles, and the real cause is an electrical voltage problem. A faucet drips, and the real cause is whole-house pressure from a regulator. An appliance trips, and the real cause is a shared circuit overload. If you repair only the symptom in your domain, the fault returns and the callback is yours. If you reach across into a trade you are not licensed for, you take on liability you cannot insure and may violate code. The skill is recognizing when the cause has crossed a trade boundary, then deciding cleanly whether you own it, refer it, or fix your part and hand off the rest. This logic is genuinely universal across the trades.

Symptom presentation

The customer called you because the visible failure is in your equipment. You diagnose past the symptom and find that nothing in your scope is actually broken. The driver is upstream or adjacent: the power feeding your unit, the water pressure feeding your fixture, the structure your equipment is mounted to, the gas supply, or the controls another contractor installed.

The danger is the path of least resistance: replacing your component because that is what you were called for and what you are equipped to do, even though your component was a victim, not the cause.

Quick checks

Establish the trade boundary before deciding ownership:

• Is my component actually failed, or reacting? A part that fails again immediately after replacement was reacting to an external cause.
• Where does the cause physically live? Trace one step upstream of your equipment: the breaker, the supply line, the regulator, the shared neutral, the structural mount.
• What license and code govern that cause? If correcting it requires a license or permit you do not hold, the cause is out of your scope to repair, even if you can diagnose it.
• Is it safe to operate as-is? A cross-trade cause that creates a hazard changes the decision from "refer at leisure" to "make safe now and refer immediately."

Isolation tree

1. Is the cause within my licensed scope?

   • Yes: own it. Diagnosing past your symptom into an adjacent-but-still-yours cause is normal good work. Fix the real cause.
   • No: proceed; you will refer or coordinate.

2. Is the cause creating an immediate hazard?

   • Yes: make safe within your authority (de-energize, isolate, shut off supply, tag out), inform the customer, and refer to the correct trade without delay. Document the hazard.
   • No: proceed to the ownership decision.

3. Can I fix my part now and is that part worth fixing independently?

   • Yes: fix your component, but tell the customer in writing that the underlying cause is in another trade and the symptom will likely return until that cause is corrected. Do not let your repair imply you solved the root.
   • No, my part will just fail again: hold the repair. Replacing a victim part repeatedly is throwing parts at someone else's problem.

4. Who should the customer call, and can I coordinate it?

   • Name the trade, describe the finding in their language, and offer to coordinate if you have a referral relationship. A clean handoff with documentation protects you and serves the customer better than a vague "call an electrician."

Confirming diagnosis

Confirm the cause really is cross-trade before referring, so you do not hand off a problem that was yours:

• Re-verify your own component is genuinely sound and is only reacting.
• Demonstrate the external cause with a measurement: the supply voltage, the inlet pressure, the shared-circuit load, the structural movement. A number, not a hunch, is what the next trade and the customer will trust.
• Confirm that correcting (or temporarily removing) the external cause makes the symptom stop, where it is safe to test that.

If your component still misbehaves after the external cause is ruled out, the fault was yours after all. Reclaim it.

Common scenarios

The pattern repeats across trades with the same shape:

• HVAC symptom, electrical cause: a unit short-cycles or trips not because the equipment is failing but because of low or unbalanced voltage, a loose feed, or a shared circuit overload. Replacing the contactor or board fixes nothing; the electrical feed is the cause.
• Plumbing symptom, pressure cause: a fixture drips or a valve fails repeatedly because whole-house pressure is too high from a failed regulator. Replacing the cartridge again and again treats the victim, not the regulator.
• Appliance symptom, supply cause: an appliance faults or will not heat because of a shared overloaded circuit, low voltage, or inadequate supply, not because the appliance is broken.
• Equipment symptom, structural cause: vibration, leaks, or misalignment driven by a settling or inadequate structure the equipment is mounted to.

In each, the tell is the same: your component fails again immediately after replacement, because it was reacting to an external cause you did not address.

Next steps

Document the finding with measurements, photograph the boundary, and put the referral in writing so the customer understands why your repair alone would not have held. Where you fix your part and refer the cause, make the dependency explicit on the invoice and work order so the customer cannot later believe you left a job half done. A measured cross-trade finding handed off cleanly earns trust; a silent symptom-patch earns a callback and a dispute.

References

• OSHA 29 CFR 1910 Subpart S (Electrical) and the lockout/tagout requirements of 29 CFR 1910.147 for making cross-trade hazards safe before referral.
• ISO 14224 on as-found condition recording and failure attribution across system boundaries.
• ACCA and PHCC scope-of-work and referral guidance on staying within licensed trade boundaries.
• NARI (National Association of the Remodeling Industry) coordination guidance for multi-trade jobs and handoffs.