Field sales benchmark 2026: what 3,508 planned routes from 107 teams say about the working day.

Why a field sales benchmark built from routes

Most numbers quoted about outside sales come from surveys: reps and managers estimating how many calls they make and how long they drive. Estimates drift in a predictable direction. A route plan does not estimate. It lists the stops, orders them, and a routing service returns the kilometres and minutes between them. Aggregate enough of those plans across enough teams and you get a picture of the field day as it is designed on the morning it starts.

That is what this page is: 3,508 routes planned by 107 teams over twelve months, reduced to medians and quartiles. It is written for the sales manager running 20 to 100 reps, and each figure is translated once into team arithmetic, marked as a model.

The typical planned route, in six measures

The chart below is the core of the benchmark. Each row shows one measure of a route. The pale band is where the middle half of routes fall, from the 25th to the 75th percentile. The filled dot is the team median, the ring is the pooled median.

Read across the rows and a typical day takes shape. A rep plans roughly 8 to 10 stops, drives 75 to 93 km (47 to 58 miles) to reach them, spends 107 to 114 minutes behind the wheel and plans about four hours (232.5 to 240 minutes) at the stops themselves. That is close to six hours of planned field time before breaks, admin and the drive home from the last stop.

The bands matter as much as the medians. The middle half of routes runs from 6 to 22 stops and from 21 to 198 km. A route of 22 short stops in one postcode and a route of 6 long stops across a region are both normal field sales, and a benchmark that only printed one average would describe neither. If your team sits inside the band, it is typical. If it sits outside, that is not automatically bad, but it is worth knowing why.

The complete benchmark table. Medians do not multiply into each other: the median route is not made of median stops, which is why 7.8 stops times 8.2 km does not equal 93.2 km. Use each row on its own.

Driving takes about 30 percent of the planned field day

Take the minutes a rep plans to drive and the minutes a rep plans to spend at stops, and ask what share of the total goes to the car. At the team median the answer is 29.7 percent; pooled across routes it is 27.4 percent. Put differently, of every planned hour in the field, around 16 to 18 minutes are driving.

The quartiles are where this gets useful for a manager. A quarter of routes spend 13.4 percent or less of their planned time driving: dense territories, stops close together, long visits. Another quarter spend 41.6 percent or more: rural territories, short visits, or routes where the stop order was never questioned. Geography alone can put two similar teams at opposite ends, so compare your team against itself over time, with this band as the outside reference.

Team arithmetic (model). Assume a team of 20 reps each running one planned route per working day, five days a week, at the team median of 114 drive minutes per route. That is 100 routes and 11,400 drive minutes a week: 190 hours in the car, the equivalent of 4.75 full 40-hour weeks. At 50 reps it is 475 hours, at 100 reps 950 hours. Every 10 minutes taken out of the average route is worth 16.7 hours a week for 20 reps and 83.3 hours for 100.

Model, not measurement: one route per rep per working day and the team median of 114 drive minutes are assumptions for illustration. Replace them with your own route count and drive time.

Distance per stop: 6 to 8 km

Spread the route's kilometres over its stops and the typical stop costs 6.0 km (pooled median) to 8.2 km (team median) of driving, or 3.7 to 5.1 miles. In time, that is 9.0 to 10.8 minutes of driving per stop. The quartiles run from 1.7 km to 15 km and from 3.3 to 18.6 minutes.

Kilometres per stop is the cleanest single measure of territory density, and it is the number most directly shaped by how accounts are assigned. A rep whose accounts are scattered across two regions cannot get below the upper quartile no matter how well each day is ordered. A rep with a compact patch and a sensible visit sequence lands near the bottom of the range without trying. That is why this figure belongs as much to territory management as to routing.

Team arithmetic (model). At the team median of 7.8 stops per route, 20 reps running five routes a week plan 780 stops a week; 100 reps plan 3,900. Every kilometre removed from the average stop is then 780 km a week for the 20-rep team, and every minute removed per stop is 780 minutes, or 13 hours a week. For 100 reps the same minute is worth 65 hours.

Model: 7.8 stops per route and five routes per rep per week are assumptions. The per-stop and per-route medians are measured separately and do not sum to each other.

8 to 10 stops per route

The team median route has 7.8 stops, the pooled median 10. The difference between the two is itself a finding: teams with many routes tend to plan more stops per route than the median team does. The middle half of all routes carries between 6 and 22 stops.

Stop count differs most by sales motion: 22 stops means short visits in a tight area, 6 stops looks more like account management with longer meetings. The benchmark does not split by industry, so read your own figure against the band.

Team arithmetic (model). For a manager, stops per route is the capacity number. At 7.8 planned stops a day, a rep covers about 39 planned stops a week. If a territory holds 400 accounts that each need a visit every four weeks, that is 100 visits a week, or about 2.6 reps of capacity at the median. Moving the same team from 7.8 to 10 stops per route, the pooled median, is 28 percent more planned visits without a new hire. Whether that is achievable depends on the drive share above: extra stops only fit where driving time is freed.

Model: account count and visit cycle are illustrative; 39 stops a week assumes five routes at 7.8 stops. Turning stop counts into daily routes is what a sales route planner is for.

Tuesday is the strongest day, Friday the weakest

Routes are not spread evenly across the week. In the pooled sample of 763 routes, Tuesday carries 194, a quarter of the week. Monday follows with 172, then Wednesday with 141 and Thursday with 138. Friday carries 94, about half of Tuesday. Weekends together account for 24 routes.

The shape is a front-loaded week. Monday and Tuesday together hold 48 percent of all routes; Thursday and Friday together hold 30 percent. The data shows the pattern, not the reason behind it.

Team arithmetic (model). Apply these shares to a team that runs 100 routes a week and the week reads roughly 23 on Monday, 25 on Tuesday, 18 on Wednesday, 18 on Thursday and 12 on Friday. If the team's routes are capacity-limited on Tuesday and slack on Friday, the cheapest capacity in the building is Friday: moving routes from Tuesday to Friday adds visits without adding reps. Check your own distribution first. A team that already runs level across the week has no such reserve.

Model: 100 routes a week distributed by the benchmark shares, rounded. Your team's own weekday split is the number to compare.

One planned stop in three: how often reps depart from the plan

When a rep drives a planned route in Lead Mapper's drive mode, each stop is marked done or skipped. Across 3,984 such events from 32 teams, the median team (22 teams with at least 10 events) marked 37.2 percent of stops as skipped. Pooled over all events the figure is 51.8 percent, pulled up by the teams with the most events.

This number needs careful reading. Skipped does not mean the customer was not seen. A stop can be skipped because the visit moved to another day or the rep reordered the route on the road. What the figure does say is that at about one planned stop in three, the day did not go as planned. The morning plan is a starting point, not a script, and a route tool that cannot absorb change is only right for two thirds of the day.

Team arithmetic (model). At 780 planned stops a week for 20 reps, 37.2 percent is about 290 stops a week where the plan changed; at 100 reps, about 1,450. If even a fraction of those are visits that were never rescheduled, they are the accounts that quietly go uncovered. The practical question for a manager is not how to push the figure to zero but whether every departure is recorded somewhere a manager can see it.

Model: 780 planned stops a week (20 reps, five routes, 7.8 stops) times the team median of 37.2 percent. Drive-mode events cover 32 of the 107 teams, so this measure rests on a smaller base than the route figures.

What the field sales benchmark means for a team of 20 to 100 reps

The five numbers condense into one weekly picture. For a team running one route per rep per working day at the benchmark medians:

Model built from the team medians on this page. Five routes per rep per week is an assumption; kilometres and stops are computed from separate medians and should not be combined with each other.

Three things follow for a manager. First, the drive share is the lever with the largest absolute size: at 20 reps, 190 hours a week sit in the car, and any change to it is multiplied by every route. Second, distance per stop is decided before the day starts, by how accounts are grouped into territories. Third, the plan changes at about a third of stops, so the question worth asking about any sales routing software is how it behaves after the first change, not how good the morning plan looks. Our field sales software comparison and the field sales software price index cover what the tools themselves cost and offer.

Methodology of the field sales benchmark

What was measured. Routes planned in Lead Mapper between October 2025 and September 2026 (September up to the day of calculation, 27 September 2026). A route is a dated, ordered list of stops. Drive time and distance come from the routing service that computes the route when it is planned, and the planned time at each stop comes from the rep or the team's settings. These are plans, not GPS recordings of what was actually driven.

What was excluded. Demo, test and our own internal teams; routes with fewer than two stops; routes without a drive time; and routes of more than 1,500 km, which are almost always planning errors or multi-day trips entered as one route. After exclusions, 3,508 routes from 107 teams remain.

Why two medians. A single team contributed a large share of all routes. A plain median over every route would therefore mostly describe that one team. The team median solves this by first taking the median of each team with at least 3 routes (38 teams) and then the median of those team medians, so every team counts once. The pooled median keeps route-level detail but caps each team at 100 randomly drawn routes, 763 routes in total. The quartiles (p25 and p75) and the weekday split are taken from this pooled sample. Where the two medians agree, the figure is stable. Where they differ, as with stops per route, the gap tells you something about how the heaviest users plan.

Plan departures. Drive mode records each stop as done or skipped: 3,984 events from 32 teams. The team median uses the 22 teams with at least 10 events.

Privacy. Only aggregates are published. No figure on this page describes a single team, customer or location.

What this benchmark does not measure

It is not GPS. Traffic, parking, detours and stops added during the day are not in a plan, so actual driving can differ from the planned figures shown here.

It is not a random sample of all field sales. It describes teams that plan their routes in Lead Mapper, which skews towards teams that plan routes at all. There is no split by industry, company size or country.

It does not measure outcomes. There is no revenue, win rate or order value in this data, so nothing here says which kind of day sells more. It describes how the field day is built, not what it earns.

Planned stop time is only reported per route. The per-stop field did not reconcile with the route totals, so it was left out rather than published with a caveat.

How to cite this data

The figures on this page are free to quote in articles, reports and presentations. Please name the source and link to this page so readers can find the methodology.

Short form: Source: Lead Mapper Field Sales Benchmark 2026, lead-mapper.com/field-sales-benchmark. When quoting a single number, please keep the qualifier that goes with it: "planned" for drive time and distance, and "departed from the plan" rather than "missed" for skipped stops. If you need a figure that is not on this page, such as a different cut of the data, get in touch through the contact form.

FAQ

How much time do field sales reps spend driving?

In the Lead Mapper Field Sales Benchmark 2026, driving takes about 30 percent of the planned field day: the team median is 29.7 percent of drive time plus planned time at stops, the pooled median 27.4 percent. The middle half of routes sits between 13.4 and 41.6 percent. These are planned routes with drive times calculated by a routing service, not GPS tracks.

How many stops does a field sales rep make per day?

A planned route has 7.8 stops at the team median and 10 at the pooled median, so 8 to 10 stops is the typical day. The spread is wide: the middle half of routes runs from 6 to 22 stops.

How far do field sales reps drive between stops?

The benchmark puts distance per stop at 8.2 km (5.1 miles) at the team median and 6.0 km (3.7 miles) at the pooled median, with 10.8 and 9.0 minutes of driving per stop. A whole route is 93.2 km (57.9 miles) at the team median and 75 km (46.6 miles) pooled.

What is the busiest day of the week in field sales?

Tuesday. Of 763 routes in the pooled sample, 194 were planned for a Tuesday, 172 for a Monday, 141 for a Wednesday, 138 for a Thursday and 94 for a Friday. Friday carries about half of Tuesday's volume; weekends together account for 24 routes.

How often do field reps depart from the planned route?

At about one planned stop in three. Among 22 teams with at least 10 drive-mode events, the median team marked 37.2 percent of stops as skipped. Pooled over all 3,984 events from 32 teams the figure is 51.8 percent. Skipped means the rep left the plan at that stop, not necessarily that the customer was never seen.

Where does the field sales benchmark data come from?

From 3,508 routes planned in Lead Mapper by 107 teams between October 2025 and September 2026, after removing demo, test and internal teams, routes with fewer than two stops, routes without drive time and routes over 1,500 km. Only aggregates are published; no team, customer or location is identifiable.

Can I use these numbers in an article or presentation?

Yes. Quote the figure, name Lead Mapper Field Sales Benchmark 2026 as the source and link to https://lead-mapper.com/field-sales-benchmark. A ready-made citation sentence is on this page.