Safety Management System (SMS) Implementation Level KPI

Safety Management System (SMS) Implementation Level measures how effectively safety protocols are integrated into operations, impacting both operational efficiency and regulatory compliance.

A robust SMS can significantly reduce incident rates, thereby enhancing employee morale and reducing costs associated with accidents.

Organizations with high SMS implementation levels often see improved financial health, as fewer incidents translate into lower insurance premiums and liability costs.

Additionally, a well-implemented SMS fosters a culture of safety, which can lead to better overall business outcomes.

Prioritizing SMS not only aligns with strategic goals but also serves as a leading indicator of organizational maturity.

How Safety Management System (SMS) Implementation Level Connects to Your Strategy

Safety Management System (SMS) Implementation Level belongs to one KPI group in KPI Depot: ISO 39001. That KPI group carries one hundred and twenty-nine metrics, and this one ranks nineteenth. The eight metrics ahead of it, in priority order, are Road Traffic Fatality Rate, Road Traffic Accident Rate, Zero Fatality Goal Progress, Traffic Safety Community Initiatives, Driver Training Programs Implemented, Employee Road Safety Training Compliance, Safety Incident Reporting Rate, and Number of Reported Incidents. Read that list for what it counts: deaths, crashes, progress against a fatality target, community projects, training delivered, incidents reported, incidents logged. Outcomes and activities. This metric counts neither. It counts the apparatus that is supposed to produce them.

Nineteenth is a high placement, and the size of the KPI group is what makes it worth stating carefully. One hundred and twenty-nine metrics is an unusually large KPI group, far more than any road safety program reviews on a cycle, and most of that population exists to be available when a particular question comes up: a fleet question, a fatigue question, a community question, an insurance question. A rank of nineteenth puts this metric inside the band that gets looked at routinely rather than in the long tail that gets queried occasionally. It also sits outside the top eight, and the top eight in this KPI group is where fatality and crash outcomes live. The accurate description is that this metric is reviewed but not judged. That distinction has a practical consequence for the data. A number an executive is held to gets challenged on its definition. A number that is reviewed and nodded at usually gets accepted as presented, and this one is unusually easy to present favorably.

The KPI group files this metric in the internal process perspective, alongside Road Traffic Accident Rate, Zero Fatality Goal Progress, Safety Incident Reporting Rate, and Number of Reported Incidents. Road Traffic Fatality Rate and Traffic Safety Community Initiatives sit in the customer perspective here, and Driver Training Programs Implemented and Employee Road Safety Training Compliance sit in learning and growth. The shared label hides a real difference inside the internal set. Accident rates and reported incident counts are outcomes that happen to be filed as process. This metric is structural. It describes whether the machinery exists, not what the machinery produced, which makes it leading in the strict sense rather than in the loose sense the word usually carries on a safety dashboard.

Be blunt about how long the lag is. An element adopted this quarter changes what supervisors do over the following months. Changed supervision changes driver behavior over a longer window than that. Changed behavior changes exposure, and exposure has to accumulate before it moves an injury or fatality series at all. Road casualties are rare events measured against a noisy baseline, so even a genuine improvement takes several reporting periods to separate from ordinary variation, and by then the fleet, the routes, the contractor mix, and the seasons have all turned over as well. Nobody attributes a movement in Road Traffic Fatality Rate to a particular SMS element cleanly. The practical use of this metric is not to forecast next quarter's outcome series. It is to answer whether the organization has built the thing that gives improvement a chance.

The sharpest tension in this KPI group is with Driver Training Programs Implemented at priority five and Employee Road Safety Training Compliance at priority six. Implementation and training draw on the same safety resource, and in most operations that resource is a handful of people. A safety function that commits to raising this ratio spends its quarter on gap assessments, procedure drafting, register maintenance, audit preparation, and finding closure. That is desk work. The same people are the ones who would otherwise be riding along, running toolbox sessions, watching loading and securing, and coaching after a near miss. Field time moves the training metrics and changes what happens in the cab. Desk time moves this one. Both come out of the same budget line, and a program under pressure to show system maturity before a certification visit will reliably choose desk time.

The uncomfortable version of that tension is that the two can diverge for years without anyone being dishonest. The element register can be complete, every procedure current, every audit finding closed, and the conditions a driver actually faces can be identical to what they were before the program began. Nothing in the formula detects that. It is why the KPI group's own guidance pairs this metric with SMS Effectiveness Score instead of treating implementation as a sufficient account of the system, and why that guidance tells teams to push on both when Lost Time Injury Frequency Rate stays high. Implementation and effectiveness are separate questions, and only one of them is in this formula.

A second and quieter tension runs through Safety Incident Reporting Rate at priority seven and Number of Reported Incidents at priority eight. A maturing system usually raises both, because reporting channels, investigation procedures, and the expectation that reporting is safe are themselves SMS elements, and working ones surface events that previously went unrecorded. A period in which this ratio climbs and reported incidents climb with it is the expected pattern rather than a contradiction, and a program that treats the raw incident count as a target will find itself penalized for the system it just finished building. The KPI group carries reporting rate and incident count as separate metrics so that the two can be read apart.

Watch the interaction with Corrective Action Closure Rate as well. A procedure drafted and filed closes a finding and advances an element in the same afternoon, so both measures move together on documentary work while the hazard that generated the finding is untouched. When the pair rises and neither Road Traffic Accident Rate nor the injury series responds over a long enough window, that combination is the thing to investigate.

Measuring Safety Management System (SMS) Implementation Level in Practice

Both halves of this formula are judgments. The numerator counts SMS elements successfully implemented, the denominator counts total SMS elements, and neither figure is read off a system. Someone decided what an element is, someone decided how many there are, and someone decided when one is finished. Two operations running the same framework with the same real safety performance can report ratios that are nowhere near each other.

The element breakdown is the first fork and the largest. The denominator is a constructed list, not a fact about the framework. Broken coarsely into a few headline elements such as policy, leadership, risk assessment, competence, operational control, emergency preparedness, and performance evaluation, the same framework produces a ratio that moves in large steps and reads high or low on the strength of two or three judgments. Broken finely into every clause, procedure, and supporting control, it produces a ratio that moves in small increments and is dominated by the administrative long tail. The same organization, the same day, two element lists, two very different numbers. Fix the breakdown, approve it, publish it beside the ratio, and treat any comparison against an element list you have not seen as meaningless.

The underlying evidence sits in several places, and none of them was built to answer this question on its own.

• The SMS Manual and Its Element Register. The manual states what the system is meant to contain and the register is the working list of elements with their current status and owner. Where no register exists, the denominator is reconstructed from the manual's contents page every time someone asks, which is why the count drifts between reports.
• Internal Audit and Gap Assessment Reports. The only place an element's status is examined by someone who did not deliver it. The original gap assessment carries the baseline and the audits carry the movement since, so the pair is what turns a status list into a defensible series.
• Corrective Action Tracking. Open and closed findings against named elements, with dates. This is where an element that was marked implemented and then failed becomes visible, and it is the main check on a register that otherwise only ever moves forward.
• Training Records. Competence elements are only real for the people who were trained, and the record says who, when, and against which version of the procedure. A procedure revised after the training round leaves an element reading implemented and a workforce competent in the superseded text.
• Incident Investigation Files. Investigations name the elements that failed at the moment it mattered. An element cited as a contributing factor in an investigation while carried as implemented in the register is a direct contradiction, and it is the most useful contradiction available to a safety manager.
• Contractor Management Records. Prequalification files, contract safety schedules, induction records, and contractor audit results decide whether an element extends past the direct payroll. For an operation with subcontracted haulage or brokered capacity, this is often where most of the road exposure actually sits.
• Management Review Minutes. Review is itself an element in every version of the framework, and the minutes are the evidence of whether it happened, what was decided, and whether the previous round of decisions was followed up. They also date each status change, which is what lets you rebuild the series honestly after the register has been edited.

Keep the element identifier, the site, the assessment date, the assessor, and the grade of evidence on the row. A single enterprise figure with none of that behind it cannot be audited, cannot be segmented later, and cannot be restated when the element list changes.

The remaining forks have to be settled before anyone computes a figure, and each one moves the result.

• What Successfully Implemented Means. Four bars are defensible and they are not close to each other. Documented means the procedure exists and has been approved. Deployed means it has been issued, trained out, and put into the working routine. Verified in operation means an independent check found it being followed in the field on a day nobody arranged. Demonstrably effective means the element can be shown to control the hazard it was written for. The ratios fall steeply as you move along that list. Pick one bar, state it wherever the figure appears, and if the figure goes to a customer, a regulator, or an insurer, give the documented and the verified readings together rather than the flattering one alone.
• Who Adjudicates. The default is that the safety function assesses the system the safety function built, which is a conflict whether or not anyone abuses it. The alternatives are internal audit reporting outside the safety line, peer assessment between sites, and a certification body. A self-assessed figure is not worthless, but it belongs labeled as self-assessed, and the gap between the self-assessed and the independently assessed ratio is itself worth tracking.
• Partial Implementation. An element in progress can round up, round down, or score fractionally. The round down rule is the most conservative, and it moves the ratio in visible steps that match completed work. Fractional scoring carries the most information and is the easiest to inflate, because the fraction is an opinion. Whichever rule you adopt, apply it to every element, and never let a stalled element sit at a comfortable fraction for consecutive periods without challenge.
• Scope and the Unit of Assessment. A system implemented at head office and at one flagship site is not a system implemented across a network of depots, yards, and subcontractors. State the unit plainly: the enterprise as a whole, each site scored separately, or a composite weighted by exposure such as vehicles, drivers, or distance travelled. An unweighted average across sites gives the smallest depot the same voice as the largest terminal, which is how a fleet with a well run head office reports well and crashes elsewhere.
• Elements Not Applicable to the Operation. Some framework elements will not apply. They can be removed from the denominator, counted as implemented, or carried in a third state. Removal raises the ratio, and counting them as implemented raises it further while being indefensible. Removal is the reasonable choice provided the exclusion list is approved, published, and revisited, because otherwise the not applicable category becomes the disposal route for the elements nobody wants to do.
• Point in Time or Sustained. An element can be implemented and then decay. The procedure stops being followed once the pressure lifts, the supervisor who ran it leaves, the pre trip check becomes a signature collected at the gate. Decide whether implemented status expires without re-verification, and how long that window runs. A register with no expiry is a record of work once done, not a description of the system in operation.

Segmentation is what makes this metric usable rather than merely reportable. Cut by site first, because the enterprise figure is an average over units that differ enormously and the weakest site is the one that will generate the event. Cut by contractor against direct employee population next, since the two are usually governed by different controls, assessed by different people, and carry different exposure per kilometre, and the contractor figure is the one most often missing. Cut by element category, so that leadership, risk assessment, competence, operational control, emergency response, and review can be read separately instead of blended into a single number that hides which part of the system is thin. Then cut operational elements against administrative ones. That last split is the most revealing one available on this metric, because it separates the work that changes what happens on the road from the work that changes what is in the binder.

Most of the traps here push the ratio up.

• Documentation Completeness Standing In for Implementation. The dominant failure mode of this metric, and the reason it is so easy to present favorably. A written, approved, distributed procedure is visible, dateable, and countable. Whether anybody follows it is none of those things. A register assembled from documents alone measures the safety function's output, not the organization's behaviour.
• A Finding Closed by Writing a Procedure. An audit finds a control missing, a procedure is drafted in response, the finding closes and the element advances. Nothing in the yard changed. The tell is a closure record whose only evidence is a document reference and a revision date.
• The Easy Elements First. Policies, terms of reference, document control, and reporting templates are quick, so the ratio rises fast in the early phases and then stalls on fatigue management, journey risk assessment, in vehicle monitoring, contractor control, and emergency response. The early slope is not a forecast of the later one. Re-forecast from the character of the elements that remain, not from the rate achieved so far, or the second year of the program will look like failure against a plan built on the first.
• Contractors and Subcontractors Left Outside the Scope. The exclusion is usually practical rather than deliberate: their records are harder to obtain, their sites are not yours, and the contract may not oblige them to hand over anything. The effect is that the population carrying much of the road exposure is absent from both numerator and denominator, and the reported ratio describes the part of the operation that was already easiest to control.
• A Reorganization or a Framework Update Resetting the Element List. A revised standard, a merged division, or a new adviser's model produces a new denominator, and the series breaks silently. Restate the history against the new list before publishing anything, or the reset reads as backsliding in one period and as rapid progress in the next, and neither happened.
• Strong Implementation Beside a Poor Incident Record. These two coexist comfortably for a long time, and nothing about the arithmetic is contradictory. The temptation is to explain it away with lag, with fleet mix, with a bad quarter, with a small population. Treat it instead as the most informative pattern this metric produces. A high ratio sitting next to an unmoved Road Traffic Accident Rate or Lost Time Injury Frequency Rate is evidence either that the elements counted as implemented are not the elements governing the exposure, or that they are implemented on paper only, and both of those are findings worth having.

What the metric cannot tell you is the important part. It counts elements, not effectiveness, so it carries no information about which elements matter most for the hazards this particular operation faces. A count based ratio treats the element governing the highest consequence risk on the network exactly like a document control element: one unit each, equal weight, identical contribution. Two organizations can report the same ratio while one has completed the controls around night driving, fatigue, and journey planning and the other has completed its policy set. The formula cannot distinguish them, and no amount of precision in the scoring will make it. Read the ratio beside SMS Effectiveness Score, beside the elements named as contributing factors in recent investigations, and beside a deliberate view of implementation status on the small number of elements that stand between this operation and its worst credible outcome.

Common Pitfalls

Many organizations underestimate the importance of a comprehensive SMS, leading to fragmented safety practices that can jeopardize employee well-being and compliance.

• Inadequate training programs can leave employees unprepared to handle safety protocols. Without proper education, even the best systems can fail to prevent incidents, resulting in costly repercussions.
• Neglecting to regularly review and update safety policies can create outdated practices that do not reflect current regulations. This oversight may lead to compliance issues and increased liability exposure.
• Failing to engage employees in safety discussions can result in a lack of ownership and accountability. When workers feel excluded, they may not report hazards or near misses, which undermines the SMS effectiveness.
• Overlooking the importance of data-driven decision-making can hinder continuous improvement efforts. Without analyzing incident data and trends, organizations miss opportunities to enhance safety measures and reduce risks.

Improvement Levers

Enhancing SMS implementation requires a commitment to continuous improvement and employee engagement at all levels.

• Invest in comprehensive training programs that cover all aspects of safety management. Regular workshops and refresher courses ensure that employees stay informed about best practices and regulatory changes.
• Establish a feedback loop that encourages employees to report safety concerns and suggestions. This fosters a culture of transparency and accountability, empowering staff to take an active role in safety initiatives.
• Utilize data analytics to track safety performance and identify trends. Regularly reviewing incident reports and safety metrics can reveal areas for improvement and inform strategic decisions.
• Integrate safety objectives into overall business goals to ensure alignment. When safety is prioritized alongside operational efficiency and financial targets, organizations can achieve better outcomes.

KPI Depot is trusted by consulting, strategy, finance, and analytics teams at leading organizations worldwide, including those listed below.

Safety Management System (SMS) Implementation Level Benchmarks

We have 10 relevant benchmarks in our benchmarks database.

Browse the Top Benchmarked KPIs in ISO 39001

OKRs That Use Safety Management System (SMS) Implementation Level

The KPI group's objective to strengthen vehicle safety compliance to prevent accidents and injuries runs on Vehicle Safety Compliance Rate, Vehicle Safety Feature Penetration, Vehicle Maintenance Compliance Rate, and Vehicle Safety Rating Improvement, with the stated rationale that physical vehicle integrity reduces both the likelihood and the severity of a crash. The KPI group's best practice guidance is to bring vehicle safety checks inside the SMS routine, reviewing Vehicle Safety Compliance Rate and Vehicle Maintenance Compliance Rate as part of the system rather than beside it. That is where this metric earns a place on the objective, and it should be scoped rather than used whole. Carry the implementation level of the operational control elements that govern the fleet, meaning the inspection regime, the defect reporting route, maintenance scheduling discipline, and the fitness for purpose standard, as a directional key result raised over the cycle. Scoped that way it explains the compliance numbers instead of duplicating them. A compliance rate that holds while the underlying control elements remain unimplemented is being held up by individual diligence, and it will fall the moment the person doing the checking moves on.

The objective to optimize incident management and organizational learning is the second natural home, and there this metric sits upstream of everything else on the objective. Its key results are Number of Reported Incidents, Safety Incident Reporting Rate, Incident Investigation Timeliness, and Incident Investigation and Learning, and the rationale is that prompt reporting and fast investigation are what convert events into corrective action. Each of those depends on machinery the SMS element list already contains: the reporting channel, the investigation procedure and the competence to run it, the corrective action process, the feedback route back to drivers and supervisors. Set the implementation level of the reporting and investigation elements as the leading key result, moved early in the cycle, with timeliness and learning quality as the results expected to follow. The sequencing matters for reading the objective honestly, because the reporting rate should rise as those elements land, which means a rising incident count in the same period is the objective working rather than failing.

Both framings need the same guardrail, and the KPI group states it directly: press on SMS Implementation Level together with SMS Effectiveness Score, and treat a persistently high Lost Time Injury Frequency Rate as the signal to keep pressing on system maturity rather than as evidence that the system is finished. An implementation key result met alongside an effectiveness score that never moves is a completed register, not a safer operation. Where a team wants a numeric target on any of this, set it as that team's own goal for its own cycle and keep it out of any comparison with another organization, since the element list underneath the ratio is local to whoever built it.

See OKR Examples for ISO 39001

Free Whitepaper

Want to achieve performance excellence in ISO 39001? Download our in-depth whitepaper: Definitive Guide to ISO 39001 KPIs.

Download the Free Guide

KPI Categories

This KPI is associated with the following categories and industries in our KPI database: