AI incident response checklist
What to do, in order, when an AI system causes or nearly causes harm.
2 min read·Updated 8 November 2026Compliance leadsSecurityAI owners
In the first hour
- 1Contain it. Pause the system or the affected feature if harm is ongoing. Use your kill switch.
- 2Log it in V77 Trust with the time you became aware. That time starts every legal clock.
- 3Tick the rules that may apply (EU AI Act serious incident, DORA, GDPR) and read the deadlines shown.
- 4Tell the right people: the system owner, compliance, security, data protection officer, and legal.
Within the first day
- 1Preserve evidence: logs, inputs and outputs, model and prompt versions, screenshots. Don't change the system before you've saved them.
- 2Assess the impact: who was affected, how, and how many.
- 3Decide on reporting. If it's a serious incident, a major ICT incident or a personal data breach, prepare the report now. Short deadlines (2 days, 4 or 24 hours, 72 hours) leave no room.
- 4If you're a deployer, tell the provider straight away.
Within the reporting deadline
- 1Submit the reports and choose Mark submitted on each deadline.
- 2Tell affected people where required.
Afterwards
- 1Find the root cause: data, model, prompt, integration, human process.
- 2Record corrective actions and track them as findings with owners and dates.
- 3Close the incident once the root cause is recorded.
- 4Update the risk assessment, tests and oversight procedure so it can't happen the same way again.
Tip
Rehearse once a year with a realistic scenario. The first time you fill in an Article 73 report shouldn't be during a real incident.
Ready to try it in V77 Trust?Open Incidents →