Plan and prepare
Choose one manageable question for a discussion exercise: how would the group publish its weekly notice if the usual computer were unavailable? Give the exercise a fixed duration and say clearly that it is a rehearsal. A narrow question makes it easier to finish with a useful change.
Write a short fictional situation using ordinary conditions. Include the time, unavailable resource, and task that still needs doing. Ask participants to work from the current plan and identify the first action, the person responsible, and the information required. Avoid turning the discussion into a contest about the most dramatic possible disaster.
Use a clear process
Assign a facilitator and a note-taker. The facilitator reveals one additional complication, such as a missing contact or an inaccessible room, after the initial response has been discussed. Participants may pause to ask questions. Record assumptions separately from facts so an unverified claim does not quietly become part of the plan.
Keep the exercise safe and clearly bounded. Do not interrupt essential services, make surprise emergency calls, or move participants into hazardous environments. If a real concern arises, stop the rehearsal and address it through normal channels. Provide the scenario in accessible formats and allow written contributions.
Worked example
A useful scenario might begin: the person who normally sends the weekly service update is unavailable, their laptop cannot be accessed, and the update is due this afternoon. Give participants the actual contact list, current notice template, and handoff instructions. Ask them to identify who can authorize the message, where the latest service details are stored, and how a replacement publisher would obtain approved access. The exercise can stop when the team either demonstrates a workable path or identifies the first missing dependency that prevents progress.
Decisions and exceptions
Prepare a few prompts rather than a complicated script. Ask what information participants need, which assumptions they are making, and what they would communicate to readers if publication is delayed. Introduce an additional condition only when it helps test the stated objective. For example, the usual messaging application might be unavailable, making the printed noticeboard relevant. Do not keep adding failures until every plan collapses; that often reveals only that unlimited disruption overwhelms a small team. A bounded exercise should produce information the group can act on with its available resources.
Check and improve
Choose an observable success condition in advance. For this scenario, success might mean that an authorized backup finds the current template, identifies verified service details, and prepares a clearly labeled practice notice through an available channel. The note-taker records each missing step and any workaround used. Finish with a short discussion of what should be retained, changed, or investigated. Store the scenario, observations, and action list together. A later repetition can then test the repaired dependency without retelling the entire fictional incident or relying on memories of what the group intended to fix.
Solo and community application
Working alone, read the scenario and use only the resources you would actually have. Note each point where you rely on memory or an unavailable login. A community team can invite someone unfamiliar with the plan to explain what they think the instructions mean; confusion is useful evidence.
Reference guidance
FEMA describes tabletop exercises as discussion-based opportunities to examine plans and solve problems. This short format is an original practice design. End by selecting one fix, an owner, and a review date. Repeat the relevant portion after the fix so the exercise produces a demonstrated improvement, not just a meeting record.