Fleet safety KPIs help companies see whether driving risks are being managed and whether agreed actions are getting completed. A useful dashboard connects incidents with exposure, checks the quality of preventive controls and prompts decisions. It should not simply rank drivers by raw alert counts.
For Malaysian fleet managers, the six measures below offer a practical starting point. Adapt their definitions to your vehicles, routes and reporting systems. They are editorial recommendations, not a legally prescribed scorecard, industry benchmark or guarantee of accident prevention.
For each measure, document its purpose, numerator, denominator, reporting period, data source and owner. Decide which vehicles and journeys are included, and keep that scope consistent. Record changes such as new devices, expanded coverage or revised incident definitions so a trend is not mistaken for a safety improvement.
HSE’s driving-for-work overview identifies the driver, vehicle and journey as key risk areas. This is a useful management framework for a balanced dashboard; its UK legal statements are not Malaysian requirements. See the HSE employer overview.
Use both outcomes and control measures. An incident rate describes what happened; overdue defect or coaching actions help reveal where controls may need attention. Neither gives a complete picture alone.
Suggested formula: recorded in-scope road incidents ÷ in-scope kilometres travelled × 100,000.
Define what counts as an incident, including how property damage and vehicle-only events are handled. Apply the same scope to the numerator and mileage denominator. Count each event once, even if it produces several reports or claims.
The 100,000-kilometre multiplier is a display convention in this guide, not a benchmark or legal requirement. For an illustrative calculation, four incidents over 200,000 kilometres produce two incidents per 100,000 kilometres. These figures are fictional and are not ADHINS results.
Review severity separately: a lower total rate should never obscure a serious injury event. Compare similar vehicle groups and routes where possible. Small fleets may have unstable short-period rates, so show counts, mileage and a longer trend alongside the headline number. Do not label an incident “preventable” without a defined, fair review process.
Suggested measure: near-miss reports reviewed within the agreed review window ÷ reports due for review in the period × 100.
Show the number of reports received alongside this percentage. A near miss is a reported event in which harm could have occurred but did not; provide examples relevant to your work so employees report consistently.
More reports may indicate greater willingness to speak up, changed exposure or worsening conditions. Fewer reports may reflect improvement or silence. Do not set “zero near misses reported” as a success target.
Review coverage measures whether the company responded, not whether the road became safer. Confirm that useful findings become actions with owners. Avoid closing reviews with a generic reminder if the underlying issue is an unsafe customer entrance or unrealistic schedule.
Suggested formula: required pre-use checks completed before use ÷ checks required for actual vehicle use × 100.
Define the required check event: for example, the start of a shift or a vehicle handover under your procedure. Do not automatically count every calendar day for vehicles that were not used. Reconcile usage records with check records so missing forms do not disappear from the denominator.
Completion is not proof of a meaningful inspection. Sample check quality through authorised observation and compare findings with subsequent defect reports. Repeated identical entries or a form submitted after departure deserve review.
Drivers need time, instruction and a safe inspection location. If completion falls, investigate those conditions as well as individual practice. A complete form cannot authorise use of an unsafe vehicle.
Suggested measure: number of unresolved safety-related defect actions past their agreed due date at the reporting cut-off.
Show age, risk priority, vehicle status and action owner beside the total. Define due dates through the authorised assessment process. Do not create a blanket repair allowance that permits unsafe vehicles to remain in service.
Distinguish a vehicle held pending assessment from one released after competent review. Closing a ticket is not enough: retain appropriate repair or assessment evidence and an authorised release decision.
Review repeated defects, unavailable parts and delayed assessments. A declining backlog is useful only if actions were genuinely resolved rather than reclassified or removed. Escalate urgent safety concerns immediately; they should not wait for the monthly dashboard.
Suggested formula: events confirmed as in-scope concerns after review ÷ kilometres covered by valid monitoring data × 1,000.
Define each event type separately, such as speeding against a validated applicable limit. State thresholds, device settings and review rules. Avoid combining different event types into a single score without explaining the weighting and its limitations.
Raw telematics or IVMS alerts are review prompts. Abrupt braking may be an appropriate response to another road user. Check device accuracy, location, route, traffic and driver explanation before treating an alert as unsafe behaviour.
Report monitoring coverage and review backlog alongside the rate. The denominator must match the vehicles and time covered by valid data; using whole-fleet mileage for a partially monitored fleet understates the result. Do not reward lower braking-alert counts in ways that discourage necessary braking.
Suggested formula: actions due in the period completed with the agreed verification by their due date ÷ all actions due in that period × 100.
Include relevant management actions as well as driver coaching. Revising an unrealistic schedule, clarifying site access or arranging vehicle familiarisation may be essential to the same concern.
Define acceptable verification when the action is assigned. Attendance at a coaching conversation is different from an observed improvement in a specific skill. Where practice needs reassessment, identify the competent observer and suitable setting.
Keep overdue actions visible rather than moving dates without explanation. Review recurring issues after closure and check whether the intervention addressed the cause. This KPI measures follow-through; it does not by itself prove that training caused a reduction in incidents.
| KPI | Suggested owner | Useful review question |
|---|---|---|
| Incident rate | Safety and fleet team | Did exposure or severity change? |
| Near-miss review coverage | Safety coordinator | Were reports reviewed and lessons acted on? |
| Pre-use check completion | Fleet supervisor | Are required checks timely and meaningful? |
| Overdue defect actions | Maintenance coordinator | What remains unresolved, and which vehicles are held? |
| Verified driving-event rate | Authorised data reviewer | Is the trend supported by valid data and context? |
| Action follow-through | Assigned action owners | Was completion verified and the cause addressed? |
A monthly management review can support trend discussion, while urgent defects, incidents and welfare concerns need immediate response. Choose targets after establishing a reliable baseline and understanding risk. Do not copy an unexplained benchmark from another fleet.
If a denominator is zero, show “not applicable” rather than manufacturing a rate. If mileage or records are missing, show the limitation instead of a reassuring green status. Limit access to identifiable driver information to authorised people and confirm applicable data-handling requirements separately.
No. Consider exposure, reporting quality, severity and whether preventive controls are working. A quiet period alone cannot establish effective risk management.
Not without context. Mileage, routes, vehicle type, device coverage and event validity affect the comparison. Review evidence before drawing individual conclusions.
No. They are a practical management starting point. Legal, sector, licensing and contractual requirements need their own review and evidence.
Start with reliable incident and mileage records, vehicle-check completion and unresolved safety actions. Add data-driven measures when the information and review process are dependable.
Bring your current reports, vehicle groups and main operational concerns to the discussion. Contact ADHINS about fleet safety, IVMS and transport advisory, and ask how the proposed scope can connect monitoring with practical action.
©2026 ADHINS Management Sdn Bhd. All Rights Reserved.