← All posts
Field service operationsRoute optimizationMay 11, 2026Clint Research Team

How to Improve Route Density in a Field Service Business

Route density is stops per hour of drive time. A pool service tech at 3.5 stops per hour adds $440-$550 in daily route revenue over a tech running 2.8. Here is how to calculate it, what kills it, and how to fix it.

10 min read

Key takeaways

  • Route density is total stops in a period divided by total hours in the field including drive time, not just service time
  • A pool service tech improving from 2.8 to 3.5 stops per hour adds 4-5 stops per day, worth $440-$550 in additional route revenue per day at $110 per stop
  • The three primary causes of low route density are geographic churn gaps, scheduling by customer time preference rather than location cluster, and emergency call insertions that break planned routes
Contents
  1. 01How to Calculate Route Density
  2. 02What Causes Low Route Density
  3. 03How to Improve Route Density
  4. 04The Financial Impact
  5. 05Which CRMs Support Route Optimization
  6. 06How Clint Surfaces Route Density Data
  7. 07Sources
  8. 08Frequently Asked Questions

Route density is the number of job stops per hour of field time, including drive time, and it is the primary operational efficiency metric for any route-based home service business. A pool service tech running 3.5 stops per hour earns more gross margin per day than a tech running 2.5 stops per hour even though labor cost is identical. The difference is pure output.

For route-based businesses (pool service, pest control, cleaning routes, lawn care, window washing), route density is the metric that separates a profitable route from a money-losing one. For dispatch-based businesses (HVAC, plumbing, electrical), it measures how efficiently jobs are grouped geographically when scheduling. The principle is the same: drive time is cost, stops are revenue.

Most field service owners know they have a routing problem. Few have measured it at the stop-per-hour level, which means they are managing a symptom (long days, tired techs, thin margins) instead of the actual variable (stops per drive hour). See how to track technician utilization rate for the parallel utilization metric.

How to Calculate Route Density

The formula is straightforward:

Route density = Total stops completed / Total hours in the field

Total hours in the field = clock-out time minus clock-in time for the route,
including all drive time between stops

Do not exclude drive time. That is the point. A tech who completes 20 stops in 8 hours has a density of 2.5. A tech who completes 28 stops in 8 hours has a density of 3.5. Same shift, same labor cost, 40% more output.

Calculate it per tech, per route, per week. Aggregate to a company number second. The per-route view is where the problems live.

Data inputs you need: job start time and end time (from the CRM or scheduling software), plus GPS or reported clock-in/clock-out for the day. Most field service CRMs (Jobber, Housecall Pro, ServiceTitan, Workiz) have job timestamps. The calculation is a report query, not a new tracking system.

Text Clint: "what is my average stops per hour by route this week, excluding travel to the first job and from the last job home?"

Industry benchmarks by trade:

  • Pool service, well-run route: 3.5-5 stops per hour. Below 2.5 is a density problem.
  • Pest control, residential: 3-5 stops per hour depending on service type (interior service is slower than exterior spray).
  • Residential cleaning crew: 2-3 jobs per day depending on home size (a cleaning "stop" is measured differently because job duration varies by 2-4 hours).
  • Lawn care: 5-8 residential stops per day per crew for a full-service route.
  • Window washing: 2-4 stops per day, highly variable by property size.

What Causes Low Route Density

Three causes account for the majority of route density problems in a $1M-$10M field service business.

Cause 1: Geographic churn gaps

When a customer cancels and you do not backfill that stop with a new customer nearby, the tech's route develops a hole. They still drive through that area (for surrounding customers), but they have dead time in the middle of the route with no revenue. A pool route with 30% annual churn that is not actively backfilled will develop 6-10 geographic gaps per year. Each gap adds 10-20 minutes of dead drive time per week.

The fix: when a cancellation comes in, immediately identify which existing customers are within 0.5-1.0 miles of the cancelled address. That is your win-back and growth target for the next 4-6 weeks. Marketing to the surrounding addresses is faster and cheaper than acquiring customers in a new geography. See how to win back lost customers for the lift on cancellations themselves.

Cause 2: Scheduling by customer time preference instead of geographic cluster

This is the most common cause in dispatch-based businesses. A plumber's dispatch board for Tuesday might look like: 8am in the northeast, 10am in the southwest, 12pm in the northeast, 2pm in the southwest. Two round trips across the service area in one day. The driver of this pattern is booking jobs when customers request them rather than routing the board by geography first.

The solution is offering customers two time windows (morning or afternoon) and filling each window with geographically adjacent jobs. Customers accept this more often than owners expect because the real constraint is usually "morning" or "afternoon," not the exact hour.

Cause 3: Emergency call insertions

Emergency calls break planned routes. When a tech is pulled off a route to handle an emergency, the remaining route jobs either run late (frustrating other customers) or get rescheduled (costing the route a stop). In pool service and pest control, emergency calls are rare enough that this is a minor factor. In HVAC and plumbing, this is a daily reality in summer and winter peak seasons.

The fix is a separate emergency allocation. If you average 2-3 emergency calls per day, keep one tech unscheduled before noon to absorb them rather than pulling route techs. The math: keeping one tech on emergency standby costs half-day wages. Pulling a route tech costs the full disruption to the route plus rescheduled customers. See how to schedule HVAC technicians for the scheduling pattern that absorbs these.

Text Clint: "for the last 30 days, which routes had the lowest stops per hour and what was the geographic distribution of their stops versus routes with higher density?"

How to Improve Route Density

Cluster scheduling by zip code, not by time preference

Pull your active customer list and plot it by zip code or neighborhood. Build routes around geographic clusters rather than customer-requested times. Most field service CRMs have territory assignment or route-building features. The discipline is keeping the dispatch board organized by cluster rather than by first-come-first-served booking.

For pool service and pest control, this means assigning routes by day of week geographically: Monday is the north side, Tuesday is the east side. Do not mix geographies within a day.

For dispatch trades, this means clustering appointment offers: "We have morning availability in your area on Thursday." The offer is clustered, the customer picks from within the cluster.

Backfill churn with hyper-local marketing

When a customer cancels, the highest-probability replacement is a neighbor who has the same need and can fill the same geographic slot in the route. Door hangers, direct mail, and digital ads geofenced to a 0.5-mile radius around a cancelled customer's address are the standard backfill tactic.

The data to power this: your CRM knows which addresses recently churned. Your marketing needs to target the surrounding block automatically, not wait for the owner to manually identify the gap.

Use route optimization software for planning

Route optimization software (OptimoRoute, Route4Me, the routing module in your field service CRM) reduces total drive time by 15-25% on routes with 15+ stops per day. The gains are not magic: they come from eliminating backtracking and right-turn-heavy routing. The ROI is straightforward: 15% reduction in drive time on a 7-hour route frees up 63 minutes for additional stops.

For a pool route at 3.5 stops per hour, 63 additional minutes = 3-4 additional stops = $330-$440 in additional daily revenue per tech.

Text Clint: "which of my routes this month had the most backtracking based on job address sequence and time between stops?"

The Financial Impact

The math is direct. Take a pool service business with 4 techs, each working a 7-hour route at $110 per stop.

Current state: 2.8 stops per hour average = 19-20 stops per day per tech. Target state: 3.5 stops per hour = 24-25 stops per day per tech. Difference: 4-5 additional stops per day per tech. Revenue per tech per day: 4-5 stops × $110 = $440-$550 additional. With 4 techs, 5 days per week: $8,800-$11,000 in additional weekly revenue.

The labor cost does not change. The vehicle does not change. The tech's shift does not change. The only variable is the sequence and geography of the stops. At 50% gross margin, the $8,800-$11,000 weekly revenue gain delivers $4,400-$5,500 in additional weekly gross profit.

Annually: $228,800-$286,000 in additional gross profit from route efficiency alone. For a business doing $1.5M per year, that is a 15-19% gross profit improvement from scheduling discipline. See job profitability for home services for where this gross profit lift shows up at the job level.

The route density improvement does not require any new customers. It extracts more value from the customer base you already have.

Text Clint: "calculate the revenue impact if I improve each route's stops-per-hour from current average to 3.5 stops per hour"

Which CRMs Support Route Optimization

All major field service CRMs have some route-building capability. The depth varies.

Jobber: Map view with route sequencing. Drag-and-drop reordering. Does not auto-optimize; it shows you the map and you organize manually or use the sequence tool.

Housecall Pro: Route view with auto-suggest for efficient sequencing on the dispatch board. The route wizard will recommend an efficient order for a set of scheduled jobs in a given area.

ServiceTitan: More sophisticated dispatch board with zone management and drive-time visibility. Enterprise tier has more routing intelligence. Flat-rate focused, so routing is secondary to job value.

Workiz: Route and map features are included. Similar to Jobber in capability. Better for smaller route-based businesses.

OptimoRoute / Route4Me (dedicated tools): If you are running 20+ stops per day per tech and route optimization is your primary lever, a dedicated routing tool will outperform any CRM's built-in features. Import your scheduled jobs, get an optimized sequence, export back to the CRM.

The CRM question is secondary to the data discipline question. The best routing tool in the world cannot fix a schedule that mixes geographies because booking is done on customer time preference. The scheduling process has to change first.

Text Clint: "how many miles per stop are my techs driving this week versus last month, by route?"

How Clint Surfaces Route Density Data

Clint pulls job timestamps, addresses, and tech assignments from your CRM and calculates stop-per-hour density at the route and company level without a custom report. You ask "what is my route density this week?" and get a breakdown by tech and route, including which routes are underperforming the benchmark for your trade.

Clint can also cross-reference churn location with current route gaps to identify which addresses to target for backfill marketing. The query runs against your actual customer and job data.

You do not need to export to a spreadsheet or build a BI dashboard. The data is in your CRM. The question is whether you can get to it in 10 seconds or whether it takes an afternoon.

Sources

Frequently Asked Questions

4 questions home service owners actually ask about this.

  • 01How do I account for service time variation when calculating route density?

    If service time varies significantly by job type (a 20-minute maintenance visit versus a 90-minute repair), track them separately. Calculate density for maintenance-only days and repair-heavy days as separate cohorts. Mixing them distorts the number. Most route-based businesses have a dominant job type that defines the route; calculate density for that type as the primary metric.

  • 02What if my customers require specific arrival windows and I cannot cluster by geography?

    Some customers will always require fixed windows (commercial property managers, HOA accounts with access windows). Treat those as anchors in the route and build the flexible stops around them geographically. A route with 3 fixed windows and 15 flexible stops can still be clustered effectively. The fixed stops constrain the route; they do not eliminate the optimization opportunity.

  • 03Is 3.5 stops per hour realistic for pool service in a dense suburban market versus a rural one?

    Yes, density benchmarks are market-specific. In a dense suburban market (houses on 0.25-acre lots, 10-minute drive between any two customers), 4-5 stops per hour is achievable. In a rural or exurban market with 20-30 minutes between stops, 2.5-3 stops per hour may be the realistic ceiling. The benchmark is a starting point; your market constrains the upper bound. Track your own trend (are you improving?) rather than benchmarking against a different market type.

  • 04Does route density apply to commercial accounts with multi-hour visits?

    For commercial accounts where a single job takes 3-5 hours, stops-per-hour is the wrong metric. Use revenue per hour or gross profit per hour instead. Route density as defined here is a residential route metric. Commercial field service is better measured on utilization rate (billable hours / total field hours).

See Clint in action

Clint is the pre-built AI for home service shops. Connect your CRM, email, and phone system in minutes and the agents run on your real data.