The safe way to run GPS tracking for sales reps is to tell every rep in writing what you collect and why, read location only at check-in or during work hours, and keep off-duty time out of it. Several states require notice of electronic monitoring. This is general information, not legal advice.
You want to know that a rep who says they visited a customer did visit. Reps want to know their employer isn't following them to dinner. Both are reasonable, and you can have both. The method below gives you proof of visits and leaves the rest of the rep's day alone.
What the law says about GPS tracking for sales reps
There is no single US law on tracking an employee's phone. You get a patchwork: a few state notice laws for electronic monitoring, tracking-device laws written mostly for vehicles, and general privacy law. Here is what each says, and where it may not reach a rep's phone.
Notice laws in New York, Connecticut and Delaware
These three states require employers to give notice of electronic monitoring. Read their definitions closely, because they were written around communications, not location.
| State | What it requires | What it covers | Penalty |
|---|---|---|---|
| New York Civil Rights Law 52-c | Written notice at hiring, acknowledged by the employee in writing or electronically, and the notice posted in a conspicuous place | Monitoring of telephone conversations, email and internet access or usage | Attorney general may enforce; up to $500, then $1,000, then $3,000 for repeat offenses |
| Connecticut General Statutes 31-48d | Prior written notice to affected employees of the types of monitoring, which a posted notice satisfies | Collection of information "on an employer's premises" by means other than direct observation | Labor Commissioner may levy up to $500, then $1,000, then $3,000 |
| Delaware Code Title 19, section 705 | A one-time written or electronic notice, acknowledged by the employee, or a daily electronic notice | Monitoring of telephone conversations, email and internet access or usage | Civil penalty of $100 per violation |
Connecticut limits its definition to monitoring on the employer's premises, and New York and Delaware name phone, email and internet use. A rep's location at check-in isn't plainly covered by any of the three. No ruling we found settles it, and a lawyer should answer it for your states. But the practice all three describe is the one to copy anyway: a written notice, given first, that the employee acknowledges.
Tracking-device laws
California's Penal Code 637.7 bars using an electronic tracking device to determine a person's location or movement. It does not apply when the registered owner, lessor or lessee of a vehicle has consented to tracking that vehicle. The National Conference of State Legislatures lists it as covering devices attached to a vehicle "or other movable thing", and lists many other states with laws on trackers, most of them written for vehicles or stalking.
Two statutes show how these laws treat consent and employers. New Hampshire's RSA 644-A:4 bars placing an electronic device on another person's property to obtain location information "without consent" and says nothing about employers. Florida's section 934.425 bars installing a tracking application on another person's property without consent, and exempts a person acting in good faith for a business for a legitimate business purpose.
The common thread is consent. A rep who installs the app on their own phone, after reading what it collects and agreeing to it, is on much firmer ground than a rep who learns about it later.
Privacy laws that reach employee data
In California, the state attorney general's CCPA page says the exemption for employment-related personal information expired on December 31, 2022, and it lists precise geolocation as sensitive personal information. A business covered by the CCPA must give a notice at collection, which lists the categories of information it collects and why, at or before the point of collection. The CCPA applies only to businesses above its size and data thresholds, so check whether yours is one.
Three levels of tracking, and the trust cost of each
Decide how much location you need before you pick a tool. Most teams need less than they think.
| Level | What you see | Trust cost | Fits when |
|---|---|---|---|
| Check-in only | Where the phone was at the moment the rep checked in, and how far that is from the customer | Low. Reps share one point per visit, at the customer | You need proof that the visit happened and you don't manage the drive |
| Work-hours sharing | Where reps are during the working day, such as the next stop and whether a rep is running late | Medium. It's visible all day, so the reason has to be clear | You dispatch reps, change routes during the day or handle same-day customer calls |
| All-day or always on | Location outside work hours too | High. It includes evenings, weekends and a rep's own errands | Almost never for a rep on their own phone. Avoid it |
Start with check-in only. Move to work-hours sharing only when you can name a job it does that check-in can't, and tell reps what the job is. Don't use the third level for a rep's own phone.
Write the tracking policy before you turn anything on
A written notice protects you under the notice laws above and tells reps where the line is. Keep it to one page, in plain words. Reps should be able to read it in two minutes and repeat it to a customer.
WHAT WE COLLECT The phone's location at the moment you check in at a customer. [If you share all day: and your location during work hours, from ____ to ____, Monday to Friday.] We don't collect location outside work hours or when you're checked out for the day. WHY To confirm that a visit happened at the customer's address and to plan routes. WHO SEES IT Your manager and ____________. Customers never see it. WHAT WE DO WITH IT A check-in far from the customer, a very short visit, or two check-ins in a row get a second look. We ask you about it first. We don't decide anything from one location reading. HOW LONG WE KEEP IT ____ months, then it's deleted. YOUR QUESTIONS Ask ____________. You can ask to see what we have recorded about you. I have read this notice. Name: ____________ Date: ____________
Have each rep sign it or acknowledge it electronically at hire, and for current reps before you switch tracking on. Keep the signed copies. New York and Delaware ask for exactly that acknowledgment when their laws apply.
Use the data to ask a question, not to deliver a verdict
A phone's location is a good clue and a poor witness. The US government's GPS site says GPS-enabled smartphones are typically accurate to within a 4.9 m (16 ft.) radius under open sky, and that accuracy worsens near buildings, bridges and trees. A rep who walks into a warehouse, a hospital wing or a mall office can check in far from the customer's pin.
So use a rule of thumb: a flagged visit is a reason for a conversation. Take three common flags and what each usually means.
| Flag | Often means | First question |
|---|---|---|
| Check-in more than 500 m (about a third of a mile) from the customer | A large site, a wrong pin on the customer record, or checking in from the car park next door | "Where does the door actually sit for this customer?" Fix the address if the record is wrong |
| Check-out in under a minute | A drop-off, a closed door or a check-out tapped by habit | "What happened at this stop?" |
| Check-in within two minutes of the last one | Two customers in one building, or checking in ahead of arrival | "Were these two stops one visit?" |
Those three flags are what Sales Perch raises. Whatever tool you use, tell reps the rule in advance. A rep who knows a 600 m check-in will draw a question checks in at the door. A rep who finds out in a disciplinary meeting doesn't trust the system, or you.
Coach from visit history without micromanaging
Visit history is the best coaching material a field manager has, because it shows what happened at real customers. It turns into micromanagement when the manager reads it for control and not for help. A rule that keeps the line clear: look at patterns over a few weeks, and talk about the account, not the minute.
What to look at each week
- Visits made against visits planned, by tier. Did the biggest accounts get their visits? A rep who hits 90 percent of planned visits but skips the top tier has a different problem from one who misses at random.
- Accounts not seen within their interval. List them by name. Each one is a question about the route, not about the rep.
- Time at the stop, as a range per account type. A regular visit that usually runs 25 minutes and ran 3 is worth one question. One slow day is not.
- Notes. Do they name a person, a product and a next step? A note that says "all good" six visits in a row is a coaching point.
- Customers buying less after a visit. If orders fell after two visits, the notes may show why.
What not to do
- Don't message a rep during a visit because the dot sat still for ten minutes. Meetings run long.
- Don't rank reps on number of check-ins. Reps will check in more often, and the data will get worse.
- Don't use one flagged visit as grounds for discipline. Ask first, and look for a pattern across weeks.
- Don't bring the data to the review as a surprise. Send the list the day before so the rep can add context.
- Don't review anything the rep cannot see. If a number is used in a review, the rep should have seen it first.
Then pick one account per rep per week and talk it through. Read the last three notes together, ask what the customer said that was not in the notes, and agree on one thing to try at the next visit. That conversation does more than a dashboard. Sales coaching for field reps has a longer method, and field sales KPIs defines the numbers above.
A check-in should land on the customer record, with the next step
A location pin by itself tells you where a phone was. It becomes useful when the visit is saved on the customer's record, with the time, the note and what happens next. Then the next rep, the manager and the office can read it without asking anyone.
Look for four things in any tracking tool, and ask to see each in the demo.
- The check-in attaches to the customer, not to a separate location log. Open a customer and see every visit, with the date, the time and how far the check-in was from the address.
- The note is written at check-out and stays with the customer. If a rep leaves, the note stays with your company.
- The next step has a date. A note that says "send a quote" needs a day, or it is forgotten by Thursday.
- The record can leave. If you already run a CRM or an accounting system, check how visits get there: an export, an API or a webhook, and not a retyped copy.
A tracking tool that keeps location in one system and customer history in another gives you two sets of facts that disagree. In Sales Perch, each check-in is saved on the customer with the notes and contacts, and visits can be sent elsewhere by export, the API or webhooks. A field sales CRM keeps the whole history in one place.
Rules that keep the team's trust
- Tell before you track. Reps hear about it from you, in the meeting where you introduce the tool, and not from a colleague.
- Say the reason as a job. "To confirm visits for customers who dispute them" is a job. "For accountability" isn't.
- Track work hours only. No location on evenings, weekends or days off, and a way to switch it off when the rep isn't working.
- Collect the least that does the job. If check-in location answers the question, don't turn on all-day sharing.
- Show reps their own data. Anything a manager sees about a rep, the rep can see.
- Never discipline from one reading. Ask first. Look for a pattern over weeks.
- Set a deletion date and keep to it.
- Use the same rules for every rep, including the top seller.
Does trust matter beyond the legal risk? Yes. Reps who trust the system check in accurately and write notes. Reps who feel watched find ways to look busy, and your data goes bad. For the metrics to count from the data, see field sales KPIs. For the conversation after a flag, see sales coaching for field reps.
Roll out tracking in five steps
- Name the one or two jobs the location data will do, and pick the lowest level of tracking that does them.
- Write the notice from the template above, and have a lawyer who knows employment law in each of your states read it.
- Meet the reps. Explain the jobs, show them what a manager sees, and answer questions before anyone installs anything.
- Collect acknowledgments from every rep, and file them.
- Review after 30 days. Count flagged visits, check how many were wrong pins or large sites, fix those, and tell the team what changed.
Sales Perch is built around the first level. Each check-in saves the phone's location, and a company that wants more can turn on all-day sharing for work hours. You can start a 30-day free trial with your own customers and see exactly what a manager sees before you write the policy. The route planner page shows how planned routes pair with check-ins.