Building-Wide vs Single-Unit Fault: Decision Tree

Why this matters

The first decision on any multi-unit or commercial call is scope: is this one unit's problem, or the building's problem showing up in one unit first? Get that call wrong and you either under-scope a shared failure that will keep generating complaints, or over-scope a genuinely local fault and burn time surveying equipment that was never involved. This tree is the fast path to the right scope before you commit to a diagnostic plan.

Start here: any hazard indicator present

Before scoping anything, check for a hazard signal: gas odor, burning smell, arcing, or water intrusion near live power. If present, treat it as building-wide by default until proven otherwise; evacuate or clear the immediately affected area, de-energize or shut off supply if you can do so safely, and call for the appropriate emergency response before doing any comparative diagnosis. Scope determination waits for hazard control, not the other way around.

Step 1: check one comparable point outside the complaining unit

Before you touch the complaining unit's equipment, find the nearest comparable point that is not inside that unit: a neighboring unit on the same system, a shared riser or panel, or a building-level meter or gauge if one exists.

• If the comparable point outside the unit is also abnormal, you are very likely looking at a building-wide or shared-system fault. Go to Step 2.
• If the comparable point outside the unit reads normal, the fault is more likely contained to the complaining unit. Go to Step 3.

Step 2: confirm the building-wide scope before committing resources

A single abnormal reading outside the unit is a strong signal but not full confirmation. Check at least one more point on the shared system, ideally on a different branch than the first check, to rule out a coincidental second local fault.

• If the second check is also abnormal, treat this as building-wide or shared-system in scope. Trace the shared system back to its source rather than continuing to diagnose inside individual units (see the related article on tracing a fault through a commercial distribution system).
• If the second check comes back normal, you may have two independent local faults rather than one shared cause. Diagnose each affected point separately as its own local fault.

Step 3: rule out a recently-shared cause even when the comparable point looks fine

A comparable point reading normal right now does not fully rule out a shared cause if the shared system has redundancy, buffering, or enough capacity that only the most-affected unit has shown symptoms yet. Check whether anything changed building-wide recently: a utility event, work performed in a shared space, a schedule or setpoint change made at a building-level control. If something changed building-wide and the timing lines up with the complaint, treat it as a probable shared cause even though only one unit has reported so far, and monitor the comparable points you checked for symptoms developing after your visit.

• If nothing building-wide changed and no other point shows any sign of strain, proceed with confidence as a local, single-unit fault.

Step 4: diagnose at the confirmed scope

• Single-unit scope: diagnose and repair using the unit's own equipment and supply boundary as the full extent of the investigation.
• Building-wide or shared scope: notify the property manager of the likely broader impact before proceeding, and trace from the complaint point back to the shared source rather than repairing symptoms unit by unit.

Recap

1. Any hazard signal: treat as building-wide, control the hazard first.
2. Check one comparable point outside the complaining unit.
3. Abnormal outside the unit: confirm with a second point, then trace the shared system.
4. Normal outside the unit: rule out a recent building-wide change before committing to single-unit scope.
5. Diagnose at the scope you've confirmed, not the scope of the first complaint.

References

• Trade-standard practice for scope determination in multi-unit and commercial diagnosis
• Local building code guidance on shared-system inspection access
• See related: Which Unit in a Multi-Unit Building (decision tree); The Shared System: Multiple Tenants, One Cause