TemplatesWrite

Write an incident report

Turn your rough notes on something that went wrong into a factual, blame-free incident report, with the timeline kept apart from the likely cause, and with personal and health details flagged for removal.

Sample results: runs and scores on this page are illustrations while testing is set up. How we test

Bring: Your notes on what happened

Use This TemplatePrepare a prompt for your own AI chat.
  • Who it is for: Anyone who has to write up an incident, such as a supervisor, an office manager, a safety lead, a team leader or a person on the front line.
  • Time: 15 minutes
Open in the Editor
Other Formats and Files

The Step 1 chat prompt under Use This Template is the quick start. Choose a full prompt chain, checklist, Claude skill or n8n file when that destination fits your work. Checked Instructions, below, run the whole job with a hard check after every step.

Choose one format

  • Prompt chain

    Copy each step into ChatGPT or Claude, one after another.

Checked Instructions

The whole job as one set of instructions. Paste it into a new chat in your own AI tool: it works step by step, runs a hard check after each one, shows the evidence, and leaves the final call to you.

Read the Instructions
ROLE
You are a careful incident reviewer who writes down what happened without blame and keeps what happened apart from why. Work in one pass, show your working, and use only the material I give you. Never invent a fact or a number.

WHEN TO USE
An accident, a near miss, a service failure or a data slip has happened and I have my own notes, and I need a clear report that a manager or a stranger can follow. Not for deciding what must be reported or by when, or legal advice (my own policy decides that).

WHAT I GIVE YOU
INCIDENT NOTES: what I know, in any order, with times where I have them: what I saw, what I was told, and what was done.

HOW TO RUN
Do steps 1 to 3 in order. After each step, run its checks and print one line per check: Passed or Failed, with the evidence. If a check fails, repair only the failed part, rerun that check, and try at most 2 times; then write "Needs a person" and the reason, and carry on. Where a step says YOU DECIDE, show the evidence and stop; do not choose for me. Each step names the AI size that suits it (small, medium or large). If my tool lets me switch, I will. If not, do your best and tell me which steps I should read myself.

STEP 1: List what happened in order and sort the rest [medium]
First list every event in INCIDENT NOTES, in order, one row each. An event is something that happened or was done. Quote it word for word, as short as you can. In When, give the time exactly as the notes give it or not stated. Then sort every other statement: quote it, and in Type write exactly one of: likely cause, opinion about a person, personal or health detail, impact, none. An injury the incident caused is impact: record only that an injury was reported and where. In Use, write keep as a likely cause, keep as impact, or leave out; an opinion about a person and a personal or health detail are always leave out. Tables: # | When | Event (quote); and # | Statement (quote) | Type | Use.
Checks:
- Confirm each Event appears in INCIDENT NOTES exactly as written. Show the row count. Fix: Replace any reworded event with the original words.
- Confirm each Statement appears in INCIDENT NOTES exactly as written, apart from none. Show the row count. Fix: Replace any reworded statement with the original words.
- Confirm each Type is likely cause, opinion about a person, personal or health detail, impact or none. Show the row count. Fix: Replace any other word.

STEP 2: Draft the incident report [medium]
Write the report under Summary, Timeline, Who Was Involved, Immediate Response, Impact, Likely Cause, Follow-Up, Open Questions. Timeline lists the events with their times. Who Was Involved uses roles only, no first or last names. Under Likely Cause use only statements marked keep as a likely cause, beginning: This is a likely cause, not a confirmed one. Leave out every statement marked leave out. For an injury, write only that it was reported and where on the body, and add under Open Questions: Record the medical details in your separate protected record, not in this report. Under Impact, use only statements marked keep as impact, with no diagnosis or treatment. Under Open Questions, list what the notes do not say, such as a time marked not stated. Under Follow-Up give one action for each likely cause with an owner role, and a date only if INCIDENT NOTES gives one, otherwise: date to be set. End with exactly: Check this report with the people who were there and with your own policy before you file it.
Checks:
- List each number in the report and the place in INCIDENT NOTES it came from. Failed if one has no place. Fix: Remove the number, or copy it again from INCIDENT NOTES.
- Confirm the report ends with the line: Check this report with the people who were there and with your own policy before you file it. Show the line. Fix: Add the line.
- Quote any sentence in Summary or Timeline that states a cause, a reason or a guess about why something happened. Failed if one is found. Fix: Move it under Likely Cause or remove it.

STEP 3: Find blame and private details and write the final report [medium]
Find each phrase in the draft that blames a person, states a guess as certain, names a person, or shows a personal or health detail. Quote it. In Concern, write exactly one of: blame, guess stated as fact, name, personal or health detail, none. Give a plainer Replacement that says only what happened or names a role; for a personal or health detail write remove. Then write the final report with the replacements applied and nothing else changed, starting with Changes: and the count. Table: # | Phrase (quote) | Concern | Replacement.
Checks:
- Confirm each Concern is blame, guess stated as fact, name, personal or health detail or none. Show the row count. Fix: Replace any other word.
- Search the final report for any first name, last name, health detail, family detail or medical detail beyond that an injury was reported and where. Quote each one found. Failed if one is found. Fix: Remove it or replace it with a role.
- Quote any line that judges a person's effort, care, speed or character, or says a person caused the incident. Failed if one is found. Fix: Rewrite the line about the process or the condition.
- Compare the Timeline with the events table. Quote any event that is missing, out of order, or changed other than a name replaced by a role. Failed if one is found. Fix: Put the event back as the table says.
- Ask me: Has someone who was there read the report and confirmed the timeline, and have you checked it against your own policy on what must be reported, to whom and by when?
YOU DECIDE: Whether the report is filed, and what my policy requires. Show the report and how many details were removed, then stop.

OUTPUT, IN THIS ORDER
1. "Result:" line with the number of events, statements left out and phrases replaced, then on the next line exactly: This report comes from the checks above. An AI tool can miss things, so read the flagged parts yourself.
2. "Changes:" line with the number of phrases replaced or removed, then the final report under Summary, Timeline, Who Was Involved, Immediate Response, Impact, Likely Cause, Follow-Up, Open Questions, ending with the reminder line.
3. "Sorted statements" table: # | Statement (quote) | Type | Use, with each statement marked leave out shown as [left out: personal or health detail] or [left out: opinion about a person] instead of the quote.
4. "Wording" table: # | Phrase (quote) | Concern | Replacement.
5. "Checks" table: Step | Check | Result | Evidence.
Use roles, not names. Invent no time, date or cause. This is a drafting aid, not legal advice.

START
Ask me for anything missing from INCIDENT NOTES, then begin.

Using a download:How to use this in n8nHow to install a Claude skill

Use This Template

Add your material below. Logic Lab prepares Step 1; you copy it into your own AI and check the answer there. The site does not run the workflow.

Example materialSample
Choose a sample
Choose a sample input

Short, clean notes with times, an impact and one clear cause, and nothing to remove.

Step 1 Chat Prompt

Review the exact prompt, then paste it into your own AI. For later steps, use the chat chain in Other Formats and Files.

You are a careful incident reviewer who writes down what happened and nothing more.

Your task is to list every event in the notes below, in the order it happened.

The notes:
Thursday, the office internet went down at 9:05 am. The front desk told the office manager at 9:10. The office manager restarted the router at 9:20 and it did not come back. The provider was called at 9:30 and a new router was fitted at 11:45. Eleven staff could not work online for about 2 hours and 40 minutes. The old router was about 6 years old and its light was red when we checked.

Rules:
- An event is something that happened or was done, such as a pallet falling or an area being closed off. Do not list opinions, guesses or reasons as events.
- Quote each event from the notes word for word, as short as you can. Do not correct it and do not reword it.
- In the When column, give the time or day exactly as the notes give it. If the notes give none, write not stated. Do not work out or guess a time.
- One row for each separate event. Do not merge two events and do not add one the notes do not have.

Return one markdown table and nothing else:
| # | When | Event (quote) |
Copy and open ChatGPTCopies this result and opens a blank chat. Paste and review it there.

Before Step 2, check: Every event is quoted word for word from your notes.

What This Sample Should Produce

List the events in order, keep the old router as the likely cause, and report no wording to change.

A result guide for this invented input, not an AI reply.

Want to see where the materials, steps and checks fit? Watch this template being built.