Two very different things get called "GPS attendance"

The first requests a location at the moment somebody clocks in or out, checks it against the workplace, and stops. The second runs in the background and builds a continuous record of where an employee has been.

They are sold with similar words and they are not similar products. The first answers "did this shift start at work". The second answers "where has this person been", which is a question an attendance system was never asked.

Why continuous tracking is worse at the actual job

It does not improve the clock-in check. A position at 14:20 tells you nothing useful about a clock-in at 08:59 that a position at 08:59 did not already tell you.

It drains batteries, which on a frontline team means handsets that are dead before the end of a shift — and an employee with a dead phone cannot clock out.

It produces a large, sensitive dataset that has to be stored, secured, retained, disclosed and eventually deleted. Every one of those is work, and none of it makes attendance more accurate.

What point-in-time verification looks like

Location is requested when the employee clocks in or out, and only when the workplace policy requires it. There is no background collection, and no movement history is built.

The check is more careful than a simple distance comparison, because a position comes with a confidence radius. A reading accurate to 5 metres and one accurate to 300 metres are not the same evidence, and treating them identically produces false rejections in basements and false passes in car parks.

Where location is unreliable, other signals do the work: the workplace network, or the employee’s registered device.

The obligations nobody costed for

Continuous location data is personal data, and collecting it starts a set of duties that a business rarely considers when ticking the feature box. It has to be stored securely, retained for a defined period and then deleted, disclosed accurately in a privacy notice, and produced if an employee asks what is held about them.

It also becomes discoverable. A dataset showing everywhere your staff have been for the last two years is a liability in any dispute, and it exists whether or not anyone ever looks at it.

Weighed against a feature that does not make clock-ins more accurate, this is a poor trade. The cheapest way to protect data you do not need is to not collect it.

What employees should be told

Whatever the system does, staff should be able to find out what it collects without reading a contract. If the honest summary is "your location is checked when you clock in, and at no other time", that is a sentence worth putting in front of people on day one.

Adoption problems with attendance software are usually trust problems. They are much easier to avoid than to repair.

A question worth asking any vendor

Does the app request location only at clock-in and clock-out, or does it run in the background? If the answer is not immediate and specific, treat that as the answer.