A guided incident rehearsal · 20 minutes suggested

Practice the
messy day.
Leave with a plan.

A weird supplier email. A BTP outage. A release gone sideways. Get your team talking before the real thing makes the decisions for you.

One shared screen, a fictional scenario, and a clear path from “what now?” to an action plan with owners.

No account required · No file uploads · Notes stay in this browser

Generated illustration of a team discussing an incident around a shared table
What you leave with Fictional example

A decision.
A next move.
Someone on it.

Verify supplier changes through a known contactFinance leadNext action

Decisions + unknowns + actions, ready to print or revisit.

A discussion exercise. No attacks, scans or live system changes.

Less blank-page panic.
More “we’ve got a plan.”

  1. 01

    Pick the messy situation

    Choose from ten original cyber, SAP BTP, critical-system and delivery scenarios. Gather the team around one screen; one person records.

  2. 02

    Talk through the updates

    Four fictional messages move the story on. Capture what you’d decide, why, and what you still don’t know.

  3. 03

    Make the follow-up real

    Turn gaps into owned actions. Keep a readable report, export your session and check back later.

Start with something
your team can picture.

Ten original scenarios. Four updates each. Choose a situation your team recognizes.

Explore all 10 scenarios →

Supplier payment · Email compromise

The bank details changed

An urgent supplier email lands just before a payment run. Practice how your team checks, pauses and communicates when the story starts changing.

4 incident updates · 20 minutes suggestedRehearse this →

Unavailable files · Business continuity

The shared drive goes quiet

Your team cannot open shared files during a busy morning. Rehearse decisions, safe communication and how work continues while facts are incomplete.

4 incident updates · 20 minutes suggestedRehearse this →

The point isn’t
to win the scenario.

It’s to spot the gaps while the stakes are fictional.

Who can pause a payment? Who gives the next update? What happens if the usual decision-maker is away? The app guides the conversation and organizes your own answers. It doesn’t invent advice or give your team a security score.

See a fictional rehearsal →

Your after-action report

What happened.
What we decided.
What changes next.

  • Decisions and reasons, update by update
  • Open questions that still need an answer
  • Improvement actions with owner, date and status

Readable on screen. Print to PDF. Export a portable session you can bring back.

A few things to know.

Is this a real security test?

No. It’s a safe, fictional discussion. It doesn’t scan systems, send phishing emails, certify compliance or establish whether you are secure.

Can the whole team join?

Use one shared screen with a facilitator recording the discussion. This version has no networked collaboration or participant accounts.

Where do our notes go?

Your notes stay in this tab unless you explicitly enable saving on this browser. No exercise notes are sent to the server. Export a session before closing if you haven’t enabled saving. Browser data can be cleared, so export important work.

Why build another exercise tool?

Free and commercial alternatives already exist. This prototype tests a guided, browser-local setup-to-action-report workflow for small teams. Its commercial value is unvalidated. See the Atlas signal and alternatives.