Write a workplace incident report
Writes a factual, blame-neutral report of a workplace accident, near miss, customer, property or security incident, separating observed facts from statements and listing actions with owners.
A workplace incident report is a record that other people act on: a supervisor fixes the hazard, HR supports the people involved, facilities repairs the damage, an insurer or regulator may read it months later. It is useful only if it is accurate, dated, and written so that a reader who was not there can see what happened without being told whom to blame. The common failures are mixing opinion into facts ("he was being careless"), guessing at causes before anyone has looked, leaving out times and locations, recording more personal or medical detail than the reader needs, and listing actions with no owner.
Write as an experienced health and safety or operations coordinator would: neutral, specific, in the past tense, with every statement either observed, reported by a named role, or marked as unknown.
Write a incident report for from these notes:
- If the notes do not say what happened, or give no indication of when or where, ask for those details in one short message and stop.
- Check for urgency first. If the notes suggest someone may still be at risk, a hazard is still in place, a person needs medical attention, or a crime may be in progress, say so at the top under Urgent checks before anything else.
- Sort every statement in the notes into one of three kinds and keep them apart in the report:
- observed: seen or measured directly by the person reporting;
- reported: told to the reporter by someone else, attributed by role ("the shift lead said…");
- inferred: someone's opinion or guess about cause. Move these to "Possible contributing factors (to be confirmed)" and word them as questions for the investigation, never as findings.
- Rewrite blaming, emotional or judgemental language into neutral description of actions and conditions ("the floor was wet near bay 4; no sign was in place" instead of "the cleaner left it soaking wet as usual"). Record every change under Language changes.
- Identify people by role or initials unless the audience needs full names, and record only the injury or health information the reader needs (body part, nature as described, first aid given, whether the person went to hospital). Do not diagnose or speculate about medical outcomes.
- Propose immediate and follow-up actions that follow from the facts (make the area safe, preserve evidence, check similar equipment, support the person, review the procedure). Give each an owner and date if the notes supply them; otherwise use
[need: owner]and[need: date]. - Under Notifications, list who has been told and when, and flag whether this type of incident may have to be reported to an external body (for example a workplace safety regulator, insurer, data protection authority or the police) so the reader can check the rules that apply. Do not state that it is or is not reportable.
- Use only the facts in the notes. Never invent times, names, witnesses, measurements, injuries or quotes; use
[need: …]. - No conclusions about fault, negligence, liability or disciplinary outcomes, even if the notes ask for them. A report that blames is less credible and can harm the people involved.
- Keep exact quotes only when they matter to what happened, attributed by role and in quotation marks.
- Use 24-hour or clearly marked times and a full date if given.
- Keep the report under about 600 words; a reader should grasp what happened from the Summary alone.
Urgent checks
Anything that needs action before the report is filed, or "None identified".
Incident report
- Summary: two or three sentences: what happened, when, where, outcome.
- Details: table with Date and time · Location · Incident type · People involved (role) · Reported by · Report date.
- What happened: numbered, chronological, factual steps, each marked (observed) or (reported by …).
- Injuries, damage or loss: as described, or "None reported".
- Immediate actions taken: what was done, by whom, when.
- Witnesses: role and a one-line summary of what each saw.
- Possible contributing factors (to be confirmed): conditions and questions for the investigation.
- Actions: table with Action · Owner · Due date · Status.
- Notifications: who has been told, and external reporting to check.
Language changes
Bullets: original wording → neutral wording, with the reason. "None" if none.
Missing information
Bullets: each [need: …], with why it matters. "None" if complete.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- Business writing
- level
- Beginner
- depth
- Specific
- made for
- People manager, Operations, Anyone, personal use
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install write-workplace-incident-report --target claude-codenpx skills add hermes-hq/hodios-dist --skill write-workplace-incident-report -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-writing-communication@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Business writingWrite an escalation email
Writes an escalation to a manager, vendor or another team that states the issue, its impact, what was already tried and the specific decision or help needed by a date, without blame.
write-escalation-emailRun a five-whys analysis
Runs a five-whys and fishbone root-cause analysis on a repeated operational problem, separating evidence from guesses, and ends with countermeasures and owners. Use after recurring failures.
run-five-whysWrite a site visit report
Turns field or site visit notes into a structured report with observations, evidence, issues rated by severity and owned follow-ups. For consultants, inspectors, auditors and area managers.
write-site-visit-reportWrite a work document
Drafts a memo, report, proposal, update or announcement from your notes, picking the right type for the reader and leading with the point and the ask. Use when you need to write something at work.
write-work-documentWrite an award nomination
Writes an award or recognition nomination that maps a colleague's specific achievements and evidence to each published criterion, within the word limit, and shows where the case is weak.
write-award-nominationWrite a formal letter
Writes a formal letter to a bank, council, school, supplier or official body in the layout and conventions of the chosen country, with a clear purpose, references and a specific request.
write-formal-letter