Checkpoints and geo-tracking
For work that happens away from a desk, KAMI records where someone was, not only when. Use this article to see field staff checkpoints on a map, with photos, check where someone was during the day, how long they spent at each stop and how far they travelled. Checkpoints and Geotracking are the two views of that, and they answer different questions.
Where:
- Attendance › Tools & Reports › Checkpoints, under Tools
- Attendance › Tools & Reports › Geotracking, under Tools
You need: each page has its own right on the Attendance rights screen, so someone can have one without the other. You see only the people your access covers. See Attendance user rights.
Which one, when
| The question | Use |
|---|---|
| Was this person where the job was, and how long did they stay? | Checkpoints: stops the employee recorded, with photos and notes |
| What route did this person take during their shift, and how far? | Geotracking: the movement trail of a checked-in event |
| Did they check in away from a branch? | The Is Remote filter on the Event List, or Remote check-ins under Tools. See Offline and remote check-ins |
| Is anyone faking location? | The GPS Mock Report |
Checkpoints suit roles that stop somewhere specific: site visits, inspections, deliveries with fixed stops. Geotracking suits roles where the route is the work.
How to see checkpoints
- Go to Attendance › Tools & Reports and select Checkpoints under Tools. It opens on today.
- Set the date range. Use Search Employees, or the filters for Department, Branch, Position, Group and Cost Centre.
- Read each row: Name, Datetime, Location, Reason, Total Distance and Total Time Spent.
- On a row, select Marker to see that point on a map, or Files to see the photos attached to it.
- Select Geo-Tracking above the list for a map of everyone's checkpoints. Show optimized route draws the route along the roads.
- To keep a copy, select Export, then Microsoft Excel (.xlsx).
What the checkpoint columns mean
| Column | What it shows |
|---|---|
| Name | The employee, with their position |
| Datetime | When they recorded the checkpoint |
| Location | The address of the point, where one could be found |
| Reason | The note the employee added |
| Total Distance | Kilometres travelled from this checkpoint to the next one, or to check-out |
| Total Time Spent | Time from this checkpoint to the next one, or to check-out |
Total Time Spent stays blank until the next checkpoint or the check-out is recorded, because until then the stop has no end.
How to see geotracking
- Go to Attendance › Tools & Reports and select Geotracking under Tools. It opens on today.
- Set the date range. Use Search Employees, or the filters for Department, Branch, Position, Group, Cost Centre and Activity.
- Read each row: Name, Datetime, Activity and Total Distance in kilometres.
- Select Marker on a row to see that person's trail on a map, or the map button above the list for everyone.
- Export gives you an Excel file.
What makes it work
Each branch has coordinates and a check-in distance, 50 metres by default. The mobile app uses them to tell whether someone is at the branch. See Setting up your organisation structure.
Check-ins away from a branch are flagged remote, and ones made without a connection are offline and sync later. You filter for both on the Event List.
What Happens Next
- Checkpoints and geotracking stay available for later review and in the exports.
- Location does not change attendance pay by itself, with one exception: your payroll attendance rules can pay a distance-based allowance on checkpoint kilometres above a threshold. If you use one, Total Distance affects pay, so check it before payroll.
Using it fairly
Location tracking is the most intrusive thing in Attendance, and how you introduce it matters as much as how you configure it:
- Tell people plainly what is recorded and why. Discovering it is recorded is far worse than being told about it.
- Use it for the roles that need it. Field roles have a real reason. Office roles generally do not, and applying it everywhere costs trust for nothing.
- Be specific about what you will do with it. "Confirming site attendance for client billing" is a purpose people accept. Unstated purposes are assumed to be the worst one.
- Check local law. Employee location data is regulated differently across jurisdictions, and this article is not legal advice.
Tips
- Configure branch coordinates when you create the branch, not when someone reports a problem.
- Ask for a photo at each checkpoint where the evidence matters. A location alone proves a device was somewhere.
- Review the GPS Mock Report monthly. The pattern matters more than any single entry.
- Do not use geotracking where checkpoints would do. Continuous tracking for a job with three fixed stops is disproportionate.
Troubleshooting / FAQ
Q: I cannot see Checkpoints or Geotracking under Tools. You do not have the right for that page. Ask your KAMI admin.
Q: Total Time Spent is blank. The employee has not recorded their next checkpoint or checked out yet.
Q: Location shows a dash. No address could be found for that point. Select Marker to see it on the map.