Skip to content

A tabletop exercise is a discussion-based session in which the people who would respond to an emergency walk through a realistic scenario together, around a table or on a call, and talk through what they would do. It tests your plans, roles and decisions without any real-world disruption, so gaps surface in a meeting room rather than during a live incident.

Most organisations have plans for fires, floods, cyber attacks and IT failures. Far fewer have checked those plans still work. This guide covers the main types, who should be in the room, a step-by-step method, six ready-to-use scenarios, a planning checklist and the after-action review.

Book a call with our team

What is a tabletop exercise?

A tabletop exercise, often shortened to TTX, is a facilitated walk-through of a simulated incident. A facilitator describes a scenario, such as a ransomware attack or a flooded office, and the group discusses how they would respond. As the session goes on, the facilitator adds new developments, called injects, that change the situation and force fresh decisions.

Nobody evacuates a building or shuts down a server. The value comes from the conversation: who decides what, who needs to know and what happens when the procedure does not fit the facts. It is not a test of individuals but of the plan, so people can admit uncertainty safely. If you are unsure what counts as a crisis worth exercising, our guide on what a crisis is is a useful starting point.

Why run a tabletop exercise?

Plans tend to fail in predictable ways: an out-of-date phone number, two people who each think the other is making the call, an approval process slower than the incident. A tabletop exercise surfaces those assumptions before they matter.

The main benefits are:

  • Validate your plans: Check that emergency, incident and business continuity plans work when applied to a specific situation, not just on paper.

  • Clarify roles: Confirm who leads, who decides, who communicates and who deputises when someone is unavailable.

  • Find gaps early: Spot missing contacts, unclear thresholds, single points of failure and resources you do not have.

  • Improve communication: Test how quickly and accurately you can tell employees, visitors and stakeholders what is happening.

  • Build confidence: People who have talked through a scenario respond faster and more calmly when something similar happens for real.

The UK context

In the UK, the Civil Contingencies Act 2004 and its regulations require Category 1 responders, such as local authorities, emergency services and NHS bodies, to maintain emergency plans and to exercise them and train staff. UK government guidance on emergency preparedness sets out exercising as a core part of planning. Private employers are not covered by those duties, but many work alongside responders or supply them.

Other frameworks point the same way. ISO 22301, the international standard for business continuity management, expects organisations to exercise and test their continuity arrangements. The National Cyber Security Centre offers a free tool, Exercise in a Box, to help organisations practise their response to cyber incidents. Venues preparing for Martyn's Law, the Terrorism (Protection of Premises) Act 2025, may also find tabletop sessions a practical way to talk through their procedures.

Types of tabletop exercise

A tabletop exercise sits within a wider family of exercise types. Most organisations start with discussion-based exercises and move towards more operational ones as their plans mature.

Exercise type What happens Best for
Seminar or workshop A briefing or working session on a plan, with no live scenario Introducing a new plan or new team members
Tabletop exercise A facilitated discussion of a scenario, with injects Testing decisions, roles and communication
Drill People physically practise one procedure, such as an evacuation or roll call Building muscle memory for a single action
Functional exercise Teams carry out their roles in real time using real tools, without deploying people Testing systems, notifications and coordination under time pressure
Full-scale or live exercise A realistic simulation involving people, equipment and sometimes external agencies Testing the whole response end to end

Discussion-based and functional tabletop exercises

Most tabletop exercises are purely discussion-based: players describe what they would do. In a functional tabletop, players also use the tools they would rely on, for example sending a test alert to a test group or checking a location map. This shows whether the steps described in the room can be done in the time available. It is a natural step towards testing your wider critical event management arrangements, where alerts, location data and response come together.

Cyber tabletop exercises

A cyber tabletop exercise tests your response to an incident such as ransomware, a data breach, a phishing compromise or an attack on a supplier. It should involve more than IT, because legal, communications, HR and senior leaders all have decisions to make, such as when to notify the Information Commissioner's Office and what to tell staff and customers. Unlike a penetration test, which probes technical defences, a tabletop tests the people and decisions around the technology.

Business continuity tabletop exercises

A business continuity tabletop exercise asks how you keep critical activities running after losing a building, a key supplier, a system or a large share of staff. It tests recovery priorities, workarounds and recovery time targets. If you have not yet written the plan you want to test, start with our guide to building a business continuity plan.

Emergency and people-safety tabletop exercises

These focus on keeping people safe during fire, flood, security threats, a missing lone worker or unrest abroad. The key questions are how fast you can account for everyone and who decides to evacuate, shelter or stand down.

Tabletop exercise roles

Every tabletop exercise needs a small set of clearly defined roles. In a small organisation one person may cover two roles, but the facilitator should not also be a player.

Role What they do
Facilitator Runs the session, presents the scenario, releases injects, asks probing questions and keeps time. Stays neutral and does not give answers.
Players The people who would make decisions in a real incident. They respond as they would on the day, using the real plan.
Scribe Records decisions, questions, disagreements and gaps as they happen, with times. Their notes feed the after-action report.
Evaluator Watches against the exercise objectives and judges where the plan held up and where it broke down.
Observers Attend to learn or provide expertise, for example a site manager, insurer or adviser. They do not take part in decisions.
Sponsor A senior leader who approves the exercise, sets its priority and owns the actions that come out of it.

A good facilitator guides without dominating, draws out quieter players and knows when to let a disagreement run because it is revealing something useful.

How to plan and run a tabletop exercise, step by step

1. Set clear objectives

Write down two to four specific things you want to learn. "Test our emergency plan" is too broad. Better examples are "confirm we can account for all staff at the Leeds site within 30 minutes" or "check who can authorise a message to all employees out of hours".

2. Choose a realistic scenario

Pick a plausible threat for your sites and travel patterns, starting with your highest-impact risks. A specific location, time of day and complication teach far more than a generic "major incident".

3. Pick the players

Invite the people who would actually make decisions, plus their deputies: usually operations, HR, facilities, IT, communications and a senior decision-maker, with security, legal or travel management where relevant.

4. Write the injects

Injects are timed updates that move the scenario on. Plan three to six. Mix escalations, such as a second site being affected, with complications, such as a key person being unreachable, and include at least one piece of good news to check that the team can scale back as well as up.

5. Prepare materials and ground rules

Prepare a scenario brief, inject cards, the relevant plans and contact lists, and a note template for the scribe. Share the objectives and ground rules in advance, but not the injects. Ground rules: no-fault discussion, phones away, respond as you would on the day.

6. Run the session in phases

A two-hour session works well for most scenarios.

Time What happens
0:00 to 0:10 Welcome, objectives and ground rules
0:10 to 0:30 Scenario starts: first reports, first decisions, who is told
0:30 to 1:10 Injects one to three: escalation and complications
1:10 to 1:30 Decision point: a major call with incomplete information
1:30 to 1:40 Final inject: recovery or stand-down
1:40 to 2:00 Hot debrief

7. Hold a hot debrief

Straight after the scenario ends, ask three questions: what worked better than expected, where did the plan's assumptions not hold up, and what must we change before the next exercise? Keep it short and blame-free.

8. Write up and assign actions

Within a week, the scribe and evaluator turn the notes into an after-action report with named owners and deadlines. This is covered in more detail below.

Ready-to-use tabletop exercise scenarios

Use these six scenarios as they are, or adapt the details to your sites. Each includes a starting situation, three injects and the key questions to ask.

Scenario 1: Ransomware attack

Setup: At 07:45 on a Monday, staff report that files on the shared drive will not open and a ransom note appears on several screens. The finance system is unavailable.

  • Inject 1 (15 minutes in): IT confirms the attackers claim to have copied customer and employee data.

  • Inject 2 (40 minutes in): Email is down. Staff are asking on personal phones what they should do.

  • Inject 3 (70 minutes in): A journalist calls asking for comment on a reported breach.

Key questions: Who decides to isolate systems? How do you reach staff without email? When and how do you notify the ICO and affected people? Who speaks to the media?

Scenario 2: Flooding at a site

Setup: After two days of heavy rain, the Environment Agency issues a flood warning for the area around your warehouse. A night shift of 25 people is on site.

  • Inject 1: Water is entering the loading bay and the access road is starting to flood.

  • Inject 2: Two agency workers on the shift are not on your main contact list.

  • Inject 3: The following morning, the site is inaccessible for at least a week.

Key questions: Who decides to send the shift home or evacuate, and on what trigger? How do you confirm everyone is safe, including agency staff? Where does the work move to while the site is closed?

Scenario 3: Fire at an office

Setup: At 14:10 the fire alarm sounds at your head office. Staff evacuate to the assembly point. The fire service attends.

  • Inject 1: The roll call is short by three people. One is a visitor, two are hybrid workers who may not be in today.

  • Inject 2: The fire service says the building will be closed for the rest of the day and possibly longer.

  • Inject 3: Staff at the assembly point start posting photos on social media.

Key questions: How do you account for people who may or may not be on site? How do you tell everyone, including those working from home, what happens next? Who manages the message?

Scenario 4: Travelling staff caught in civil unrest

Setup: Two employees are on a business trip in a capital city abroad. Overnight, protests escalate near their hotel and the Foreign, Commonwealth and Development Office updates its travel advice.

  • Inject 1: One employee replies to your welfare check. The other does not.

  • Inject 2: Local mobile data becomes unreliable and the main roads to the airport are blocked.

  • Inject 3: A family member of the employee who has not replied calls your switchboard.

Key questions: How do you know exactly who is in the affected area? How do you reach someone when mobile networks are disrupted? Who decides on shelter in place or departure, and who talks to the family?

Scenario 5: Lone worker incident

Setup: A field engineer working alone at a rural site misses a scheduled check-in at 16:00. Their last known location is about 40 minutes from the nearest colleague.

  • Inject 1: Calls to the engineer's mobile go straight to voicemail.

  • Inject 2: The site has poor mobile coverage and the client contact has gone home.

  • Inject 3: At 17:15 the engineer's manager, who would usually lead the response, is on leave.

Key questions: What is the escalation process after a missed check-in and how long does each step take? Who has the engineer's last known location? When do you call the emergency services? Who deputises?

Scenario 6: Major IT outage

Setup: A faulty update from a third-party supplier takes down laptops and core systems across all your UK sites at the start of the working day. It is not a cyber attack.

  • Inject 1: The supplier's fix needs each device to be repaired manually.

  • Inject 2: Customers start calling because online services are unavailable.

  • Inject 3: Restoration is expected to take three days.

Key questions: Which activities must keep running and what are the manual workarounds? How do you contact staff whose laptops do not work? What do you tell customers, and who approves it? Our guide to crisis communications covers how to plan those messages.

Tabletop exercise planning checklist

Use this as a template when planning your next exercise.

Item What to decide Done when
Sponsor Senior leader who owns the exercise and its actions Sponsor has agreed scope and date
Objectives Two to four specific, testable aims Objectives written and shared
Scenario Realistic threat with location, timing and complications Scenario brief signed off
Injects Three to six timed updates, including one de-escalation Inject cards written and sequenced
Players Decision-makers and deputies from each function Invitations accepted
Roles Facilitator, scribe, evaluator, observers Each role named and briefed
Materials Plans, contact lists, maps, note template Copies ready in the room or online
Logistics Room or call link, two hours, no interruptions Booked and confirmed
Ground rules No-fault discussion, respond as on the day Shared with players in advance
Debrief Hot debrief questions and timing Built into the agenda
Follow-up Report deadline and action owners Date set for the after-action review

After-action review

Follow the hot debrief with a short after-action report within a week. Keep it factual and focused on the plan, not individuals. A simple structure works well:

Finding What happened Action Owner Deadline
Out-of-date contacts Two agency workers were missing from the contact list Add agency staff to the contact list and review it monthly HR manager End of month
Unclear authority Nobody was sure who could approve an all-staff message out of hours Name an out-of-hours approver and a deputy in the plan Head of operations Two weeks
Single point of failure The response depended on one manager who was on leave Train and name a deputy for each lead role Sponsor Next quarter

Share the report with the sponsor and players, update the plan, and track the actions to completion. Then use the next exercise to check that the fixes work.

How often should you run a tabletop exercise?

As a minimum, run a tabletop exercise on your highest-priority scenario once a year. Many organisations aim for one every quarter, rotating through different scenarios and sites so that each key risk is covered over a year or two.

You should also run one after any significant change, such as:

  • A new or rewritten plan: Test it before you rely on it.

  • A new site, headcount change or new key personnel: New people and places bring new gaps.

  • A real incident or near miss: Exercise the lessons to check the fixes.

  • New travel or lone working patterns: Test how you would reach people in new locations.

Short, frequent sessions on a single scenario often teach more than one long annual event.

How Vismo helps you run more realistic tabletop exercises

A tabletop exercise is most useful when it tests the tools and steps your team would use for real. Vismo helps you prepare for and respond to the incidents you exercise:

  • Reach everyone at once: Mass notification sends alerts by SMS, voice call, email, app push, Microsoft Teams and Slack at the same time, and two-way replies show who has confirmed they are safe and who has not responded.

  • Target the right area: Geofencing lets you alert only the people in an affected area, such as a flooded site or a city with unrest.

  • Know where people are: Real-time employee location on a live map, through the Vismo app or dedicated devices, answers the "who is affected?" question quickly.

  • Spot threats early: Threat intelligence flags incidents near your people, which also gives you realistic, current material for scenarios.

  • Protect travelling staff: Travel security helps you keep track of and support employees abroad.

  • Support lone workers: Lone worker safety with SOS alarms, timed check-ins and escalation when a check-in is missed, backed by a BS 8484 certified service.

  • Stay connected without mobile coverage: Satellite devices keep people reachable in remote areas.

Your response procedures can also be set up as guided, timestamped steps using Vismo Workflows, so the exercise tests the same steps your team would follow for real, and the record feeds straight into your debrief. A workflow is always started by an administrator, never automatically. Every alert, reply and action is logged in an audit trail, which helps when writing the after-action report.

If your exercise shows that email is your only way to reach staff, read why email alone isn't enough for emergency employee communication. To see how alerts, location and response come together during a live incident, explore our crisis and incident management software.

Tabletop exercise FAQ

What best describes a tabletop exercise?

A tabletop exercise is best described as a facilitated, discussion-based rehearsal of an emergency or disruption. Key people talk through how they would respond to a realistic scenario, using their actual plans, so that gaps in roles, decisions and communication are found before a real incident.

What is a table top simulation?

A table top simulation is another name for a tabletop exercise. The incident is simulated through a written scenario and timed updates rather than real-world action, and participants respond by discussing decisions around a table or on a video call.

Can you give me an example of a tabletop exercise?

A simple example: a field engineer working alone misses a scheduled check-in and cannot be reached by phone. The team discusses how they would escalate, find the engineer's last known location, contact the emergency services and cover for a manager who is on leave. The facilitator adds updates every 15 to 20 minutes to make the situation harder.

How long does a tabletop exercise take?

Most tabletop exercises last between one and three hours, including the debrief. Two hours is a good length for a single scenario with four or five injects. Planning usually takes a few weeks, and the after-action report should follow within a week.

Start with one scenario

You do not need a large programme to begin. Pick your most likely high-impact risk, book two hours with the people who would respond, and use the scenarios and checklist above to find the gaps before a real incident does.

Request a product demo

Latest News stories...

Journalist reporting during disaster

Crisis Communications

Crisis communications is how you keep staff, customers and stakeholders informed when something goes wrong. Here is how to build a plan, with a template and message examples.

Read more

Rescue team searching

What Is a Crisis

A crisis is a sudden, serious threat that needs urgent decisions. This guide explains what a crisis means for an organisation, the main types and stages, real examples and how to prepare.

Read more

Businessman walking to the office

Travel Risk Management Companies

What travel risk management companies do, the main types of provider, and how UK organisations can compare them, ask the right questions and build a programme that protects travelling staff.

Read more

View latest newsfeed