Technical incident post-mortem
A blameless post-mortem draft for IT / ops leadership.
This one needs human approval before use — got it?
High-risk prompt: touches sensitive areas. Always have a human review the output before you use it. How to use AI responsibly →
When to use
After a system outage, data-loss scare, or security event. Never share credentials or personal data.
Prompt template
Produce a blameless post-mortem for the following technical incident: {TIMELINE_ANONYMISED}. Structure: what happened, impact (users, services, data), what worked in the response, what didn't, root cause (system, not person), 3–5 actions with owners and dates, what we'll change in our monitoring. No blame of named individuals.Replace each highlighted placeholder with real context. Keep names and safeguarding details out.
When to use this prompt
Reach for this prompt when you need to a blameless post-mortem draft for IT / ops leadership. It's designed for IT lead. Typically used within Data work.
Not suitable for real-time decisions about individuals, safeguarding cases, or public claims without human sign-off.
How to use it
- 1
Gather your inputs
Have your local context, audience and goal to hand. - 2
Fill in the highlighted placeholders
Copy the template above and replace every highlighted placeholder with real, local context. - 3
Run it in your AI tool
Paste into your preferred AI assistant. Ask a follow-up if the output misses your association's tone. - 4
Work through the checklist
Tick every item before you send, publish or act on the output.
Why this prompt works
Learns from IT incidents without triggering defensive behaviour.
Worked example
Timeline: booking system down 09:00–13:00, cause identified in DB migration
What good output looks like
A blameless post-mortem draft ready for the IT / ops leadership to review.
Was this useful?
Sign in to leave feedback and shape which prompts stay in the library.