Inside the service
A visit written on paper and typed up days later proves nothing, and tracking that can be fooled by a fake location is worse than no tracking. This module runs field reps through a four-language mobile app and a web supervisor console: a shift opened and closed from the phone, visits whose location the server judges, zones drawn on the map with coverage actually measured, a live map, and day-route playback. All tracking happens strictly within the shift, with explicit consent at its start, and stops when it closes.
01
One shift with real controls
The rep starts his day from his phone, and one shift per day cannot be gamed: the system refuses a second shift on the same calendar day and closes the double-tap race with a unique database constraint. The first-ever shift requires explicit consent to tracking, and the start is recorded with location and battery level. Attendance is measured against a company-defined schedule — a fixed window from which lateness and early departure derive, or a flexible model with target hours and weekly days off — with all durations shown in a precise digital format.
02
The server judges the visit
Registering a visit requires an open shift and a customer card that passed the new-customer approval flow. At check-in the server computes the distance between the rep's position and the customer's stored coordinates — or the specific branch when the customer has several sites — and itself decides inside or outside the range the company set; the device decides nothing. One visit stays open at a time, and it closes with a check-out that fixes its duration, outcome and photos.
03
Layered anti-spoofing defenses
A fake location is rejected by the server; device integrity checking turns away modified apps, rooted phones and emulators; the account binds to one device at first login and moves only when management re-binds it; an impossible-travel guard compares the visit position against the last genuine tracking point of the same shift and refuses implausible jumps; and every call carries a rate limit against automated abuse. Stacked layers with one aim: a field record you can stand behind.
04
Live map, replayable routes
During the shift the supervisor sees his reps' positions live; a rep whose phone dies mid-shift shows as a stale marker instead of disappearing, and true stop minutes are computed excluding logged visit times. Afterwards, any day's route replays: the trail is cleaned of sensor noise and matched onto the real road network, showing genuine stops with their actual dwell minutes, visit markers, and the distance travelled.
05
Zone coverage measured, not claimed
The supervisor draws a zone on the map and assigns it as a mission with a time window. Coverage is computed from two signals rather than claimed: location-verified visits to the zone's customers, and the real trail passing through a fine grid of cells covering it — with new customers the rep signed inside it counted too. On the supervisor's approval the result freezes and never shifts later. The activity log itself is disciplined: visits, calls and quotations as company-defined types, each with defined fields, never free text.