Reporting has to cost less than staying quiet
Four facts about the form, not four promises. Every one of them exists because a programme dies at the point where filing a report is more effort than walking past.
The whole form, every field of it, and the record it becomes. Hover a card to light that control on the screen — or hover the screenshots themselves to magnify them, and click to open one full size.
Filing it, in under a minute
What it becomes
Screenshots from a working build. Illustrative records.
Under a minute, one hand
Photo, category, what could have happened. On a cheap Android, on a weak signal, without going to find a laptop.
No blame surface
The form captures the condition, not a culprit. There is no field for whose fault it was, because that field is what empties a register.
The exact area, not the site
Locations resolve to Warehouse A, Aisle 4 rather than “Houston Plant”. A pattern you cannot locate is a pattern you cannot fix.
The reporter sees it close
They are told what happened to their report. Nothing kills a programme faster than reports disappearing into a void.
Rank by what could have happened, not what did
Every report gets a potential severity and a likelihood. The product multiplies them into a score, and the score decides whose week it belongs in.
All 48 reports, by what could have happened
Potential severity down, likelihood across. Shading is severity × likelihood.
| Potential | Rare | Unlikely | Possible | Likely | Almost certain |
|---|---|---|---|---|---|
| Critical | 0score 5 | 2score 10 | 3score 15 | 0score 20 | 0score 25 |
| High | 0score 4 | 0score 8 | 7score 12 | 2score 16 | 0score 20 |
| Medium | 0score 3 | 3score 6 | 15score 9 | 11score 12 | 0score 15 |
| Low | 0score 2 | 0score 4 | 3score 6 | 2score 8 | 0score 10 |
A near miss and a fatality can be the same event with a different ending. The conveyor jam above hurt nobody; the same reach with the drive running is an amputation. Ranking by potential puts the five critical reports in front of the plant director this week, instead of after the event that proves the point.
Severity × likelihood
Each report carries both. The product multiplies them and prints the result on the record — Medium × Possible gives a score of 6. Nothing about the ranking is a matter of opinion once the two fields are set.
The scale is yours
Four severities by five likelihoods here. If your matrix is 5×5, or your labels differ, that is configuration an administrator changes — and the scores recalculate against your model, not ours.
The score sets the queue
A manager works down from the top-right corner. The five critical reports get looked at this week, rather than after the event that proves they mattered.
A report nobody acts on trains people to stop reporting
The second report is filed on the strength of what happened to the first one. This is the whole retention mechanism of a near-miss programme.
- 01
Reported
From the floor, on a phone, in under a minute.
- 02
Ranked by potential
Severity × likelihood gives a score, and the score sets the queue.
- 03
Immediate action recorded
What was done on the spot, captured while it is still true.
- 04
Corrective action raised
An owner and a due date, against the hierarchy of controls.
- 05
Chased automatically
Overdue actions escalate on their own. Nobody has to remember.
- 06
Closed and verified
Verified effective before the record closes.
- 07
Briefed at the toolbox talk
And the reporter is told what happened to their report.
Grouped by state, so the two still open are the first thing anyone sees — including the person who filed them.