Template guide
Overview
Use this reliability incident report template after outages to capture facts, root causes, impact, and corrective actions in a consistent format.
Who should use this template
- SRE and platform teams
- Engineering managers
- Operations leaders
What this template covers
Incident facts and timeline
- Date, severity, impact
- Detection/mitigation/resolution timestamps
- Downtime narrative
Root cause and impact analysis
- System/process/human factors
- Users affected
- Revenue and service impact
Prevention plan
- Corrective actions
- Monitoring improvements
- Ownership and follow-up priorities
From responses to AI summary
FormGenyus is built for workflows where raw answers are long. Here is an illustrative example of how a summary differs from raw text (not from a live submission).
Sample raw response
SEV-1 outage for 52 minutes after config rollout; alerts fired late; rollback succeeded after manual intervention…
Postmortem brief
- Root cause: unsafe config release path with insufficient validation
- Failure factor: delayed detection from noisy alert routing
- Prevention: release guardrails + targeted alert redesign + rollback automation
FAQ
- Is this template blameless by design?
- Yes. It emphasizes systems and process learning, not individual blame.
- Can this be reused across teams?
- Yes. It works well as a standardized postmortem format across services.