The fastest way to lose trust is to investigate, write a report, and change nothing meaningful. One of the fastest ways to improve is to treat incidents and near misses as signals of control weakness—then strengthen the control stack in a way that holds up in busy operations.
This approach keeps the focus on exposure, control performance, and sustainability (not blame). It’s designed to help you identify actions that still make sense through congestion, changing layouts, and mixed experience levels.
Where improvements stall (examples by industry)
Warehousing / Distribution Centres
Near misses are common, but improvements often stall when conditions change faster than controls.
Common stall points to plan for:
- Dock peaks and cross-aisle congestion (the “normal day” overwhelms admin controls)
- Layout drift from overflow storage or seasonal changes (routes shift, but markings/rules don’t)
- High turnover and labour hire (learnings don’t reach the next shift/week)
- Fixes that rely on perfect behaviour (compliance drops under time pressure)
Manufacturing
Investigations often identify the right issue, but actions don’t always stick through changeovers, maintenance activity, and non-routine work.
Common stall points to plan for:
- Temporary traffic changes during downtime/changeover (controls aren’t updated or communicated)
- Contractor movements and unfamiliarity with local rules (exposure increases outside “standard work”)
- Degraded visual controls (line marking/signage) accepted as normal until the next near miss
- Improvements owned by “Safety” only (Ops/Engineering ownership isn’t clear, so changes don’t sustain)
This article is general information only. It is not legal advice or safety consulting. Always align decisions to your workplace risk management process and traffic management controls.
Step 1. Reconstruct the exposure scenario (not just the story)
A useful starting point is capturing the details that matter for traffic risk:
- location (dock/intersection/aisle end)
- movement type (reversing, turning, crossing)
- congestion level and time pressure
- visibility constraints (racking, blind spots, lighting)
- who was present (new starter, contractor, pedestrian route)
- what controls were in place (separation, markings, right-of-way rules, supervision)
Outcome: a clear “this is the scenario we need to control.”
Step 2. Identify the control gap (what failed, drifted, or wasn’t there)
Common gap types include:
- separation not practicable in that moment due to congestion or layout drift
- unclear right-of-way or conflicting rules
- signage/line marking degraded or ignored
- supervision coverage varies by shift
- training didn’t match real workflow
- a control existed but wasn’t reliable (maintenance, configuration, poor placement)
Keep it factual: focus on conditions and control performance, not blame.
Step 3. Strengthen the control stack (prioritise what holds up over time)
A hierarchy-of-controls mindset can help you pressure-test options:
- Can layout/flow be improved to reduce interactions?
- Can separation be increased, or boundaries “hardened”, at the interaction point?
- Which administrative controls may need tightening (rules, supervision, contractor management)?
- If detection/alerting is part of the site approach, what needs adjusting so it supports behaviour without creating noise?
When documenting actions, specificity helps with follow-through:
- “Refresh line marking” is vague.
- More specific: “Re-mark pedestrian crossing at Dock 3, add physical delineation for last 10m, and update right-of-way signage.”
Step 4. Assign ownership and timeframes (or it won’t stick)
For each action, it helps to capture:
- owner (e.g. Ops, Safety, Maintenance, Engineering)
- due date (or review date if it’s staged)
- verification method (walk-through, observation, data check, photo record)
- what “effective” looks like in practice
If an action has no owner, it’s usually a sign it needs to be clarified, resourced, or re-scoped.
Step 5. Verify effectiveness in real operations (not on quiet days)
Prompts to guide verification:
- Did the interaction frequency reduce?
- Did compliance improve during peak congestion?
- Did new workarounds appear?
- Did the control create any unintended risk?
If effectiveness depends on perfect behaviour, that’s often a sign a stronger control (or a better combination) is needed.
Step 6. Close the loop: update training, rules, and change control
Once you’ve learned something real, it’s worth “baking it in”:
- update induction and toolbox talk content
- refresh supervisor observation points
- update the traffic management plan and any local rules
- record any configuration changes (if technology settings were adjusted)
The credibility test
A strong program can answer:
- “What did we change?”
- “Who owns it?”
- “How do we know it’s working?”
- “How will we keep it working when the site changes?”
Sources
- Safe Work Australia – Managing risks: https://www.safeworkaustralia.gov.au/safety-topic/managing-health-and-safety/identify-assess-and-control-hazards/managing-risks
- Safe Work Australia – Code of Practice: How to manage WHS risks (PDF): https://www.safeworkaustralia.gov.au/system/files/documents/1901/code_of_practice_-_how_to_manage_work_health_and_safety_risks_1.pdf
- Safe Work Australia – Traffic management guide: warehousing (PDF): https://www.safeworkaustralia.gov.au/system/files/documents/1703/traffic-management-guide-warehousing.pdf
- OSHA – Incident Investigation: https://www.osha.gov/safety-management/accident-investigation
- OSHA – Hazard Prevention and Control: http://www.osha.gov/safety-management/hazard-prevention
