Sales rep visit tracking: plans, proof and supervisor reporting

Why field work drifts out of control

Distribution is built so that all the value is created outside the office. A rep drives to an outlet, talks to the buyer, looks at the shelf, records stock levels, takes an order. The manager only sees the outcome at the end of the day — and even then, in whatever shape the employee chose to present it.

Hence the familiar symptoms in almost every field sales team:

• An opaque day. Nobody knows how many outlets were really covered or in what order, and "I was everywhere" is impossible to check.
• Reports written from memory. Numbers are entered in the evening, backdated and rounded off, so they drift away from reality.
• Phone calls instead of management. The supervisor spends the day asking "where are you now?" and collecting statuses by hand.
• Lost commitments. Promises made to an outlet live in the rep's notebook and leave with them when they quit.

The cause matters here: the problem is almost never dishonest people. The problem is that the process leaves no trace. If a call isn't recorded at the moment it happens, every report becomes a retelling, and the manager ends up managing their own assumptions about the field rather than the field itself.

What exactly to track during a visit

Tracking works when it comes down to a small set of verifiable facts. Padding out the form does damage: the more busywork at the outlet, the worse the data quality. A practical minimum looks like this:

• Proof of presence. The call is opened and closed at a specific outlet, pinned on the map, not reconstructed afterwards.
• Time on site. The gap between arrival and departure shows whether this was real work or a box ticked in passing.
• Outcome. Order taken, refusal, outlet closed, buyer unavailable — a status picked from a list rather than typed as free text.
• Photo proof. Shelf, display, price tags, window — a picture makes conclusions checkable.
• Checklist. The same questions across every outlet: assortment coverage, stock levels, POS materials, planogram compliance.

That set answers the manager's core question: did the call happen, or was it merely reported? A mobile app for the field worker with photo reports and checklists makes this capture part of ordinary work: the rep sets a status on site, answers a handful of questions and attaches a picture — the data lands in the system straight away instead of being retyped at night.

One boundary is worth stating out loud. This is about confirming work and improving data quality, not about watching a person continuously. Rules that are transparent and announced in advance (what we record and why) are accepted by teams without much friction; covert monitoring almost always ends in sabotaged reporting.

Retail route plans: a plan instead of improvisation

Without a call plan there is nothing to check against: any fact can be explained away by circumstances when there is no baseline. So the foundation is retail route plans assigned to each rep — which addresses, on which days, at what frequency.

What a formalised route gives you:

• A baseline for plan versus actual. Once there is a list of outlets for the day, you can see which were covered, which were skipped and why.
• Frequency that holds. A-category outlets stop dropping off the schedule in favour of ones that are closer to home or friendlier to deal with.
• Less driving. A sensible order of addresses frees up time for the work at the outlet rather than the road between them.
• Cover during absences. The route lives in the system, so a colleague picks it up during holidays or sick leave without inheriting a paper notebook.

Planning by hand in a spreadsheet stops scaling the moment the number of outlets grows: nobody is going to re-sequence addresses after every change. This is where route optimisation on the OR-Tools engine helps, taking visit windows and constraints into account — the system builds the sequence, and the supervisor adjusts it where they know the context.

Supervisor reporting: from phone calls to facts

When calls are recorded as they happen, reporting stops being a separate job — it becomes a by-product of the process. The supervisor no longer collects data; they look at it and decide where to step in today.

What such reporting rests on:

• Live routes on a map. You can see where every rep is right now and how they are working through their outlets — no calls, no chasing.
• Plan versus actual by outlet. Skipped addresses and their reasons surface during the day, while the situation can still be fixed.
• Photos and checklists for every call. Disputes are settled by pointing at an image, not by arguing over what someone was told.
• Completion confirmed on site. The outcome is closed at the outlet, so the report holds a fact rather than an evening reconstruction.

This is exactly what the "Distribution management" module in itlogist is built around: assigning outlets to reps, routes on a map, a mobile web interface for the field worker with photo reports and checklists, and live call statuses. There is no need to install anything from an app store — the rep opens a link and immediately sees their route for the day, which makes onboarding new hires and covering a route noticeably easier.

So the data doesn't end up living apart from your accounting, exchange with your working systems is configured on both ends: itlogist works with 1C, AmoCRM, Bitrix24 and Excel — orders and outlets come in from your sources, and results go back without anyone rekeying them.

How to roll this out without alienating the team

Setting up visit capture technically is easier than getting people to use it. Resistance comes not from the interface but from an unclear purpose: people don't know what will happen with this data. So it pays to introduce it in short steps.

• Explain the point before you start. The goal is to take evening reports off the rep's plate and back them up in arguments with an outlet — not to hunt for reasons to dock pay.
• Start with a pilot. One route or one supervisor over two or three weeks is enough to see where the checklist is bloated and where a field is missing.
• Keep the checklist short. Every extra question on site costs you discipline in filling it in across all the calls.
• Observe first, demand later. Use the first period to gather facts and calibrate norms; holding people to targets makes sense once the plan is grounded in real data rather than expectations.
• Don't drag out the launch. itlogist is designed to go live in 7 days with no long-term contracts, so you can test the approach on your own routes quickly instead of running a lengthy implementation project.

Scale is the other thing to check. The tool has to fit your team: itlogist works for teams of 5 to 100 field workers, which covers both a small field sales unit and a growing structure with several supervisors.

Checklist: your visit tracking is up and running

A short self-check. If every line is ticked, the manager is running the field on facts rather than on retellings:

• The plan exists. Every rep has assigned outlets with a frequency and a driving order.
• Facts are captured on site. Start and finish are marked at the outlet, not backdated.
• Outcomes are standardised. Statuses come from a list rather than free-text descriptions.
• Evidence is attached. A shelf photo and a filled checklist sit with the record.
• Reporting builds itself. The supervisor sees plan versus actual and the map during the day instead of merging spreadsheets at night.
• Nothing is lost. Outlets and results are exchanged with your accounting system and CRM without manual entry.
• The rules are public. The team knows what is recorded and how that data is used.

Start with two items — an outlet plan and on-site capture of the facts. They pay off fastest: as soon as you have an honest picture of the day, every other decision (norms, outlet categories, route allocation) is made on data and stops being an argument.