MyRealityCheck.ai
Crisis Readiness

CrisisReadinessCheck

You are responsible for readiness. You have plans, roles and procedures in place. The harder question is what your organisation can actually demonstrate today — before a real disruption tests it.

Discuss your scope →

Assumed readiness is not evidenced readiness.

Most organisations know they have prepared. Fewer can show, on demand, where that preparation holds and where it rests on assumption. Assumptions are not evidence. CrisisReadinessCheck makes the distance between the two visible.

What the scan examines

CrisisReadinessCheck assesses your organisation across eight domains of crisis readiness. It places assumptions against the information and evidence available within the agreed scope, and surfaces gaps, uncertainties and priorities. It does not simulate a crisis, and it does not predict how people will actually behave when one occurs. It examines what can be demonstrated — not what is presumed.

How it works

  1. Scoping — a short conversation to understand your context and define what the assessment covers.
  2. Scoped information — you provide the information and evidence within the agreed scope.
  3. Assessment across eight domains — reviewed with an operationally tested method and necessary human judgement.
  4. Report and readout — findings, evidence gaps and priorities, explained in a short readout.

Exact steps may vary with the scope agreed during the first conversation.

What you receive

A report designed for executive use. Depending on the agreed scope, it includes:

What the scan is not

Clarity matters as much as findings. CrisisReadinessCheck is:

It is an independent assessment — independent in the position of the review, based on the information your organisation provides.

Illustrative example · fictional

What a Crisis Readiness Report looks like

HanzeGrid — a fictional mid-size critical-infrastructure operator · CRS-2026-HZG-DEMO
Emerging
61
of 100

Strong individual domains, weaker connecting layers. On this scan HanzeGrid shows the patterns of an Emerging level. Technical continuity and cyber resilience are strong; the gap sits in the connecting layers — external coordination, shared language, and overall governance oversight. The distance is not in what the organisation can do, but in who holds the whole picture when several domains come under pressure at once.

01 GOV49
02 OPS72
03 TRN58
04 COM45
05 INF84
06 EXT43
07 PSY61
08 CYB79
Maturity heat-strip across eight domains — strong verticals (05, 08, 02), weaker connecting layers (06, 04, 01).
1 · External coordination — 43

Lowest score and highest connecting weight. Continuity capacity becomes usable only when the lines to adjacent sectors and the crisis centre are warm before things go wrong.

2 · Communication — shared language — 45

Without a shared vocabulary the same situation carries different meaning on either side of the table — slowing decisions precisely when speed matters.

3 · Crisis governance — 49

Mandates exist per department; what is missing is the end-mandate over the whole — who declares a crisis when three departments each see a partial problem, but no one sees the pattern.

The ordering follows from the scores, not from opinion — the same data produce the same sequence. That the measurement places these domains on top is not advice, but structured evidence for executive judgement. What an organisation does with it is its own decision.

In a real assessment, a Crisis Readiness Report serves as a structured snapshot of crisis maturity within the agreed scope — usable to show, to regulators, partners and the board, what is demonstrable rather than presumed. It does not establish compliance, confirm legal conformity, or provide certification or attestation. It makes visible, within scope and on the basis of the information provided, what an organisation can actually demonstrate.

HanzeGrid is a fully fictional organisation. Any resemblance to real organisations is coincidental. This is an illustrative example of what a Crisis Readiness Report can look like — it is not a client case and is not based on a real assessment.

Discuss your scope

Every CrisisReadinessCheck starts with a short scoping conversation to understand your context before defining the assessment.

Discuss your scope →
Start with the individual Quick Scan →

The Quick Scan gives one individual perspective and can surface possible questions. It is not a shortened CrisisReadinessCheck, not an organisational assessment, and not organisational evidence.

Founder perspective — Prepared, based on what?