Green KRIs That Mask Deteriorating Safety Risk
A trucking and logistics company with 1,200 tractors and $900 million in revenue uses four key risk indicators on its board dashboard: driver turnover, fuel price variance, on-time delivery, and total recordable incident rate. All are green. Behind the dashboard, near-miss reports fell 30% after a no-blame policy was announced but not implemented; telematics shows harsh-braking alerts up 45%; two major customers added safety clauses to contracts; and the safety director resigned, leaving the position vacant for four months. The incident-rate threshold is 3.0 per 200,000 hours; actual is 2.8. The risk register lists driver safety as low likelihood and moderate impact. Internal audit is asked whether the KRIs provide effective risk monitoring. The CRO says the dashboard is data-driven.
1. Evaluate the design and use of the KRIs. What makes the green dashboard misleading?
Read the worked answer
The dashboard relies heavily on lagging indicators. Total recordable incident rate captures injuries after harm has occurred and can remain below threshold while leading indicators deteriorate. The 30% drop in near-miss reports is ambiguous: it may reflect fewer hazards, but the timing after an unimplemented no-blame policy points more strongly to underreporting. Harsh-braking alerts up 45% are a direct leading indicator of driver behavior and fatigue risk, yet they are absent. The safety director vacancy removes oversight and may suppress reporting. Customer safety clauses signal external scrutiny. The thresholds are set without a stated rationale and are not linked to risk appetite or trigger actions. A green status based on one lagging metric and no data-quality checks gives false comfort. The dashboard reports status, not trends, and does not test whether the data reflect actual risk.
2. Recommend a revised KRI set and reporting protocol.
Read the worked answer
The revised set should combine leading and lagging indicators: harsh-braking events per 100,000 miles, near-miss reporting rate per 100 drivers with a target range that flags both low and high reporting, driver turnover and safety-sensitive vacancy days, fatigue-related dispatch exceptions, customer safety-clause compliance, and total recordable incident rate. Each KRI should have a defined owner, data source, frequency, threshold, and required action when breached. Reporting should show trends over at least 12 months, not just red/amber/green status, and should distinguish data quality issues. A sharp drop in near-miss reporting should trigger a culture and reporting review, not a green rating. The board dashboard should include a short narrative on indicator limitations. Internal audit should verify the data pipeline and test whether threshold breaches are escalated and acted upon.
3. How should internal audit report the issue and what root cause should it test?
Read the worked answer
Internal audit should report a significant risk-monitoring weakness: the dashboard does not provide effective early warning for driver safety, and green status is not supported by the underlying indicators. The report should describe the lagging nature of the incident rate, the unresolved near-miss decline, the missing telematics indicator, the safety vacancy, and the absent threshold rationale. Root causes to test include incentives that reward low reported incidents, the no-blame policy remaining unimplemented, vacancy-related loss of oversight, and weak data governance. Internal audit should recommend a revised KRI set, threshold actions, independent validation of near-miss reporting, and board escalation of leading indicators. It should follow up to confirm that management has not simply changed thresholds to restore green status.