“Zero accidents” is one of the most common slogans in industrial safety, and one of the most misused. In its useful form, a zero accident culture is a measurement system that drives reporting, observation, and continuous improvement. In its harmful form, it is a target that drives under-reporting, because nobody wants to be the one who breaks the streak. This post explains how to build the useful version, how to avoid the harmful version, and what the fork between them looks like in a forklift operation. It sells none of these systems.
What a zero accident culture actually is
A zero accident culture is not the absence of incidents, and it is not a number on a board. It is a set of expectations: that workers report hazards and near misses without fear, that supervisors observe operations and correct behavior in the moment, that every report gets a response, and that management reviews the data regularly. The goal of zero is the aspiration that makes the expectations coherent. The measurement system is what makes them real.
The fork: goal versus suppression
The failure mode is well documented. When a zero target is attached to incentives, or to a public streak counter, the rational response is to stop reporting. A worker who nearly caused an incident keeps quiet, a supervisor reclassifies a recordable as a minor event, and the numbers look better while the risk stays. The fork is visible in the data: a program with high near-miss reporting and a rising inspection count is working, even if its zero counter has reset. A program with zero reported near misses in a forklift operation is almost certainly not working, because the events happen. This site’s dataset of 5,154 forklift-involved severe injury reports for 2015-2025 shows that struck-by and caught-between events, which dominate the serious-injury patterns, are preceded by near-miss versions of the same mechanisms.
Leading indicators are the engine
A zero accident culture is run on leading indicators: near-miss reports logged, safety observations completed, pre-shift inspections finished, corrective actions closed within their due date, training sessions delivered. These are activities, and they can be acted on this week. Lagging indicators, recordable rates, lost-time incidents, and days away from work, tell you whether the leading indicators are working, but they arrive too late to drive behavior. The accident statistics guide on this site frames the same distinction with the site’s own data.
How leadership sustains the culture
A zero accident culture is sustained by leadership behavior, not by posters. The behaviors that matter are: management attends the weekly safety review and acts on its output, so the meeting is a decision point rather than a ritual; management responds to every reported near miss, so the reporting channel has visible consequences; management treats safety metrics with the same seriousness as production numbers, so the competing pressures resolve in favor of the rules; and management resists the temptation to celebrate the zero counter, because the counter rewards silence. The telematics data layer supports the leadership side by making the event stream visible to everyone, and the safety rules guide structures the weekly review. The culture is the sum of these behaviors repeated until they are the default.
What it looks like in a forklift operation
In practice, the culture shows up in specific behaviors. Operators complete the daily inspection and report defects, which the inspection checklist guide covers in detail. Near misses on the floor, a pedestrian stepping into an aisle, a load shifting, are logged and reviewed rather than ignored, which is where proximity detection and telematics help by logging events automatically. Supervisors hold short weekly reviews of the alarm log and the report log, which the safety rules guide structures. And management reviews the leading indicators monthly, with the same seriousness as the production numbers.
The starting point is to score the operation and build the measurement around it. Run the Risk Scorer to see where your exposure sits, compare the control families on the systems index, and when you are ready for vendor numbers, send your scope through the quote form. The methodology page documents how the scorer derives its inputs, and your state’s injury series shows the local context.
