ModulesIncident ReportingReport & Learn
Report it while it is fresh.The facts as reported, and every decision made after them.
For the person who saw it and the responder who owns it: close a report with no action, review it first, or start an investigation. The facts stay as they were sent.
- Sent
- 21 Oct 2026, 10:41
- Reporter
- Tomás Ortega
- Where
- Loading bay 3 · Harbour site
- When
- 21 Oct 2026, 10:35
- What happened
- During tanker unloading the hose coupling at bay 3 came apart. Sodium hypochlorite sprayed onto the bay. I had a splash on my left forearm and used the safety shower.
- Photos
- 2
An example report; the fields are the product’s, the values illustrative.
Where it connects
On the same loop: Concern Reporting, Chemical Management, Absence & Return to Work and 38 more modules in one workspace.
Method note
Investigate every incident, or only some? Both rules have a cost.
Investigating everything spreads the team thin. Investigating by outcome misses the near miss that could have killed someone.
Leandro · Founder, UProcess
HSE’s guidance sets the depth of an investigation by the worst credible outcome and the chance of it happening again, not by what actually happened. Many sites still run a rule that every recordable gets a full investigation, because a fixed rule is easy to audit.
So the responder decides per report, and the reason is kept.
- Close with no actionRecorded in the report’s status history, with who closed it and when.
- Start reviewCase details and classification first. Investigate later if the facts call for it.
- Start investigationIt opens with the report at the top. One investigation per report.
Where Incident Reporting usually breaks
Four places an incident report goes wrong, and what the record does about each.
The form puts people off reporting.
US recordkeeping rules treat a reporting procedure as unreasonable if it would deter a reasonable employee from reporting accurately. Long or punitive reporting does exactly that.
Source: 29 CFR 1904.35(b)(1)(i)
In UProcess The report asks what happened, where and when, in the reporter’s words, with photos. Severity, causes and classification come later, from the responder.
Report an incident
- What happened?
- The hose coupling came apart during unloading.
- Where?
- Loading bay 3
- When?
- 21 Oct, 10:35
- Photos
- 2
Severity, causes and classification come from the responder, later.
Reports pile up with no decision.
At Texas City, the CSB found the refinery had investigated only three of eight earlier releases from the same blowdown system before the 2005 explosion.
Source: U.S. Chemical Safety Board
In UProcess Each report has a responder and a status: under review, an investigation started from it, or closed with no action. Every step goes into the status history.
IR-2026-0091 · responder Grace Okafor
Process safety events are counted as injuries.
A Safety Science paper on Texas City and Longford shows sites with good injury rates while loss-of-containment events climbed. Injury statistics do not measure major hazards.
Source: Hopkins, Safety Science 47 (2009)
In UProcess Classification has separate parts for people, process safety and the environment. A release can name the product, with its safety data sheet revision, from Chemical Management.
Classification · IR-2026-0091
- People
- First aid · Visible to permitted readers
- Process safety
- Loss of containment · 40 L
- Environment
- Sodium hypochlorite 12% · SDS rev 4
Three parts, three questions. One event can count in all of them.
The story is rewritten once blame enters.
HSE’s investigation guide warns against assigning blame before the investigation is complete, because it costs the cooperation of the people who know what happened.
Source: HSE, HSG245
In UProcess Once sent, the facts as reported cannot be edited. The responder’s case details and classification sit beside them, not over them.
IR-2026-0091
- As reported · locked
- “The hose coupling at bay 3 came apart …”
- Sent
- 21 Oct 2026, 10:41 · Tomás Ortega
- Case details · responder
- Coupling CPL-305, cam arms found unpinned
- Added
- 21 Oct 2026, 13:30 · Grace Okafor
Two voices, side by side.
Report IR-2026-0091Area Loading bay 3 · Harbour site
| When | Step | By | Note |
|---|---|---|---|
| 21 Oct, 10:41 | Sent | Tomás Ortega | 2 photos |
| 21 Oct, 10:52 | Responded | Grace Okafor | Bay closed, area washed down |
| 21 Oct, 13:30 | Case details completed | Grace Okafor | Equipment, activity, contractor |
| 21 Oct, 13:45 | Classified | Grace Okafor | People part restricted |
| 21 Oct, 14:02 | Investigation started | Grace Okafor | INV-2026-014 |
The record an auditor asks for.
The first account matters most when the event is reviewed a year later.
- The report exactly as it was sent, with its photos.
- Who responded, and what they decided.
- The classification, with the people part readable only by those allowed.
- The investigation it started, or when it was closed with no action.
What’s in a report
- Report
- What happened, where and when, with photos. Kept as sent.
- Responder
- Under review, start an investigation, or close with no action. Each step is in the status history.
- Case details
- Equipment, activity, contractor company and damage, completed by the responder.
- Classification
- People, process safety and environment. The people part is restricted to those allowed to read it.
- Links
- To an investigation, to the chemical product released, and to an absence record.
Questions
Can the reporter correct a report after sending it?
The facts are kept as sent. The responder records what changed in the case details, so both versions stand.
Who can read injury details?
Only members allowed to read the people part of the classification.
Does every report need an investigation?
No. The responder can close it with no action, or review it first.
Was a contractor involved?
The responder names the contractor company in the case details, and the report appears on that company’s contracts in Contractor Management.