What This Is Not For
The uses a location system gets put to that it does not support, stated plainly in one place.
The record answers a narrow question well. Nearly every problem in this collection comes from asking it a wider one.
Not a productivity measure
Presence at a location is not output. Dwell time contains waiting, travel, conversation and breaks, and separates none of them.
Where to look instead: job outcomes, first-time fix rate, customer response.
Not a lie detector
A discrepancy between a record and an account has ordinary explanations — wrong address, vehicle swap, indoor fix, phone left behind.
Acting before asking is how straightforward cases become lost ones.
Not an attendance system
It shows a vehicle near an address. It does not show who was in it or what they did.
Where to look instead: a job record, paired with the location event rather than replaced by it.
Not a disciplinary tool
A record supports a process; it does not constitute one.
And the data was collected for dispatch, attendance, safety or cost — using it for discipline is a different purpose requiring its own basis.
Not a substitute for talking to people
The data shows that a round overran. It never shows why.
The driver knows, and asking takes ten minutes.
Not a safety system, unless it was designed as one
A tracker with a safety justification attached is not lone worker protection.
The difference is when the position is read — on alarm, or continuously — and whether an alarm reaches a human being who does something.
Not permanent
Every collection has a retention period. A system holding a year of positions is not being thorough; it is holding a liability with no operational use.
What it is
A way to find the nearest vehicle, confirm a visit, locate someone in an emergency, and count distance.
Four things, done reliably, with the accuracy stated.
Defending that boundary is what keeps those four worth having — and it is also, in this field more than most, what keeps the deployment lawful.
The four it does support
Worth stating alongside the negatives.
Which vehicle is nearest, for dispatch.
Whether a vehicle was at a site at a time, within a stated accuracy.
Where someone is, when an alarm is raised.
How far was driven, and for how long.
Four questions answered reliably is a system worth running, and defending that boundary is what keeps those four trusted rather than discounted along with the overreach.
An implementation prompt
During configuration, open the workflow reference can prompt questions about fields, ownership and output. Confirm current capabilities and document each plan, integration or policy assumption.