Using People's Own Phones
The cheapest deployment option and the one that asks the most of workers. What it actually requires of them, and what to provide instead.
The boundary · Analysis
Most geofenced attendance runs on personal phones, because that is what makes it cheap. It is worth being clear about what is being asked.
What you are asking for
Installation of employer software on a device the person bought and pays for.
Location permission, which on modern operating systems means an explicit grant the person can see and revoke.
Battery, which location checks consume.
Data allowance, modest but not nothing.
Availability: the phone has to be charged, present and working for the person to be paid correctly.
That last point is the serious one. Pay now depends on the condition of a device the employer does not supply.
The requirements this creates
A phone is not a condition of employment unless it is in the contract, and making it one retrospectively is a change to terms.
Someone without a suitable phone must have another way to clock in. An older device, no device, or a broken screen cannot mean unpaid work.
Battery and data cost something, and several jurisdictions expect employers to cover work-related device costs.
Check what your jurisdiction requires, because this is an area where practice has been ahead of the law and the law is catching up.
Permissions in practice
Operating systems have tightened location permissions repeatedly.
"While using the app" is the normal grant, and it is enough for a clock-in that happens while the app is open.
"Always" is not needed for attendance and asking for it is the thing that makes people suspicious — reasonably, because it permits background collection.
Ask for the minimum, and be able to say plainly that the app cannot see location when it is closed.
Check what the product actually requests. Several ask for more than the function needs.
What to provide instead
Company devices, for anyone who wants one, which removes the whole question.
A fixed terminal or tablet at the entrance, which is cheap and works for everyone.
An NFC tag or a code, which requires a phone but not an app with location permission.
Offering an alternative is not an edge case. People change phones, lose them, and work in places where carrying one is impractical.
What to say
That the app checks location only when they tap to clock in.
That it cannot see where they are at other times — and only say it if it is true.
How to check the permission themselves.
That there is another way to clock in if their phone is unavailable, and what it is.
These four sentences prevent most of the resistance, and the resistance is otherwise reasonable.
Offer an alternative from the start
Not as an exception handled case by case.
A terminal at the entrance, a tag, or a company device for anyone who wants one.
Announced at the same time as the app, so nobody has to ask.
Because people change phones, break them, and work in places where carrying one is impractical — and none of that should affect whether they are paid.
An implementation prompt
During configuration, employee activity tracking can prompt questions about fields, ownership and output. Confirm current capabilities and document each plan, integration or policy assumption.
Independent reference
For an external point of reference, see NCSC guidance. This popular specialist source offers a useful reference beyond product documentation.