Nursing Incident Report
An incident report is read later by people who were not there: a manager, a patient safety team, sometimes a regulator or a court. Reports go wrong when they speculate, assign blame, or leave out the times. This skill writes what was seen, done and said, in order, and keeps analysis in a separate section. It helps with wording. It does not replace the organisation's reporting system or duty-of-candour process.
What This Skill Produces
- A factual narrative in the first person and past tense
- A timeline with times as recorded, and "approximately" where the time is estimated
- Immediate actions taken and the patient's condition afterwards
- Notifications: who was told, when, and what they advised
- A separate, clearly labelled list of possible contributing factors for the reviewer
- The fields most incident forms require, ready to paste
Required Inputs
Ask for these if not provided. Never guess a time, a dose or a name.
- Type of incident: fall, medication, pressure injury, equipment, aggression, near miss, other
- Date, time and exact location
- Who was involved (roles, not names, unless the form requires names) and who witnessed it
- What the reporter saw and did, in order
- The patient's condition before and after, including observations taken
- Who was informed: nurse in charge, doctor, patient, family, and the times
- Anything already done to prevent a repeat on the shift
Framework: Facts First, Analysis Apart
- Write only what was seen, heard or done. "I found the patient sitting on the floor beside the bed" and not "the patient fell out of bed".
- Quote where it matters. The patient's own words go in quotation marks.
- Time everything. Use the 24-hour clock and say when a time is estimated.
- State harm objectively. Injuries observed, observations taken, treatment given. Use the organisation's harm grading if supplied.
- Record notifications and candour. Who was told and when, including the patient and family.
- Separate contributing factors. Staffing, equipment, environment, communication, task design. List them as observations for the reviewer, not conclusions.
- Leave out blame, apology wording that admits liability beyond policy, and guesses about cause.
Output Format
Incident report draft
Type: [type] | Date and time: [dd/mm/yyyy, hh:mm] | Location: [ward, bay, bed]
Reported by: [role] | Witnesses: [roles or none]
What happened
[Factual narrative, first person, past tense, in time order.]
Timeline
Patient's condition and immediate actions
- Before: [as known]
- After: [observations, injuries seen, treatment given]
- Actions: [what was done]
Notifications
For the reviewer: possible contributing factors (not conclusions)
Assumptions and gaps
- [Times or details that were estimated or not supplied]
- [Information the reviewer will need that is missing]
Check against the clinical record before submitting through the official system.
Quality Checks
Anti-Patterns
- Do not assign blame to a colleague, the patient or yourself.
- Do not speculate about cause in the narrative.
- Do not write "patient found on floor, no injury" without the checks that support it.
- Do not alter times to make the sequence tidier.
- Do not treat this draft as the report. It is filed through the official system by the person who was there.
Example Trigger Phrases
- "Help me write up a fall I found at 03:10. Here is what happened."
- "I gave a dose late. Word the incident form factually."
- "Write a near-miss report: wrong patient label caught before giving."
- "Take the blame language out of this incident report."
Run this skill in your browser: https://mohitagw15856.github.io/pm-claude-skills/skill/nursing-incident-report.html