Windshield Time Is the Dispatch Metric Your Routing Report Hides

Every routing tool shows a map. Few measure unproductive drive time per technician per day, the number that directly sets production value and determines whether a twenty-truck fleet runs at margin or at break-even.

Windshield Time Is the Dispatch Metric Your Routing Report Hides

Every routing tool shows a map. ServiceTitan shows a dispatch board. Jobber shows a calendar. What neither one surfaces by default is the number that actually sets your margin: unproductive drive time per technician per day, measured as a percentage of total shift hours. As of 2025, the average field service technician spends between 28 and 40 percent of the workday behind the wheel, generating zero revenue while payroll, fuel, and vehicle wear accumulate at full cost. On a twenty-truck fleet, that is not a routing inefficiency. It is a structural profit leak hiding inside a report that looks fine.

Windshield time is the dispatch metric your routing report hides because most platforms measure where trucks went, not how much of the day was wasted getting there. The distinction matters more than most operators realize, and the math behind it is not subtle.

What Windshield Time Actually Costs on a Twenty-Truck Fleet

Unproductive drive time is a payroll problem wearing a routing costume. When a technician's shift runs eight hours and 35 percent of it is transit, the business is paying for 2.8 hours of movement that produces nothing. Multiply that across twenty trucks, five days a week, and the number becomes structural.

Consider the arithmetic at a fully loaded technician cost of $85 per hour. At 28 percent windshield time, each technician loses roughly 2.2 billable hours per day to transit. Across twenty technicians, that is 44 hours of paid capacity consumed by driving every single day. At $85 per hour, that is $3,740 per day, or roughly $935,000 per year, in payroll spent on windshield time alone, before fuel and vehicle depreciation are added.

The inverse is equally precise. Research on routing optimization at scale shows that a 25 percent improvement in routing efficiency recovers approximately half an hour of productive capacity per technician per day. On a twenty-truck fleet, that is ten hours of recovered capacity daily, enough to add two to three additional completed jobs to the schedule without hiring a single additional technician. Production value per technician rises. Overtime exposure falls. The fleet runs at margin instead of at break-even.

Why does the routing report miss this number?

Because most routing reports are built around the map, not the clock. They show sequence, distance, and estimated arrival. They do not show drive time as a percentage of shift hours, they do not compare that percentage against the technician's production value for the day, and they do not flag when a technician's route structure is the reason a job ran into overtime rather than the job itself. The metric exists in the GPS data. It is simply never surfaced as a primary KPI.

The Technology Services Industry Association has found that the average field service organization operates at only 60 to 65 percent technician utilization. That means more than a third of paid technician time is not generating revenue. Windshield time is the single largest contributor to that gap, and it is the most fixable one.

Production Value Per Technician Is the Number Routing Optimizes Around the Map Instead of Around the Output

Production value per technician is the metric that connects routing decisions to financial outcomes. It is not jobs completed per day. It is revenue generated per technician per shift, net of the time cost of getting between jobs. A technician who completes eight jobs but drives all over a metro area may generate less production value than a technician who completes five jobs clustered in two adjacent zip codes, because the second technician's drive time percentage is 10 percent instead of 40 percent.

This is the distinction that most field service management platforms, including ServiceTitan and Jobber, do not make natively. ServiceTitan's dispatch board is a sophisticated tool for managing what a dispatcher has already decided. It records the decision. It does not optimize the decision against production value per technician before the truck rolls. Jobber's route optimization operates on a single-technician basis and offers limited capacity planning across a fleet. Both platforms stop at "here is the data, now you figure it out."

The affinity and region filter problem

Windshield time is not only a routing problem. It is a scheduling problem that precedes routing. If jobs are booked in the wrong sequence, or assigned to technicians whose home base is on the wrong side of the service territory, no routing algorithm fully recovers the lost time. The damage is locked in before the route runs.

Affinity filters, which assign technicians to recurring customers they have already served, and region filters, which cluster new jobs within a technician's established geographic zone, are the scheduling decisions that determine whether the routing algorithm has anything useful to optimize. Without them, the routing tool is correcting a bad plan rather than executing a good one. With them, windshield time drops before the first truck leaves the yard.

McKinsey's Operations Practice estimates that active scheduling, which scores jobs against skills, location, parts availability, and traffic in real time, can cut field service travel time by 15 to 25 percent and lift first-time fix rates by as much as 20 percent.

Variable Job Cutoff Logic and Its Downstream Dispatch Consequences

Variable job cutoff logic is the dispatch rule that determines when a technician's schedule is considered full for the day. Most operations set a fixed cutoff: no new jobs after 3 p.m., or no jobs that cannot be completed within the remaining shift hours. The problem is that a fixed cutoff ignores the technician's current location, current drive time percentage, and the geographic relationship between their last job and any available new job.

A technician who finishes a job at 2:45 p.m. in the northeast quadrant of a service territory, with a 12 percent drive time percentage for the day, can absorb a 3:15 p.m. job in the same quadrant without overtime exposure. A fixed cutoff rejects that job. A variable cutoff, calibrated against current location, remaining shift time, and drive time percentage, accepts it. The difference is one additional completed job per technician per day on the days when the geography cooperates, and that frequency is higher than most operators expect.

On a twenty-truck fleet, variable cutoff logic recovering one additional job per truck every three days adds roughly 33 additional completed jobs per month. At an average ticket value of $350, that is $11,550 in monthly revenue that a fixed cutoff rule was leaving on the table. The jobs existed. The technician capacity existed. The scheduling logic was the constraint.

This is the kind of decision that sits inside the orchestration brain WeLaunch built for the Facility19 control tower. Dex, the dispatch agent, does not apply a fixed cutoff. It evaluates each potential job assignment against the technician's current GPS position, remaining shift hours, drive time percentage for the day, and overtime threshold set by the operator. Iris, the overtime agent, has already flagged the shift boundary before the assignment is made. The decision is not made by a dispatcher checking a clock. It is made by a system that holds all the variables simultaneously. See how the orchestration brain handles dispatch without a dispatcher in the Facility19 control tower.

Geofenced Checkout as an Escalation System, Not Just a Verification Tool

Geofenced checkout is typically described as a proof-of-presence mechanism: the technician checks out of a job only when their GPS position confirms they are at the job site. That is accurate, but it understates what geofenced checkout does when it is connected to the dispatch layer.

When checkout is geofenced and connected to the orchestration brain, the moment a technician's GPS confirms job completion, the system knows three things simultaneously: the job is closed, the technician's current location, and the technician's remaining shift capacity. That combination is the input the dispatch layer needs to evaluate the next assignment. The checkout event is not just a billing trigger. It is a dispatch signal.

In the Facility19 control tower, Molly, the checkout agent, prepares the invoice the moment Dex confirms the job is closing. The route agent receives the technician's confirmed location and evaluates available jobs within the optimal radius. The compliance agent checks whether the next assignment would push the technician past the overtime threshold Iris is monitoring. All three decisions happen in the same state, without a coordinator in the loop. The technician receives the next assignment before they have left the parking lot of the completed job.

That sequence, checkout to next dispatch in under two minutes, is what eliminates the idle time between jobs that most fleet operators accept as unavoidable. It is not unavoidable. It is a coordination gap, and coordination gaps are exactly what an orchestration brain is built to close. Read how field service automation dispatches, invoices, and closes the loop in a single connected system.

What the Capital-First Players Are Missing When They Buy a Fleet

More than $3 billion has been deployed into AI roll-ups as of 2025, with General Catalyst allocating roughly $1.5 billion from its Creation Strategy and Thrive Capital launching a vehicle of more than $1 billion. Long Lake reached $100 million in EBITDA in under two years and took American Express Global Business Travel private for $6.3 billion. These are serious capital commitments to a serious thesis.

The thesis is correct. The sequencing is the problem. Every one of those players is capital first. They acquire the business, then build or source the AI layer. A facility management portfolio company running on a legacy CMMS or on ServiceTitan does not become autonomous because a fund bought it. The windshield time problem does not get solved by the acquisition. It gets solved when the orchestration brain is live in production and the agents are making dispatch decisions in real time.

WeLaunch built the brain first. The Facility19 control tower is not a pilot. It is a running system: eight agents, one brain, twenty trucks, dispatch handled, compliance tracked, overtime managed. The production value per technician number moves because the system is making better dispatch decisions on every job, not because a new owner sent a consultant to review the routing report.

For a PE partner evaluating a facility management portfolio company, the question is not whether the routing report looks acceptable. The question is whether the system behind the routing report is making decisions or recording them. See what field service automation looks like when the brain actually runs, not just when it records.

The Density Compounding Effect: Why Every Completed Job Makes the Next One Cheaper

Windshield time is not a static problem. It compounds in both directions. A fleet with high windshield time accumulates route inefficiency over time because the dispatch decisions that created the inefficiency are never corrected by the system. The dispatcher who built a bad route on Monday builds a similar one on Tuesday, because the feedback loop between route outcome and future dispatch decision does not exist in most FSM platforms.

The inverse is also true. When the orchestration brain closes the loop between completed job data and future dispatch decisions, route efficiency compounds. Every completed job adds GPS confirmation of actual drive time, actual job duration, and actual technician performance at that location. That data feeds back into the dispatch scoring model. The next job on the same property or the same street is assigned faster, routed better, and closed cleaner than the one before it.

This is what density means in a fleet context. A twenty-truck fleet that has been running the Facility19 control tower for six months has six months of route outcome data informing every new dispatch decision. The windshield time percentage does not stay flat. It declines, because the system is learning the territory, the technicians, and the job types in a way that no dispatcher and no static routing algorithm can replicate.

The fleet that runs this system does not just operate more efficiently today. It operates more efficiently every month, because the data compounds and the dispatch decisions improve. That is the difference between a routing tool that shows a map and an orchestration brain that runs the work. Explore the orchestration brain and the full system architecture at WeLaunch.

Software watched the work. We do the work.

Frequently Asked Questions

What is windshield time and why does it matter for fleet profitability?

Windshield time is the portion of a technician's shift spent driving between jobs rather than performing billable work. It matters because it is a direct payroll cost with zero revenue attached. At industry-average rates, windshield time above 35 percent of a shift is a red flag where labor cost bleeds into pure transit, and on a multi-truck fleet the annual dollar impact runs into six figures.

Why don't standard routing reports surface windshield time as a primary metric?

Most routing reports are built around map sequence and estimated arrival, not around drive time as a percentage of shift hours. The GPS data to calculate windshield time exists in most fleet systems, but it is rarely connected to production value per technician or to the dispatch decision layer that could act on it in real time.

What is production value per technician and how does it differ from jobs per day?

Production value per technician measures revenue generated per shift net of the time cost of transit, while jobs per day counts completions without weighting for how much of the shift was consumed by driving. A technician completing five clustered jobs with 10 percent windshield time typically generates more production value than one completing eight scattered jobs with 40 percent windshield time, even though the second technician's job count looks better on a standard report.

How does variable job cutoff logic reduce windshield time and overtime simultaneously?

Variable cutoff logic evaluates each potential late-day job assignment against the technician's current GPS position, remaining shift hours, and drive time percentage rather than applying a fixed time threshold. This allows the system to accept geographically proximate jobs that a fixed cutoff would reject, recovering completed jobs without pushing technicians into overtime, because the location and time variables are evaluated together rather than independently.

What is the difference between a routing tool and an orchestration brain for dispatch?

A routing tool optimizes the sequence of jobs already assigned. An orchestration brain makes the assignment decision itself, evaluating technician location, skill match, overtime exposure, compliance requirements, and production value simultaneously before the truck rolls. The routing tool corrects a plan. The orchestration brain builds the plan and executes it, then feeds the outcome back into the next decision.

How does the Facility19 control tower handle windshield time on a twenty-truck fleet?

The Facility19 control tower runs eight agents on a single orchestration brain. Dex, the dispatch agent, evaluates each job assignment against technician location, shift capacity, and drive time percentage in real time. Iris monitors overtime thresholds before assignments are made. Geofenced checkout by Molly triggers the next dispatch evaluation the moment a job closes, eliminating idle time between jobs. Every completed job feeds route outcome data back into the dispatch scoring model, so windshield time declines over time as the system learns the territory.

See the Orchestration Brain Running in Your Fleet

If you operate a facility management fleet or a multi-truck field service operation and want to see dispatch, windshield time reduction, and overtime management running without a coordinator in the loop, the systems walkthrough covers the full Facility19 control tower in production.

• See the orchestration brain running in your industry and review the full system architecture, agent framework, and live deployment proof points.
• Book a systems walkthrough and see the Facility19 control tower handling dispatch, compliance, and overtime on a real twenty-truck fleet.