GPS time tracking software is built for work that happens where the customer is. The features that matter are the ones that cope with the realities of that work: travel between jobs, patchy signal, phones with flat batteries, and a workforce who reasonably want to know what is being recorded about them.
Travel time is working time
Movement between jobs during the day is commonly working time, and a system that only records arrival at sites will systematically under record hours. Ask how the product treats the gap between a clock out at one job and a clock in at the next, and check the answer against your own rules rather than accepting a default.
Design for a poor signal
Punches must queue locally and send later, site radii must be generous, and automatic arrivals should be confirmable by the worker. Tight automation on unreliable data produces a queue of exceptions that a supervisor resolves by guessing, which is worse than a slightly manual process everybody trusts.
Tell people what is collected
What, when, why, how long and who sees it, in writing, before rollout. Collection should end at clock out and there should be an indicator the worker can see while it is running. These two measures do most of the work in making mobile tracking acceptable, and they cost nothing.
Questions people ask about gps time tracking software
Does GPS drain the battery?
Continuous tracking does, noticeably, and it is a common reason apps get force quit. Punch only location avoids the problem.
Can we use it to check routes?
Where there is a stated operational reason and staff are told. Using it to check on people generally rather than to answer a question is where it goes wrong.
What about staff who refuse?
You need an alternative that does not disadvantage them. In practice a shared device or a manual record covers it.