Why it matters
Consistent incident definitions make escalation, regulatory reporting, root-cause analysis, and cross-system learning possible.
What this looks like in practice
- 01Define reportable events and near misses before launch, not during a crisis.
- 02Capture system version, inputs, outputs, affected groups, controls, and decision logs.
- 03Connect incident findings to model changes, control improvements, and risk reassessment.