The Most Expensive Person in Your Company Does Not Know It

In most field service operations, the dispatcher is the highest-leverage role in the company. A single routing decision determines whether a $95-per-hour technician spends the next 45 minutes driving or the next 45 minutes generating revenue. Multiply that by 8 decisions per technician per day, 15 technicians, and 250 working days per year, and the dispatcher is allocating roughly $2.8 million in labor productivity annually.

Most dispatchers make these decisions using a combination of a whiteboard, a spreadsheet, personal knowledge of the service area, and whatever scheduling software the company has, which is frequently used as a calendar rather than an optimization engine. The result is predictable: field technicians in manually dispatched operations spend 28 to 35% of their working hours in transit, according to data from the Service Council and Aberdeen Group.

That number should be 15 to 20%. The gap between those two figures represents the dispatch problem: a structural inefficiency that costs mid-size field service companies between $400,000 and $1.2 million per year in lost productivity.

Field Technician Day: Manual Dispatch vs Optimized Dispatch
Manual Dispatch
32%
DRIVING
42%
ON-SITE WORK
26%
ADMIN / IDLE
4.2 jobs completed / day
Optimized Dispatch
17%
DRIVING
61%
ON-SITE WORK
22%
ADMIN / IDLE
5.8 jobs completed / day

Source: Fulcrum analysis of Service Council field operations data and Aberdeen Group workforce management benchmarks (2023)

Why Dispatchers Cannot Solve This

The dispatch problem is not a people problem. It is a combinatorial math problem that exceeds human cognitive capacity at any meaningful scale.

Consider a modest operation: 12 technicians, 50 open jobs for the day, each job requiring a specific skill set, each customer having a preferred time window, and each technician starting from a different location. The number of possible schedule combinations is not in the thousands or millions. It is in the billions. A dispatcher considering even a fraction of these possibilities would never finish scheduling.

Instead, dispatchers use heuristics. They route geographically (all the northside jobs to one tech, all the southside jobs to another). They assign based on familiarity (send the same tech to the same customer). They front-load priority jobs and backfill with whatever fits. These heuristics are reasonable, but they leave enormous value on the table.

Research from the Operations Research Society shows that heuristic routing typically achieves 60 to 70% of theoretical optimal efficiency, while algorithmic optimization achieves 85 to 92%. On a fleet of 15 trucks covering a metropolitan area, that difference translates to 2 to 3 additional completed jobs per technician per week.

For a company billing $200 per service call, that is $60,000 to $90,000 per technician per year in additional revenue capacity. Across 15 technicians, the number reaches $900,000 to $1.35 million.

The Cascading Failure Pattern

The dispatch problem does not stay contained to routing. It cascades through every aspect of field operations.

First-time fix rates drop. When dispatch is purely geographic, the nearest available technician gets the job, not the best-qualified technician. A 2023 Field Technologies Online survey found that companies with manual dispatch have first-time fix rates of 71%, compared to 83% for companies using skill-based dispatch optimization. Every return visit costs the full truck roll ($150 to $300) plus the customer satisfaction impact.

Overtime escalates. Poor routing means jobs run late, which pushes afternoon appointments into overtime territory. Field service companies with manual dispatch report overtime rates of 12 to 18% of total labor hours, versus 5 to 8% for optimized operations. For a company with $2M in field labor costs, that is an additional $80,000 to $200,000 per year in overtime premiums.

Customer windows get wider. Because the company cannot predict arrival times accurately, they quote 4-hour windows instead of 2-hour windows. Customers accept this because the industry has normalized it, but it is a competitive disadvantage in an era where Amazon has trained consumers to expect precision logistics. Companies that narrow their arrival windows to 1 to 2 hours see 22% higher customer satisfaction scores and 15% higher referral rates, according to the Service Council.

The dispatcher becomes a bottleneck. As the fleet grows, the dispatcher's cognitive load increases nonlinearly. A dispatcher managing 8 technicians has a manageable morning. A dispatcher managing 20 technicians is making reactive decisions all day, constantly reshuffling routes as jobs run long, emergencies appear, and technicians call in. The quality of routing decisions degrades throughout the day, with afternoon routes averaging 23% more drive time than morning routes in manually dispatched operations.

The Dispatch Cascade: How Routing Failures Compound
1
Suboptimal routing
32% of day in transit vs 17% optimal
-15% capacity
2
Wrong tech for the job
First-time fix rate drops from 83% to 71%
-12% FTF
3
Jobs run late, overtime escalates
12-18% OT rate vs 5-8% optimized
+$140K/yr
4
Wide arrival windows, lower satisfaction
4-hour windows vs 1-2 hour optimized
-22% CSAT
5
Dispatcher burnout limits growth
Cannot scale past 15-20 techs per dispatcher
Growth cap

The Dispatcher Ceiling

There is a hard limit to how many technicians a human dispatcher can effectively manage. The consensus among field service operations researchers puts this number at 15 to 20 technicians per dispatcher for complex, multi-skill operations, and 20 to 30 for simpler, homogeneous service calls.

This creates a staircase growth pattern that is expensive and fragile. At 18 technicians, you need one dispatcher. At 22 technicians, you need two. But dispatchers are hard to hire and harder to train. The institutional knowledge required to dispatch effectively in a specific service area takes 6 to 12 months to develop. During that learning curve, routing quality drops, customer complaints increase, and technician productivity suffers.

The companies that grow past 30 to 40 technicians either accept degrading service quality, invest in algorithmic dispatch tools, or build management layers that create their own overhead. The ones that invest in optimization find that a single dispatcher supported by routing algorithms can effectively manage 40 to 60 technicians, essentially removing the staircase and replacing it with a ramp.

What the Fix Actually Looks Like

The companies that solve the dispatch problem follow a three-stage progression. Skipping stages or implementing them out of order consistently produces poor results.

Stage 1: Data capture. Before you can optimize routing, you need accurate data on three things: how long each job type actually takes (not the scheduled duration, the actual duration), where your technicians actually are throughout the day (GPS tracking), and what skills and certifications each technician has. Most companies have partial data on each of these. Getting to complete, accurate data typically takes 60 to 90 days of disciplined capture.

Stage 2: Algorithmic scheduling. With clean data, routing optimization software can produce daily schedules that minimize drive time while respecting skill requirements, customer time windows, and technician work rules. The initial improvement is typically 15 to 25% reduction in total drive time and a 20 to 30% increase in jobs completed per technician per day. Tools like ServiceTitan, FieldEdge, and Skedulo offer this capability, though the quality of results depends entirely on the quality of input data.

Stage 3: Dynamic re-optimization. The morning schedule never survives the day. Jobs run long, emergencies appear, cancellations happen, and parts are unavailable. The most advanced field service operations re-optimize routes continuously throughout the day, automatically reassigning jobs as conditions change. This requires real-time data integration (GPS, job status updates, inventory systems) and algorithms that can reschedule in seconds rather than minutes.

Companies that reach Stage 3 report first-time fix rates above 85%, drive time below 18% of total hours, and overtime rates below 6%. More importantly, they can scale their fleet without proportionally scaling their dispatch staff, which changes the fundamental economics of growth.

The Math That Should End the Debate

For a field service company with 15 technicians, each billing at $175 per hour with a fully loaded labor cost of $45 per hour, the numbers are straightforward.

Moving from 32% drive time to 18% drive time recovers 1.12 hours per technician per day. That is 16.8 additional productive hours per day across the fleet. At the $175 billing rate, that represents $2,940 per day in additional revenue capacity, or roughly $735,000 per year.

The fuel and vehicle savings from shorter routes add another $30,000 to $60,000 per year. Overtime reduction contributes $80,000 to $120,000. Improved first-time fix rates reduce truck rolls by an estimated $50,000 to $100,000 per year in avoided return visits.

The total annual impact for a 15-truck operation: $895,000 to $1,015,000.

The cost of implementing route optimization, including software, GPS hardware, and the process change management required, typically runs $40,000 to $80,000 in the first year and $20,000 to $40,000 annually thereafter.

The ROI is not subtle. It is 10:1 or better in the first year. The reason most companies have not done it is not the cost. It is that the problem is invisible. Drive time is accepted as a fixed cost of field service, like fuel or insurance. It is not. It is the single largest controllable cost in the operation, and most companies have never measured it accurately enough to know how much they are losing.

If your technicians are completing fewer than 5 jobs per day on average, the dispatch process is almost certainly the constraint. Run a free diagnostic to quantify the gap in your operation.