A useful incident report preserves the difference. Record what you observed, attribute what others told you, and leave unresolved details open. The next reviewer needs an account they can follow without guessing where each statement came from.
The fictional example below turns a blame-heavy account into a factual report. It includes a complete narrative, a source map, and a blank working version.
Gather the supplied facts before writing
This training scenario takes place on November 3 in Room 2 of a community workshop. Times use America/New_York. R1 and W1 are training identifiers; the example omits real names and contact details.
| Time | Supplied information | Source or status |
|---|---|---|
| 14:05 | R1 sees a display board lying on the floor beside the easels | R1's direct observation; R1 did not see the board fall |
| 14:07 | W1 says, “I saw a cart touch the left leg” | Statement attributed to W1 |
| 14:08 | The facilitator pauses setup and moves participants to the adjacent designated waiting area | Recorded action in this fictional scenario |
| 14:20 | R1 writes the report | Report time, separate from observation and event times |
The packet also includes photo reference A3, which shows the board's position after the fall, and R1's observation of a small dent in a frame corner. The actual fall time, cause, and injury information have not been supplied.
Harper College's documentation guidance emphasizes specific event details, observable behavior and impact, responses, and avoiding speculative labels. Those principles help keep this example reviewable. Read its tips for documenting incidents.
Replace the conclusion with an attributed account
An unsupported version might read:
A reckless volunteer hit the display with a cart and caused it to fall. Nobody was injured.
The supplied facts do not identify a reckless action, establish the cause, or support the injury statement. A more useful narrative reads:
On November 3 at 14:05 America/New_York, I observed a display board lying on the floor beside the easels in Room 2. I did not see it fall. I observed a small dent in one frame corner. At 14:07, W1 told me, “I saw a cart touch the left leg.” At 14:08, the facilitator paused setup and moved participants to the adjacent designated waiting area. Photo reference A3 shows the board's position after the fall. It does not show how the board fell. The time of the fall and its cause remain unconfirmed. Injury information was not supplied in this training packet. I prepared this report at 14:20.
That account gives a reviewer several things to follow up. It does not require the reporter to settle them in advance.
The facilitator's action belongs in the record because it happened in the scenario. It is not a general instruction for handling other incidents; actual responses depend on the situation and the organization's procedures.
Keep event time and report time separate
In this example, 14:05 is when R1 first observed the board on the floor. It is not the established time of the fall. The report was written at 14:20.
Use separate fields for the event time, the first observation time, and the report time when those differ. An unknown value should remain visibly unknown. Copying the first observation time into an “incident occurred” field would make the record more precise than the evidence allows.
Apply the same care to attachments. A3 supports a statement about the board's later position. It cannot establish the sequence before the photo was taken. Write what an attachment shows and identify any limit that matters to the account.
Review the report by statement type
In the working example, select a statement to see whether it is a direct observation, a witness account, an immediate action, or an unresolved detail. Compare the unsupported version with the attributed narrative and check which claims were removed or qualified.
The narrative preview uses the fixed training facts. The separate blank report lets you enter a date, location, observations, attributed accounts, actions, attachment references, and follow-up questions. Missing date or location produces a visible reminder rather than a fabricated value. Your typing stays in place while you review the form.
For a real report, use the organization's designated reporting channel and handle identifying details there. The public example is a training worksheet; it does not file a report, notify anyone, or decide fault.
Copy this prompt to create the worksheet
Create a complete self-contained HTML incident-report training worksheet.
My sanitized training context: [location/event]. Supplied observations:
[details with time/source]. Attributed accounts: [details]. Actions:
[details]. Unresolved information: [gaps]. Do not infer missing facts.
Include a separate clearly fictional community-workshop case. On
November 3 at 14:05 America/New_York R1 sees a display board on the
floor beside easels in Room 2; R1 did not see it fall. R1 observes a
small dent in a frame corner. At 14:07 W1 says “I saw a cart touch
the left leg.” At 14:08 the facilitator pauses setup and moves people
to the adjacent designated waiting area. This is a recorded scenario
action, not general safety advice. Report written at 14:20. A3 photo
reference shows the board after the fall, not its cause. Actual fall
time, cause, and injury information remain unknown. No real identities.
Show unsupported blame-heavy wording beside an attributed factual
narrative built only from those fixed facts. Allow statement-type
inspection: observation, witness account, action, or unresolved detail.
Distinguish event, first-observation, and report times. The narrative
preview uses fixed training facts; keep a separate blank report with
date, location, observation, witness, action, attachment, and question
fields. Name missing date/location in visible feedback, preserve typed
entries through validation, and confirm before reset. No filing,
notifications, diagnosis, disciplinary decisions, or legal claims.
Explain real reports use the organization's designated channel.
Use labeled keyboard-accessible controls, visible focus, system fonts
at least 16px, and readable 360px layout without horizontal scrolling.
Put CSS/JavaScript inline, load no dependencies, return complete HTML.
Improve the training wording before reuse
When reviewing the worksheet in NOS, look for a heading such as “What happened?” that might encourage a learner to fill gaps with an explanation. Directly revise that static heading to “What did you observe, and what was reported to you?” A small wording change gives the next person a clearer starting point while keeping the underlying reporting task intact.