Requests to Refuse

An asset-focused deployment attracts requests to extend it. Each one changes what the deployment is.

"Show me where everyone was last month"

Why to refuse: position history of identified drivers is personal data collected for no stated purpose, and retaining it brings obligations the asset deployment does not have.

Offer instead: if there is a specific operational question — a disputed delivery, an incident — a scoped, recorded lookup.

"Turn on driver scoring, it comes with the subscription"

Why to refuse: a free feature is still processing that needs a basis, a notice and probably consultation. And an asset-focused deployment that acquires driver metrics stops being one.

Offer instead: decide it separately on its own merits, with its own justification.

"Use idle time as a productivity measure"

Why to refuse: idling runs tail lifts, chillers and heaters. A crude target produces drivers switching off equipment they need.

Offer instead: idle by site and round, investigated as a structural finding.

"Keep everything for three years in case we need it"

Why to refuse: retention is per purpose. Position data has no purpose at that horizon and enlarges every request and every breach.

Offer instead: asset data long, position short, with an incident hold so a claim is covered.

"Immobilise the vehicle remotely when it leaves the area"

Why to refuse: immobilisation has physical consequences and reputable systems restrict it to stationary vehicles under narrow authorisation.

Offer instead: movement alerts and a tested recovery process.

"Fit devices without telling the drivers"

Why to refuse: covert monitoring is an exception requiring specific justification, and a device found in a vehicle nobody mentioned destroys the deployment's credibility in one afternoon.

Offer instead: say what it reads. For an asset deployment the answer is reassuring and true.

"Compare depots on cost per mile"

Why to refuse as framed: it compares geography and vehicle mix.

Offer instead: the four comparable figures, with the work type stated.

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.

Decide who decides

Before the first request arrives.

Name the person or forum that rules on exceptions.

Name what evidence an exception requires.

Agree it with whoever owns risk.

Publish it internally, so a requester meets a process rather than one person's judgement — and so the first decision does not silently become the precedent.

Connect policy and data

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