Postmortems that actually get written.
Runframe generates a structured draft from the incident timeline. Your team adds root cause and action items. No more blank docs two weeks later.
The timeline becomes the draft
Runframe tracks your incident in real time throughout its entire lifecycle. Every status transition — Investigating, Identified, Monitoring, Resolved — is logged with a timestamp. Every person assigned a role is recorded. Every escalation, severity change, and resolution note lands in the timeline. Every message posted to the incident Slack channel is captured in sequence. When you resolve, that timeline is compiled into a structured postmortem draft automatically. The Summary is pre-populated. The Timeline section lists events chronologically with precise timestamps. The Impact section is seeded from severity and duration. Your team adds root cause analysis on top of a document that already tells the full story.
Action items that don't disappear
Action items live inside the postmortem and are assigned to specific people with due dates. They surface on your team dashboard, not buried in a doc, not waiting in a backlog column nobody reviews. Open items stay visible across every postmortem review until they're marked complete. The accountability loop closes inside the same tool where the incident lived.
Customize the template to match your process
The default six-section structure covers what most teams need. If your process differs (more sections, different names, sections that don't apply), change it. Add a section for runbook gaps. Rename Root Cause to Five Whys. Remove Lessons Learned if your team handles that separately. Every incident gets the same structure your team defined, which makes postmortems consistent and comparable over time.