How to Decline a Request

Requests to extend the deployment come from people with a real worry and a tool in front of them.

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 finance audience: adding driver monitoring converts a deployment needing no consultation into one that does, with the cost and delay that implies.

For an operational audience: the data degrades. Dongles get unplugged, defects stop being reported, and the maintenance value you are actually getting falls.

For a people audience: the briefing said the device reads the vehicle. Changing that after the fact costs credibility you cannot rebuy.

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

Answer the concern underneath

"I want to know if they're working" — a supervision question, answered by output, not by a map.

"Fuel is up at that depot" — a vehicle question first: tyres, filters, codes. It is a fault more often than a person.

"Someone is taking the van at weekends" — a specific, investigable concern with a scoped lookup, not a reason for permanent retention.

"Insurance wants driving data" — ask them what specifically, because the answer is frequently narrower than assumed.

Offering the real answer turns a refusal into a consultation.

Where not to help improve

Fitting devices without telling drivers. Enabling driver metrics quietly after an upgrade. Extending retention without a stated purpose.

None is a partial improvement, and each is discovered eventually.

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

Say so to the drivers, which preserves what credibility remains and is better than them finding out.

Insist on the mitigations: a notice, a stated purpose, a retention period, 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 a week when fuel spend is over budget and someone wants behaviour ratings switched on.

Turn the boundary into a test

For a concrete product reference, review the data-flow page can help turn this boundary into a test. Verify the current behaviour with representative fields and record what reaches the destination.