How do you reduce windshield time for field techs?
Measure it first: have every crew clock travel as its own activity for two weeks, because the real number is almost always higher than the dispatcher's estimate. Then make three changes: cluster jobs by geography instead of by customer relationship, put the furthest job first and start before rush hour, and give crews an optimized route on a phone map instead of a printed job list. Most teams recover five to eight hours per tech per week this way.
Windshield time, meaning the hours crews spend behind the wheel instead of on a job site, is the single largest hidden cost in most field-service P&Ls. It doesn't appear on an invoice, doesn't get flagged in QuickBooks, and doesn't show up in end-of-day reports. But it eats 20% to 35% of a typical tech's day.
Measure it before you fix it
You cannot manage what you don't measure. Start by asking every truck to clock 'travel' as a distinct activity for two weeks. Most teams are shocked: the number is almost always higher than the dispatcher's guess.
Three changes that consistently cut windshield time
1. Cluster jobs by geography, not by customer relationship
Dispatchers instinctively assign the 'good' customer to the 'good' tech. That's usually wrong. Assign by proximity first, and let routing win over relationships. Use a two-tier rule: assign by zone for standard work, override only for jobs that genuinely need a specific technician.
2. Front-load the morning
The first job of the day is the one most sensitive to traffic. Push start times to before rush hour when possible, and put the furthest job first while the tech is fresh and the roads are clear.
3. Give techs a real map, not a list
A route optimized by a computer, shown on a phone map with turn-by-turn built in, will beat a printed job list every day. This is the single highest-ROI feature in a modern FSM tool.
What the reclaimed hours are worth
A five-truck team that reclaims one hour per tech per day, at an $85 fully-loaded billable rate, adds $110,000 of capacity per year. That's before considering the fuel, wear, and overtime savings.
"We didn't hire a sixth tech last spring. We just gave the five we had their afternoons back."
The best windshield-time reduction is not a big software rollout. It is a two week measurement pass followed by three small changes. Do that first, then let the platform automate what you've already proven works.
Common questions
- How much of a tech's day is windshield time?
- In most field service businesses travel takes 20% to 35% of a tech's day, and it rarely appears anywhere in reporting because it is not billed and is not broken out in payroll. The only way to know your own figure is to track travel as a separate time entry for a couple of weeks.
- Should we pay techs for drive time?
- Travel between job sites during the workday is generally paid time, and your obligations depend on state law and how you classify the commute to the first job and home from the last. Talk to your payroll advisor about your state. Operationally, tracking travel separately is what lets you see the cost either way.
- What is reclaimed drive time actually worth?
- Take the hours recovered per tech per day, multiply by your fully loaded billable rate, and multiply by crew size and working days. A five-truck team recovering one hour per tech per day at an $85 loaded rate adds roughly $110,000 of annual capacity, before fuel, vehicle wear, and overtime savings.