Windshield Time: The 94 Minutes a Day You Pay For and Never Bill

If you want to understand a field service company's economics, do not look at its schedule. Look at a map of where its trucks went yesterday.

Renée did this for the first time in her eleventh year running a commercial HVAC service business in Edmonton. Her operations coordinator plotted one ordinary Wednesday: twelve technicians, sixty-one completed service calls, every route drawn as a line.

The map looked like someone had dropped a plate of spaghetti on the city. Trucks crossing each other's paths. One technician driving from the far northwest to the southeast and back again before lunch. Two technicians who had, at 10:15 that morning, been four blocks apart working for two different clients, then driven forty minutes in opposite directions.

Nobody had made a mistake. Every one of those assignments was defensible in isolation. The northwest-to-southeast run was an emergency call from a good client. The two technicians four blocks apart had different certifications. Every dispatch decision that day was reasonable.

The aggregate was still costing Renée roughly $210,000 a year.

The Number Most Operators Have Never Calculated

Windshield time is the portion of a paid workday a technician spends in a vehicle between jobs. Not the commute from home, not the drive to the first job, and not the drive home. Just the unproductive travel in the middle of the day, sandwiched between billable work.

Across most field service operations, that figure sits somewhere between 75 and 110 minutes per technician per day. It is paid at full loaded labour cost. It is billed to no one. And it is almost never measured, because no timesheet has a field for it.

Renée's twelve technicians averaged 94 minutes.

Here is the arithmetic that gets people's attention. Ninety-four minutes is roughly 20% of an eight-hour day. On a twelve-technician crew at a loaded cost of about $78 per hour:

Not all of that is recoverable. Some travel is irreducible, because clients are geographically where they are. But operators who take route density seriously typically pull windshield time down by 30 to 40%, which on Renée's numbers is $107,000 to $143,000 a year. Add the fuel, vehicle wear, and the additional billable capacity that appears when trucks stop driving, and $210,000 is a fair estimate of the total swing.

That is a meaningful number for a business her size. It is also completely invisible in her financial statements, where it sits distributed across wages, fuel, and vehicle maintenance without ever being named.

Density Beats Speed

Most operators who try to fix this reach for route optimisation software, which computes the fastest path between a fixed set of stops. That helps, and it is worth doing, but it addresses the smaller half of the problem.

The larger half is which stops end up on the same route in the first place. That is route density, and it is a scheduling decision, not a navigation decision. Optimising the driving order of a badly clustered day is polishing the wrong thing.

The distinction matters because the two levers live in different parts of the business. Route optimisation is a tool you buy. Route density is a set of scheduling habits you build.

Habit One: Geographic Clustering as a Scheduling Constraint

Most field service scheduling treats geography as an afterthought. The job gets booked for the date and time the client wants, assigned to whoever is available and qualified, and the route falls out of whatever remains.

Density-aware scheduling inverts that. Geography becomes a first-class constraint alongside skills and availability. When a client asks for Tuesday, the scheduler offers Tuesday morning because there are already three jobs in that quadrant that morning, rather than offering an open Tuesday afternoon slot that would require a cross-city run.

Clients accept this far more readily than schedulers expect. A client who says "Tuesday" almost never means "Tuesday at 2:40 PM specifically." Offering a two-hour window that happens to fit your route is not a worse client experience. Often it is better, because the technician arrives on time.

Habit Two: Zone Assignment With Deliberate Overlap

Hard territories create a different problem: a technician sitting idle in a quiet zone while an adjacent zone is overloaded.

The version that works is overlapping zones with a primary owner. Each technician has a home quadrant they cover by default and familiarity, plus explicit secondary coverage in one or two adjacent quadrants. Density improves because most work stays local. Flexibility survives because overflow has a defined path.

The side benefit is real and underrated: technicians who work the same geography repeatedly get faster at those buildings. They know the access quirks, the mechanical rooms, the site contacts. First-time fix rates rise in familiar territory for reasons that have nothing to do with driving.

Habit Three: Protect Emergency Capacity Instead of Absorbing It

Emergency calls are the single largest destroyer of route density, and the standard response makes it worse. A call comes in, dispatch finds whoever can get there, and that technician's carefully clustered afternoon is abandoned mid-route.

The alternative is to schedule for emergencies rather than react to them. That means deliberately leaving a portion of daily capacity unassigned, and rotating which technician holds it.

It feels wasteful. It is the opposite. A technician holding open capacity absorbs an emergency without destroying a route. A fully booked technician absorbing an emergency destroys their own route and often cascades into a second technician's route to cover the displaced work. This cascading effect is the same mechanism that turns one late start into three SLA breaches.

Habit Four: Batch Recurring Work Geographically, Not Alphabetically

Recurring maintenance contracts are the easiest density win available, and the most commonly wasted. Recurring work has flexible timing by definition. Nobody with a quarterly maintenance agreement cares whether the visit lands on the 8th or the 11th.

Yet recurring schedules are frequently generated by client name, contract start date, or whatever order they were entered into the system. Rebuilding a recurring schedule around geography rather than administrative order routinely removes 15 to 25% of travel with no change to service levels and no client conversation required.

If you do one thing from this article, do this one. It is the cheapest and it is entirely within your control.

Where Automated Dispatch Fits

Modern dispatch tooling, including the kind of AI-assisted dispatch that has moved into production over the past two years, is genuinely good at the density problem. It can hold skills, availability, SLA windows, travel time, and route density in view simultaneously and propose an assignment in seconds, which no human dispatcher can do consistently across sixty jobs.

Two caveats worth stating plainly.

It only works on structured data. A dispatch engine needs verified service addresses, real skill matrices, and honest job duration estimates. If your addresses are inconsistent and your durations are all set to the default sixty minutes, the engine will produce confident nonsense.

And it should propose, not decide. The operators getting real value keep a human approving assignments, because the dispatcher knows that the client at the third stop is mid-renewal negotiation and should not get the newest technician. That context is not in the data.

The NowKleen Version

NowKleen.ca had a density problem specific to recurring commercial cleaning: their schedule had been built up client by client over several years, and the geography of it was accidental.

They did three things. Every recurring contract was re-slotted around geographic clusters rather than contract start date. Technicians were given primary quadrants with defined secondary coverage. And a rotating portion of daily capacity was held open for same-day requests instead of being pre-assigned.

The headline is the jobs-per-day figure. Going from 4.6 to 5.8 completed jobs per technician is a 26% capacity increase with the same crew, the same trucks, and the same working hours. They did not hire anyone. They stopped driving.

The on-time start improvement was the one they had not predicted, and it turned out to matter most commercially, because on-time starts were what their commercial contracts actually measured.

Start Here

Move one: plot one ordinary day on a map. Take last Wednesday, every technician, every stop, drawn as lines on a single map. This is a two-hour exercise and it is the most persuasive thing you will show your leadership team this quarter. Nobody argues with the spaghetti.

Move two: rebuild your recurring schedule around geography. Recurring work is flexible and it is probably 40 to 60% of your volume. Group it by quadrant and by day. No client conversation required, no software purchase required, and it is typically worth 15 to 25% of your travel time on its own.

Move three: start measuring travel time as its own number. Not total hours worked. Not drive time bundled into job duration. A specific, reported figure for unbillable between-job travel per technician per day. You cannot manage the 94 minutes until it has a name and appears on a report somebody reads.

Renée keeps the spaghetti map printed on the wall behind her desk. Not the new one. The original, from that Wednesday in her eleventh year.

Her technicians finish 27% more jobs than they did, and they finish their days earlier. Nobody works harder. The trucks just stopped crossing each other.

*Basis: SynchronApp scheduling, routing, and GPS check-in data, NowKleen.ca implementation results, and general field service operating benchmarks. Figures in the composite cost model are illustrative and scaled to a twelve-technician operation. Content was rephrased for compliance with licensing restrictions.*