Route Density / Stops-Per-Day Calculator

Cross-trade capacity calculator: enter workday length, fixed overhead, service time, and drive time per stop to get daily stops, drive-time share, and optional revenue.

Service type:
Your day

Total paid shift. e.g. 8

Lunch + morning load + end-of-day admin. e.g. 60

Per stop

On-site time per stop (minutes). e.g. 20

Avg travel between consecutive stops. e.g. 10

Show revenue & monthly capacity

Optional. Gates the revenue estimate.

Optional. Gates the monthly roll-up.

Multiplies the monthly roll-up.

Achievable stops

stops per day, per technician

Productive minutes / day workday − fixed overhead
Minutes per stop cycle service + drive per stop
Drive-time share of day drive minutes ÷ productive day
Daily revenue / tech stops × avg ticket
Monthly capacity — stops stops × working days × techs
Monthly capacity — revenue monthly stops × avg ticket
Export
How this is calculated

The estimate is a bottom-up stop-cycle model. Subtract your fixed daily overhead from the paid workday to get productive minutes, divide by the time one stop takes (service + drive), and round down — you never count a stop you cannot finish.

productiveMin   = workdayMin − fixedOverheadMin     (workdayMin = hours × 60)
cycleMin        = serviceMin + driveMin
stops/day       = floor(productiveMin ÷ cycleMin)
driveShare      = (stops/day × driveMin) ÷ productiveMin
dailyRevenue    = stops/day × avgTicket
monthlyStops    = stops/day × workingDays × techs
monthlyRevenue  = monthlyStops × avgTicket
sensitivity     = floor(productiveMin ÷ (serviceMin + max(driveMin − 5, 0))) − stops/day

Round down, always. Capacity is a physical ceiling; a fractional stop is no stop. The monthly roll-up floors the daily count first, then multiplies by working days and technicians.

Drive time is the dominant lever. The sensitivity hint shows what shaving 5 minutes of drive between stops would add — on a typical general-pest route, one or two more stops per day. A drive-time share above 40% of the productive day triggers an advisory flag; it never caps the computed stops/day.

Sources: ServiceWorks technician-utilization / capacity model (productive ÷ available); CalcMyBid "5–7 productive hours/day" anchor; Pest Control Millionaires route-efficiency bands (12–18 stops/day, $800–1,200/route, for general pest). Lawn and pool preset defaults require separate figure research — those chips are blank until sourced.

Route density is the term for what this page measures: how tightly the stops sit, and therefore how many of them a day can hold. What each of those stops is worth moves with average ticket, which is why a tighter route and a bigger ticket are two different answers to the same shortfall.

Two neighbouring tools work the same ground from a different angle. The stops per day capacity estimator carries pest trade benchmark bands, and the production rate and job time estimator works out the per-property service minutes this model asks you to supply.

Turning the ceiling into a schedule is the job of the route day planner, and the drive minutes this model is so sensitive to cost real money, which the vehicle cost per mile calculator quantifies per mile.

Sources

  1. Technician Utilization & Capacity Calculator. ServiceWorks. Retrieved .
  2. Billable Hours: How Many Are Realistic?. CalcMyBid. Retrieved .
  3. How to Improve Route Efficiency in Pest Control. Pest Control Millionaires. Retrieved .

Get early access

Fieldwynn is the field-first app we are building for small crews — simple in the truck, powerful in the back office. It is not out yet; join the early-access list and be first when it launches for your trade.