Skip to main content

Your buyers are asking AI. Are you the answer?

Find out with OptimizeCamp →

Incident Post-Mortem Report

Pro

Write blameless post-mortem reports with timeline reconstruction, root cause analysis, and concrete action items

SREOperationsReliability

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. 1

    Fill in Company / Service

    e.g., Acme API, Our production system

  2. 2

    Fill in Incident Summary

    e.g., 45-minute API outage, Payment processing failures for EU customers

  3. 3

    Fill in Incident Date

    e.g., March 15, 2025

  4. 4

    Fill in Severity

    Enter the severity for your prompt.

  5. 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. 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. 7

    Fill in Root Cause (if known)

    What caused the incident? Include technical details.

  8. 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.

Company / ServicetextRequired

A required input that takes a short line of text.

Example: e.g., Acme API, Our production system

Incident SummarytextRequired

A required input that takes a short line of text.

Example: e.g., 45-minute API outage, Payment processing failures for EU customers

Incident DatetextRequired

A required input that takes a short line of text.

Example: e.g., March 15, 2025

SeverityselectRequired

A required input that takes one option from a list. Choose from 4 preset choices.

Available choices:

P1 (Critical outage)P2 (Significant degradation)P3 (Minor impact)Near-miss (no user impact)
Timeline of EventsmultilineRequired

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

User / Business ImpactmultilineRequired

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

Root Cause (if known)multiline

An optional input that takes a longer, multi-line value.

Example: What caused the incident? Include technical details.

Use This Template

This is a Pro template. Upgrade to access.

Related Resources

Blog Post

16 AI Prompts for Manufacturing Operations: Quality, Downtime, and SOPs

Use these AI prompts to structure manufacturing shift handoffs, quality investigations, maintenance planning, work instructions, and continuous improvement.

Blog Post

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.

Blog Post

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.

Blog Post

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.

Related Templates

Professional Email Reply

Draft clear, professional email responses

Meeting Summary

Summarize meetings with key points and action items

SOP Documentation

Create clear Standard Operating Procedures

Project Brief

Create comprehensive project briefs for team alignment