The Cab-Facing Camera

General orientation, not legal advice.

More disputes, resignations and union objections arise from cab-facing cameras than from every other element of driver monitoring combined.

The case for

Fatigue and distraction are strongly associated with collisions and are not detected by any other method available in a vehicle.

In long-haul operation, microsleep detection has a genuine safety case that other measures do not address.

And after a collision, the cab view establishes what the driver was doing, which protects them roughly as often as it implicates them.

The case against

A person is filmed for their entire working day, in a space that functions as their workplace and frequently as somewhere they eat and rest.

The intrusion is continuous rather than event-based, even where the recording is triggered, because the camera is always pointed at them.

And the detection is imperfect: a driver glancing at a mirror can register as distraction, and beards, glasses and headwear affect accuracy.

What makes it defensible

A specific, documented risk — long-distance driving, night work, a fatigue-related incident history — rather than a general wish to see inside the cab.

Event-triggered only, with no live viewing.

No continuous recording retained.

Short retention, days rather than weeks, with an incident hold.

Access on incident only, logged, with the driver told when their footage is viewed.

Consultation completed before deployment, which in several jurisdictions is a requirement rather than good practice.

What makes it indefensible

Enabled because it came with the package.

Live viewing available to a supervisor.

Used for anything other than safety — timekeeping, breaks, phone use unrelated to an incident.

And any use where the stated purpose was fatigue and the actual use is discipline, which is discovered quickly and permanently.

The proportionality sentence

"A cab-facing camera is necessary here because…"

Finish it honestly.

"Our drivers cover long distances overnight and we have had two fatigue-related incidents" is an argument.

"It was included" is not, and writing the sentence down is what forces the question.

If the answer is no

Say so and say why, which is a decision worth recording because the question returns annually.

Forward-facing plus the fatigue measures in their own note address most of the same risk without the cab view.

Revisit it annually

Because the question returns whether or not you answer it.

If it was declined, record why, so the next request meets a decision rather than a blank.

If it was enabled, check the original justification still holds: the route profile, the incident history, the risk that was named.

A justification that has expired is a deployment running on inertia, which is the position that fails an assessment.

Turn the boundary into a test

For a concrete product reference, stealth monitoring software boundaries can help turn this boundary into a test. Verify current behaviour with representative roles and record what reaches the destination.

Independent reference

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