For risk consultants

Stop operating the exercise. Start reading the room.

Prophyion turns the briefing documents you already have into a live, AI-scored crisis simulation. Injects fire on their own timeline, every decision is graded against sector standards, and the after-action review is ready before your team leaves the room.

Bring your own clients, your own doctrine and your own judgement.

2 runs
baseline and re-test per engagement
1–10
every decision scored against sector standards
0 hrs
spent writing the after-action review
Simulation live
T+ 00:14:32

Inject timeline

  • 00:04 First responder arrives on scene
  • 00:11 Casualty figures leak to press
  • 00:14 Secondary device reported firing
  • 00:21 Conditional: cordon not set → crowd surge held
Escalation Elevated

Decision graded

Evacuation corridor to north exit

Latency 47s · Coordination 8.1

7/10
Evacuation Triage Cordon Media

Illustrative consultant view

Fictional, non-operational scenarios only. Built for government, defence, emergency services, utilities, media and corporate crisis teams.

Key highlights

Four things that make it behave like a real crisis

The design principles behind every scenario you build, and the reason an exercise here puts far more pressure on a team than a paper tabletop can.

01

Multi-agency coordination

Crises do not respect a single jurisdiction, and operational success usually depends on coordinated action across several. Every participating agency works inside one shared environment, entering decisions concurrently rather than waiting its turn. The pressure lands where multi-agency response actually fails: asset deployment across organisations, communication workflows, and joint command.

02

Information asymmetry

No agency ever holds a complete assessment of the theatre, so nobody is given one. Information is deliberately partitioned into role-specific intelligence streams, stripping out the artificial clarity that makes conventional exercises easy. What is left is the real bottleneck: whether teams can build the protocols to validate each other’s information quickly enough to construct a shared operational picture.

03

Real-time adaptive injects

There is no storyboard to work through. A condition-dependent engine evaluates what participants actually do and branches the scenario in real time, so the incident escalates or settles according to the speed and quality of the response. That removes predictability entirely. The trajectory follows the decisions, not a script.

04

Team interdependency and storyboard synthesis

Operational domains are interdependent, so no decision is made in isolation. One team’s intervention alters the conditions every other team is working in, because a central synthesis layer feeds the output of each module straight back in as live input to the others. Separate operational threads run as a single engine, and teams have to absorb the compounding friction their counterparts create.

The problem

Most of your exercise day is admin

Reading inject cards aloud. Watching the clock. Scribbling observations you will try to turn into a report next week. None of it is the part your client is paying for.

Paper tabletop

Scenario prep
Days of writing, formatting and printing
Injects
You read cards aloud and watch the clock
Scoring
Subjective, from memory and margin notes
After-action review
Written over the following week
Replay
Whatever people remember
Branching
One fixed script, the same ending every time
With Prophyion

Prophyion

Scenario prep
Generated from the brief you already have
Injects
Fire on a timeline, or when conditions trigger
Scoring
Graded 1–10 against sector standards, with decision latency
After-action review
Generated when the simulation ends, exports to PDF or Excel
Replay
Full timeline of every decision, message and inject
Branching
Escalation and de-escalation paths. No two runs are the same

How it works

Four steps, start to signed-off report

  1. 01

    Bring your brief

    Upload the incident brief, doctrine or SOP you already work from. The blueprint engine drafts the scenario, the NPCs, the fact sheets and each team’s storyline. You review and edit every line.

  2. 02

    Invite the teams

    Send one join link. Participants sign in through a browser, read their role briefing and wait in the lobby. Nothing for them to install.

  3. 03

    Run it live

    Injects fire on schedule or when conditions trigger. Adversary NPCs push back, misinformation spreads, the clock runs at the speed you set. You observe, nudge and take notes.

  4. 04

    Hand over the AAR

    The after-action review is written for you: narrative summary, per-team metrics and recommendations. Export it, then walk your client through the timeline replay.

Producing the AAR also closes out the engagement and queues your payout.

Capabilities

The machinery a good exercise needs

You keep the judgement and the facilitation. The platform takes the switchboard.

Scenarios from your own documents

Drop in a brief and the blueprint engine extracts objectives, teams, intel dependencies and fact sheets. Your doctrine, not a generic template.

Injects that fire themselves

Time-based, condition-triggered, or pushed manually when you want to lean on a team. You are never the bottleneck in the tempo.

Decisions measured, not guessed

Every call is graded for robustness against sector standards, with decision latency and a coordination score. Defensible numbers for the debrief.

Outcomes that actually branch

Late or weak decisions escalate the situation. Timely ones de-escalate it. Run the same scenario twice and you get two different exercises.

An adversary that pushes back

Hostile actors probe your teams, and a watchdog fact-checks every public statement they issue. Sloppy comms get caught out in front of everyone.

The report writes itself

Narrative summary, per-team and per-participant scores, recommendations and a full audit trail. Export to PDF or Excel and send it the same day.

Voice and comms built in

In-app voice, role-scoped chat channels and inter-agency lines. Recorded for the debrief.

Two runs per engagement

Baseline the team before training, then prove the improvement after, on the same scenario.

Fictional by design

Non-operational scenarios only, so sensitive clients can rehearse without exposure.

Exercise types

Three very different rooms to put a team in

Same platform, same scoring, same report. Pick the format that fits the objective.

Format 01

Multi-agency coordination

A shared common operating picture where police, medical, comms and command see different slices of the truth. The exercise is about information flow, chain of command and who tells whom.

  • Deliberate information blind spots between teams
  • Role-scoped channels and resource negotiation
  • Best for executive and command-level audiences

Format 02

Mass-casualty field response

A live map of a real location with a crowd simulation running underneath it. Move units, set cordons, open evacuation corridors, and watch the crowd actually respond to what you did.

  • Physics-driven crowd evacuation and casualty deterioration
  • Fog of war, hazards and unit-level vision
  • Built on real building footprints and street layouts

Format 03

Corporate Crisis war room

A simulated feed, inbox and news cycle that turns on your client. Comms, legal, procurement and sales fight a reputational fire while misinformation outruns them.

  • Simulated posts, DMs, groups and news coverage
  • AI-generated images and video in the feed
  • Hostile actors coordinating against your statements
Walk through one, act by act

Measurement

Walk out with numbers, not impressions

The question every client asks is “so how did we do?” This is your answer, and it is the same answer every time you run an exercise.

Metric 01

Decision latency

How long each team took to act once the inject landed, measured to the second.

Metric 02

Coordination score

Whether teams shared what they knew, and with whom, or sat on it.

Metric 03

Robustness, 1–10

Each decision rated against sector standards. Generic answers score poorly by design.

Metric 04

Impact matrix

Which team’s call created which team’s problem, laid out side by side.

Live escalation meter Full timeline replay Per-participant scoring PDF and Excel export

Working with us

You bring the client. We handle the billing.

You keep the relationship and the room. The administrative half of running a training business is not your problem.

We invoice your client

Your client organisation is invoiced directly and pays online. They never need an account with us, and you never have to chase a payment or raise a document.

Your access opens up

Once the engagement is confirmed, your scenario build and both live simulation slots become available. Nothing to request, nothing to schedule with us.

You are paid after the report

Your share of the engagement is released to your own bank account once you have delivered the after-action review. Terms are set out when you join.

How an engagement runs

  1. 1

    You enroll the client

    Add the organisation and its contact. Takes a minute.

  2. 2

    We invoice and collect

    Your client gets a hosted payment page by email. They never need an account with us, and you never chase them.

  3. 3

    Your access opens

    The scenario build and both live simulation slots unlock as soon as the engagement is confirmed.

  4. 4

    You get paid

    Deliver the after-action review and your share is queued for release, typically within two business days.

Payouts run through Stripe to your own bank account. A one-time identity and bank verification is required before your first release.

Questions

What consultants ask first

How do I become a Prophyion consultant?

Apply online with your details. The platform prepares the Prophyion Consultant Agreement with your name on it; you sign it, on paper or digitally, and upload the signed copy. We review every application personally and aim to respond within five business days. Once approved, you can enroll clients straight away.

Do I have to write scenarios from scratch?

No. Bring the material you already use, whether an incident brief, a doctrine document or a client SOP, and the platform drafts the scenario, the teams, the NPCs and the inject schedule from it. You then edit anything you disagree with. The point is to skip the blank page, not to take your expertise out of it.

What do my participants need to install?

Nothing. They open a join link in a browser, on a laptop or a phone. Voice comms run in the browser too, so there is no separate conference bridge to manage.

Can I run the exercise remotely, or does everyone need to be in one room?

Either works. Everything is real-time over the web, so teams can sit in separate rooms, separate buildings or separate countries. Splitting teams up often makes the exercise harder in a useful way, because they can no longer read each other across the table.

Why two simulations per engagement?

So you can show movement. Run the scenario before your training to establish a baseline, teach, then run it again afterwards. Because outcomes branch on what the team actually does, the second run is a genuine test rather than a memory exercise. The score difference is the strongest thing you can put in front of a client.

When exactly do I get paid?

Your share is set aside as soon as your client’s invoice is settled, and it is queued for release the moment you produce the after-action review. Release is typically within two business days, straight to the bank account you verified during payout setup. The commercial terms are shared with you when you join.

Is any of this connected to real operations?

No. Scenarios are fictional and non-operational by design, and the simulated feeds, inboxes and news outlets exist only inside the exercise. Nothing your participants post can reach a real platform, which is what makes it safe to hand to a sensitive client.

Every agency can rehearse chaos, safely

Your next exercise could score itself

Apply and sign the consultant agreement. Once we approve you, enroll your first client and see the whole thing end to end.

Already have an account? Sign in