GDS Technology — Built, Wired and Secured podcast banner
Watch on YouTube →
Built, Wired & Secured episode artwork: The Forgotten Circuit: When Your Building's Critical Systems Share One Weak Link
Episodes Built
Episode 186

The Forgotten Circuit: When Your Building's Critical Systems Share One Weak Link

November 18, 2026
Key takeaways
  • A small breaker can create a building-wide operational disruption when critical systems share its circuit.
  • Panel schedules and labels can become unreliable as building equipment and loads change.
  • A generator does not guarantee resilience if a transfer switch, feeder, panel, or other component remains a shared point of failure.
  • Have a licensed electrician map critical loads, trace circuits, and verify isolation; do not treat the audit as DIY work.
  • Use periodic thermal scans and prioritize repairs by business impact, while considering inexpensive preventive fixes.

Show Notes

One breaker, multiple failures

A building can appear to have backup power and separate critical systems while still depending on one small, overlooked component. In the episode’s opening example, a 20-amp breaker in a panel that had not been reviewed for years took security, elevators, and HVAC offline. The building had not simply lost a circuit: it had exposed a shared dependency that turned one electrical fault into a building-wide operational problem.

When a breaker trips, several systems can fail together, leaving tenants unable to enter, stuck in an elevator, or working in uncomfortable conditions. The failure is especially difficult to manage when teams do not know the systems share a power path until the outage happens. The size of the breaker is not a useful measure of the business impact.

How critical systems end up sharing a weak link

Electrical distribution reflects the building’s design assumptions at a particular point in time. Over the years, access control may be added, an elevator controller upgraded, or HVAC equipment installed. If circuit destinations are not traced and records are not updated, the original panel schedule can stop describing reality. Labels may be wrong, and changed loads may share circuits with systems that operations now considers critical.

Some loads may have been grouped as non-essential on old drawings, even though their role has changed. The result can be a security system and an elevator on one branch circuit, or several business-critical systems dependent on one panel, transformer, or feeder. The operational risk comes from the dependency—not from how small or unremarkable the component looks.

Why a generator does not guarantee resilience

A generator can be correctly sized and still fail to protect the systems that matter. The transfer switch could be undersized, or a feeder serving a critical panel could also carry non-critical loads. A shared component may bypass the intended backup path. Redundancy on a drawing is not proof that systems are isolated in practice.

A useful question for property and facilities teams is: “What breaks if this goes down?” Apply it to each panel and shared component. If losing one panel means losing everything, the building has a concentration of risk worth investigating. The goal is to find where critical loads converge and determine whether the power paths are genuinely independent.

What a practical audit includes

The property team can prepare, but circuit tracing and electrical testing should be performed by a licensed electrician. This is not a DIY project. The electrician can review one-line diagrams and panel schedules, trace circuits with a toner, perform a load study, and use a thermal imager to look for abnormal heat. The property team’s knowledge of building operations helps make the investigation more efficient.

  • List the critical loads: security, elevators, fire alarm, life-safety systems, and HVAC needed for server rooms.
  • Trace each load back to its source and verify what else shares its breaker, panel, transformer, or feeder.
  • Ask the electrician to verify isolation and compare field conditions with diagrams and panel schedules.
  • Identify shared dependencies and rank them by the likely business impact of failure.

Finding a shared circuit is only the start. Teams need to decide which issue to address first. Consider the downstream cost of a tenant being unable to access an office or an elevator being unavailable for a day. At the same time, do not dismiss inexpensive repairs simply because they are not large capital projects. A contactor replacement costing a few hundred dollars may avert substantial downtime. Prioritization should account for both the consequences of failure and practical quick wins.

A routine test catches a failing contactor

One example from the discussion shows why preventive inspection matters. During quarterly generator load testing at a facility, the team noticed a slight flicker in the lights. An electrician thermally scanned the panels afterward and found a contactor running hot on the circuit feeding the fire alarm panel. If it had failed, the fire alarm would have gone down. The team replaced the contactor for a few hundred dollars.

The point is not that every flicker signals a major hazard. It is that a small observation during routine testing can prompt a targeted inspection before a component fails. A regular inspection schedule, including thermal scans of panels serving critical systems, can help reveal problems before they become emergency repairs.

Three actions to take next

  • Map critical loads so you know exactly where each life-safety and business-critical system gets power.
  • Have a licensed electrician verify isolation and identify critical systems that share a breaker or panel.
  • Schedule periodic thermal scans of panels serving those systems to look for trouble early.

Do not wait for an outage to discover that redundancy exists only on paper. A focused audit helps property teams understand their electrical dependencies, make informed repair priorities, and protect daily operations. The best operational outcome is often invisible: systems keep working, tenants carry on, and a preventable failure never becomes an emergency.

Listen to the episode

Listen to this episode of Built, Wired & Secured for a practical discussion of mapping critical loads, verifying isolation, and maintaining the electrical distribution that supports building operations. Additional episodes, articles, and resources are available at builtwiredsecured.com.

Deeper dive

The hidden dependency behind a building outage

When a commercial building loses power, a generator may start and a transfer switch may operate—yet critical systems can still go dark. The reason may be far less dramatic than a failed generator: several systems may depend on the same breaker, panel, contactor, transformer, or feeder. If that shared component fails, it can take down more than one system at once.

In the episode’s opening example, a 20-amp breaker in a panel that had not been reviewed in years took security, elevators, and HVAC offline. The component was small; the operational consequences were not. Tenants could have trouble entering the building, elevators could become unavailable, and offices could become uncomfortable. A single electrical fault can become a cascade when the affected systems share a power path.

Why the circuit map can drift from the building

Buildings change after their original electrical design. A team may add access control, upgrade an elevator controller, or install an HVAC unit. These changes can alter which systems depend on which circuits. If someone does not trace the new or modified circuits and update the records, the panel schedule and labels may no longer match the installation.

That mismatch can hide a critical dependency. Systems once considered non-essential on drawings may now support daily operations. A security system and elevator might share a branch circuit, or multiple important systems may converge at one panel or feeder. The question is not only whether the building has backup equipment. It is whether each critical load can remain supplied when another part of the distribution path fails.

Documentation is useful only when it reflects field conditions. An old one-line diagram or a neat panel schedule does not prove that loads are isolated. Over time, small changes and incomplete records can create an arrangement nobody intended—and nobody notices until the circuit trips. The hidden dependency is often the difference between what a property team believes is connected and what an electrician finds when tracing the circuit.

Redundancy must work in practice

A generator can be sized correctly and still leave a building exposed. The transfer switch may be undersized, or the feeder to a critical panel may be shared with non-critical loads. A shared point in the distribution path can undermine the backup arrangement, even when the major equipment appears redundant.

For property managers and facilities leaders, the key question is: “What breaks if this goes down?” Ask it about panels and other shared components. If one panel fails and the answer is “everything,” that is a sign to investigate. The aim is to identify where two or more critical loads share a dependency and determine what the consequences would be if it failed.

This is a practical resilience issue, not simply a drawing exercise. The value of an audit is knowing what the building actually depends on, not assuming that an installed generator or labeled circuit has eliminated the risk. Backup equipment matters, but so does every component between that backup source and the systems it is meant to support.

Build a useful critical-load audit

The property team can make the work more efficient by preparing a list of important systems and describing their operational role. The episode identifies security, elevators, fire alarm, life-safety systems, and HVAC that supports server rooms as examples of critical loads. Then a licensed electrician should trace each one back to its source and verify what shares the path.

This is not a DIY project. A licensed electrician can review one-line diagrams and panel schedules, trace circuits with a toner, conduct a load study, and use a thermal imager to spot components running hot. The property team’s preparation helps focus that professional work on systems that matter to people and operations.

  • List the life-safety and business-critical systems in the building.
  • Record where each system gets power, then have an electrician trace that path back to its source.
  • Check for shared breakers, panels, transformers, and feeders.
  • Compare the actual installation with panel schedules and one-line diagrams.
  • Ask the electrician to verify isolation rather than relying on drawings alone.

The output should make dependencies visible. If critical systems share a point, the team can understand the failure scenario and choose a response based on impact, rather than waiting for an outage to expose the connection. The audit also gives the property team a more concrete basis for discussing repairs and capital planning.

Prioritize fixes by impact—and do not ignore small repairs

An audit may find several choke points, but a building may not be able to fix all of them at once. Rank the issues by what a failure would mean for tenants and operations. What would it cost if occupants could not access their offices? What would an elevator being out of service for a day mean? Considering downstream impact can make the value of a repair clearer than looking only at the equipment’s price.

Capital planning also has to balance large risks with quick wins. A small repair can prevent substantial disruption. In the episode, the example is a contactor replacement costing a few hundred dollars; the discussion notes that a repair of this scale can avert a far costlier day of downtime. The lesson is not to ignore major projects, but to avoid overlooking inexpensive work that addresses a meaningful risk.

Use both the likely consequence of failure and the scope of the repair when setting priorities. A focused sequence of improvements can be more useful than either deferring every issue or spreading resources so thinly that the most consequential dependency remains untouched. The decision is not simply “cheap versus expensive.” It is how the cost and effort of a repair compare with the interruption it could prevent.

How routine testing exposed a hot contactor

During quarterly generator load testing at one facility, the team noticed a slight flicker in the lights. It was not a dramatic failure, but the electrician followed up with a thermal scan of the panels. The scan found a contactor running hot on the circuit feeding the fire alarm panel. If that contactor had failed, the fire alarm would have gone down. The team replaced it for a few hundred dollars.

This example shows how a routine test and attention to a small warning sign can lead to preventive maintenance instead of emergency repairs. Periodic thermal scans of panels serving critical systems are described as an inexpensive, non-invasive way to identify trouble before failure. Regular inspections help catch issues while there is still time to plan the work. The best outcome is that tenants never notice the problem because the repair happens before an interruption.

Three steps to start tomorrow

First, map critical loads. Know exactly where each life-safety and business-critical system receives power. Second, have a licensed electrician verify isolation and confirm that critical systems do not share a single breaker or panel. Third, schedule periodic thermal scans for the panels serving those systems.

These steps do not promise that every outage can be prevented, and they are not a substitute for professional electrical work. They give property and facilities teams a practical starting point: understand the real power paths, identify shared dependencies, and address the most consequential risks before they interrupt tenants or operations.

Waiting for a failure means discovering the dependency at the worst possible time. A deliberate audit and inspection schedule can make resilience more than a line on a drawing. For a deeper discussion of critical loads, isolation, and preventive inspection, listen to the episode of Built, Wired & Secured.

Frequently Asked Questions

How can one breaker affect security, elevators, and HVAC in a commercial building?

Several systems can go down together when they share a breaker or another part of the same electrical path. The episode describes a 20-amp breaker that took security, elevators, and HVAC offline. Outdated panel schedules and changes to building loads can hide these shared dependencies until a circuit fails.

Does having a backup generator mean my building’s critical systems are protected?

Not necessarily; the generator can be correctly sized while another shared component remains a single point of failure. The episode gives an undersized transfer switch or a feeder shared with non-critical loads as examples. Property teams should have a licensed electrician trace critical loads and verify isolation in practice.

What should a property manager do to find electrical single points of failure?

Start by listing life-safety and business-critical loads, including security, elevators, fire alarm, and relevant HVAC. Then have a licensed electrician trace each load to its source, check shared breakers, panels, transformers, and feeders, and verify isolation. Periodic thermal scans can also help spot problems before failure.