How to verify field visits without accusing your own team
Visit verification fails when it feels like surveillance. The methods that work verify the work, not the worker, and give agents something back.
6 min read
Every field sales organisation eventually asks the same question: did the visit actually happen? The question is reasonable, because reimbursements and incentives are paid against the answer. The way it gets implemented is often unreasonable, and that is why so many tracking rollouts fail quietly, with agents leaving phones at home or in a drawer at the depot.
Verify the work, not the worker
There is a real difference between recording that an agent completed a scheduled visit and recording an agent's location continuously through their day, including their lunch break and their commute home. The first is a business record. The second is surveillance, and it will be treated as such.
The practical rule: tracking starts when the agent starts a route and stops when they end it. That single boundary does more for adoption than any amount of internal communication.
Three methods that hold up
Geofenced check-in
A geofence is a radius around the customer's location. The agent can only check in when physically inside it, typically 50 to 100 metres. This is the strongest single control, because it ties the claim to a place rather than a time.
Set the radius honestly. Too tight and agents cannot check in from a legitimate parking spot; too loose and it verifies nothing. Large campuses and market complexes usually need their own values.
Odometer capture with a photo
Asking for a photo of the odometer at the start and end of a route gives a physical cross-check on the distance claimed. It is low-tech and unusually effective, because it produces evidence that does not depend on GPS at all.
Customer-side confirmation
A signature or approval from the customer makes the visit record independent of the agent's own device. It slows the visit slightly, so it is best reserved for high-value calls or for a sample rather than every stop.
Give agents something back
Verification is a cost to the agent: extra taps, a phone that must be charged, a feeling of being watched. Rollouts succeed when the same system also removes work from them.
- Automatic distance calculation, so they stop filling in reimbursement forms by hand
- Faster claim settlement, because the data no longer needs manual checking
- Order history at the outlet, so they stop phoning the office to ask
- A defensible record when a claim is disputed, which protects honest agents most
The last point is the one worth saying out loud in the rollout meeting. Verification protects the majority who are doing the work properly, because it ends the situation where everyone is suspected equally.
Be straight about the data
Tell agents what is recorded, when recording starts and stops, who can see it, and how long it is kept. Put it in writing. In our own product, location is captured only during an active route, employers see route history for verification and allowances, and the detail is set out in our privacy policy.
Teams that skip this step usually end up relitigating it later, under worse conditions.
Related guides
- What is sales force automation (SFA) software?SFA software manages what a field sales team does outside the office: who they visit, what they sell and what it costs to get them there. Here is how it differs from CRM, and what to look for in India.
- Beat planning for distributors: a practical guideA beat plan decides which outlets get visited, how often, and in what order. Get it wrong and agents quietly rewrite it themselves.
- Fuel and mileage reimbursement for field teamsReimbursement is usually the largest uncontrolled line in a field sales budget, not because people are dishonest, but because nobody can check the number.
- Why GPS tracking stops working on AndroidGaps in field tracking data are usually the operating system doing its job, not an agent avoiding theirs. Here is what actually stops location recording on Android.
- How to choose field sales softwareEvery vendor demos well. The differences show up on a three-year-old handset, in a basement, at four in the afternoon. Design your evaluation around that.