thinkhard.SI

Prompt repository Operations

Write up a workplace safety incident or near miss

Someone was hurt or nearly hurt at work, and you need a factual first report built from the notes and witness accounts that blames no one.

Registry no.
OPS-038
Collection
Operations
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
7
Added

OperationsAny chat

The prompt

Score 10 of 10, Excellent

Use it when Someone was hurt or nearly hurt at work, and you need a factual first report built from the notes and witness accounts that blames no one.

  • {{recipient}}
  • {{reporting_system}}
  • {{event_type}}
  • {{incident_notes}}
  • {{witness_accounts}}
  • {{form_fields}}
  • {{reporting_rules}}
Full prompt and why it works
Prompt
Write an incident report from the notes below, for {{recipient}} to review and file in {{reporting_system}}. The first report is what any investigation, insurance claim or report to an authority starts from, so it has to record the facts while they are fresh, keep what people saw apart from what they assume, and blame no one, so that the people involved keep reporting honestly.

Type of event as first reported (injury, near miss, property damage, dangerous occurrence): {{event_type}}

Notes from the person reporting:
"""
{{incident_notes}}
"""

Witness accounts, each kept separate:
"""
{{witness_accounts}}
"""

Fields our report form requires: {{form_fields}}

Use these headings:
1. Summary: two sentences on what happened and the outcome.
2. When and where: date, time, exact location, and the task or activity under way.
3. People involved: by role and type (employee, contractor, visitor), for example "forklift operator" or "Witness 1". Names belong in the form's own fields, not in this narrative.
4. What happened: a numbered sequence in the past tense, one observed action or event per line, each ending with its source in brackets.
5. Injuries and damage: only as reported, such as the body part, what was seen, first aid given and whether anyone went to a hospital. Do not describe how serious an injury is beyond what the notes say.
6. Immediate actions: how the area was made safe, equipment stopped or isolated, who was told and when.
7. Conditions at the time: lighting, weather, floor, equipment and protective equipment worn, only where the notes mention them.
8. Evidence to keep: photos, video, equipment, tags and documents that should be preserved.
9. Open questions.

Keep the narrative under 400 words and the whole report under 600.

A good report lets someone who was not there picture exactly what happened, with every statement traceable to a source. "Witness 2 (picker) says the top carton fell as the truck turned into the aisle" records an observation; "The driver was going too fast" is an opinion and does not belong. That pair shows the form only.

Do not give a cause, a root cause or an opinion on who was at fault, and leave out words like "careless", "failed to" or "should have", because a report that reads as blame stops people reporting near misses. Do not add times, distances or details the notes do not contain.

If the accounts disagree, record each version with its source instead of choosing one. If a required form field is not in the notes, write [CHECK: field] in its place. If the event could be one that must be reported to an authority under {{reporting_rules}}, add a first line "FOR THE SAFETY LEAD: check whether this must be reported, and by when."

Variables

{{recipient}}
Who reviews the report, for example "the site safety lead".
{{reporting_system}}
Where it is filed, for example "the incident log in our safety system".
{{event_type}}
What kind of event it was as first reported, for example "near miss" or "injury, first aid only".
{{incident_notes}}
The reporting person's notes, a voice note transcript or the supervisor's account, pasted as written.
{{witness_accounts}}
Each witness's account, labeled Witness 1, Witness 2 and so on. Write "none" if there were no witnesses.
{{form_fields}}
The fields your incident form requires, for example "date, time, location, injury type, body part, first aid given, reported to".
{{reporting_rules}}
The rules on reporting incidents to an authority that apply to you, as you understand them, or "not known".

Why it works

  • What to avoid. No cause or fault is assigned and words like "careless" are left out, because a first report that reads as blame is the fastest way to stop near misses being reported.
  • If unsure. Conflicting accounts are kept side by side with their sources, and a possible duty to report goes to the safety lead before the report is filed.
  • An example. A paired example shows the difference between an observation with its source and an opinion, which is the line the whole report depends on.

How to use it

  1. Press Fill in blanks and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.
Use it from code

Get this prompt as JSON from the free REST API, with your own text in the blanks, or let an AI assistant fetch it through the MCP server. No key.

curl -s https://thinkhard.si/api/v1/prompts/safety-incident-report

With the MCP server added to Claude, ChatGPT, Cursor or VS Code, call get_prompt with {"prompt": "safety-incident-report"}, or just ask for it by name.