How to Decline a Request

Requests here come from people with a genuine safety concern and a system in front of them that appears to answer it.

What does not work

Expressing discomfort, which reads as obstruction and invites someone else to be asked.

Citing policy without explaining it, which invites a request to change the policy.

A flat no with no alternative, which gets routed around.

Overstating the legal position, which is checked and discredits the accurate parts.

Name the reason that lands

For a safety audience: it will stop the reporting. A driver who believes the system is used against them stops reporting near misses, which is the cheapest safety information you have.

For a legal audience: the purpose was stated at deployment, and a use outside it is a change requiring its own basis — and the change is discoverable.

For a commercial audience: a score that cannot be explained cannot be defended, and the first grievance establishes that publicly and expensively.

All three are true. Lead with the one that will be heard.

Answer the worry underneath

"I think one of them is dangerous" — a real concern, answered by a scoped review of specific events with context, not by a ranking.

"We had a bad collision" — answered by an investigation that examines schedule, vehicle and location, which usually finds more than the driving does.

"The insurer wants data" — ask them precisely what, because the answer is frequently narrower than assumed.

"Everyone else has cameras in the cab" — answered by the proportionality sentence, finished honestly.

Offering the real answer turns a refusal into a consultation.

Where not to help improve

Enabling live cab viewing quietly. Presenting a proprietary score as validated when it has not been. Extending retention without a purpose. Using safety data for timekeeping.

None is a partial improvement, and each is discovered.

Recording it

What was asked, by whom, when. What was declined and why. What was offered instead. Who decided.

Findable, so the second identical request is answered by reference.

If overruled

Tell the drivers what changed, which is better than them discovering it.

Insist on the mitigations: a stated purpose, a retention period, access logging, and a review date.

Record your position in writing, dated.

Prepare the position in advance

Written before it is requested.

The categories you will not do, with the reason for each.

Who decides on an exception.

Agreed with whoever owns risk, before anyone asks.

Deciding calmly is much easier than inventing it in the week after a serious collision, when the pressure to extend the system is at its highest and the judgement at its worst.

Connect policy and data

The choices in this note can be compared with the scheduling reference. Keep the written purpose in control and enable only the information needed at this boundary.

Independent reference

For a thematic point of reference, see the European Data Protection Board. This established source is a useful independent reference for the issue discussed here.