What a Real Tabletop Exercise Looks Like

May 9

It's a Monday morning. You're twelve minutes into the weekly team check-in when you say: "Okay - it's 11 PM on a Saturday. A tenant calls. Water is coming through their ceiling on the 4th floor. Walk me through your response."

Silence.

Then someone says, "I'd call the engineer."

You respond, "He's not answering. What next?"

More silence.

That silence is the reason you need run tabletop exercises.

What a Tabletop Exercise Actually Is

A tabletop exercise is a scenario-based discussion - no actual execution, no fire alarm pulled, no vendors dispatched. You gather your key people, present a realistic crisis scenario, and walk through the response step by step. A facilitator drives the scenario forward and injects complications. Participants describe what they would actually do, not just what the plan says to do.

The distinction matters. What the plan says and what your team would actually do in the moment are often two different things. A tabletop is how you find out which gaps exist before a real incident exposes them.

This is not a drill. It's not a training seminar. It's a stress test on your planning - conducted in a conference room with coffee, not at 11 PM in a flooded parking garage.

Why Most Property Teams Skip It

Because nothing is on fire. Because the quarter is busy. Because the engineer just left and you're short-staffed and the roof project is already two weeks behind schedule.

Ironically, those are the type of conditions under which your team could face a real emergency and the tabletop prepares them for it.

The most basic goal of a tabletop exercise is to ensure your team members know exactly what to do in an emergency - not in theory, but in sequence, under pressure, when the person who usually handles it isn't available.

People don't rise to the occasion. They fall to their level of training. If you haven't walked through a scenario, your team will hesitate. That hesitation costs you - in damage, in tenant trust, and sometimes in safety.

See content credentials

Who Needs to Be in the Room

Keep it small enough to be productive. For a standard commercial office building, a core tabletop group looks like this:

Property manager
Chief engineer and technicians
Front desk or security staff
A tenant contact, if they'll participate - especially a floor warden or office manager from a major tenant

For annual exercises, consider pulling in your restoration vendor or security contractor. Tabletop exercises are a great way to strengthen key relationships before a crisis occurs and a vendor who has walked through your response protocol with you will perform better when it's real.

Ownership can participate when the scenario involves financial authorization or major communication decisions. Many owners appreciate the window into how their building actually operates under pressure.

How to Run One

Step 1 - Pick a scenario that reflects a real risk to your building

Don't start with a tornado if your building's historical incidents are water intrusion and fire alarms. Start with what actually happens. Rotate scenarios monthly so you're covering your exposure over time. Common starting scenarios for commercial office:

Water intrusion from a burst pipe or roof drain overflow
Fire alarm activation with your engineer not yet on site
Medical emergency in a common area
Power outage during business hours
Elevator entrapment with multiple occupants

Step 2 - Set the scene with specificity

Generic scenarios produce generic responses. Give your team a real setup: time of day, day of week, who's on site, what was just happening. "It's 7:45 AM. Your chief engineer called in sick. Your fire panel is in alarm. Your front desk has two people in the lobby. Walk me through the next five minutes."

The specificity forces real decision-making rather than policy recitation.

If you want to fully commit to the exercise, print out your floor plans and spread them on the table. Think of it as Dungeons & Dragons for property teams - your characters have experience levels and authority limits, and the challenges come from the building itself, the equipment, and the people inside it.

Step 3 - Inject complications as the response unfolds.

This is where the exercise becomes valuable. Once your team starts walking through the response, introduce the friction that real incidents carry:

"The tenant you just called isn't answering."
"The emergency shutoff valve is in a space only the engineer knows how to access."
"Ownership is calling you while you're still trying to confirm the situation."
"It's now 25 minutes in and your second vendor contact also isn't available."

The more realistic your script, the better. The complications don't need to be dramatic - they just need to reflect the actual failure points in your building's response capability.

Step 4 - Debrief like it was real

Don't let the team scatter. Spend ten to fifteen minutes asking three questions: What worked? What broke down? What do we need to fix before we do this again? Capture the answers. Assign owners and deadlines to any action items that surface.

This is where the exercise pays for itself. One gap identified and closed - a missing vendor contact, an unclear authorization threshold, a shutoff valve nobody could locate - is worth more than a dozen policy documents sitting in a binder.

How Long Does It Take?

A focused tabletop with a single scenario takes 20 to 45 minutes. Plan for 60 minutes and use the extra time for the debrief if the scenario surfaces significant gaps.

You don't need a full day. You don't need outside consultants. You need a facilitator who takes it seriously and a team willing to engage honestly with where their response breaks down.

What to Do with What You Find

The output of a tabletop isn't a report. It's a short list of specific things to fix: a contact number to update, a protocol step that no one understood, a vendor relationship to establish before you need it, a shutoff location to map and label.

The best property teams treat tabletops as a laboratory. The goal isn't to pass - it's to fail in a controlled environment where the cost is a conversation, not a flood claim.

Run one this week. Pick a scenario your team hasn't practiced. See what the exercise reveals to you.

If you found this newsletter interesting, consider checking out these past editions:

Matt Faupel