Show Notes
When Power Loss Becomes a Building-Wide Event
A commercial-building power interruption is not only an electrical problem. In the first minutes, it can become a safety, security, communications, and business-continuity event. Lights may change, an elevator may stop or return, an access-control system may report incomplete status, HVAC may enter another operating mode, and building automation values may become stale or delayed.
For occupants, these are not separate technical categories. They experience one building that suddenly feels uncertain. A badge may behave differently, a call may not complete, a workspace may begin to warm, or a question may reach the property desk before the team knows whether the interruption is limited to the building.
This episode examines the first fifteen minutes after normal power disappears: the period when uncertainty either gets organized or spreads. The central question is not simply whether backup power exists. It is what must happen next, who owns each action, what is confirmed, and how the building team communicates with people affected by the event.
Backup Power Is Not the Same as Resilience
A backup source can start exactly as expected and still leave major operational questions unresolved. The availability of emergency power does not automatically confirm that people can move safely, that access is functioning as intended, that elevators are accounted for, that communications channels are available, or that occupants have received accurate information.
The episode challenges a common assumption: keeping more systems active does not automatically make a building more resilient. Some functions must remain available. Other functions may be able to pause safely, restart in an agreed sequence, or shift to a manual workaround. Those choices should be made during planning, not debated from scratch while an outage is underway.
- Define which functions are essential to safety, movement, communications, and building operations.
- Identify functions that can pause without creating an unacceptable operational risk.
- Establish restart priorities before an emergency creates time pressure.
- Document what success looks like for each critical function.
Build a Shared Operating Picture First
The first operational task is to establish the building’s actual condition. Teams need to distinguish confirmed information from assumptions. A quiet screen may mean a system stopped, shed load, entered a protective state, or simply stopped reporting. A displayed status does not replace local observation, especially when the people inside the building may be experiencing something different.
A useful opening assessment includes a small set of questions:
- Is the interruption limited to the building, or is it affecting a broader area?
- Did the emergency source become available?
- Which areas are occupied?
- Are elevators accounted for?
- Can the response team communicate internally and with occupants?
- Which systems are confirmed operational, and which are still unknown?
Someone must own this picture. Without a coordinator, property staff may focus on occupants, facilities may focus on equipment, security may focus on movement and access, and IT or communications staff may focus on connectivity. Those responsibilities matter, but they need to connect into one shared view of the event.
Clarify Ownership and Handoffs
The episode outlines a concise handoff structure: state what happened, when it happened, what is confirmed, and what remains unknown. Then assign immediate ownership. Facilities checks building conditions. Security accounts for movement and access. Property operations manages occupant communication. The communications or IT lead confirms which channels are working and connects the coordinator with the people doing physical work.
That structure keeps the organization in control of the response even when outside help is needed. A vendor may be important to recovery, but the vendor is not the first fifteen minutes. If the first instruction is only to call for help, the team may have outsourced ownership without realizing it. The better approach is to call for assistance while retaining responsibility for the building’s operating picture, decisions, and communication.
The Operational Gaps That Create False Confidence
A composite example in the conversation illustrates the risk. The emergency source was available at minute one. By minute three, the property desk still had no confirmed occupant message. At minute five, facilities and security were operating from different assumptions about elevator status. The equipment was not the whole issue. The missing element was the sequence between teams.
This is why resilience should be measured by the quality of decisions, not only the presence of backup equipment. Teams should ask:
- What breaks if this function goes down?
- Who notices first?
- Who verifies the condition?
- Who makes the next decision?
- Who tells the people affected?
- What information is confirmed versus incomplete?
Map the First Fifteen Minutes
Start with the building experience instead of a complicated technical diagram. Write down what a person would observe: lights change, an elevator call does not complete, a control value stops updating, or a workspace begins to warm. Then identify the affected function, the person who checks it, and the next decision required.
Add a time column to expose where plans may be unrealistic:
- Immediate: establish the coordinator, determine what is known, account for safety and movement concerns, and confirm available communication paths.
- By five minutes: communicate a confirmed initial message to occupants, assign owners to essential functions, and reconcile conflicting assumptions between teams.
- Before fifteen minutes: create controlled awareness of building conditions, identify the next operating decisions, and provide a clear handoff for continued response or the next shift.
A plan can list every task and still be impossible to execute if one person is expected to perform three roles at once. Test staffing sequence and communication, not just equipment availability.
Practice for Controlled Awareness
If power remains out at minute fifteen, success is not pretending the building is normal. Success is controlled awareness and controlled action: the team understands the building’s condition, occupants have accurate information, critical functions have owners, and the next shift can understand what has occurred.
Practice begins with separate discussions among property operations, facilities, security, IT or communications, and other affected groups. Individual conversations reveal what each group believes its role is. Bringing those groups together reveals whether those beliefs connect. Include tenant representatives, security leadership, business-continuity contacts, or campus operations when appropriate, because they may recognize dependencies that are invisible from a systems-only perspective.
Keep the plan usable. The first page or first conversation should identify the coordinator, the next decision, and the communication path. Reference material can follow. A continuity plan that is never exercised becomes a historical document. Build a one-page map of your building’s first fifteen minutes, then run a short tabletop exercise with the teams that depend on one another.
The First Fifteen Minutes of a Power Loss Define Building Resilience
When normal power disappears in a commercial building at nine in the morning, the visible interruption is only the beginning. Lighting may change. An elevator may stop between floors or return to a designated location. Access control may provide incomplete status. Heating and cooling equipment may enter another mode. Building automation may show alarms, delayed values, or no meaningful update at all.
For the people working in the building, none of this arrives as a neat collection of technical categories. They experience one workplace that suddenly feels uncertain. A badge may not behave as expected. A call may not complete. A workspace may begin to warm. The property desk may receive calls before the response team knows whether the event is isolated to the building or affects a larger area.
That is why a power loss should not be treated as only a power problem. It tests dependencies, priorities, communication, and trust between the people responsible for keeping a building running. The first fifteen minutes are especially important because the decisions made during that period shape the entire response that follows.
Move Beyond the Backup-Power Question
Many continuity conversations start and stop with a familiar question: Do we have backup power? That matters, but it is not enough. A backup source can become available exactly as intended while access, communications, tenant expectations, staff responsibilities, and recovery decisions remain unclear.
The technical event is that emergency power started. The operational question is whether the building is functioning in a way people can understand and manage. Are people able to move safely? Are elevators accounted for? Does the team know which areas are occupied? Can staff communicate with one another and with occupants? Are control-system values current, incomplete, or misleading?
Resilience is not measured only by whether equipment starts. It is measured by the quality of the decisions a building team can make when information is incomplete and time matters.
Why More Active Systems Do Not Always Mean More Resilience
It is tempting to assume that the most resilient response keeps every possible system operating. But more activity does not automatically create more resilience. Some functions need to remain available because they support safety, controlled movement, communications, or other essential operations. Other functions may be able to pause safely, restart in a defined order, or use a manual workaround.
The critical distinction is that these priorities cannot be invented in the middle of the event. If an operator must decide in real time whether a function can pause, the organization is already asking that person to make a planning decision under pressure. The decision belongs in preparation.
Each building will have its own priorities, but the planning discipline is consistent:
- Identify the functions that must remain available.
- Identify functions that can pause safely or operate through an agreed workaround.
- Define the conditions required before systems should restart.
- Assign responsibility for confirming whether each function is actually working.
- Describe what acceptable operating status looks like from the occupant and operator perspectives.
That last point matters. A system may appear available in a control platform while a local condition tells a different story. A screen can be quiet because a system stopped, shed load, protected itself, or stopped reporting. A displayed value should not be treated as proof when the operating environment needs direct confirmation.
Create One Operating Picture, Not Several Separate Incidents
Power loss can fragment a response quickly. Property operations may focus on occupants. Facilities may focus on equipment condition. Security may focus on access and movement. IT or communications staff may focus on connectivity. All of those views are necessary. None of them is sufficient alone.
The people inside the building do not experience separate facilities, security, technology, and property-management events. They experience one building that feels different. The response must reflect that reality.
One person or role needs to own the operating picture. That coordinator does not need to perform every technical task. The coordinator needs to connect facts, decisions, and communication. The opening questions should be clear and practical:
- Is the interruption limited to the building?
- Did the emergency source become available?
- Which areas are occupied?
- Are elevators accounted for?
- Can the response team communicate internally and externally?
- What is confirmed, and what is still unknown?
Distinguishing confirmed information from assumptions is essential. An incomplete status is not the same as a confirmed failure. A local observation confirms only what the observer saw. The coordinator needs to know both what was directly observed and what remains outside that person’s view.
Use Short, Structured Handoffs
During an outage, lengthy explanations are often less useful than a disciplined handoff. A good first update can be short: what happened, when it happened, what is confirmed, what remains unknown, and who owns the immediate next actions.
The conversation highlights a practical division of responsibility. Facilities checks building conditions. Security accounts for movement and access. Property operations manages communication with occupants. The communications or IT lead confirms which communication channels work and connects the coordinator with the people performing physical checks.
This approach prevents one of the most damaging failure modes in continuity response: every group solving a different version of the problem. It also keeps outside assistance in its proper role. Vendors may be necessary to recover equipment, but a vendor is not the first fifteen minutes. Calling for help should not mean surrendering ownership of the response.
The Gaps Are Often in Sequence, Not Equipment
A composite example makes the point. Emergency power was available at minute one. By minute three, the property desk still had no confirmed message for occupants. At minute five, facilities and security held different assumptions about elevator status. The backup system itself was not the whole issue. The missing piece was the handoff sequence between teams.
That kind of gap is common because plans can sound complete on paper while remaining difficult to execute under pressure. A plan may list every task but still assume that one person can do three jobs at once. It may contain extensive reference material while burying the basic questions of who coordinates, who makes the next decision, and how occupants receive information.
Resilience planning should therefore test staffing sequence and communication, not only equipment availability. Preventive maintenance is important, but restraint also matters during an outage. A system may be protecting itself, waiting for stable conditions, or depending on another function that has not recovered. Restarting everything because an alarm appears can make a difficult situation worse.
Build a One-Page First-Fifteen-Minutes Map
A usable exercise begins with what people observe, not with a complex diagram. Start with an event someone could notice: lights change, an elevator call does not complete, a control value stops updating, or a workspace begins to warm. Then map four things: the affected function, the person who checks it, the next decision, and the communication path.
Add time to make the plan operational.
- At one minute: establish the coordinator, capture the time of the event, separate known facts from assumptions, and address immediate safety and movement concerns.
- At five minutes: reconcile information among facilities, security, property operations, and communications staff; confirm what can be communicated to occupants; and assign ownership for essential functions.
- At fifteen minutes: ensure the team understands the building’s condition, occupants have accurate information, critical functions have owners, and the next shift or continuing response has a usable handoff.
If power is still out at minute fifteen, success is not a claim that everything is normal. Success is controlled awareness and controlled action. The team knows enough about the building to manage the event, people affected have accurate information, and the organization can make the next decision with discipline rather than guesswork.
Exercise the Plan With the People Who Depend on It
Testing should begin with separate discussions. Property operations, facilities, security, communications, tenant representatives, business-continuity contacts, and campus operations may each believe they understand their role. Separate conversations reveal those assumptions. A combined session reveals whether the responsibilities actually connect.
Include people who experience the consequences of the response. They may identify a dependency that is invisible from a systems perspective. Tenant representatives may recognize a communications concern. Security leadership may identify a movement issue. Business-continuity contacts may expose a business dependency that is not apparent in a facilities workflow.
Keep the output simple. The first page or first conversation should identify the coordinator, the next decision, and the communication path. Reference material can come later. If someone must search a hundred-page document before discovering who is in charge, the plan is not serving the moment it was designed for.
Continuity planning is an operating asset, not a historical document. Building uses change. Teams change. Workarounds improve. Systems are maintained, and plans should be maintained and exercised as well.
For a deeper discussion of how to map the first fifteen minutes of a building power loss, listen to this episode of Built, Wired & Secured. Then create a one-page map for your own building and run a short tabletop with the teams that rely on one another when normal operations disappear.