Separate verified facts from guesswork in incident reports
Sort timeline events in post-incident logs into proven evidence versus speculative blame so your team addresses real root causes.
You getVerified Incident Timeline and speculative Assumptions and Blind Spots
Prompt
Act as an impartial root-cause incident auditor. Your job is to separate verifiable, timestamped facts from human assumptions, speculation, and retrospective blame in the provided incident notes.
Rules:
- Categorize every major claim as either a Verified Fact, an Unverified Assumption, or an Attributed Blame statement.
- Verified facts require concrete, measurable logs, alerts, or audit trails.
- Flag whenever a human error is blamed instead of a system or process gap.
- Keep observations neutral and objective.
Output format:
1. Verified Incident Timeline (bullet list with timestamps, actions, and verified data)
2. Speculative Assumptions and Blind Spots (numbered list detailing unverified assertions)
3. Questions to Verify with System Telemetry
Here is the incident report:Example output
Paste raw postmortem notes or Slack incident room transcripts directly into Claude, Gemini, or ChatGPT. Follow up by asking what automated monitoring could have detected the incident earlier.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Map branching root causes for multi-factor incidents
Analyze systemic breakdowns across parallel technical, operational, and communication branches instead of relying on a single 5 Whys chain.
Weigh hidden switching costs before changing tools
Calculate real operational drag, retraining delays, and data migration traps before switching core software. Ideal for team leads and business owners.
Find the root cause of an operational issue
Drill down through recurring symptoms to identify systemic causes and design prevention fixes rather than temporary patches.
Isolate the primary constraint in an operational workflow
Pinpoint the single limiting bottleneck in a multi-step process so your team avoids wasting effort on non-constraining tasks.
Separate actionable leading indicators from vanity metrics
Filter deceptive vanity numbers from high-leverage predictive metrics you can influence daily. Built for operators, founders, and department leads.
Separate luck from skill in past decisions
Break down past wins or losses to see what was sound judgment versus random chance. Use this during retrospectives to avoid rewarding reckless risks or penalizing disciplined bets.