Show Notes
Why short outage drills matter
This episode focuses on a problem many building teams already know too well: outages rarely stay contained to one system. A UPS trip can expose a noisy fiber handoff. Badge readers can fail at the same time. Lobby lighting can go dark. Tenants feel the impact immediately, and what looks like a technical issue quickly becomes an operations and communication problem.
The discussion centers on a simple idea: most failures become expensive because nobody practiced the interactions between systems or the decisions required to keep a property operating. The point of a drill is not to create drama. It is to force clear decisions under controlled conditions before a real incident puts tenants, staff, and vendors under pressure.
The standard for a useful exercise
One of the clearest ideas in the episode is the standard used to judge whether a drill worked. If the session ends with named people, a defined workaround, and a timeline, the exercise succeeded. If it ends with vague notes and a promise to follow up later, it did not.
That framing matters because many tabletop sessions drift into discussion without producing ownership. This episode argues for a more practical benchmark:
- Did the team define a short-term workaround that protects critical tenant functions?
- Did the team agree on an expected time to full restoration?
- Did specific people leave with responsibility for action?
Those two success criteria, temporary continuity and full restoration, keep the exercise grounded in operations instead of theory.
How to choose the right scenario
The recommendation is to start with system interactions rather than isolated failures. Power plus communications is described as a reliable pair because it exposes dependencies quickly. Adding an access control issue forces ownership questions that many teams have not settled in advance.
That matters in modern buildings because tenant experience depends on several systems working together. If comms degrade, doors may still need to operate. If power transfer does not complete cleanly, teams need to know who can authorize a manual step. If the network path is unstable, building staff still need a way to notify tenants and coordinate vendors.
The practical takeaway is to pick one scenario tied to a critical service, then define what success looks like in the first hour and what success looks like at full restoration.
Who needs to be in the room
The episode strongly recommends inviting decision makers, not delegates. That keeps the session short and prevents the common problem of people saying they need to check with someone else before acting.
The suggested group is tight:
- Facilities director
- IT network lead
- Security operations manager
- Vendor account lead
- Tenant liaison, if possible
The target size is five to eight people. Observers can attend quietly and join a short debrief, but the core exercise should stay small enough to move quickly. That structure makes the drill more realistic because the people in the room are the ones who would actually make the call during a real outage.
How to handle vendor participation
Vendor participation is another practical point. Some property teams worry vendors will avoid these sessions because they sound like blame exercises. The answer given here is framing.
When the drill is positioned as mutual risk reduction, with a no-blame rule and a short prep packet, vendors are more likely to participate. The benefit for them is straightforward: fewer escalations, clearer expectations, and fewer surprise failures during a real event.
And if a vendor still resists, the guidance is direct. Escalate to the contract owner and make participation part of expected service behavior. The point is not conflict for its own sake. It is recognizing that resilience depends on shared response, not isolated contracts.
What good facilitation looks like in 45 minutes
The facilitation model in this episode is intentionally simple. Start with a five-minute scene setter that covers the timeline, objectives, and the two success criteria. Then use timed injects to force choices.
Examples from the conversation include:
- The carrier reports a three-hour restoration window
- Power transfer did not complete
- Badge access is no longer functioning as expected
Each inject should create a specific decision. What workaround is authorized? Who enacts it? How are tenants notified? The team should capture decisions live, not after the fact.
One of the strongest operational points in the episode is that communication must be part of the exercise itself. The team should name who sends the tenant advisory, what it says, and when it goes out. Someone should actually read the message aloud. That exposes approval gaps and messaging weaknesses before they become a problem in production.
Tabletop first, live drill later
For teams debating realism, the guidance is to start tabletop heavy. Use tabletop exercises to validate playbooks, escalation paths, and workarounds in conversation first. Once those steps are proven, a live drill can be planned in a controlled window with tenant notice.
That sequence keeps the cost and disruption down while still building readiness. Live drills have value, but they are expensive and can create avoidable risk if the underlying decisions and procedures are still unclear. Tabletop is the lower-friction way to expose ownership gaps early.
Examples of high-impact findings
The episode gives two concrete examples that show why short drills work.
In one exercise, the generator transfer alarm routed only to a contractor pager, not to building operations. During the drill, nobody authorized a manual transfer, so the load stayed on UPS too long. The fixes were simple but meaningful: reroute alerts, update the escalation tree, and add a manual transfer checklist to the emergency playbook.
In another drill, a fiber outage was paired with badge authentication failures. Teams first assumed the cloud system was down. The real dependency was local time sync. When the NTP source went dark, authentication behavior changed and the local override had not been practiced. The fixes were again small but high value: document the override, update vendor SOPs, and add a time sync fallback.
That is the pattern this episode keeps returning to. Drills uncover the small details that have an outsized effect on uptime and tenant confidence.
A repeatable plan for getting started
The closing recommendation is intentionally simple:
- Pick one scenario tied to a critical service
- Write two clear success criteria
- Invite decision makers for a 45-minute session
- Capture actions with owners and deadlines
- Publish a one-page after-action report within 72 hours
- Repeat quarterly and track closed actions
The after-action report should stay short enough for leadership to read. The suggested format is a one-page document with an executive summary, a prioritized action list with owners and due dates, and a verification step. Supporting materials like decision logs and the tenant messaging template can be attached for reuse.
What building teams should take away
The message of this episode is straightforward. Resilience does not come from having a binder on a shelf. It comes from running short, decision-focused exercises often enough that people know what to do when systems fail together.
For commercial properties, that means less downtime, clearer tenant communication, and fewer surprises when power, communications, and access systems interact in ways no single team owns alone. A 45-minute tabletop can reveal those gaps before a real outage turns them into a tenant-facing incident.
If your building team has not practiced one of these scenarios recently, this episode makes the case for starting now, keeping the scope tight, and turning every drill into a visible set of fixes.
Running realistic outage drills for building technology
Many building teams know they should prepare for outages. Fewer teams actually run exercises often enough to make a difference. And when they do, the session can feel too abstract to change anything. People talk through a scenario, someone takes notes, and a week later nobody can say what decisions were made or who owns the next step.
This episode of Built, Wired, and Secured argues for a more practical approach. Instead of treating outage exercises as compliance theater, the conversation focuses on short drills that surface real ownership gaps and end with fixes. The goal is not to simulate chaos for its own sake. The goal is to make the next real incident smaller, shorter, and easier to manage.
The scenario that opens the episode makes the point quickly: the UPS trips, the fiber handoff is noisy, badge access stops working, tenants cannot reach critical suites, and the lobby goes dark. None of those failures lives in a single operational silo. That is exactly why outages balloon. Power, communications, physical access, and tenant communications all intersect, but many teams have never practiced those interactions together.
Good drills produce decisions, not discussion
One of the strongest lines in the episode is also the simplest. If a drill ends with named people, a clear workaround, and a timeline, it worked. If it ends with vague follow-up, it did not.
That distinction matters for any building team responsible for uptime, tenant experience, or incident coordination. It is easy to run an exercise that feels productive while avoiding the uncomfortable parts. Who is authorized to approve a workaround? Who sends the first tenant message? How long can a critical function operate on a temporary measure before risk becomes unacceptable? Those are decisions, not observations, and they need to be made before a live outage forces them.
The episode recommends using two success criteria for every drill. First, define the short-term workaround that keeps critical tenant functions running. Second, define the expected time to full restoration. Those two lines keep the exercise grounded. They turn a general conversation into an operational test.
Start with interactions, not isolated failures
One reason outage drills feel unrealistic is that they are often built around a single failure. Real incidents are rarely that tidy. A networking issue can affect door access. A transfer problem can keep a load on UPS longer than planned. A cloud-dependent service may actually fail because a local dependency disappeared first.
That is why the episode recommends choosing scenarios based on interactions. Power plus communications is described as a reliable pair because it quickly exposes hidden dependencies. Add an access control nuance and the exercise starts revealing ownership questions fast.
For commercial real estate teams, that is the right level of realism. Buildings now rely on a mesh of connected systems that span facilities, IT, security, and outside vendors. If teams only rehearse within their own lane, they miss the handoffs that usually decide whether an incident stays contained or spreads across tenants and common areas.
Keep the room small and decision focused
Another practical takeaway is who belongs in the exercise. The recommendation is direct: invite decision makers, not delegates. A 45-minute drill only works if the people in the room can actually commit to an action.
The suggested core group is five to eight people:
- Facilities director
- IT network lead
- Security operations manager
- Vendor account lead
- Tenant liaison when possible
That lineup reflects how building incidents really unfold. Facilities may own the physical environment. IT may own network path visibility. Security may own badge behavior and access exceptions. Vendors often own critical pieces of restoration or escalation. And if tenants are affected, someone needs to speak for continuity and communication needs from the occupant side.
Observers can still attend, but they should stay quiet until the debrief. The exercise moves faster when the people at the table are the ones who can make the call.
Vendors need to be part of the drill
Many teams struggle to get vendors to participate in outage exercises. Sometimes the resistance is obvious. Sometimes it shows up as scheduling friction or reluctance to engage in scenario details. The concern is usually the same: nobody wants to walk into a blame session.
The episode offers a useful reframing. Position the exercise as mutual risk reduction. Keep a no-blame rule. Provide a short prep packet. Show the agenda and commit to a short time window. When vendors understand that the output will be a one-page after-action report and a defined action list, the exercise starts to look less like finger-pointing and more like a way to reduce escalations and clarify expectations.
And if that still does not move things, there is a contract reality involved. Participation in readiness planning should be treated as expected service behavior, especially when the vendor owns a critical path in restoration or alerting.
How to run a 45-minute drill that stays useful
The structure described in the episode is compact on purpose. Open with a five-minute scene setter. State the timeline, the objectives, and the two success criteria. Then move into timed injects that force decisions.
These injects do not need to be complicated. A carrier reports a three-hour restoration estimate. Power transfer did not complete. Badge authentication behavior changes. The point is to introduce small facts that require someone to act.
During the exercise, capture decisions live:
- What workaround is authorized?
- Who enacts it?
- How are tenants notified?
- Who approves the message?
- What condition ends the workaround and returns the building to normal operations?
One of the best operational habits discussed in the episode is to make communication part of the drill itself. Do not just note that a tenant advisory would be sent. Name who sends it. Draft what it says. Read it aloud. That is where approval delays, unclear language, and messaging ownership often surface.
Why tabletop usually comes before a live drill
Some teams want live exercises because they feel more realistic. Others avoid them because of disruption risk. The episode lands in a practical middle ground: start tabletop heavy, then move to live drills after the playbooks and workarounds hold up in conversation.
That sequence makes sense. Live drills are valuable, but they are also expensive and disruptive. If a team has not yet aligned on ownership, escalation paths, messaging, and workaround authority, a live drill can create noise without adding much learning. Tabletop exercises give teams a low-friction way to expose the weak points first.
Once those gaps are fixed, a controlled live exercise becomes more valuable because it is validating a process, not searching for one.
Small findings can produce large resilience gains
The examples in the episode show why these drills are worth doing. In one case, a generator transfer alarm routed only to a contractor pager instead of building operations. During the drill, nobody authorized a manual transfer and the load stayed on UPS too long. The fixes were not expensive. Reroute alerts. Update the escalation tree. Add a manual transfer checklist to the emergency playbook. But those changes materially improve uptime and response quality.
In another example, a fiber outage was paired with badge authentication failures. The team initially assumed the cloud service was the problem. The actual issue was local time sync after the NTP source went dark. The workaround existed, but nobody had practiced it. The fixes were again precise: document the local override, update vendor SOPs, and add a fallback for time sync.
That is the real value of a well-run tabletop. It finds the tiny details that create large operational consequences.
What to do this month
The closing call to action in the episode is simple enough to execute immediately. Pick one scenario tied to a critical service. Write two clear success criteria. Gather decision makers for a 45-minute session. Capture actions with owners and deadlines. Publish a one-page after-action report within 72 hours. Then repeat quarterly and track closed actions.
The report format matters too. Keep it short enough for leadership to read. A one-page document with an executive summary, prioritized actions, owners, due dates, and a verification step is far more likely to drive follow-through than a long narrative nobody revisits.
Building resilience is rarely about dramatic redesign. More often, it is about clarifying who acts, how quickly they act, and what temporary measures are acceptable while full restoration is underway. For building teams responsible for tenant trust, that kind of clarity is not optional.
If your property has never practiced how power, communications, access control, and tenant messaging interact during a real disruption, this episode makes a strong case for changing that. Keep the drill short. Keep it decision focused. Make the fixes visible. Then listen to the next outage feel smaller because the room already knows what to do. Listen to the full episode here: https://builtwiredsecured.com/episodes/tabletop-ready-outage-drills-building-technology