Which Unit in a Multi-Unit Building: Decision Tree

Why this matters

A complaint from one tenant in a multi-unit building or a multi-zone commercial system does not mean the fault lives in that tenant's space. Shared risers, shared mechanical rooms, and shared distribution systems mean the actual cause can sit two floors away, behind a wall nobody thought to check, feeding several units at once. Diagnose only inside the reporting unit and you can spend a full visit finding nothing, while the real fault keeps producing the same complaint from a different tenant next week.

Start here: is there a shared hazard indicator

Before narrowing to one unit, check whether the complaint pattern includes any hazard signal, gas odor, an electrical burning smell, or water intrusion near power, reported from more than one location at similar times. A shared hazard across units is treated as a building-wide event: get affected units clear if there is any active danger, and escalate to the building's emergency shutoff or the utility before doing unit-by-unit diagnosis. Do not let "just check the one unit that called" delay a building-wide safety response.

Step 1: is this complaint isolated to one unit, or has more than one unit reported something similar

Ask the property manager or check the work-order history, not just the one call in front of you, before you start.

• If only one unit has reported the issue, the fault is more likely local to that unit's own equipment or the last shared point immediately feeding it. Go to Step 2.
• If more than one unit has reported something similar, even if the symptoms described sound a little different from each other, treat this as a probable shared-cause fault from the start. Go to Step 3 rather than diagnosing the first unit in isolation.

Step 2: does the fault stop at the unit's own equipment, or trace back past it

Test at the boundary between the unit's dedicated equipment and whatever shared system feeds it (a riser, a shared trunk line, a shared electrical feed, a shared mechanical room). If the supply at that boundary is normal and the fault only appears past it, the cause is local to the unit. If the supply at the boundary is already abnormal, the fault originates upstream even though only one unit has complained so far, likely because the other units have not yet noticed or reported it.

• If local to the unit, diagnose and repair as a standard single-unit call.
• If the boundary supply itself is abnormal, stop working inside the one unit and move to Step 3.

Step 3: trace the shared system from the complaint point backward to its source

Work backward through the shared distribution, the riser, the trunk line, the shared panel or mechanical room, checking the condition at each branch point until you find where the fault starts. The complaint from a single unit tells you where the symptom surfaced, not where the branch is that actually failed. A fault near the source of a shared system typically affects every unit downstream of that branch point; a fault only affecting one branch narrows your search to that specific branch, even if the failure point itself is in a shared space.

• If the fault traces to a component serving multiple units, notify the property manager before proceeding: a shared-system repair may require access to common areas or a temporary shutdown affecting units that have not complained yet.
• If the trace dead-ends at a point that only serves the original complaining unit, you have circled back to a local fault; treat it as Step 2's local case.

Step 4: confirm the fix against every affected unit, not just the one that called

Once you repair the identified cause, verify normal operation at every unit downstream of the fix point that could plausibly have been affected, not only the unit that originally complained. A shared-cause fault that seems fixed from one unit's perspective can still be active for a neighboring unit on a different branch of the same system.

Recap

1. Any shared hazard signal across units: treat as building-wide, act on safety first.
2. One complaint only: check the unit's equipment against its own supply boundary.
3. Multiple related complaints, or an abnormal boundary reading: trace the shared system backward to the actual branch point.
4. Confirm the fix at every unit that could have shared the cause, not just the one that reported it.

References

• Trade-standard practice for shared-system fault isolation in multi-unit buildings
• Local building and utility guidance on shared mechanical and electrical room access
• See related: The Shared System: Multiple Tenants, One Cause; Building-Wide vs Single-Unit Fault (decision tree)