Why Companies Measure the Wrong Fleet Safety Metrics

Many companies do not have a fleet safety measurement problem.

They have a timing problem.

They measure risk after it has already turned into damage.

They track collisions, claims, complaints, violations, repair costs, and near misses after something has already happened.

Those metrics matter.

But they are not enough.

If an organization only measures what happened after failure, it is managing fleet safety from the rear-view mirror.

A stronger fleet safety system measures the behaviours, habits, exposures, and conditions that make incidents more likely before the incident occurs.

That is the difference between recording fleet safety and improving fleet safety.

Some Companies Do Not Measure Anything

The weakest fleet safety system is the one that does not measure at all.

No incident trends.

No close-call review.

No vehicle damage patterns.

No complaint tracking.

No coaching records.

No driver behaviour indicators.

No fuel or idling review.

No assessment history.

No way to compare locations, teams, supervisors, vehicles, or routes.

In that environment, leaders may believe the fleet is safe because nothing major has happened recently.

But absence of evidence is not evidence of safety.

If an organization is not measuring, it cannot confidently know whether its drivers are improving, declining, drifting, or simply getting lucky.

The Metrics Most Companies Track Are Lagging Indicators

Many organizations that do track fleet safety focus mainly on lagging indicators.

Lagging indicators show what already happened.

Examples include:

• collisions
• insurance claims
• vehicle damage
• speeding tickets
• policy violations
• customer complaints
• roadside incidents
• injury reports
• repair costs
• days lost
• incident frequency
• incident severity

These metrics are useful.

They show cost, consequence, and historical performance.

But they do not show enough about the conditions that created the outcome.

A collision tells the company that risk matured.

It does not always explain how long the behaviour was developing before that day.

A complaint tells the company that someone noticed a problem.

It does not reveal how often the same behaviour occurred without being reported.

A claim tells the company what the damage cost.

It does not reveal how many warning signs were missed before the damage occurred.

Lagging indicators tell you where the fire was.

They do not always tell you where the smoke started.

Close Calls Are Better, But Still Not Enough

Tracking close calls is a step forward.

A close call gives the organization a chance to learn before damage occurs.

But many companies still underuse close-call data.

Some workers do not report close calls because they fear blame or embarrassment.

Some supervisors do not investigate them deeply.

Some organizations record the event but do not turn it into coaching, route review, policy improvement, or system change.

And even when close calls are tracked well, they still represent moments when risk had already become visible.

The next level is measuring the behaviours that make close calls more likely.

The Better Question Is Not “What Happened?”

The better question is:

What was happening before something happened?

That is where meaningful fleet safety measurement begins.

Before a rear-end collision, there may have been:

• poor following distance
• weak scanning
• late hazard recognition
• distraction
• harsh braking trends
• route pressure
• fatigue
• overconfidence
• poor space management
• schedule pressure
• inadequate coaching

Before a backing incident, there may have been:

• repeated rushed reverses
• weak mirror use
• no get-out-and-look habit
• poor site planning
• lack of spotter communication
• unfamiliarity with vehicle dimensions
• no low-speed vehicle-control training

Before a public complaint, there may have been:

• aggressive acceleration
• speeding
• close following
• poor lane discipline
• visible phone use
• unsafe parking
• a driver who sees the vehicle as transportation instead of representation

The incident is the final signal.

The behaviour existed before it.

Lagging Damage Metrics vs. Leading Behaviour Metrics

ADS separates fleet safety measurement into two broad categories.

Lagging Damage Metrics

These show what already went wrong.

They include:

• crashes
• claims
• repair costs
• complaints
• violations
• injuries
• lost time
• property damage

These metrics are necessary for accountability and trend review.

But they are late.

Leading Behaviour Metrics

These show patterns that increase or reduce risk before the damage occurs.

They may include:

• harsh braking
• harsh acceleration
• speeding trends
• cornering behaviour
• following-distance concerns
• idling time
• fuel efficiency
• seatbelt use
• phone or device events where measurable
• reverse events
• low-speed impacts
• inspection completion
• coaching completion
• assessment results
• repeat deficiencies
• close-call themes
• driver feedback patterns
• route or location risk patterns

Leading behaviour metrics are not perfect.

They need interpretation.

But they give the organization a chance to act earlier.

Telematics Data Is Useful, But It Is Not the Whole Answer

Some companies believe telematics solves the measurement problem.

It does not.

Telematics can provide valuable signals.

It may show:

• speed
• harsh braking
• acceleration
• cornering
• idling
• route history
• seatbelt use
• vehicle utilization
• fuel use
• engine alerts

Those are useful indicators.

But telematics does not automatically explain why the behaviour occurred.

A harsh braking event may indicate:

• poor scanning
• close following
• distraction
• traffic complexity
• sudden hazard
• poor route planning
• schedule pressure
• defensive action that prevented a collision

Without coaching and context, the metric can be misunderstood.

Data tells you where to look.

It does not replace trained observation.

Observation Is the First Step

Improvement begins with observation.

If a company cannot observe driver behaviour, it cannot reliably improve driver behaviour.

Observation may come from:

• telematics
• dashcam review
• supervisor reports
• trained driver-coach ride-alongs
• practical assessments
• incident reviews
• close-call reports
• fuel and idling trends
• maintenance patterns
• public complaints
• driver self-assessments

The important point is that observation must lead somewhere.

Collecting data without coaching is not a safety system.

It is storage.

Coaching Is the Second Step

Once behaviour is observed, the organization must respond.

That response should not automatically be discipline.

Many metrics reveal development needs, not misconduct.

A driver with harsh braking trends may need work on:

• visual lead time
• following distance
• hazard prediction
• speed control
• stress management
• route planning
• distraction control
• defensive mindset

A driver with poor fuel efficiency may need work on:

• acceleration habits
• smooth braking
• speed management
• anticipation
• idle reduction
• route efficiency
• vehicle familiarity

A driver with repeated low-speed damage may need work on:

• spatial awareness
• reference points
• mirror setup
• reversing habits
• front swing
• rear-wheel off-tracking
• patience

The pattern should trigger coaching.

Then the organization should observe again.

That creates the improvement loop:

Observe. Coach. Reassess. Repeat.

Metrics Should Connect to Behaviour, Not Just Cost

Many companies track costs because costs are easy to understand.

Fuel.

Repairs.

Claims.

Insurance.

Downtime.

Those numbers matter because they speak the language of business.

But cost alone does not tell the organization what to change.

For example:

High repair cost may be caused by:

• poor low-speed control
• tight worksites
• inadequate backing procedure
• poor route selection
• weak vehicle familiarization
• rushed drivers
• no coaching after minor damage

High fuel cost may be caused by:

• idling
• aggressive acceleration
• poor route planning
• unnecessary vehicle use
• heavy loads
• poor maintenance
• poor speed management

High claims may be caused by:

• weak driver onboarding
• no refresher training
• inconsistent supervisor standards
• poor close-call learning
• lack of practical assessment
• organizational pressure

Good metrics connect cost to behaviour.

That connection is where improvement becomes possible.

Smooth Driving Is a Safety Metric

Smoothness is often underrated.

A smooth driver is usually doing several things well at once.

They are:

• looking farther ahead
• anticipating hazards
• managing space
• adjusting speed early
• braking progressively
• accelerating with control
• positioning with purpose
• reducing passenger discomfort
• reducing vehicle wear

A rough driver may not be unsafe in every moment, but the pattern deserves attention.

Harsh control can indicate:

• late decisions
• weak scanning
• impatience
• poor planning
• distraction
• overconfidence
• lack of vehicle feel

Smoothness matters because it connects safety, professionalism, passenger comfort, vehicle wear, and fuel efficiency.

It is not just a style preference.

It is a performance indicator.

Idling Is More Than an Environmental Metric

Idling is often measured for fuel savings or emissions.

That is valid.

But idling can also reveal operational habits.

Excessive idling may point to:

• weak policy communication
• lack of driver awareness
• poor route or task planning
• comfort habits
• poor supervision
• no accountability
• poor understanding of cost

Reducing unnecessary idling can directly affect the organization’s bottom line.

It also shows whether drivers are thinking professionally about the vehicle as a business asset, not just a tool they happen to be using.

Fuel Efficiency Can Reveal Driver Behaviour

Fuel economy is not only a maintenance or vehicle issue.

It can also reflect how the driver operates.

A driver who accelerates hard, brakes late, speeds unnecessarily, idles excessively, and fails to anticipate traffic will often use more fuel.

Tracking fuel trends can help identify:

• heavy-footed driving
• inefficient acceleration
• poor speed control
• unnecessary idling
• route inefficiency
• vehicle misuse
• coaching opportunities

Fuel data should be interpreted carefully.

Loads, routes, traffic, terrain, weather, and vehicle type matter.

But when compared fairly, fuel trends can help reveal behaviour that affects both safety and cost.

The Best Metrics Are Actionable

A metric is only useful if it can lead to a decision.

If a company tracks a number but does nothing with it, the number has little value.

Strong fleet safety metrics should help answer:

• Who needs coaching?
• What behaviour needs attention?
• Which routes or locations create repeated risk?
• Which vehicles require familiarization?
• Which supervisors need assessor training?
• Which policies are unclear?
• Which teams are improving?
• Which issues are repeating?
• Which risks are being normalized?
• Which interventions worked?

A good metric points toward action.

A weak metric only fills a report.

Companies Often Confuse Compliance With Insight

Many fleet safety metrics exist because someone needs proof that something was done.

Training completed.

Policy signed.

Inspection submitted.

Ride-along performed.

Assessment form filed.

Those records matter.

But completion is not the same as improvement.

A driver can complete training and still drive poorly.

A supervisor can complete a ride-along and still miss the real issue.

A form can be filled out and still provide no useful insight.

Compliance metrics answer:

Was the activity completed?

Insight metrics answer:

Did the activity improve behaviour, reduce risk, or reveal something useful?

Both have a place.

But companies often stop at completion.

Measuring Only Incidents Creates a False Sense of Safety

If a company has no incidents this quarter, leadership may assume the fleet is performing well.

Maybe it is.

Maybe it is not.

There may be:

• unreported close calls
• hidden vehicle damage
• near misses
• harsh braking trends
• speeding patterns
• growing driver complacency
• repeated low-speed errors
• weak inspections
• public frustration
• supervisors avoiding difficult conversations

The fleet may look safe because the organization is only counting the final outcome.

This is similar to complacency in experienced drivers.

Nothing happened, so the system assumes everything is fine.

That is dangerous.

The absence of incidents is not the same as the presence of safety.

Metrics Must Be Paired With Culture

Measurement can improve safety.

It can also damage trust.

If every data point is used to punish drivers, drivers will resist the system.

They may hide information, disable tools, avoid reporting, or treat metrics as surveillance.

That does not create professional development.

It creates defensive behaviour.

A strong culture uses metrics to:

• identify patterns
• coach earlier
• support drivers
• improve systems
• reduce preventable exposure
• recognize strong performance
• hold people accountable when needed

The message should be clear:

We measure because we are trying to improve, not because we are looking for excuses to blame.

Accountability still matters.

But development should come before punishment when the issue is coachable.

The D.R.I.V.E. Safe System Helps Organize Metrics

The ADS D.R.I.V.E. Safe System can help companies measure more intelligently.

D: Defensive Mindset

Possible indicators:

• openness to coaching
• complaint patterns
• close-call reporting
• attitude during assessments
• response to feedback
• policy respect

R: Risk Management

Possible indicators:

• speed trends
• harsh braking
• following distance concerns
• route risk
• incident exposure
• unsafe parking or reversing patterns

I: Insight and Awareness

Possible indicators:

• scanning observations
• late hazard recognition
• missed signs or signals
• distraction concerns
• mirror-use patterns
• coach observations

V: Vehicle Control

Possible indicators:

• smoothness
• cornering
• low-speed damage
• backing events
• vehicle positioning
• braking and acceleration trends
• fuel efficiency

E: Environment Adaptation

Possible indicators:

• speed adjustment in weather
• route decisions
• winter-driving behaviour
• terrain-specific incidents
• visibility-related errors
• service-road readiness

The point is not to measure everything.

The point is to measure what helps the organization see driver behaviour more clearly.

The Fleet Safety Measurement Ladder

ADS describes fleet safety measurement as a ladder.

Level 1: No measurement

The company relies on assumptions and reacts only when something obvious happens.

Level 2: Damage measurement

The company tracks collisions, claims, violations, complaints, and costs.

Level 3: Event measurement

The company tracks close calls, harsh braking, speeding alerts, idling, fuel use, and other behaviour-related signals.

Level 4: Behaviour interpretation

The company connects events to coaching themes, driver habits, vehicle types, routes, locations, and operational pressure.

Level 5: Development measurement

The company tracks whether coaching, training, assessments, and follow-up are actually improving driver performance over time.

Most organizations need to move at least one level higher.

Not all at once.

But deliberately.

What Companies Should Measure Instead

A stronger fleet safety measurement system may include:

• collisions and claims
• vehicle damage
• complaints
• close calls
• speeding trends
• harsh braking trends
• harsh acceleration
• cornering events
• idling time
• fuel efficiency trends
• low-speed manoeuvring incidents
• backing events
• inspection completion quality
• coaching completion
• reassessment outcomes
• repeated driver deficiencies
• route or location risk patterns
• vehicle-type risk patterns
• supervisor assessment consistency
• training effectiveness
• driver improvement over time

The exact metrics depend on the organization.

A utility fleet, municipal fleet, construction fleet, sales fleet, healthcare fleet, and service fleet may not need identical measurements.

But they all need metrics that connect behaviour to risk.

The Better Question

Companies often ask:

How many incidents did we have?

That question matters.

But it is not enough.

Better questions include:

What behaviours are increasing our exposure?

What are we seeing before incidents happen?

Which drivers need coaching before damage occurs?

Are our interventions improving performance?

Are we measuring safety, or only measuring failure?

Fleet safety cannot improve if the organization only studies the aftermath.

The goal is not to collect more numbers.

The goal is to see the right things early enough to act.