Governing AI and human actions across the tools your teams already use
- Claude
- ChatGPT
- Slack
- Microsoft Teams
- Microsoft 365
- Gmail
- GitHub
- GitLab
What it does
- Reads the continuity standard that applies to the named service
- Runs the exercise against that service, on the scope defined
- Records what recovered, and how long each step actually took
- Names what fell outside tolerance instead of rounding it away
- Files the result as evidence against the obligation it satisfies
What you get
A tested recovery record
A tested recovery record: the standard applied, the scope exercised, what recovered and in how long, and what fell outside tolerance — recorded as it happened rather than summarised into a pass.
What it needs from you
The continuity standard you test against, the services in scope, and the tolerances you have already agreed. Nothing is exercised that you have not named.
Where it stops
It does not mark a failed exercise as passed. What fell outside tolerance is recorded as it happened, and the remediation decision is yours.
What starts it
A scheduled exercise
A continuity or recovery test falls due under your testing calendar.
An exit-readiness review
A critical service must be shown to be exitable within tolerance.
A material change
A critical service changes in a way that invalidates the last test.
Start with one service.
A 30-minute scoping session with your risk owner and your IT contact.