Insights:Incident Response and Troubleshooting Pre-Launch Checklist: Item-by-Item Verification
10-Point Checklist
| # | Check Item |
|---|---|
| 1 | Incident severity matrix defined |
| 2 | First responder assigned |
| 3 | Monitoring covers sites and resources |
| 4 | Alert recipients configured |
| 5 | Containment playbook readable on one screen |
| 6 | Rollback process verified in practice |
| 7 | Contact info locked in group chat |
| 8 | Escalation path clearly defined |
| 9 | Post-mortem template prepared |
| 10 | Drill record exists |
Three Key Verifications
Rollback Verification
Actually performed a rollback, not just "theoretically able to." Verify code, configuration, and data.
Alert Verification
Proactively trigger an alert and confirm it can be received, recognized, and traced.
Drill Record
Simulate a "site unreachable" scenario and record elapsed time from detection to recovery.
Only after these three verifications is the process considered usable.
Inspection Method
- Open each item individually to confirm.
- Mark uncertain items and set a deadline.
- Retain screenshots or records for critical items.
Maintenance After Launch
- Recheck quarterly.
- Update responders on the day of any staffing change.
Common Failures
- Alerts sent to former employees' email addresses.
- Runbooks are too long; nobody consults them when issues arise.
- Only practiced "rebooting," never practiced "data rollback."
Scope
This checklist is designed for small to medium-sized sites. For multi-team collaboration or highly regulated environments, add approval and escalation procedures.
Related Reading: