November 14, 2026
How to Run a Tabletop Exercise: A Step-by-Step Guide
How to plan, run and debrief a tabletop exercise that tests your team under realistic pressure, step by step, with the mistakes to avoid.
How to run a tabletop exercise
To run a tabletop exercise, set two to five objectives, build a realistic scenario that fits your risks, and break it into injects released over time. Then run it live with the people who would make the real decisions, capture every decision as it happens, and finish with a debrief and an after-action report that assigns each fix an owner and a date.
The goal isn't a good conversation. It's a rehearsal: the team should feel enough pressure to show how it would actually perform when a real crisis hits. The nine steps below cover the before, during and after.
Before the exercise
1. Set objectives
Decide what the exercise should prove or expose. Good objectives are specific enough to judge afterward:
- "Confirm who has authority to activate the continuity plan, and how fast that happens."
- "Test whether we can notify patients, customers or regulators within our required window."
- "See how the team works with a critical vendor that has stopped responding."
Two to five objectives is enough. More than that and nothing gets tested properly.
2. Build a realistic scenario
Start from a risk your organization actually faces, not a generic disaster. The best scenarios are specific: the claims vendor your billing depends on, the substation that feeds your main campus, the cloud region your product runs in. Set a start time, a starting situation and what the team knows at minute one.
3. Break it into injects
Injects are the developments that move the scenario forward: a status page that stops updating, a reporter's call, a regulator's question, a second system going down. Plan 6 to 12 of them, each tied to an objective, and decide when each will land. Build in a few you can hold back or swap in depending on what the team decides.
4. Choose participants and set up logistics
Invite the people who would make the real decisions, usually 6 to 20, plus any outside parties you want in the room (or simulated). Block two to four hours, choose in-person or remote, and send a short pre-brief: the purpose, the ground rules, and that it's a no-fault rehearsal, not a test of individuals.
During the exercise
5. Open with the situation, not a speech
Skip the long introduction. State the date, time and starting situation, then put the first decision to the team within the first five minutes. Pressure early sets the tone for the rest of the exercise.
6. Release injects as the situation develops
Release each inject on schedule or when the team's decisions call for it. Adjust when you need to: if the team solves a problem too easily, raise the stakes; if it's stuck, give it what it would realistically know. The scenario should react to the team, not just play out a script.
7. Bring in outside pressure
Real crises come with outside voices: reporters, regulators, vendors, customers, families. Have them arrive as injects, played by a facilitator, simulated, or by real partners joining the exercise. This is where many teams find their biggest gaps.
8. Capture every decision as it happens
Record each decision, who made it, when, and what it was based on. Track open questions and observations too. Reconstructing this from memory afterward loses the detail that makes the debrief useful.
After the exercise
9. Debrief, report and follow through
Run a short debrief (often called a hot wash) right after the exercise, while memories are fresh: what went well, what didn't, what surprised people. Then turn the decision record into an after-action report within a week. Each finding should have an owner, a due date and the objective it relates to.
The exercise isn't finished until the fixes are. Track them like any other project, and test the riskiest ones in your next exercise.
Common mistakes
| Mistake | What it looks like | What to do instead |
|---|---|---|
| It becomes a discussion | People say what they would do, nothing changes, nobody feels pressure | Put real decisions on a clock and let the scenario react to them |
| A fixed script | Injects arrive in the same order whatever the team decides | Hold injects in reserve and adjust based on the team's choices |
| An overloaded facilitator | One person runs the clock, reads injects, plays every outside party and takes notes | Split the roles, or use a platform that delivers injects and captures decisions |
| The wrong people in the room | Delegates without authority, or decision-makers missing | Invite the people who would make the real calls |
| Notes reconstructed afterward | The report is built from memory and misses who decided what, and when | Capture decisions as they happen |
| No follow-through | Findings sit in a report and the same gaps show up next year | Give every fix an owner and a date, and retest it |
Running a tabletop exercise in Crewcible
Every step above can be done by hand, but steps 6 to 8 are where one facilitator runs out of hands. Crewcible is built to make the exercise a real rehearsal again.
- Scenario and injects in minutes. Start from the Global Library, build your own, or let AI build one from a short description.
- Injects on every screen. Schedule, approve, release or modify injects live. Each one reaches every participant at once, including breaking-news video that takes over their screens.
- A scenario that reacts. AI challenges suggest new pressure based on the team's decisions, and the facilitator decides what to release and when.
- Outside parties, simulated or real. AI drafts messages from reporters, regulators and vendors for the facilitator to approve, and real partners can join from their own devices.
- Decisions captured automatically. Every response is time-stamped and flows into the after-action report.
Run your next tabletop exercise in Crewcible. See plans and get started
Frequently asked questions
How long does it take to plan a tabletop exercise? Planning by hand usually takes two to six weeks, mostly spent writing the scenario and injects. Starting from a ready-made scenario or an AI-drafted one cuts that to days or hours.
Who should facilitate? Someone who knows the plans well but won't be making decisions in the exercise. Many organizations use their emergency management, business continuity or security lead, or an outside facilitator for high-stakes exercises.
How many injects should a tabletop exercise have? Six to twelve for a two-to-four-hour exercise, each tied to an objective. Keep a few extra in reserve so the scenario can react to the team.
Should participants see the scenario in advance? No. Share the purpose, the ground rules and the time commitment, but not the scenario. Knowing what's coming turns the rehearsal back into a discussion.
What goes in an after-action report? The objectives, a timeline of key decisions, what worked, what didn't, and an improvement plan with an owner and a due date for each fix.