Incident Post-Mortem Report
ProWrite blameless post-mortem reports with timeline reconstruction, root cause analysis, and concrete action items
About the Incident Post-Mortem Report Prompt Template
This operations template assigns the AI the role of a site reliability engineering lead who writes blameless post-mortems that drive real improvements and prevent recurrence, so the prompt it builds is framed by genuine subject-matter expertise rather than a generic request.
What it does: Write a your severity post-mortem for the your incident incident at your company that occurred on your date.
You fill in 7 fields (6 required, 1 optional), and SurePrompts assembles a complete, structured prompt you can paste straight into ChatGPT, Claude, or Gemini.
Streamline operations with AI-generated documentation, SOPs, reports, and process guides.
How to Use This Template
- 1
Fill in Company / Service
e.g., Acme API, Our production system
- 2
Fill in Incident Summary
e.g., 45-minute API outage, Payment processing failures for EU customers
- 3
Fill in Incident Date
e.g., March 15, 2025
- 4
Fill in Severity
Enter the severity for your prompt.
- 5
Fill in Timeline of Events
What happened in order: - 14:00 Deploy went out - 14:15 First alerts fired - 14:20 On-call acknowledged - 14:45 Root cause identified - 15:00 Fix deployed - 15:15 Service fully recovered
- 6
Fill in User / Business Impact
Who was affected and how: - 2,000 users saw errors - $15K estimated revenue loss - 45 support tickets filed
- 7
Fill in Root Cause (if known)
What caused the incident? Include technical details.
- 8
Copy your prompt
Click the copy button to copy your generated prompt, then paste it into your preferred AI tool.
Template Fields
Every field below maps to a part of the finished Incident Post-Mortem Report prompt. Required fields shape the core request; optional fields add detail and control.
A required input that takes a short line of text.
Example: e.g., Acme API, Our production system
A required input that takes a short line of text.
Example: e.g., 45-minute API outage, Payment processing failures for EU customers
A required input that takes a short line of text.
Example: e.g., March 15, 2025
A required input that takes one option from a list. Choose from 4 preset choices.
Available choices:
A required input that takes a longer, multi-line value.
Example: What happened in order: - 14:00 Deploy went out - 14:15 First alerts fired - 14:20 On-call acknowledged - 14:45 Root cause identified - 15:00 Fix deployed - 15:15 Service fully recovered
A required input that takes a longer, multi-line value.
Example: Who was affected and how: - 2,000 users saw errors - $15K estimated revenue loss - 45 support tickets filed
An optional input that takes a longer, multi-line value.
Example: What caused the incident? Include technical details.
This is a Pro template. Upgrade to access.
Related Resources
Proof of Work: Show How AI 10x'd Your Output
Make your AI-boosted productivity visible to managers and clients without overclaiming. Honest, concrete ways to document and present the impact of your work.
Prompt Engineering for Business Teams: Marketing, Sales, Engineering, Ops
How business teams prompt AI for real work — briefs, discovery, architecture reviews, SOPs. Function-specific patterns across marketing, sales, engineering, and ops.
AI SOP Writing Prompts (2026): Standard Operating Procedures That Work
Prompt patterns for SOPs — process decomposition, step ordering, exception handling, and ownership. Structure the prompt and the SOP is usable.