Mobile Check-In and What a Phone Reports
What a phone check-in records, why the accuracy radius matters more than the coordinates, and the two settings that decide whether it is worth anything.
One mobile check-in, and what it was asked to establish
One claim supported, one consistent with the record, three not shown at all. Accuracy radius and integrity checking are both configurable and both were left at the default. This is one employer's own file.
A mobile check-in records that a device reported a position, with an accuracy radius attached — and the radius is the part that decides whether the record means anything. A position accurate to ten metres and a position accurate to a hundred and fifty metres look identical in a report and answer completely different questions about whether somebody was on site.
The practical lesson in “Mobile Check-In and What a Phone Reports” is that visibility is not certainty. For teams researching workforce analytics software, workforce analytics software can add time and project context to the operational record, provided the purpose is explained, access is restricted and any material inference is checked through conversation and proportionate human review.
Most systems store the radius and most reports omit it, which is how a check-in from the car park becomes a check-in from the building.
A broader reference for the question in “Mobile Check-In and What a Phone Reports” is the Electronic Frontier Foundation privacy resources. Read it alongside the local facts so that an external framework informs the assessment without replacing case-specific judgement.
What the record actually contains
The device's estimate of where it was, how confident it was, when it reported, and which credential was signed in. That is all.
It does not contain who was holding the phone, whether the person was working, or whether the position was genuine. Each of those is an inference, and two of them have no support in the record at all.
The accuracy radius
Positioning accuracy varies enormously with surroundings: open ground gives a few metres, dense urban or indoor positions can be a hundred and fifty or worse, and a device falling back to network positioning can be out by hundreds.
| Reported accuracy | What it supports | What it cannot distinguish |
|---|---|---|
| Under 20 m | Presence at a specific entrance | Which side of a doorway |
| 20–60 m | Presence on a site | Building against car park |
| 60–150 m | Presence in an area | Site against the street outside |
| Over 150 m | Presence in a neighbourhood | Almost nothing useful |
A geofence tighter than the accuracy radius is not a geofence; it is a coin toss with a map attached.
Falsification, and the setting that addresses it
Position can be falsified on a device the user controls, and every serious platform offers some form of integrity or mock-location check. Most deployments leave it off, because switching it on generates support calls.
That is a legitimate operational choice and it has an evidential consequence: without it, the record cannot support a claim that the position was genuine. Knowing which setting you have is part of knowing what the record is worth.
Battery, permissions and the gaps
Mobile records have gaps that have nothing to do with the person: location permission downgraded by an operating system update, battery optimisation suspending the app, a device switched off, no signal.
Each produces a missing check-in that looks exactly like a missed one. Before treating an absence as significant, check whether the app reported anything at all that day, and whether the gap is shared by other people on the same device model.
Check-ins are instants
A check-in at eight and a check-out at half past four establish two instants. Nothing in between is recorded unless the system is configured to track continuously, which is a different proposition with its own questions about notice and proportionality.
So a mobile system that records two instants supports two claims, and the claim about the eight and a half hours between them rests on something else entirely.
What people should be told
Whatever is collected, when, and what it is used for. Where tracking is continuous rather than at check-in, that distinction is exactly the kind of thing people assume the other way round.
What notice is required, and whether a given level of tracking is permissible at all, differs by jurisdiction and is a question for somebody qualified in the place concerned. The operational point is narrower: an employer that cannot describe its own configuration cannot give accurate notice about it.
Devices the employer does not own
Where check-in runs on personal phones, the employer is relying on a device it does not control, cannot configure and cannot inspect.
That has an evidential consequence and a practical one. Evidentially, the integrity of the record depends on settings the employer cannot verify. Practically, somebody without a suitable phone needs another route, and an employer requiring a personal device for work should expect to be asked who pays for it.
Writing the configuration down
Accuracy threshold, geofence radius, integrity checking on or off, tracking continuous or at check-in, retention period. Five lines, per deployment.
That page is what lets anybody say what a given check-in is worth. Its absence is why a reasonable system, correctly installed, produces records nobody can interpret two years later — which is the same failure as an unsynchronised clock, arriving by a different route.