Providers need evidence that a shift happened where it was rostered. Workers are professionals doing skilled, often intimate work, and they notice when a tool treats them like suspects. A GPS clock-in policy has to hold both of those truths at once, and most fail by ignoring the second.
This guide covers the mechanics of a location reading, the failure modes that punish honest workers, and the policy decisions that keep evidence collection fair.
What a GPS reading actually is
A phone does not report a location. It reports an estimate: a coordinate plus an accuracy radius, which is the phone's own statement of how far off it might be. Indoors, in a group home surrounded by other buildings, or in poor conditions, that radius can be wider than the property itself.
Any policy that compares a raw pin against a street address and calls the mismatch dishonesty will punish workers for physics. The radius is part of the reading, and a fair policy uses the whole reading.
Review, never auto-reject
An out-of-range reading is a question, not a verdict. The honest handling is to flag it for a coordinator to look at — amber, not red — and to resolve it with the worker, not about them.
Support also happens in the community. The rostered address is where a shift starts, not everywhere it goes. A worker clocking in from the park where the participant asked to meet is doing the job well, and the policy has to leave room for that.
- Record the reading, its accuracy radius and the distance involved
- Record the worker's account, in their own words
- Record the resolution and who made it
Never tie location to pay
The moment an out-of-range flag can withhold pay automatically, the tool has become a disciplinary system and workers will treat it as one. Pay disputes belong with a human who has seen the context — a flag is context, nothing more.
The same discipline applies to tracking. A clock-in policy captures a point-in-time reading at the start and end of a shift. It does not follow workers between them, and it should say so in writing.
Write the policy with the people it measures
The policies that survive contact with a real workforce are drafted with worker input and written in plain language: what is captured, when, who can see it, how long it is kept, and how a dispute is raised.
- Capture: a single reading at clock-in and clock-out, never continuous tracking
- Visibility: who sees readings, and that workers can see their own
- Handling: out-of-range goes to a review conversation, worker first
- Pay: no automatic consequence from a location flag, ever
How Nexrosta handles it
Nexrosta records the accuracy radius with every clock event and shows the manager the whole reading, not just a pin. Out-of-range is flagged amber for review — never auto-rejected, and never used to withhold pay. Every clock event is written to the append-only audit log, so the evidence is there when an auditor asks, and the worker's account sits beside it.