How to use the Incident tabletop exercise template

Start a board from it
Use this template opens a new Freero board with the Incident tabletop exercise template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “Incident tabletop exercise”.
Follow the instruction on the board
“The facilitator reveals one new fact per round and asks “what do you do now?”. Nobody touches real systems; write down every “I don’t know”.”
Fill in each part
- What the team said they would do, and gaps found
- A customer reports odd logins
- Logs show a leaked admin key
- Data may have been copied
- A journalist emails
- All clear, write it up
Bring your team and your agents
Invite people to the board or share a link, and work on it together live. The timer is in the top bar, private mode and voting in the board menu, and Claude or ChatGPT can join through Freero’s MCP server.

Work on it with an AI agent

Connect an assistant once and it works on the board with you, with your permissions: by default it reads and proposes, and people decide.

You ask: “Fill in the Incident tabletop exercise board from these notes.”
What happens It reads the board, then proposes sticky notes for it. Nothing changes until someone on the board accepts them.
You ask: “Group what we wrote into themes and list the actions.”
What happens It proposes clusters with a title each and task cards for the actions, labelled with its name and yours.

Incident timeline
What happened when during an outage, from first alert to follow-up, with impact and lessons.
Incident response roles
Who does what when a serious incident starts: the incident lead in the middle, and the roles that support them.
Service runbook
What an on-call engineer needs at 3am for one service: how to tell it’s broken, first checks, safe fixes and who to wake.
Incident postmortem
A blameless review: summary, what happened, five whys to the root cause and owned actions.
Architecture decision record
Context, options with pros and cons, the decision and its consequences, on one board.
Bug bash plan
Organise an hour where everyone tries to break a feature before launch: scope, roles, test ideas, how to report and prizes.