How it works
From your context to an evidence packet in one sitting.
Five concrete steps. You bring the people and the plan; ControlDrill tailors the scenario, runs the room, and hands back the record.
1. Enter your context
After purchase you complete a short intake: which exercise type to run, company, stack assumptions, people and roles, and the frameworks you may cite later (as citations, never as a grade). The intake baseline is enough to tailor a useful exercise even without uploading a document.
Six exercise types
2. Optionally upload your IR or BCDR plan
Paste plan text or attach PDF, Word (.docx), OpenDocument (.odt), .txt, or .md. Optional and high value: the tailor can cite your escalation matrix, RTO commitments, and named systems. PDF and Office files convert to text on the same platform that runs the app. Scanned or image-only PDFs may not extract cleanly; paste the text if that happens.
3. We tailor a scenario grounded in that reality
Background prep builds a scenario for the exercise type you chose, with timed injects that name your systems, people, RTOs, and contractual clocks where the context supports it. Prep usually takes about a minute. If tailoring cannot complete, the exercise still runs on the solid base scenario for that type so you are not blocked.
Illustrative inject · what "grounded" looks like
At 02:14 your EDR flags encryption on prod-db-01 in us-east-1. Your Northwind MSA requires notification within 24h of confirmed exposure. Go.
Cites prod-db-01, 4h RTO, Northwind MSA (fictional example org)
4. Run the timed live exercise with your team
Schedule a time and name participants. Everyone joins by personal magic link (no enterprise identity provider required). The shared view holds the clock and the current inject; each person answers in their own pane. The moderator drives phases, fires injects, and escalates on silence. AI assists; it never makes the call for you. If live generation is briefly unavailable, prompts come from the prepared script. The clock, attribution, and record are unaffected.
5. Get the evidence packet for your auditor
When the session ends, ControlDrill builds a self-contained HTML evidence packet: attendance (including invited-but-absent), timeline of injects and decisions, gaps with remediation owners, and a control cross-reference as citations only. We deliberately do not print Tested / Partial / Untested grades. Your auditor judges the evidence.
Who should attend
- Incident commander / security lead who owns the exercise outcome.
- On-call engineering who would contain and recover systems.
- Communications / PR who would handle external messaging.
- Legal or privacy when notification clocks and classification matter (an empty Legal seat is itself a useful finding).
- Observers as needed; the record attributes participants who engage.