How to Run a Tabletop Exercise With a Small Team
A 90-minute tabletop you can run next week: one objective, six injects with timings, the questions that find real gaps, and an after action report people act on.

You need a meeting room, ninety minutes, six people and four sheets of printed paper. No systems are touched, no tooling is required, and nobody has to prepare anything. That is the entire cost of finding out whether your incident response plan is a document or a decoration.
The reason tabletops work is that they test the part nobody can test in production: whether a specific group of people, under time pressure, with incomplete information, can make a decision that costs money. NIST SP 800-84, which is still the clearest reference on exercise programs, describes tabletops as discussion-based events using a scenario rather than live systems. That limitation is the feature. It means you can run one next Tuesday.
Step 1: Pick one objective, and make it a decision
"Test our incident response plan" is not an objective. It produces a ninety-minute discussion that confirms everyone has read the plan, which is not information you needed.
Write the objective as a single decision with a clock on it. For example:
- Can we decide, within four hours, to take the booking system offline, and who signs that off?
- If the finance manager's mailbox is compromised on a Friday afternoon, can we contact every supplier who received a message from it before Monday?
- Can we establish, inside one working day, whether personal data left the organization, and who drafts the notification?
One objective per exercise. Two objectives means the second one gets eight rushed minutes at the end.
Step 2: Cast the room
Four roles, and the casting matters more than the scenario.
- Facilitator. Delivers the injects, keeps time, asks the follow-up questions. Must not be the author of the plan, who will instinctively defend it, and must not be the most senior person in the room, because people do not freely admit confusion to whoever writes their appraisal.
- Note-taker and evaluator. One person whose only job is to record decisions, gaps and the time each arose. Not a participant. This role is routinely dropped and its absence is why most exercises produce no findings.
- Participants. Five to eight people who play themselves: whoever owns IT, whoever owns finance, whoever owns the customer relationship, whoever can speak for the business, and whoever would actually pick up the phone at 6pm.
- Observers. Optional, silent, and told in advance that they are silent. One or two are useful. Six turn the room into an audience.
The senior decision-maker has to be present. An exercise that discovers a decision nobody in the room can make has found something real, but you will spend the next fortnight chasing an answer you could have had in the session.
Step 3: Choose a scenario that could actually happen to you
Three rules. Use a system your team genuinely depends on, by name. Use an attack pattern that happens to organizations your size, which in practice means ransomware, a compromised mailbox leading to invoice fraud, or a supplier breach that reaches you. And start the scenario at an awkward hour, because incidents do.
You do not have to write it from scratch. CISA's Tabletop Exercise Packages give you template objectives, scenarios, discussion questions, an invitation template, a slide deck, a feedback form and an After Action Report template, and are customizable: the cyber scenarios include ransomware, insider threats and phishing, with sector-specific packages beyond that. The UK's NCSC runs Exercise in a Box as a free self-service tool with ready-made exercises. Take one and change the names of the systems to yours. That last step is what makes it bite.
Step 4: Write six injects with timings
An inject is three or four sentences of new information, handed out at a set point, that changes the situation. It is not a question. Questions come from the facilitator afterwards.
A worked set, for a scenario where a cloud accounting system is affected on a Friday afternoon:
- T+0 (16:10 Friday). Two staff report they cannot open files on the shared drive. A third says a document opened with scrambled text. The IT provider's phone goes to voicemail.
- T+20. A text file on the shared drive names your organization and demands payment. A directory listing shows files modified in the last forty minutes across three departments.
- T+40. Your largest customer emails to ask why they received an invoice this morning with different bank details. Finance did not send it.
- T+55. A journalist emails the general enquiries address asking for comment on a claim that your data is listed on a leak site.
- T+70. The backup console shows the most recent successful job was eleven days ago. The last four jobs show warnings nobody opened.
- T+80. The operations lead, who holds the supplier contact list, is unreachable and on a flight for the next six hours.
Notice what those injects are doing. Each one removes an assumption: that IT support is available, that the problem is contained, that the incident is private, that backups work, that a key person is reachable. The scenario's technical realism is irrelevant. The pressure it applies to your decision-making is the whole point.
Step 5: The ninety-minute agenda
- 0 to 5 minutes. Ground rules. No laptops or phones. Nothing said here is used against anyone. "I don't know" is an acceptable and useful answer. We are testing the process, not the people.
- 5 to 10 minutes. Read the scenario opening aloud. Confirm the objective on a flip chart where everyone can see it.
- 10 to 70 minutes. Injects at the timings above, with facilitated discussion after each. Keep roughly ten minutes per inject and move on even when it feels unfinished.
- 70 to 75 minutes. Facilitator reads back the decisions the group made, in order, with times. This is often the first moment people realize what they committed to.
- 75 to 90 minutes. Hotwash. Covered below, and do not skip it.
Step 6: Ask the questions that find gaps
The facilitator's real skill is refusing to accept a plausible answer. "We'd check the backups" is a plausible answer. The follow-ups are: which backup, where is it, who has credentials for it, how long does a restore of that system take, when was that restore last tested, and does it include the database or just the files?
A set of probes worth having written on your own sheet:
- Authority. Who declares this an incident? Who can authorize taking the system offline during business hours? Who can approve unbudgeted spend, and up to what figure, at 17:00 on a Friday?
- Reachability. Where is the phone number for the IT provider written down, and is that place also encrypted? Who is the named deputy for every person in this room? Have you ever called the out-of-hours number?
- Communication. If email is unavailable, how does this group talk to each other? Who speaks to customers, and who approves the wording? Who answers the journalist, and what do they say in the first hour?
- Obligations. What does your cyber insurance require you to do, within how long? Who notifies the regulator, and when does that clock start? Which contracts oblige you to tell a customer?
- Evidence. Who decides whether a machine is reimaged or preserved? That decision is contested in every real incident, and the sequence is in our guide to preserving evidence before you clean up.
- Data. What was actually in that system? Can anyone in this room say whose personal data it held without going to look?
Two facilitation rules make these land. Do not let the group solve the technical problem; redirect to the decision. And do not rescue someone who is stuck, because the silence is the finding.
Step 7: Run the hotwash before anyone leaves
Fifteen minutes, in the room, straight after. Three questions, around the table, everyone answers:
- What worked better than you expected?
- What was the moment you did not know what to do?
- What is the one thing you want changed before the next one?
Write the answers verbatim on the flip chart. The honest version of question two has a shelf life of about fifteen minutes, after which it becomes "we handled that reasonably well". The note-taker captures all of it, and the facilitator resists the urge to explain or defend anything.
Running a phishing inject? Paste a real message or link into CyberWatch AI Scan for a free check to use as the artifact.
Step 8: Write a short report that produces work
Within a week, one or two pages. Date, objective, who attended, the scenario in a paragraph, the decision timeline, then the findings. CISA's packages include an After Action Report template if you want the structure handed to you.
Three rules for the findings:
- Ten maximum. A list of thirty is a list of none.
- A named person and a date against every one. Not a team. A person.
- At least three closed inside thirty days. Pick the cheap ones deliberately: the printed contact sheet, the out-of-hours number tested, the insurance notification clause read and summarized in four lines. The team's willingness to take the next exercise seriously depends entirely on whether anything changed after this one.
Book the follow-up review before people leave the room. Thirty minutes, four weeks out, agenda is the findings list and nothing else.
Step 9: Make it a habit, and raise the difficulty
Twice a year for a small team, with the previous report's actions reviewed in the first five minutes. Rotate the scenario so you are not re-running the same muscle: ransomware one cycle, a compromised mailbox and invoice fraud the next, a supplier or cloud provider outage after that.
Then add stress deliberately as the team gets comfortable. Run one without the IT lead present, since that is a realistic Tuesday. Run one where the first inject arrives by text message to the facilitator and nobody knows the exercise has started. Invite your IT provider to the next one, which usually surfaces a mismatch between what you think they do out of hours and what the contract says.
And feed the output into the documents it belongs in. Findings about who decides what go into the plan itself, using the structure in our walkthrough for creating an incident response plan. Findings about what people did or did not recognize go into training, which our security awareness training guide covers. Findings about missing controls belong in the broader programme described in our small business cybersecurity guide. An exercise that only produces a report has produced nothing; the point is a shorter, better-rehearsed version of the real thing, which is also what a good post-incident review is for. The wider framing sits in our incident response guide.
Frequently asked questions
How long should a first tabletop be?
Ninety minutes, including the debrief, with six to eight people in the room. Longer than that and attendance becomes the constraint. A tight ninety minutes on one decision finds more than a half day spent reciting a plan.
Who should facilitate it?
Not the person who wrote the incident response plan, and not the most senior person present. The plan's author will defend it instead of testing it, and a facilitating boss turns the exercise into a performance review. Pick someone organized who is willing to ask the same question three times.
Do we need a realistic technical scenario?
No. A tabletop is discussion-based, with no live systems and no technical artifacts, which is exactly what makes it cheap to run. Plausibility matters more than technical depth: use a system your team actually depends on and an attack that happens to organizations your size.
Where can we get a scenario for free?
CISA publishes Tabletop Exercise Packages with template objectives, scenarios, discussion questions, an invitation template, a slide deck, a feedback form and an After Action Report template, covering ransomware, insider threat and phishing among others. The UK NCSC runs Exercise in a Box, a free self-service tool with ready-made cyber exercises.
What is the most common finding in a first tabletop?
Almost never a technical one. It is usually that nobody knows who has the authority to make a specific expensive decision, or that the one person who knows a critical thing was not in the room. Both are cheap to fix once named and impossible to fix during a real incident.
What is a hotwash?
The short debrief held immediately after the exercise, while everyone is still in the room, asking what worked, what did not, and what needs to change. It is separate from the written report because the written report takes days and the honest answers have a shelf life of about fifteen minutes.
How many findings should the report have?
No more than ten, each with a named owner and a date, and at least three that are genuinely done inside thirty days. A report with thirty findings and no owners produces nothing, and the team learns that the exercise was theatre.
How often should we do this?
Twice a year is a realistic rhythm for a small team, with a different scenario each time and the previous report's actions reviewed at the start. Annual is better than nothing but tends to re-find the same gaps, because the people and the systems both change faster than that.
Should we tell participants the scenario in advance?
Tell them the date, the duration, the objective and that no technical preparation is needed. Do not circulate the scenario or the injects. Preparation turns the exercise into a rehearsal of the plan rather than a test of whether people can find and use it under time pressure.
What if the exercise exposes that we have no plan at all?
That is a successful exercise and a cheap way to learn it. Write the three decisions you could not answer into a one-page document before you leave the room: who declares an incident, who can authorize taking a system offline, and who calls the insurer. A real plan grows outward from those.
Sources
- CISA Tabletop Exercise Packages, CISA
- Exercise Planning and Conduct Support Services, CISA
- SP 800-84, Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities, NIST
- SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management, NIST
- Exercise in a Box, National Cyber Security Centre
- Federal Government Cybersecurity Incident and Vulnerability Response Playbooks, CISA
- I've Been Hit By Ransomware!, CISA
- RFC 3227: Guidelines for Evidence Collection and Archiving, IETF


