Show Notes
When the Emergency Plan Meets Reality
A fire alarm sounds in a fully occupied building. The property manager is delayed, the engineer’s radio is dead, and a newly hired security guard does not know how to unlock the stairwell doors. The plan assigns responsibilities, but the people and systems it depends on are not ready to carry them out. That gap between a plan on paper and a response that works is the focus of this episode.
The discussion centers on a practical distinction: documentation is not the same as readiness. Some plans are written to satisfy an insurance requirement or lease clause, then left untouched. A usable playbook has to reflect real building conditions, current personnel, working communication channels, and clearly understood roles.
Assumptions That Fail Under Pressure
Emergency plans can hide assumptions about who will be on site, where equipment is located, whether a system activates automatically, and whether staff can reach one another. In an incident, those assumptions become delays.
- A water leak on the 14th floor exposed a missing detail: the plan instructed engineering to shut off a zone valve, but did not say where it was or that reaching it required a special key. The engineer on duty had been in the building for two months and had not seen it. The search took 20 minutes, and water reached an elevator shaft.
- During a gas-smell incident on a loading dock, poor cell coverage and radios that worked for only about half the floors left the person on the dock unable to reach anyone. He had to walk two flights to get a signal.
- In a fire drill, security was expected to unlock stairwell doors but lacked the right key. The engineer was the only person who knew the override code, leaving tenants stuck in the stairwell for five minutes.
- A power-outage tabletop raised a basic unanswered question: who shuts off the elevators? The plan did not say, and the team had to call the elevator vendor to find out.
Coordination Includes Tenants
Property management, engineering, and security each know different parts of a building. Property management knows tenants; engineering knows building systems; security understands access points. A real response needs all three groups to act in sync, with roles that do not depend on one person being available or one communication method working.
Tenants are part of the response, too. A one-page instruction to evacuate to an assembly area may not tell people which stairwell is safe or that the assembly area is across a busy street. If hundreds of people leave without clear direction, accounting for them with a clipboard can quickly become chaotic. A practical plan needs to address tenant understanding and coordination, not just staff duties.
Tabletops and Live Drills Find Different Gaps
A tabletop exercise brings the key players together, presents a scenario, and walks through decisions step by step. It can reveal missing responsibilities and unclear procedures without the expense and disruption of a live exercise. In one tabletop, nobody knew who should shut off the elevators during a power outage.
A live drill tests the physical environment. In a simulated fire on the third floor, the team went to locate the extinguisher identified in the plan. It was supposed to be on the wall beside the stairwell, but a stack of boxes blocked it. The response was both to update the plan and to clear the storage.
The episode does not treat one format as a universal answer. Tabletop exercises can be a lower-cost way to uncover coordination gaps, while physically walking a route can expose conditions a conference-room discussion will miss. The useful choice depends on the gap being tested; both approaches can be part of a testing program.
Test the Systems the Plan Depends On
One generator ran successfully during a full load bank test. But when the team simulated a utility failure and switched to generator power, the fire alarm panel did not come back up. The panel was on a circuit that was not backed up, despite the plan saying the generator powered life-safety systems. Testing the actual transition exposed a failure that a general statement in the plan could not.
Communication details need the same attention. A drill found that the emergency contact number for the security director went to a disconnected line. The team began reviewing the contact list quarterly and testing it during drills. A list is only useful if it is current and its contacts can be reached.
Build a Living Playbook One Fix at a Time
The suggested starting point is a tabletop with property management, engineering, security, and, where appropriate, a tenant representative. Walk through a scenario without scripting every response. Let the discussion reveal what people know, what they do not know, and where the plan leaves decisions unclear.
- Choose a realistic incident and identify the people who would need to respond.
- Walk through actions and communications in sequence rather than assuming the written assignments are understood.
- Pick one discovered gap—the one that would have caused the greatest harm—and fix it.
- Run another drill in a month and find the next issue.
- Keep contact information under review and test it in exercises.
Trying to overhaul an entire plan at once can be daunting. Incremental testing and correction turns it into a living playbook that improves through use.
Curiosity and Humility Are Operational Tools
The episode closes with a reminder that readiness starts with admitting the plan could be wrong. Humility makes room to question assumptions; curiosity drives people to find out whether a valve is reachable, a radio works, a contact answers, and a life-safety system actually receives backup power. A quiet day in building operations is not simply luck. It can reflect the work of testing before a real emergency forces the answers.
In This Episode
- Why a polished emergency document may still fail in practice
- How access, location, staffing, and communications assumptions create delays
- Why tenant instructions and coordination belong in the response plan
- What tabletop exercises can reveal—and what live drills add
- How to start improving a plan through one fix at a time
An Emergency Plan Is Only as Good as Its First Real Test
A building can have a polished emergency plan and still be unprepared when an alarm sounds. The problem is often not that nobody wrote a plan. It is that the plan assumes people, equipment, and communication will behave exactly as expected.
Consider a fire alarm in an occupied building. The written procedure says property management coordinates with engineering, security sweeps floors, and tenants gather at an assembly point. But the property manager is delayed, the engineer’s radio is dead, and a new security guard does not know how to unlock the stairwell doors. The response depends on details the document never tested.
That is the difference between documentation and readiness. An emergency plan becomes operational only when the people who must use it understand their roles, the instructions match the building, and the systems behind those instructions have been tested.
Plans Often Hide Assumptions
Emergency procedures can rely on unstated assumptions: the right engineer will be on site, the phone tree is current, the generator powers the systems that matter, or a valve is easy to find. In a real event, a single incorrect assumption can cost time and make a manageable problem worse.
A water leak on the 14th floor illustrates how an apparently simple instruction can fail. The plan told engineering to shut off a zone valve but did not explain where the valve was or that access required a special key. The engineer on duty had been in the building for two months and had never seen it. The search took 20 minutes, and water reached an elevator shaft.
The lesson is not merely to add more words to the plan. The team has to verify that the person expected to act can locate the equipment, access it, and carry out the procedure. If a valve is behind a panel, the plan needs to identify the panel and the key. If the step depends on someone’s knowledge, the knowledge cannot remain undocumented and untested.
Communication and Access Must Work in the Actual Building
Emergency instructions frequently depend on people reaching one another quickly. Yet cell service, radio coverage, and access controls can vary throughout a property. During a gas-smell incident on a loading dock, poor cell coverage and radios that worked for only about half the floors prevented the person on the dock from reaching anyone. He had to walk two flights to get a signal.
That delay is a warning about plans that say “notify the property manager” without confirming how a person in each location can do so. Teams should test the channels they expect to use from the places where an incident could happen. If radios do not work throughout the building, that limitation belongs in the response design—not in a post-incident surprise.
Access responsibilities also need to be practical. In one fire drill, security was supposed to unlock stairwell doors but did not have the correct key. The engineer alone knew the override code, and tenants were stuck in the stairwell for five minutes while staff worked out what to do. A plan that assigns a task to a role is incomplete if that role lacks the key, training, or authority to perform it.
Include Tenant Actions, Not Just Staff Assignments
Property management, engineering, and security each understand different parts of the building. Management knows tenant relationships, engineering knows systems, and security knows access points. An emergency response requires those perspectives to come together rather than operate as separate silos.
Tenants need usable instructions as well. A one-page notice that says to evacuate to an assembly area may leave important questions unanswered: which stairwell is appropriate, where is the assembly area, and how should people get there? The episode describes an assembly area across a busy street and hundreds of people moving outside while property management tries to account for them with a clipboard. This is not a reason to assume tenants will figure things out. It is a reason to make directions clear and test whether they make sense.
Planning should account for the people who will act, the people who need instructions, and the ways information will move between them. Otherwise, the plan can assign every group a role and still fail to coordinate the building.
Use Tabletop Exercises to Expose Missing Decisions
A tabletop exercise brings the relevant people together, introduces a scenario, and walks through the response step by step. It can reveal uncertainty before an incident, without the expense and disruption of a live drill.
In one power-outage tabletop, the property manager asked who shuts off the elevators. Nobody knew, and the plan did not specify. The group had to call the elevator vendor to get an answer—a five-minute delay in the scenario. That exercise surfaced a missing decision and the need to clarify the process.
Tabletops work best when participants are allowed to think through the situation rather than simply recite the document. Ask what happens next, who makes the call, how they communicate, and what they do if the expected person cannot respond. The goal is not to prove the plan correct; it is to find where the plan stops being useful.
Use Live Drills to Check Physical Reality
A tabletop cannot reveal every physical obstacle. In a live drill simulating a fire on the third floor, staff went to find the extinguisher the plan placed beside the stairwell. A stack of boxes blocked it. The team updated the plan and cleared the storage.
Live exercises can be more expensive and disruptive, and they can repeat mistakes if nobody learns from them. They are not automatically the answer to every question. But physically walking a route can reveal conditions that are difficult to reproduce in a meeting room: an obstructed extinguisher, an inaccessible panel, or a route that does not work as expected.
Tabletops and live drills serve complementary purposes. Use discussion to explore roles, decisions, and communications. Use physical tests when the question depends on the building’s layout, equipment, or access conditions. Match the method to the gap.
Test the Systems Behind the Written Claims
A generator can pass a test and still fail to support the system the emergency plan says it will. In one example, a generator ran during a full load bank test. But when the team simulated a utility failure and switched to generator power, the fire alarm panel did not come back up. It was on a separate circuit that was not backed up.
The important distinction is between testing a component and testing the actual sequence the building depends on. If the plan says life-safety systems are powered by the generator, test the transition and confirm that those systems return. A successful equipment test alone may not demonstrate that the complete emergency arrangement works.
Contact lists deserve the same discipline. A drill found that the emergency number for the security director had been disconnected. The team responded by reviewing the list every quarter and testing it during drills. A contact list should be treated as part of the operating plan, not as an administrative page that can be assumed current.
Improve the Plan One Gap at a Time
For a property team that has a plan and has already held a drill, the next step can be modest: start with a tabletop. Bring together property management, engineering, security, and perhaps a tenant representative. Choose a scenario and walk through it without scripting every answer.
Then pick one discovery and fix it—the issue that would have caused the most harm. Do not try to rebuild the entire plan at once. Run another drill in a month and address the next gap. Over time, the document changes alongside the building and the team’s understanding of it.
This approach turns a static PDF into a living playbook. The process depends on humility: accepting that the plan may be wrong. It also takes curiosity: asking “what if?” and following the question until the answer is verified. The best day in operations may be the one nobody notices, but that outcome depends on work done before an emergency begins.
To hear the full conversation about emergency planning, testing assumptions, and building a more reliable response playbook, listen to this episode of Built, Wired & Secured.
Frequently Asked Questions
How can a commercial building test whether its emergency plan will work?
Start with a tabletop exercise involving property management, engineering, security, and possibly a tenant representative. Walk through a realistic scenario without scripting every response, then choose one consequential gap to fix. Follow with another drill, using a live exercise when the question depends on physically testing the building.
Why can an emergency plan fail even when it names who is responsible?
Assignments can rely on assumptions the plan never verifies: the right person is present, communication works, or staff can access the equipment. In the examples discussed, a valve required a special key, radios lacked coverage in parts of the building, and security lacked the right stairwell key. Each gap delayed action.
What should a building team check about its emergency communication plan?
Check whether people can actually reach one another from the locations where incidents could occur, and whether emergency contacts are current. A loading-dock worker could not get through because cell coverage was poor and radios covered only about half the floors. A drill also found a disconnected security director number.