How to know your rep actually visited the customer

Monday morning the sheet says fourteen visits. The uncomfortable question is a different one: did they happen, at the customer's place, in the order the route called for? Most arguments between supervision and the field start right there, in the gap between what gets reported and what can be checked.

A sheet is memory, not evidence

A report written at the end of the day isn't a record — it's a recollection. It gets filled in the car, in a hurry, and it tidies the day into the shape the rep believes it had. There's no bad faith in that; there's fatigue. The problem starts when that recollection is the only thing the company has when it sets routes, quotas and commissions.

And it decides a lot. That sheet builds next month's route, settles the argument about why a territory isn't growing, and splits the quarterly bonus. When the input is memory, everything built on top inherits its margin of error — and nobody knows how big that margin is.

What leaves a trace and what doesn't

The difference between a checkable visit and a reported one has nothing to do with the rep's honesty. It has to do with whether logging it took five seconds or meant opening a notebook at night.

• Leaves a trace: the order taken on site, the time the customer's file was opened, the place the visit was logged from, the photo of the display, the receipt for a partial payment.
• Leaves nothing: the visit written down three hours later, the customer who "wasn't there" with no note saying why, the purchase commitment agreed verbally, the route changed over the phone and never written down.

The second list isn't anyone's fault. It's what happens when the tool asks the rep for extra work on top of selling. If logging costs more than remembering, people remember.

Three signals worth checking every week

You don't need to audit every visit. Looking at three patterns once a week is enough to tell whether the operation is healthy or whether something needs fixing before it becomes a habit.

1 · Visits logged in a block

Eight visits entered between 6:40 and 6:48 p.m. aren't eight visits — they're one report written in a single sitting. All eight may well have happened, but the timestamps are worthless and the detail of each stop is gone. It's the easiest signal to spot and the fastest to fix.

2 · Repeated no-sale visits to the same customer

Two in a row is normal. Four in a row is a conversation you owe someone: either the customer stopped buying and nobody said so, or the call frequency is wrong, or there's a credit problem the rep would rather not report. None of the three gets solved by going back again.

3 · Distance between stops

If the route order forces the rep to cross town twice in one day, the problem isn't the rep — it's the route. That lost time shows up on no sheet anywhere, but it gets paid in full, in visits that never happened.

The point isn't to watch the rep. It's to build Tuesday's route out of Monday's data instead of Monday's recollection.

The mistake of turning it into surveillance

There's a sure way to make this go wrong: present it as monitoring. If the team understands that location is stored to catch them out, they'll learn to work around it, and the data you get afterwards will be worse than the sheet — because now it will also look trustworthy.

What works is the opposite. Logging has to save the rep work — the order is taken once, not copied out at night — and the time and place come out of that act on their own. Nobody has to report anything extra. When a rep gains half an hour a day, they stop arguing about where the data comes from.

And it's worth saying out loud: the data exists to build better routes and to keep commissions out of dispute, not to point fingers. A team that understands why something is measured cooperates; a team that doesn't, defends itself.

What changes in Tuesday's conversation

This is the part you feel. The supervisor comes in on Tuesday, sees Monday's route laid out, and instead of asking "did you go?" asks "what happened with these three who didn't buy?". The first question puts the rep on the defensive. The second puts both of them on the same problem.

It's a different conversation, and it's the one that moves the number. The first spends the meeting arguing about the past; the second decides what happens on Wednesday.

How to start without breaking anything

You don't have to change the whole process at once. Three steps are enough to have checkable data within a month:

• Take the order at the customer, on the phone, even with no signal. That alone takes time and place out of the hands of memory.
• Log the no-sale visits too, with a two-tap reason: not there, didn't buy, closed, over credit limit. Without that, half the rep's day is invisible.
• Review the three signals once a week, with the team in the room rather than behind their backs. What gets looked at together gets fixed; what gets looked at in secret gets hidden.

What you get

In the end the real change isn't about control, it's about the calendar: you stop auditing last week and start fixing next week. The route is built from what actually happened, the quota gets discussed with numbers both sides recognize, and the quarterly bonus stops being a fight over interpretations.

That's what the question is really after when someone asks whether the rep visited the customer. It isn't distrust. It's wanting to make Tuesday's decision on something firmer than Monday's memory.