Windshield Time Is Still Rising and Your Routing Software Already Ran
Routing tools optimize at job assignment and stop. Idle time, skipped stops, and technician utilization gaps accumulate after the route locks, where no software is watching.
Windshield Time Is Still Rising and Your Routing Software Already Ran
Routing software does one thing well: it builds the best possible route at the moment a job is assigned. Then it stops. The route locks, the technicians roll out, and from that point forward, every skipped stop, every job that runs long, every mid-morning cancellation, and every idle gap between appointments accumulates without any system watching or responding. As of 2025, windshield time still accounts for 15 to 30 percent of total technician hours across field service operations, according to industry benchmarks, and the average technician utilization rate sits at 60 to 65 percent of available hours. Those two numbers are not separate problems. They are the same problem wearing different labels, and routing software does not fix either one after the route is set.
The Dispatch Problem Starts After the Route Locks
Every routing tool optimizes at job assignment and stops. The gap it cannot close is the one that opens the moment the day begins moving.
A dispatcher using Jobber or ServiceTitan builds a route in the morning. The algorithm sequences the stops, minimizes drive time, and produces a clean board. That is the full extent of what the software does. It does not watch what happens next. It does not know that the first job ran 40 minutes long, pushing every subsequent stop into a tighter window. It does not know that the third stop cancelled at 10 a.m. and left a technician with 90 minutes of unstructured time in the middle of a territory. It does not know that a technician is now sitting idle two miles from an unassigned job that could have been inserted into the route.
The route was optimized. The day was not.
What does "idle time" actually cost on a twenty-truck fleet?
The math is not abstract. A fleet of twenty technicians, each averaging two hours of windshield time and idle gaps per day, is carrying roughly 40 technician-hours of non-billable time every single day. At a blended billable rate of $100 per hour, that is $4,000 per day in capacity that exists on the payroll but produces nothing. Over 200 working days, that is $800,000 in recoverable production value sitting inside a schedule that no software is actively managing after 8 a.m.
Route optimization models can reduce travel distance by roughly 15 percent and improve time efficiency by nearly 20 percent when applied at the scheduling stage, according to research cited by industry analysts. But those gains are captured at assignment. The 20 to 30 percent of the day that erodes after the route locks is a different problem entirely, and it requires a different kind of system to address it.
Production Value Per Technician Is a Routing Problem, Not a Headcount Problem
The number that matters is not how many technicians are on the payroll. It is how many billable hours each technician produces per day, and whether the dispatch system is actively protecting that number throughout the shift.
A non-optimized schedule typically allows a technician to complete five jobs per day. An optimized route at assignment can push that to seven. But the difference between five and seven is not just a routing algorithm applied once in the morning. It is a system that watches the day unfold, identifies the gap when a job cancels or runs short, and inserts the next available job before the technician has time to go idle. That is not what Jobber does. That is not what Housecall Pro does. ServiceTitan's Dispatch Pro module moves closer to this with continuous re-evaluation during business hours, but it is a premium add-on, and it still operates within the boundaries of what a dispatcher chooses to act on. The decision still requires a human to notice the gap and respond.
Affinity filters and region logic: why the right job is rarely the nearest job
Routing software optimizes around the map. The orchestration brain optimizes around the output. Those are not the same thing.
A technician finishing a job in the northeast quadrant of a territory is not best served by the nearest open job. The best next job is the one that accounts for the technician's skill set, the customer's service history, the compliance window on the work order, the overtime exposure if the job runs long, and the density of remaining stops in that region for the rest of the day. Routing software does not hold all of those variables simultaneously after the route is set. It held them once, at assignment, and then it stopped.
Affinity filters, region logic, and variable job cutoff times are the mechanisms that determine whether a technician's afternoon produces three more jobs or one. They are not features of a routing tool. They are decisions that require a system with shared state, persistent context, and the ability to act without waiting for a dispatcher to notice a gap on the board.
What the Facility19 Control Tower Does After the Route Locks
The Facility19 control tower is the clearest available proof that this problem is solvable. Eight agents, one orchestration brain, a twenty-truck fleet. The brain does not build a route and stop. It watches the entire day.
Dex, the dispatch agent, holds the route in shared state alongside every other agent in the system. When a job cancels, Dex does not wait for a dispatcher to notice. It identifies the gap, evaluates the available jobs in the region against the technician's skill set and remaining schedule, and inserts the best available stop. The fast brain suppresses double contact, so no customer receives two notifications from two agents acting on the same gap. Every assignment, every override, and every escalation is logged and auditable.
The overtime agent watches the back half of the day. When a technician's schedule is trending toward overtime, the system does not wait for the dispatcher to catch it at 4 p.m. It surfaces the exposure early, with the context already assembled, so the decision to reassign or cut the last stop is made at the right moment rather than after the cost is already locked in.
According to McKinsey research, automation applied to field service operations can deliver labor savings of 20 percent or more, with processing time reduced from days to minutes and the ability to operate at scale without proportional headcount increases. Source: McKinsey, Driving Impact at Scale from Automation and AI
The Facility19 system does not produce those gains by building a better route at 7 a.m. It produces them by running the day from first dispatch through final checkout, with agents that share state and a brain that never stops watching. See how the orchestration brain runs dispatch, not just records it, and the specific decision domains each agent owns inside the control tower.
Why Routing Software Stops Where the Real Problem Starts
Routing software is not broken. It does exactly what it was designed to do. The problem is that it was designed to solve a scheduling problem, not an operational one. Scheduling happens before the day starts. Operations happen during it.
ServiceTitan records the dispatch board. Jobber records the route. Housecall Pro records the job status. Every one of those platforms produces a data trail of what happened. None of them act on what is happening right now, in the gap between the job that just closed and the next one that has not been assigned yet.
The distinction matters because that gap is where windshield time lives. It is not a routing failure. It is a real-time decision failure. The route was correct when it was built. The day changed, and no software was watching.
Is the problem the routing algorithm or the system around it?
The routing algorithm is rarely the bottleneck. Most modern FSM platforms, including ServiceTitan and Jobber, use competent sequencing logic at assignment. The bottleneck is the absence of a system that holds shared state across the entire day, monitors the gap between what was planned and what is actually happening, and acts on that gap without requiring a dispatcher to notice it first.
That is an orchestration problem, not a routing problem. And it is why adding a better routing module to an existing FSM platform does not close the gap. The module optimizes at assignment. The day still runs without a brain.
For a deeper look at how tribal knowledge and disconnected systems compound this problem before the route is even built, read how the second brain problem precedes every real dispatch automation project.
The Density Argument: Every Serviced Job Makes the Next One Cheaper to Win
There is a compounding effect that routing software cannot capture because it does not run the full loop. When the orchestration brain dispatches a job, closes it, collects the review, and routes the next lead in the same geography, the cost of winning that next customer drops. The route data from the completed job informs the density of the next assignment. The review from the satisfied customer surfaces in the next outbound sequence to the neighbor two doors down.
Routing software optimizes a single day. The orchestration brain compounds across every day, because the data from each completed job feeds back into the next dispatch decision, the next lead acquisition, and the next route sequence. That is the loop that field service businesses are not running yet, and it is the reason windshield time keeps rising even as routing tools keep improving. The tools are getting better at the slice they own. Nobody is running the circle.
See how the full loop from dispatch through collection runs without staff in the Facility19 deployment, and what the density effect looks like across a twenty-truck fleet over time.
What This Means for a Fleet Operator Right Now
The operational implication is direct. If windshield time on your fleet is above 20 percent, the routing software has already done everything it can do. The remaining gap is not a routing problem. It is a real-time orchestration problem, and it will not close until a system is watching the day as it unfolds, not just the route as it was planned.
Three metrics move together when the orchestration layer is running: windshield time drops, technician utilization rises, and overtime exposure shrinks. A fleet that moves from 65 percent technician utilization to 75 percent across twenty technicians, at a $100 blended billable rate over 200 working days, recovers roughly $400,000 in annual production value without adding a single truck or technician. The route did not produce that. The brain running the day did.
The U.S. field service management market reached $1.5 billion in 2025, according to IMARC Group, and is projected to grow at a 14 percent compound annual rate through 2034. Source: IMARC Group, U.S. Field Service Management Market. The operators who capture that growth will not be the ones with the best routing algorithm. They will be the ones whose system keeps running after the route locks.
For PE firms acquiring field service businesses, the implication is the same. See how one orchestration brain redeploys across an entire portfolio without rebuilding the system for each acquisition, and what the EBITDA case looks like when the back office runs itself.
Software watched the route. The brain runs the day.
Frequently Asked Questions
What is windshield time and why does it keep rising even with routing software?
Windshield time is the unbillable hours a technician spends driving between jobs rather than working on them. It keeps rising because routing software optimizes at job assignment and then stops. Every cancellation, delay, or schedule change that happens after the route locks creates idle gaps that no software is actively managing or filling in real time.
What is production value per technician and how does dispatch affect it?
Production value per technician is the total billable output a technician generates per day, measured against their available hours. Dispatch directly determines this number because the sequence, density, and real-time adjustment of job assignments controls how much of each technician's day is spent on billable work versus driving or waiting. A system that only optimizes at assignment leaves the afternoon unmanaged.
How is an orchestration brain different from a routing tool or FSM platform?
A routing tool or FSM platform like ServiceTitan or Jobber builds the best route at the moment of assignment and records what happens afterward. An orchestration brain holds shared state across all agents and all jobs throughout the entire day, identifies gaps as they open, and acts on them without waiting for a dispatcher to notice. It runs the day rather than recording it.
What does the Facility19 control tower actually do differently from standard dispatch software?
The Facility19 control tower runs eight agents on one brain across a twenty-truck fleet. When a job cancels or a technician goes idle, the dispatch agent identifies the gap, evaluates available jobs against skill set, region, and compliance requirements, and inserts the best available stop, all without a dispatcher in the loop. Every action is logged and auditable. The overtime agent monitors the back half of the day and surfaces exposure before the cost locks in.
Can a routing tool be upgraded to do what an orchestration brain does?
Not by adding a better routing module. The routing algorithm is rarely the bottleneck. The gap is the absence of shared state across the full day, persistent context across all agents, and the ability to act on real-time changes without human intervention. That requires an orchestration layer, not a routing upgrade.
What three metrics move together when the orchestration layer is running?
Windshield time drops, technician utilization rises, and overtime exposure shrinks. These three move together because they are all downstream of the same root cause: a system that watches the day as it unfolds and fills gaps before they become costs. A single metric improving in isolation is a sign that something else got worse to produce it. All three moving together is the signal that the system is working.
See the Orchestration Brain Running in Your Fleet
If windshield time on your fleet is above 20 percent and technician utilization is below 70 percent, the routing software has already done its job. The remaining gap belongs to a different system.
