simler
Docs · Running a session

Running exercises

Running a session

From setup to debrief — the lifecycle of an exercise and the few controls that shape it.

Setting up

  1. 1

    Assign the roles

    Decide which roles real people will play and which are left to AI. At least one role must be a human — a tabletop can't run on AI alone.
  2. 2

    Pick the exercise language

    A simulation runs in English or Dutch. The whole war room — the AI roles, system messages, and the debrief — follows the language the scenario was written in.
  3. 3

    Start the session

    The clock begins and the first injects go out.

Know your role

When you enter the war room, a Your rolecard is pinned at the top with your responsibilities. It's private to you — a quick reminder of what your role is expected to handle, so you know when to step in.

Two clocks

Exercise time is the real time the session runs: a fixed budget of 30 to 120 minutes. A facilitator can pause and resume — the clock freezes while paused. When the full duration is reached, the session closes automatically; an organiser can also end it early.

Scenario timeis where the incident has got to. The story opens at a set moment — say Tuesday 07:40 — and runs along with the exercise, so ten minutes of discussion is ten minutes in the story. Some injects move the story ahead (“6 hours later”): everyone sees it happen, whichever channel they have open. Messages, documents and the debrief all read their times off this clock, written as T+ from the moment the story opened.

The debrief

Once the session ends it becomes read-only and a debrief is generated: response times, how the team did against good practice, and concrete recommendations. It's where the learning lands — review it together.

Want the full transcript?

The debrief includes the complete conversation, labelled by channel, so you can see exactly how the exercise played out.