AI incident response template generator
When an AI system misbehaves in production — a biased recommendation, a harmful generation, a leaked record, or a hard failure — the worst time to design your response is during the incident. This generator produces a structured incident-response runbook tailored to the type of AI incident you select, so you can open a clean checklist instead of improvising under pressure.
How it works
Pick an incident type and the tool loads a profile for it: a default severity level, the stakeholders who must be notified, and a remediation checklist specific to that failure mode. Add a one-line system description and an estimate of affected users, and the runbook fills those into a five-phase structure — triage, notification, containment, remediation, and post-incident. Everything is assembled in your browser as plain Markdown that you can copy straight into your incident channel or ticket.
Tips and notes
- Contain before you root-cause. Phase 3 exists on purpose: disable, filter, or gate the failing path before you start the deep investigation.
- Watch the breach clock. For data leaks, the GDPR 72-hour notification window can start the moment you become aware — confirm your duties early.
- Add a regression test. The post-incident phase asks for an eval or test that would have caught the issue; that is what stops a repeat.
- It is a template, not advice. Severity defaults and notification lists are reasonable starting points, not a legal determination for your situation.