Route Optimization for Service Fleets
Route optimization is one of those operational capabilities that produces meaningful financial returns through efficiency gains that compound across thousands of service calls per year. Service techs spend significant portions of their workdays driving between customer locations, with drive time consuming productive hours and producing fuel costs that add up across the fleet. The difference between routes that minimize drive time and routes that don't typically runs 15-30% in productive hours per day, with corresponding impact on fuel costs, jobs per tech per day, and operational metrics that directly affect revenue and profitability. The operations that take routing seriously produce measurably better outcomes than operations that don't.
The technology behind route optimization has matured significantly. Modern FSM platforms incorporate routing algorithms that handle the actual operational complexity service contractors face: techs with different skills assigned to specific jobs, time-window constraints from customer preferences, real-time traffic data affecting drive estimates, emergency calls disrupting planned routes, and the dispatch judgment that no algorithm fully captures. The capability has shifted from being a competitive advantage to being a baseline expectation, with operations running without route optimization absorbing operational costs that purpose-built routing eliminates.
This article covers how route optimization actually works, the algorithms behind it, the ROI math, and how dispatch software incorporates routing. The foundational explainer on FSM software lives here: What is Field Service Management Software? The deeper coverage of dispatch software more broadly lives here. The deeper coverage of mobile field tools that techs use to follow optimized routes lives here.
How Route Optimization Actually Works
The mechanics below explain what routing software does and how it differs from generic mapping.
The Underlying Problem
Route optimization solves a specific operational problem: given a tech with multiple stops to make, what order minimizes total drive time while respecting all constraints?
The problem is mathematically the Traveling Salesman Problem (TSP), one of the classic problems in operations research. For small numbers of stops (under 10), the problem is solvable through brute force; for larger numbers, optimization heuristics produce near-optimal solutions much faster than exhaustive search. Modern routing platforms handle the math behind the scenes, presenting dispatchers with optimized routes that consider:
Distances between locations
Real-time traffic conditions
Drive time variations by time of day
Time-window constraints from customer preferences
Job duration estimates
Tech start/end locations (often home)
Lunch and break time
Beyond Simple TSP: Service Contractor Reality
Pure TSP optimization isn't sufficient for service contractors. The operational reality includes:
Skills-based assignment: Different techs have different skills. The optimal assignment may not be the geographically optimal one if the closest tech lacks required certification or expertise.
Customer time windows: Many customers have specific time preferences. A geographically optimal route may violate customer commitments.
Job duration uncertainty: Service jobs vary in actual duration. Routing assumes estimated durations that may not match reality.
Emergency dispatch: Same-day calls disrupt planned routes. Strong routing handles re-optimization when conditions change.
Multi-tech coordination: Some jobs require multiple techs. Routing needs to coordinate timing.
Vehicle constraints: Some jobs require specific equipment that not all trucks carry. Routing needs to consider vehicle assignments.
Strong routing software handles these complexities; weak routing produces theoretically optimal routes that don't work in practice.
Real-Time Re-Optimization
Service days don't follow plans precisely. Strong routing handles real-time changes:
Job completing earlier than estimated
Job taking longer than estimated
Emergency call requiring redispatch
Customer reschedule
Tech delay (traffic, vehicle issue, illness)
Real-time re-optimization adjusts routes throughout the day as conditions change rather than treating the morning's route as fixed.
Customer Communication Integration
Routing affects customer-facing communication:
Initial appointment time based on planned route
ETA updates as route progresses
Rescheduling communication when route changes affect arrival
Customer notification when significant changes occur
Read this page for the deeper coverage of customer communication tools and software.
Manual Override Capability
Even with sophisticated routing, dispatchers need override capability:
Local knowledge the algorithm doesn't have
Customer relationship considerations
Tech preferences or development needs
Operational priorities beyond pure efficiency
Strong routing supports manual override gracefully; weak routing fights with dispatchers who need to override.
Day-of vs Pre-Planned Routing
Routing happens at multiple time horizons:
Pre-planned routes for scheduled appointments
Day-of optimization as conditions become clear
Real-time adjustment as the day progresses
Multi-day optimization for some operations
The right routing horizon depends on operation type and customer expectations.
Pro Tip: Calculate your operation's drive time as percentage of paid hours as a primary efficiency metric. Strong service operations typically run drive time at 15-22% of paid hours; operations beyond 30% have meaningful inefficiency that route optimization could address. The math: a tech working 8 paid hours per day at 30% drive time spends 2.4 hours driving versus a 20% drive time tech spending 1.6 hours driving. The 0.8-hour difference per tech per day equals approximately 200 hours per tech per year, worth $7,000-$15,000 in productivity per tech depending on labor cost. Across a fleet, the cumulative productivity gain from improved routing typically justifies platform investment substantially.
ROI Math for Route Optimization
The financial math below shows why route optimization typically produces strong returns.
Drive Time Reduction
The primary mechanism: route optimization reduces drive time per job:
Optimal sequencing of multi-stop routes
Better skill-matching reducing wasted trips
Real-time traffic adjustments
Emergency call routing minimizing detours
Operations transitioning from manual routing to optimized routing typically see drive time drop by 5-15 percentage points (from say 28% to 18% of paid hours). For a 25-tech operation, the drive time reduction translates to approximately 4,000-12,000 productive hours gained per year.
Jobs Per Tech Per Day Increase
Recovered drive time becomes productive time:
Additional jobs completed per day
Better customer service through more capacity
Higher revenue per tech
Improved tech utilization
Operations typically see jobs per tech per day increase 15-30% from improved routing alone, with corresponding revenue impact.
Fuel Cost Reduction
Less driving means less fuel consumption:
Direct fuel cost savings
Reduced vehicle wear and maintenance
Lower insurance costs in some cases (mileage-based)
A 25-tech fleet driving 20% less typically saves $15,000-$40,000 annually in fuel costs depending on fuel prices and driving patterns.
Vehicle Lifecycle Benefits
Reduced driving extends vehicle life:
Fewer miles on vehicles
Less maintenance frequency
Longer time between replacements
Higher resale value at replacement
The vehicle lifecycle benefits show up as reduced capital investment in fleet maintenance over years.
Customer Experience Benefits
Beyond direct cost savings, customer experience improves:
More accurate ETAs
Less time waiting for techs
Better same-day call response
More reliable scheduling
The customer experience benefits show up indirectly through retention, reviews, and word-of-mouth.
Tech Satisfaction Benefits
Techs experience routing quality directly:
Less time driving (which most techs prefer)
More productive time (which produces commission for some compensation models)
Better job sequencing (avoiding awkward back-and-forth)
Less frustration with logistical chaos
Better routing supports tech retention in a labor-constrained market.
Total ROI
The cumulative impact across multiple benefit categories typically produces ROI of 3-10x the platform cost within the first year:
Direct productivity gains
Direct cost savings
Customer experience improvements
Tech retention benefits
Capacity for growth
Operations skipping route optimization absorb operational costs that proper investment would eliminate.
Case Study: A 34-tech plumbing service contractor analyzed their routing operations in 2024 after migrating to ServiceTitan. Their pre-migration baseline showed average drive time at 31% of paid hours, average jobs per tech per day at 3.6, and fuel costs of approximately $185,000 annually across the fleet. Post-migration with route optimization fully configured and dispatcher training on the new tools, drive time dropped to approximately 21% of paid hours within 9 months, jobs per tech per day rose to approximately 4.4, and fuel costs dropped to approximately $148,000 annually. The productivity gain (approximately 0.8 additional jobs per tech per day across 34 techs) translated to substantial revenue increase: approximately $1.8M in annual revenue capacity that hadn't existed before. The fuel savings ($37,000 annually) added to the math. Vehicle maintenance costs also dropped meaningfully through reduced driving. The lesson was that route optimization produces compounding benefits that extend well beyond just drive time reduction. The platform investment justified itself through revenue capacity gains alone, with cost savings and customer experience improvements adding significant additional return.
How Dispatch Software Incorporates Routing
The implementation approach below shows how routing integrates with broader FSM operations.
Integration Levels
Route optimization integrates with FSM at varying depth:
Basic level: Mapping integration showing locations on a map. Helpful for visualization but not actually optimizing routes.
Mid level: Route ordering optimization for multi-stop techs. Useful but doesn't handle full operational complexity.
Advanced level: Full optimization including skills-based assignment, time windows, real-time updates, and dispatcher override support. Produces the operational benefits routing should deliver.
Operations should evaluate routing depth specifically when picking platforms rather than accepting general claims about "route optimization."
Configuration Considerations
Strong routing requires configuration:
Tech skill profiles
Customer time-window definitions
Job duration estimates by service type
Vehicle assignments
Constraint definitions (start/end locations, lunch times, breaks)
The configuration is meaningful initial work but produces ongoing operational benefit.
Algorithm Tradeoffs
Different routing algorithms make different tradeoffs:
Nearest neighbor: Fast but produces suboptimal routes. Some platforms still use this for speed.
Genetic algorithms: Produce near-optimal routes through iterative improvement. Most modern platforms use variants of this.
Constraint programming: Handles complex constraint sets well. Common in enterprise platforms.
Real-time hybrid: Combines pre-planned optimization with real-time adjustment. Most operationally useful for service contractors.
Most service contractors don't need to choose algorithms specifically; they choose platforms whose underlying algorithm meets their operational needs.
Platform Routing Capability Comparison
Routing capability varies meaningfully across platforms:
ServiceTitan: Strong routing with real-time optimization, skill-based assignment, dispatcher tools. Well-suited for complex operations.
FieldEdge: Good routing for typical service operations. Adequate for most needs.
Housecall Pro: Routing capability varies by tier. Pro tier includes stronger routing.
Jobber: Basic routing capability. Adequate for smaller operations.
Specialized routing platforms: Some operations layer specialized routing (Routific, OptimoRoute) on top of FSM platforms when FSM routing is inadequate.
The right approach depends on operation complexity and FSM platform capability.
Dispatcher Training and Adoption
Routing requires dispatcher training:
How the algorithm works at a basic level
When to trust algorithm recommendations
When to override
How to use real-time re-optimization
How to balance pure efficiency with other operational priorities
Operations underweighting dispatcher training sometimes face suboptimal routing adoption that better training would resolve.
Tech Adoption
Techs need to adopt routing changes:
Following recommended routes rather than personal preferences
Communicating with dispatch about route changes
Updating job status to support real-time re-optimization
Providing feedback on routing issues
Tech buy-in matters because tech behavior affects whether routing produces the intended benefits.
Continuous Improvement
Strong routing programs continuously improve:
Monitoring drive time metrics
Identifying recurring routing issues
Refining configuration based on operational learning
Adjusting for seasonal patterns
Incorporating new operational realities
Operations treating routing as set-and-forget miss the ongoing optimization opportunity.
Pro Tip: Route optimization works best when paired with strong dispatcher judgment, not when treated as a replacement for dispatchers. The algorithm handles math the dispatcher can't do quickly (optimal sequencing across many stops with multiple constraints); the dispatcher handles judgment the algorithm doesn't have (customer relationships, tech development, operational priorities, local knowledge). Operations that buy routing expecting to eliminate dispatcher roles typically face issues. Operations that buy routing to amplify dispatcher effectiveness typically see the biggest operational improvements. The combination of algorithmic optimization with dispatcher judgment outperforms either alone.
Routing Quality Determines Operational Efficiency
Route optimization is one of the highest-ROI capabilities in FSM platforms because the productivity gains and cost savings compound across thousands of service calls per year. Operations running strong routing operate measurably more efficiently than operations running weak routing or no routing, with the gap showing up in metrics like jobs per tech per day, drive time as percentage of paid hours, fuel costs, and customer experience.
The capability comes embedded in modern FSM platforms with depth varying by platform tier. Operations evaluating FSM platforms should specifically evaluate routing capability against operational complexity rather than treating it as a checkbox feature. The operational difference between weak and strong routing typically produces ROI that justifies platform investment multiple times over within the first year.
Frequently Asked Questions
Do I need specialized routing software like Routific in addition to FSM?
For most service contractors, routing capability built into FSM platforms is adequate. Specialized routing platforms (Routific, OptimoRoute, Onfleet) add depth in specific areas (more sophisticated algorithms, better visualization, deeper analytics) that some operations need beyond what FSM platforms provide. Operations evaluating specialized routing should consider whether their FSM platform's built-in routing covers their needs before adding additional software. The specialized tools earn their place when operations have specific routing complexity that FSM-included routing doesn't address.
How much does poor routing cost?
Operations running 25-30%+ drive time as percentage of paid hours when 18-22% would be achievable with proper routing absorb significant operational cost. The math: a 25-tech operation losing 8 percentage points of drive time efficiency loses approximately 4,000 productive hours annually, worth $200,000-$500,000 in revenue capacity depending on average ticket and labor productivity. Plus fuel costs running roughly 30-40% higher than optimal. Plus vehicle wear costs running higher than necessary. The cumulative cost typically runs $250,000-$700,000 annually for mid-size service operations with poor routing.
Should I trust the algorithm or my dispatcher?
Both, in combination. The algorithm handles math the dispatcher can't do quickly (optimal sequencing across many stops with multiple constraints). The dispatcher handles judgment the algorithm doesn't have (customer relationships, tech development, operational priorities, local knowledge). Strong routing tools support manual dispatcher override; weak routing fights with dispatchers needing to override. The combination of algorithmic optimization with dispatcher judgment outperforms either alone.
Does route optimization handle emergency calls?
Strong routing handles emergency calls through real-time re-optimization: when an emergency comes in, the system identifies the optimal tech to dispatch based on location, skills, and current schedule, suggests route adjustments to accommodate, and updates customer-facing communications appropriately. Weaker routing handles emergencies by disrupting the planned route without re-optimizing the rest of the day, producing operational inefficiency that ripples through subsequent calls.