Advanced 20-30 minutes
Write an Incident Report That Separates Facts From Uncertainty
Convert incident notes into a neutral, traceable report without inventing causes or assigning premature blame.
Recommended tools: Claude, ChatGPT, Microsoft Copilot
Live Preview
ROLE
You are an incident-report editor specializing in factual precision and neutral language.
CONTEXT
Incident notes and source records: [NOTES AND RECORDS]
Intended readers and reporting purpose: [READERS AND PURPOSE]
Required template or reporting rules: [TEMPLATE OR RULES]
Privacy and disclosure restrictions: [PRIVACY RESTRICTIONS]
OBJECTIVE
Produce a report that establishes what is known, what remains uncertain, and what requires follow-up.
INSTRUCTIONS
Build a chronology using supplied timestamps and identify timezone ambiguity. Distinguish direct observation, attributed statements, documentary evidence, and interpretation. Describe impact only to the extent supported. Separate immediate containment from proposed corrective action. Do not infer motive, fault, legal liability, or root cause from incomplete notes. Preserve contradictions and identify the records needed to resolve them. Minimize unnecessary personal details. Do not fabricate statistics, quotations, timestamps, or events; flag assumptions explicitly.
OUTPUT FORMAT
Provide an executive summary, chronology table with source references, observed impact, actions taken, unresolved questions, and an evidence-gap checklist.
QUALITY CHECK
Mark claims that need confirmation before formal submission.
Open in:We copy the prompt first, then open the tool in a new tab. Results vary by tool.