The Thing You Are Spending
Location systems depend on people leaving the devices alone. What that cooperation is worth, and how it is spent.
Every deployment in this field rests on something not in the specification: the people being tracked not working around it.
What working around it looks like
A phone left in the depot, or in a colleague's van.
A plug-in device removed and forgotten.
An app force-stopped every morning.
Routes chosen because they look better on a map rather than because they are sensible.
Jobs rushed because dwell time is being watched.
Each degrades exactly the data the system was bought for, and none of it is detectable as sabotage — it looks like poor coverage and ordinary variation.
What spends the cooperation
Tracking outside working hours.
A map open all day.
Dwell time in a performance conversation.
A gap treated as evasion.
Any use the notice did not describe.
One instance of the last is enough, because in a field operation it is known across the depot within a week.
What builds it
Collecting less than you could, visibly.
A pause control that works and is demonstrated.
Showing people their own data, and who read it.
Fixing something the data revealed about the work — a round that overruns, a site that takes longer than quoted — and saying so.
Declining a request publicly, which is the clearest possible signal about what the system is for.
The asymmetry
Cooperation is slow to build and fast to lose.
And its loss is invisible in the system, which continues reporting confidently while the data quietly stops describing reality.
Which is why the data quality checks matter beyond their technical purpose: a coverage figure falling across a depot is sometimes a hardware problem and sometimes an answer.
The honest tension
Some people do take advantage, and pretending otherwise helps nobody.
But the response to one person is not a system change for everyone, which is the most common mistake here.
Deal with the individual through the ordinary process and leave the arrangement that works for the other forty alone.
A tightening applied to everyone punishes the compliant and is adapted to within days by the person it was aimed at.
The measure
Are the devices where they should be?
Is coverage stable?
Do people raise problems with the data, or ignore it?
A workforce that reports a misfiring geofence is cooperating. One that lets it produce wrong events has told you what it thinks of the system, and no configuration will replace what has been lost.
Read the coverage figure both ways
A falling number has two explanations.
Hardware or environment, which is the usual one and is checkable.
Or people working around the system, which looks identical in the data.
Check the hardware first, because assuming the second and being wrong is expensive.
But if the hardware is fine across a depot, the figure is telling you something about the deployment rather than about the devices.
A concrete product reference
When translating this principle into a buying test, employee screen monitoring software provides a concrete workflow reference. Verify the current behaviour in a trial and judge it against the purpose and limits described above.