FieldFlowSales
FieldFlow

Tracking sales reps' location fairly: consent, hours and policy

Location tracking can settle mileage disputes and prove visits, or it can poison a team's trust. The difference is mostly in how it is introduced and where the limits are.

7 min read

Tracking where outside sales reps go during the workday is common and, done well, useful to everyone: it backs up mileage claims, proves visits and keeps coverage honest. Done badly, it feels like surveillance, and good reps leave. This guide covers the practices that keep tracking on the right side of that line.

Track work, not people

The single most important rule is to track only during working time. Tracking a rep's personal phone on evenings and weekends gives you nothing useful and creates most of the legal and trust risk. The cleanest approach is tracking that runs only while a rep has a work route in progress: they start it when the working day begins and end it when the day ends.

Give written notice and get consent

Tell reps in writing what is tracked, when, why, and who can see it, and get their signed acknowledgment before tracking starts. Some states require this. New York, Connecticut and Delaware, for example, require employers to give notice of electronic monitoring, and California's privacy law gives employees rights over the personal information their employer collects. Even where notice is not required, it is the fair thing to do and your best protection in a dispute.

What a tracking policy should cover

  • What is collected: location during work routes, visit check-ins, photos taken in the app
  • When: only between the start and end of a work route, never outside it
  • Why: mileage reimbursement, visit verification, coverage planning
  • Who can see it: the rep, their manager, and named administrators
  • How long it is kept, and when it is deleted
  • How a rep can see their own data and question a record they think is wrong

Company phones vs personal phones

Many reps use their own phones for work. That is workable, but it raises the stakes on the work-hours-only rule, because the device goes everywhere the rep does. Make sure the app makes it obvious when tracking is on, and that reps can see a route has ended. If you supply company phones, the device question is simpler, but the policy still matters.

Limit who sees the data

Location history should be visible to the people who need it for the purposes in your policy, and no one else. A rep's peers do not need to see each other's routes. Access controls should be part of the software you choose, not a promise in a handbook.

Use it the way you said you would

Trust is lost the first time data collected for mileage is used to accuse someone over a long lunch. If you said tracking is for reimbursement and visit verification, use it for those. When a record looks wrong, ask the rep before you conclude anything. GPS has gaps, phones die, and an innocent explanation is far more common than a guilty one.

Where FieldFlowSales fits

In FieldFlowSales, location is recorded only while a rep has a route running: tracking starts when they start a route and stops when they end it. On Android the phone shows a notification while recording is on. Each organization's data is kept separate from every other organization's, and our security page explains how location data is stored and protected.

Related guides