Using It in an Emergency
The moment the system justifies itself, and the preparation that decides whether it actually helps.
A vehicle is missing, a driver has not checked in, a serious incident has occurred. The system can help, and only if some things were arranged beforehand.
What has to exist in advance
Current position available on demand, which for a safety-designed system means unlockable rather than continuously logged.
A named person who can unlock it, available out of hours.
Emergency contacts for every driver, current.
A written response path: who is called, in what order, what they do, when the authorities are involved.
Tested once, because the first live use is the wrong time to discover the on-call person cannot log in.
The sequence
Attempt contact directly — phone, radio, message. Twice, not a barrage.
Check the last known position and whether it is consistent with the plan.
Consider the ordinary explanations first: a dead zone, a phone battery, a job overrunning, a device fault.
Escalate on a defined trigger — a missed check-in plus no contact for a stated period — rather than on a feeling.
Involve the authorities where the situation warrants, and knowing in advance that this is an option prevents hesitating for an hour.
What to tell the driver afterwards
That their position was accessed, when, and why.
Always, including when it turned out to be nothing.
This is what keeps emergency access from becoming general access, and it is the practice that makes the whole arrangement credible to the workforce.
Log it, and include it in the quarterly access review.
What not to do
Do not use an emergency as an opportunity to look at the wider history.
Do not skip the notification because it was a false alarm — those are the cases where the practice matters most.
Do not let the on-call account become a general-purpose login, which is how emergency access drifts into routine access.
Reviewing each use
Was the escalation trigger right? Too sensitive produces alarm fatigue; too slow is worse.
Did the position help, or was it stale or absent?
How long from concern to human contact?
What would have helped? Frequently the answer is a better dead zone map or a working check-in schedule.
The honest framing
This is the use of location data that workers most readily accept, because it is plainly for them.
It is also the one most often cited to justify collection that serves other purposes.
Keep them separate: emergency access unlocked by an event, logged and disclosed, is a different thing from a map open all day — and conflating them spends the goodwill the safety case earned.
Tell the driver afterwards, always
Including when it turned out to be nothing.
That their position was accessed, when, and why.
This is what keeps emergency access from becoming general access.
The false alarms are the cases where it matters most, because those are the ones where skipping the notification feels harmless.
Log it and include it in the quarterly review.
Connect policy to configuration
The practical choices behind this note can be compared with the legal-services use case. Keep the written purpose in control of the setup, enable only the data needed and review the result with affected workers.
Independent reference
For an external point of reference, see what3words. This popular location service illustrates an alternative way to communicate a position during a specific incident.