Rep Route Planning: From Spreadsheet to Map

Route planning means deciding in advance which customers each rep visits, in what order, and how often. The working method: divide your territory into zones, classify customers (A/B/C) with a visit frequency per class, check that rep capacity covers the required visit load — then review planned-vs-actual every week.

Most distributors run routes from a spreadsheet and a supervisor's memory. The sheet says "Route 4 — Tuesday," but nobody knows who was actually visited, or why a customer hasn't seen a rep in two months. This is an operator playbook for moving routes from paper to a system. The same logic applies whether you run pre-sales or van sales; the product side is covered in full on our distribution page.

Why does spreadsheet route planning break down?

A spreadsheet records intent, not reality. The supervisor writes customer names under weekdays, the rep drives off — and the thread is cut. The sheet doesn't know which visits happened, how long they took, or whether an order came out of them. Field management collapses into phone calls and evening reports written from memory.

The second failure: nobody builds the capacity math into a route sheet. Excel can calculate anything, but a sheet of names under weekdays carries no visit-load model — add thirty customers and nothing warns you that Tuesday's route now exceeds what one rep can physically do. When a rep quits, his customers get redistributed by guesswork. The third failure is isolation — the visit lives in one file, the order in another, collections in a third, so nobody can answer a basic question like "what share of this week's visits ended in a sale?" We compared the two approaches line by line in Tawrida vs. Excel spreadsheets.

How do you divide a territory into zones?

A zone is a geographic patch owned by one rep; a route is one day's visit sequence inside that zone. Zones come first. Put your customers on a map — literally, even pins on a paper map — and draw boundaries so each zone is one contiguous block a rep can cover without crossing the city back and forth.

Three rules govern the cut. First, natural boundaries beat tidy lines: a highway or a canal separating two zones is better than an imaginary border a rep must cross daily. Second, balance zones by required visit load, not by customer count or area — a zone with fifty active accounts can demand more effort than one with a hundred dormant ones. Third, keep the rep fixed on the zone. The relationship with the shop owner is a commercial asset built by repetition, and rotating reps monthly demolishes it.

How do you set visit frequency by customer class?

Customers are not equal, so their visits shouldn't be either. Classify accounts by the last three months of actual sales from your own books: class A is the small group producing most of your revenue, class B the steady middle, class C the small and irregular tail. Rank by real value, never by impression — impressions flatter the loudest customer, not the largest one.

Then attach a frequency to each class. A simple starting pattern: A weekly, B every two weeks, C monthly — then adjust for your product's purchase cycle; a fast-turning SKU may justify visiting class A twice a week. The hard discipline is cutting class-C frequency, not adding to class A: every visit to a small account is paid for with time taken from a large one. Re-run the classification quarterly, because a growing B customer deserves the upgrade before your competitor notices him first.

How do you do the coverage math?

This is the most important calculation in the whole file, and it runs on your numbers, nobody else's. Capacity: a rep's realistic visits per day — taken from your own field data, not from wishful thinking — multiplied by working days per month. Required load: each class's customer count times its monthly visit frequency, summed.

A worked example with illustrative figures: 500 customers — 80 class A × 4 visits = 320, 170 class B × 2 = 340, 250 class C × 1 = 250. Required: 910 visits per month. A rep averaging 25 visits over 24 working days delivers 600. You need one and a half reps' worth of capacity: hire a second rep, cut class-C frequency, or prune the base. A names-under-weekdays sheet has nowhere to show this deficit. You discover it months later as class-C accounts nobody has visited — and they are always the first to churn silently.

What is planned-vs-actual, and why is it the core of field management?

The plan is half the picture; what actually happened is the other half. Planned-vs-actual is the daily comparison between the drawn route and the visits that occurred: who the rep visited, who he skipped, who he added off-route. Without it, the plan stays an essay and rep evaluation stays a matter of opinion.

Read it for pattern, not for violations. A rep skipping the same customer every week is usually a customer problem — a debt dispute, refused deliveries — which is commercial intelligence worth a supervisor's intervention, not a demerit. Heavy off-route activity means either the route is drawn far from reality and needs redrawing, or the rep is selling where he's comfortable instead of where he's assigned. In Tawrida, supervisors see planned versus actual visits as the day unfolds — not in an evening report reconstructed from memory. Details on the distribution page.

How do you verify a visit actually happened?

Every sales manager knows this question and dislikes asking it out loud: did the rep visit the customer, or log the visit from a café? Paper cannot answer it. The modern answer is location: the visit is recorded from an app in the rep's hand, so the record carries a place and a time instead of a word written at day's end.

The real value is not catching a cheat. It is protecting the diligent. When visits carry place and time, rep evaluation stops being an argument and becomes a reading, and the rep who ground through a full route on a hard day has the record to show for it. In Tawrida, supervisors follow trucks and visits on a live map during the day, so they know where the field stands without a single phone call. And if you run van sales, the truck is a real stock location — loaded, sold from, and reconciled — covered under inventory management.

What should you measure weekly?

One weekly meeting with five numbers is enough — provided the numbers come from the system, not from manual collation:

1. Coverage rate: customers actually visited ÷ customers planned. This is the health number of the plan itself.
2. Route adherence: visits done on their planned day ÷ total visits. Chronically low means the routes need redrawing, not the reps need shouting at.
3. Strike rate: visits that produced an order ÷ total visits. Low strike with high coverage means the rep is passing by, not selling.
4. Average order value per productive visit: exposes shallow selling — a token line or two to silence the visit.
5. Customers unvisited beyond their frequency: your neglect list, and the quiet channel through which accounts churn.

Start with these five. Compare each rep against his own trend across weeks before comparing him to colleagues — zones are never identical.

FAQ

What is the difference between a zone and a route? A zone is a geographic patch owned by one rep, containing all his customers. A route is one day's visit sequence inside the zone. Zones change rarely; routes get reviewed regularly as the customer base and visit frequencies shift.

How many customers fit on one route? There is no universal right number. The right number derives from your own data: your reps' actual average visits per day, set against the load implied by your classification and frequencies. Any ready-made figure from outside your operation is a guess.

Should reps plan their own routes? Structure is drawn centrally — zones, frequencies, and balance are management decisions that need visibility above rep level. But listen to the rep on within-day sequencing: he knows which trader won't receive in the morning. Central plan, documented daily flexibility.

How often should routes be redrawn? Re-run classification and frequencies quarterly, and revisit routes at every material change: a wave of new customers, a departed rep, a zone outgrowing its rep. Weekly is for monitoring; quarterly is for redrawing.

Do pre-sales and van-sales routes differ? The logic is identical: zones, classification, frequency, coverage math. Van sales adds a load constraint — you can only sell what was loaded that morning — so the loading mix shapes route design, and reconciling truck stock becomes part of closing the day.

Do I need software to start, or is paper classification enough? Start today with what you have: classify customers and run the coverage math on any tool. But planned-vs-actual and visit verification cannot run on paper, because paper records intent, not reality — and that is precisely where the spreadsheet ends and the map begins.