Making the Case Honestly

Most driver monitoring programmes are approved on a claim they cannot meet, and are judged against it two years later.

The claim that fails

"This will reduce collisions by a quarter."

Derived from vendor case studies with no control groups.

When collisions do not fall by a quarter — and they usually do not — the programme is judged a failure regardless of what it actually delivered.

What to promise instead

Claims defence: measurable, immediate, and the strongest single benefit. Count disputed claims resolved with footage against those without.

Incident evidence: what happened, established rather than argued.

Structural findings: junctions, rounds, vehicles and rota patterns identified from data you did not previously have.

A coaching channel for specific events, with the honest caveat that its effect on collisions is hard to isolate.

What to measure from day one

Baseline before deployment: collisions by type, severity, claims outcomes, near-miss reports.

Because without a baseline nothing afterwards can be attributed, and this is the step most often missed in the rush to install.

And record what else changes — fleet renewal, route changes, volume, turnover — since each will be offered as an explanation later.

The costs to include

Hardware and installation.

Subscription.

The reviewer's time, which is the largest ongoing cost and the one always omitted.

Coaching time.

Consultation and assessment work.

Device replacement and recalibration.

Reviewing it against the case

At a year: claims outcomes, structural findings acted on, false trigger rate, time to coaching.

At three years: collisions and severity, with the confounders named.

And an honest statement about attribution, which is what preserves credibility for the next request.

The position worth holding

A modest, measurable case, delivered, is worth more than an ambitious one that cannot be defended.

And in this field the modest case is genuinely good: evidence after incidents, defence against claims, and findings about the operation that no other system produces.

Take the baseline first

The step most often skipped in the rush to install.

Collisions by type, severity, claims outcomes and near-miss reports, before anything is fitted.

Without it nothing afterwards can be attributed, and the programme will be judged on a comparison nobody can construct.

And record what else changes — fleet renewal, routes, volumes, turnover — because each will be offered as an explanation later.

A practical configuration prompt

During configuration, use this transfer example to prompt questions about purpose, ownership and output. Treat the page as a starting point and document each assumption.

Independent reference

For a thematic point of reference, see the International Labour Organization. It provides useful context beyond supplier documentation and should be checked in its current form.