GPS tracking
Track field routes with schedules, permissions, geofences, and operational alerts.
Audience: Admin · Supervisor
GPS tracking in Chekku answers where the team moved during authorized hours—not continuous off-duty surveillance. It complements visit check-ins by showing routes between stops and alerting when users enter or leave operational areas.
How tracking works
- Mobile app records location samples when tracking is enabled for the user and within configured schedules.
- Web Tracking view renders the route polyline, last known position, and timestamps.
- Geofences (when configured) generate alerts on entry/exit events tied to places or custom areas.
Tracking requires explicit mobile permissions (location, often background on Android). Users should understand company policy before rollout.
Schedules and permissions
Admins define when tracking is active:
| Control | Purpose |
|---|---|
| Work schedule | Limit sampling to shift hours (e.g. Mon–Fri 07:00–19:00) |
| User / team toggle | Enable tracking only for roles that need it |
| Visit type linkage | Some setups tie high-accuracy capture to specific activities |
Outside the schedule, the app should not accumulate route points—reducing battery drain and privacy exposure.
Supervisors see routes for teams they manage; admins configure global rules.
Web experience
Open Tracking on the web to:
- Pick date + user (or team) and replay the day's path.
- Inspect stops correlated with visits when timestamps align.
- Export or screenshot routes for dispute resolution (availability varies by plan).
Tracking is operational context: use it to verify coverage and response times, not as a standalone HR discipline tool without local policy review.
Geofences and alerts
Geofences define circular or polygon areas around places or custom regions:
- Entry alert — user arrived at depot or client site radius.
- Exit alert — user left assigned territory during shift.
Route alerts to supervisors via in-app notification or email depending on configuration. Tune radius carefully—GPS drift in urban canyons causes false positives.
Pair geofence alerts with Visit control to confirm whether a check-in form was also submitted.
Tracking vs. visit GPS
| Feature | Visit GPS | Continuous tracking |
|---|---|---|
| Trigger | Check-in / visit type rules | Schedule + permission |
| Output | Point at visit | Route polyline |
| Best for | Proof of presence at job | Logistics, security patrols |
Many teams enable visit GPS for everyone and continuous tracking for a subset.
Privacy and compliance
- Communicate tracking policy to field staff in writing.
- Restrict supervisor access to legitimate operational needs.
- Disable tracking for off-duty hours via schedules.
- Document retention if your jurisdiction requires it.
Tips
- Pilot with one team before company-wide enablement.
- Compare tracking replay with Visit control map pins when investigating discrepancies.
- If routes look sparse, check battery optimization settings on Android (Chekku should be exempted).
- Geofence too tight → noise; too loose → missed exceptions.