Employee GPS tracking, without losing your team's trust

Decide what you are actually trying to learn

Most tracking projects fail because nobody wrote this down. "Visibility" is not a goal; it is a feeling. The questions worth answering are narrow, and each one implies a different amount of data.

• ▸Did they reach the customer? A punch with a location at arrival answers this. You do not need the route.
• ▸How long was the visit? Punch in and punch out at site.
• ▸Where did the day go? This one needs the duty route — and it is the one you should be able to justify to the person being recorded.
• ▸Is someone claiming travel they did not do? This is a dispute question, and it needs a record that cannot be edited afterwards more than it needs precision.

Record duty, not lives

The single decision that determines whether staff accept this: tracking runs during duty hours and stops outside them. An employee who believes they are followed home will defeat the system, and they will be right to try.

Write the hours down, tell people what those hours are, and make the app show plainly when recording is on.

Tell them before you turn it on

A one-page note, in the language your staff actually read, covering five things. This is not a legal document — if your contracts need updating, take proper advice — but it is what stops the rumour mill.

• ▸What is recorded: punch photo, punch location, position during duty.
• ▸When: duty hours only, with the dates it starts.
• ▸Why: attendance, travel claims, safety of staff who work alone.
• ▸Who sees it: named roles, not "management" in the abstract.
• ▸How to correct a mistake: the missed-punch request, and who approves it.

Hand this out before the app is installed, not after the first argument. The companies that skip this step spend the next month fighting a story they could have written themselves.

Do not invent data you do not have

This is where a lot of tracking software quietly lies. The phone loses signal for 40 minutes, and the map draws a neat line across the gap as though it knew.

It did not know. A guessed line in an attendance record is worse than a blank one, because somebody will eventually make a decision about a person based on it. A gap should look like a gap, labelled, with the time it started and ended — and if someone switched location off, that should be recorded as what it was.

We removed route estimation from our own product for exactly this reason: a customer told us plainly that an estimate presented as a fact is not something they would use to question an employee.

Handle evasion as a management problem

Location switched off, permission revoked, a mock-location app, a phone left charging at the office. It happens, and software cannot stop a determined person from leaving a phone behind.

What software can do is make it visible in the moment — the officer is told while the shift is running, rather than discovering it in a report three weeks later when nothing can be done. The conversation that follows is a manager's job, not the app's.

Where tracking stops paying

Two honest limits worth knowing before you spend money.

For staff at a fixed site all day, the route adds nothing — the punch does all the work. And for senior field staff who are measured on outcomes, tracking often costs more in resentment than it returns in information. Use it where the question is genuinely "did the visit happen", which is most service and delivery work, and skip it where it is not.