The Symptom Is Coming From a Different Unit Than Reported: Decision Tree

Why this matters

A tenant reports water staining their ceiling, a noise in their wall, or a smell in their unit, and the source turns out to be the neighbor's equipment, not theirs and not a shared main. This is different from a shared-riser fault where one cause hits many units. Here a fault lives entirely inside one unit's own dedicated system and its symptom migrates next door, so the unit that calls is the victim, not the location of the problem. Chase the fault only inside the complaining unit and you find nothing, because there is nothing there to find. This tree walks the three places the source can be: the reporting unit, a shared component, or a different unit entirely.

Safety first when the symptom is a hazard

Before tracing anything, judge the symptom for danger. Water spreading toward light fixtures, outlets, or a panel gets treated as an electrical hazard: keep people clear and de-energize the affected area before you go hunting for the source. A gas or exhaust odor migrating between units gets the gas-leak response, get people out, no switches or sparks, call the utility, because a leak in one unit can pool in another. A hazard that crosses a unit boundary is more dangerous, not less, because the people breathing it or standing in it are not the ones who caused it and may not know to act. Handle the danger across every affected space first, then diagnose.

Start here: is the source even inside the complaining unit

Stand in the complaining unit and ask whether the fault could physically originate there at all.

• If the symptom is above, behind, or below the complaining space (a ceiling stain, a wall noise, a floor leak), gravity and geometry say the source may be in an adjacent unit, not this one. Widen the search early.
• If the symptom is at the complaining unit's own fixture or equipment, start local, but stay alert to a shared-supply cause.

Step 1: rule the reporting unit in or out

Test the complaining unit's own equipment and connections first. If you can find an active fault there that fully explains the symptom, you are done, treat it as a normal single-unit repair. If the unit's own equipment tests clean and the symptom persists, the source is elsewhere: either shared or a neighbor. Do not keep re-testing a unit that has already proven innocent; that is how the wasted visit happens.

Step 2: shared component, or a different unit's private equipment

This is the branch that separates this problem from a shared-riser fault.

• If the suspected path is a component that serves several units (a common drain, a shared vent, a trunk or riser), you are in shared-system territory; hand off to the shared-system trace method rather than blaming one neighbor.
• If the path traces to equipment that belongs to one specific other unit (that unit's condensate line overflowing, its water heater weeping, its appliance draining wrong, its equipment vibrating a shared wall), the source is a peer unit's private fault, and the complaining tenant is the downstream victim. This is the case people miss because it lives behind someone else's door.

Step 3: confirm the cross-unit source before you accuse it

Do not tell a tenant their neighbor is the cause on a hunch. Confirm it: make the symptom change by operating the suspected neighbor's equipment where access and permission allow, or find physical continuity from the neighbor's fault to the affected space (a wet path, a shared cavity, a common wall the noise transmits through). A confirmed cross-unit source also changes who authorizes and pays for the repair, so proof matters here for reasons beyond the diagnosis.

Recap

1. Hazard crossing a unit boundary: safety response across every affected space first.
2. Symptom above, behind, or below the complaining space: suspect an adjacent unit early.
3. Test the complaining unit's own equipment; if clean, look outward.
4. Serves many units means shared, hand off to the shared trace; traces to one other unit means a peer fault.
5. Confirm the cross-unit source physically before naming it, because it changes who pays.

References

• OSHA and NFPA general guidance on water-near-electrical and gas hazard response
• Trade-standard practice for cross-unit fault isolation on multi-unit properties
• See related: Tracing a Fault Across a Shared System; The Wrong Unit Reported on a Multi-Unit Property