The Near Miss That Wasn't Reported
At a bottling plant, a pallet of full glass bottles (about 600 kg) shifted on a racking beam at 14:20 and fell into an aisle. No one was in the aisle; the only injury was a cut to a cleaner's hand from flying glass. The cleaner reported it to the shift supervisor, who told her it was 'just a near miss, don't bother with the form'. The pallet was restocked by 15:00 and the broken glass swept up. Two weeks later a similar pallet fell in the same bay and struck a forklift driver's leg. The investigation found the racking beam had been struck by a forklift some months earlier and its safety clip was missing. There is no record of the first event, no maintenance request for the beam, and the cleaner has since left the company.
1. Was the supervisor's decision defensible under a typical incident-reporting standard? Explain what should have been reported and why.
Read the worked answer
No, it is not defensible. The event meets the usual test for a reportable incident: an unplanned release of energy (falling load) that could have caused serious injury and did cause a minor injury (the cleaner's cut). Calling it a 'near miss' does not remove the duty to record it - near misses are the highest-value reports precisely because they are free lessons.
What should have been reported:
- The falling pallet, with time, bay, load weight and a description of what was seen.
- The cleaner's injury, however minor - a cut from flying glass is an injury, not a near miss.
- The condition of the racking (beam, clip, damage) as observed at the time.
- Any witness names and the location of the pallet.
Why the label matters: the supervisor's framing converted a reportable event into silence. That is a reporting-culture failure, not a paperwork failure. The correct response to 'don't bother with the form' is that the form exists so the next person does not get hit.
2. The second event has happened. Using the evidence available, carry out a root cause analysis and separate the immediate cause from the underlying causes.
Read the worked answer
Immediate cause: the pallet fell because the beam's safety clip was missing and the beam had been struck, so the beam was not positively located.
Underlying causes (use a simple 5-Why / causal tree):
- Why was the clip missing? Forklift impact some months earlier, not reported.
- Why was the impact not reported? No routine racking inspection and no easy route to report damage.
- Why was the first fall not investigated? Supervisor suppressed the report ('just a near miss').
- Why did suppression work? Reporting is seen as blame-generating; no feedback loop; no consequence for suppressing.
- Why was the beam not repaired? No maintenance request was raised because no report existed.
Root causes (system level):
- No periodic racking inspection regime with a damage-rating scheme.
- Reporting process that depends on a supervisor's discretion.
- No management-of-change or feedback when damage is found.
Note the evidence limits: the cleaner has left, the pallet was restocked and the glass swept, so physical evidence is thin. The investigation should say so rather than over-claim.
3. Design the reporting and racking-inspection changes, and give two leading and two lagging indicators you would track.
Read the worked answer
Reporting changes:
- A single reporting route that any worker can use without a supervisor's permission - a card, an app, or a box - with acknowledgement within 24 hours.
- A written definition of 'reportable' that explicitly includes near misses and minor injuries, so the label cannot be gamed.
- Just-culture rule: honest reporting is never punished; concealment is a disciplinary matter.
- Feedback: every reporter hears what was done, even if the answer is 'no action needed'.
Racking inspection:
- Visual check by trained staff weekly; formal inspection by a competent person at a defined interval (e.g. quarterly) with a damage-rating chart.
- Any missing clip, bent beam or impact damage = bay taken out of service and tagged until repaired.
- Forklift impact reporting made mandatory, with a simple form at the charging bay.
Indicators:
- Leading: number of near-miss reports per 100 workers per month; percentage of reported racking defects closed within the target time.
- Lagging: number of falling-load events; lost-time injuries from falling loads.
A rising near-miss count with a falling injury count is the pattern you want - it means people are reporting before someone is hurt.