BCSP CIT study materials
BCSP CIT study resources

The Refresher Request at the Loading Dock

BCSP CIT · Put your knowledge to work in context.

All case studies

The Refresher Request at the Loading Dock

A regional distribution center has logged 22 powered-industrial-truck near-misses in 11 months, 15 of them at the three loading-dock doors closest to the break room. The site's EHS manager asks you to build a 4-hour 'operator refresher' for all 340 operators, citing the near-misses in the request. Before you agree, you have access to: the near-miss narratives, 14 months of turnover data, the current 2-day certification curriculum, a 6-month-old traffic-flow redesign that added two blind corners, and shift-level supervisor staffing. Operators are certified under an internal program that is not audited. Budget is fixed and the request has executive sponsorship. Two supervisors have already told you 'the new hires just don't care.'

1. What evidence would you gather before accepting or reframing this request, and what would each piece tell you?

Read the worked answer

Separate the request (a refresher course) from the problem (near-misses at the dock). Gather:

  • Coded near-miss narratives by time of day, location, tenure, and behavior. Tells you whether the pattern is person-based (novices everywhere), place-based (three doors), or system-based (shift change).
  • Turnover and certification records matched to incident dates. Tests the 'new hires don't care' claim directly. If the near-miss cohort is not disproportionately new, the story collapses.
  • Traffic-flow redesign documents plus a walk of the two new blind corners. If the environment changed after certification, the gap is obsolete conditions, not absent knowledge.
  • Supervisor staffing by shift. A supervision gap at shift change is a performance-environment factor no course fixes.
  • Direct observation at shift change. What operators actually do, not what the SOP says.

Decision rule to state in writing: if near-misses cluster by place and time regardless of tenure, training is not the intervention. If they cluster by tenure, a knowledge or skill deficiency is plausible and a refresher may be part of the fix.

2. The narratives show 19 of 22 near-misses occurred in the 20 minutes after shift change. What does that pattern suggest, and how does it change your recommendation?

Read the worked answer

A fixed 20-minute window that ignores who is driving is a system signal, not a person signal. Near-misses don't respect individual competence.

Likely concurrent conditions: dock congestion at handoff, forklifts and pedestrians sharing an aisle, incomplete shift-to-shift communication, supervisors tied up in handoff meetings.

Recommendation changes from a 4-hour refresher to:

  1. A short shift-change traffic protocol - 15-20 minutes, delivered in the first week.
  2. Engineering controls at the three doors: physical separation or markings, staggered break release.
  3. Supervisory presence at handoff, scheduled rather than hoped for.
  4. Measurement: near-misses inside the 20-minute window versus a comparison window, tracked for 90 days.

Before you commit to the pattern, check one rival explanation: whether a reporting campaign launched partway through the 11 months concentrated the counts. Pull near-miss reports by month. If reporting volume jumped in one month and the proportion in the window did not, the pattern is an artifact of reporting, not a change in the floor.

3. The executive sponsor has already announced the refresher to the site. How do you proceed?

Read the worked answer

Do not fight the announcement in public. Reframe in private, in writing, with the sponsor's own data.

  1. Request 20 minutes with the coded narratives and the 19-of-22 chart. Sponsors respond to their site's data far better than to a rationale about training theory.
  2. Offer a version of their request that preserves the visible commitment: a short shift-change protocol session for all 340 operators on the original timeline, plus the engineering fixes. Something visible happens; the announcement survives.
  3. Name the risk of the full refresher plainly: it consumes the fixed budget, frames near-misses as an operator-attitude problem, and if the real cause is congestion at shift change, the near-misses continue and both your credibility and the sponsor's take the hit.
  4. Document the recommendation and the decision either way. You are accountable for the analysis, not for the sponsor's call.
  5. If overruled, build the refresher so it also generates evidence - a pre/post check on the shift-change protocol - and set a 90-day checkpoint with the sponsor in advance.