Introducing It

Drivers have heard about these systems from other fleets. The first announcement either confirms what they expect or contradicts it.

Decide before announcing

Cab-facing video: yes or no. The single question that dominates everything else.

Whether scores are linked to pay. Decide no, and say so.

Whether a single event can be disciplinary, and what the serious threshold is.

Who reviews footage and how quickly drivers hear the outcome.

Retention, in days.

Announcing before these are settled invites the answers to be assumed, and the assumptions will be the worst available.

Set thresholds before anyone sees a score

A month of silent logging, by vehicle type.

Thresholds from your own distribution.

Calibration checked, mounting verified, outlier vehicles investigated.

A first week of implausible scores destroys the programme's credibility permanently, and it is entirely avoidable.

The sequence

Consult, where required and where sensible.

Configure to what the consultation produced.

Brief in person, with the field list available.

Pilot with a depot that volunteers.

Report back what it found about the work — a junction, a round, a vehicle — before reporting anything about people.

What to say

What is measured and what is not.

What happens to a hard brake that avoided a collision.

Who sees what, when, and whether viewing is logged.

That it is not linked to pay, if that is true.

And what would have to happen for it to become a disciplinary matter, stated specifically rather than left open.

The first finding should be structural

Publish something the data showed about the operation, not about a person.

A junction generating events across drivers. A round that cannot be driven in the time allowed. A vehicle with a mounting problem.

Fix one of them visibly.

This does more for acceptance than any briefing, because it demonstrates what the system is for.

What undermines it in the first month

A score published before thresholds were tuned.

A disciplinary case from an early clip.

A driver discovering the cab camera was not mentioned.

Any of these and the programme is understood as surveillance from then on, regardless of what it does afterwards.

Make the first finding structural

Before anything is reported about a person.

A junction generating events across drivers. A round that cannot be driven in the time allowed. A vehicle with a mounting fault.

Fix one visibly and say the data found it.

This does more for acceptance than any briefing, because it demonstrates what the system is for rather than asserting it.

Reproduce the workflow

For another way to make this requirement testable, consult remote employee monitoring rollout. Reproduce the case with real roles, failures and recovery steps.

Independent reference

For a thematic point of reference, see the Royal Society for the Prevention of Accidents. It provides useful context beyond supplier documentation and should be checked in its current form.