The zero incident process is the data-driven version of the zero accident goal: the pursuit of zero serious incidents, organized as a measurable process rather than a slogan. The process rests on the PSIF distinction that this site covers: the incident count is the lagging measure, and the precursor stream is the leading measure that the process actually manages. This post is the process: the measures, the reviews, and the loop that pursues zero.
The two measures
The process runs on two measure families. The lagging measures, the recordable injuries and the serious events, are the outcome, and they are too rare and too late to manage by. The leading measures are the process’s real instrument: the near-miss rate, the PSIF rate, the at-risk behavior rate, the inspection completion rate, the training currency, and the speed compliance. The leading vs lagging post on this site sorts the two families, and the KPI post gives the full list.
The data layer
The process runs on the data layer that this site covers: the telematics log, the incident platform, the observation log, and the Risk Scorer that scores the exposure from the data. The process requires the data to be complete and honest, which is the reporting culture requirement: the floor that reports freely gives the process the precursor stream it needs, and the floor that hides gives the process nothing to manage.
The review loop
The process is a loop, not a report. The weekly review reads the leading measures and the precursor log, and assigns the owners and the fixes. The monthly review reads the trends and the corrective action closure. The quarterly review rescores the exposure and re-runs the SIF review. Each review closes with the named owners and the written outcomes that the safety culture on this site requires, and the loop turns the data into the fixes that lower the next review’s numbers.
The honest frame
The process is honest about what zero means. Zero is the target for the serious events, the SIF and the PSIF outcomes, and the process manages toward it by driving the precursor rate down and holding it there. The process does not pretend that all incidents are eliminated; it sorts the low-potential events into the routine stream and concentrates the deep review on the high-potential ones. The honesty is what keeps the reporting culture alive, because the floor that sees the process respond to the high-potential precursor trusts the process, and the trust is the engine.
The result
The process in one page
The zero incident process fits on one page, and the one-page version is worth writing down. The goal: zero serious injuries and fatalities, the SIF target. The measures: the leading indicators, the near-miss and PSIF rates, the inspection completion, the training currency, and the speed events. The reviews: the weekly and the monthly slots with the named owners and the written outcomes. The tools: the Risk Scorer, the incident platform, and the data layer. And the rhythm: the quarterly rescore and the SIF review that keep the exposure current. The one-page process is the zero accident culture made operational, and the page is what the management review reads. The process that is written down is the process that runs.
The zero incident process is the zero accident culture made operational: the same goal, run on leading measures, a data layer, and a review loop instead of a poster. The operation that runs the loop quarterly, with the Risk Scorer rescoring the exposure and the precursor rate falling, is the operation that can say it is pursuing zero with a process rather than a wish, and the process is the difference between the goal and the outcome. The process is a promise kept by measurement: the weekly reviews, the named owners, and the quarterly rescore are the evidence that the goal is being pursued with a method, and the method is what the operation can defend when the inspector and the insurer ask how zero is being pursued. The process is the promise made measurable, and the operation that runs the weekly, monthly, and quarterly rhythm with the data complete is the operation that can honestly say it is pursuing zero with a method, not a wish.
