How to Reduce Windshield Time for Field Technicians (and Add 1-2 Jobs per Day)

Windshield time is the most expensive thing on your P&L that nobody is tracking. It is the drive time between jobs. It is unpaid by the customer. It is paid by you. And for most field service businesses we have looked at, it is eating 25 to 35 percent of every technician shift.

The math is brutal once you look at it. A technician running 5 calls a day at a $200 average ticket bills out about $1,000 in revenue per day. Across 22 working days, that is roughly $22,000 of monthly revenue per tech. If a quarter to a third of their day is spent driving, the upside from compressing that window is not a rounding error — it is one extra job per day. At 22 working days, that is $4,000 to $5,000 of additional monthly revenue per tech. Run 10 techs and the number is $40,000 to $50,000 a month. The same payroll. The same trucks. The same dispatcher.

This post walks through what windshield time actually costs, why it gets out of hand, the four or five changes that move the number the fastest, and a 30-day plan to bring your team from a 30 percent baseline toward the 12 to 18 percent range we consistently see in the best-run shops.

Windshield time is the clock that runs from the moment a tech leaves one job site to the moment they start the next one. Not driving back to the warehouse for a part. Not the morning commute. Not the lunch detour. Job-to-job transit. Pure overhead.

The reason it does not show up on your P&L is that it is hidden inside labor cost. You pay your tech for an eight-hour shift. They bill out billable hours to customers. The gap between the two is your windshield time plus admin time, and most shops treat both as a fixed cost of doing business. They are not fixed. They are a variable cost that responds to scheduling decisions you are making right now.

The industry baseline most shops settle into is somewhere in the 25 to 35 percent range. Two hours of every eight hour shift in the truck, between jobs. We have seen organized shops with disciplined zoning and tight appointment windows operate sustainably in the 12 to 18 percent range. The delta — roughly 10 to 15 percentage points of an eight hour day — is one full job per tech per day. That is the prize.

We are going to do this with conservative numbers. Adjust them to your shop, but the shape of the curve will hold.

Assume a tech doing 5 jobs per day, average ticket $200, working 22 days per month. That tech is generating about $22,000 of monthly revenue. If their day is 8 hours, and they spend 30 percent of it driving between jobs, they have 5.6 hours of billable customer-site time spread across 5 calls — roughly 67 minutes per job on site.

Now compress windshield time to 18 percent. They now have 6.56 hours of on-site time available. That is just under one extra hour. Most residential or light commercial service calls are 60 to 90 minutes on site. You just fit another job into the day without adding a single hour to anyone's timecard.

The revenue uplift on a single tech is $200 per day × 22 days = $4,400 per month. Across a 10-tech operation, that is $44,000 per month of pure-margin revenue — because the truck, the tech, the dispatcher, and the office are all already paid for. The marginal cost of that extra job is roughly the cost of parts plus maybe a small fuel and depreciation delta. At even a 50 percent gross margin on the extra revenue, you are adding $22,000 of monthly gross profit on the same payroll base.

Two caveats before anyone runs the numbers to their CFO. First, this assumes you have enough demand to fill that sixth slot. Most service businesses we talk to do — the bottleneck is dispatch capacity, not lead flow. Check your booking backlog. Second, this assumes ticket size holds. Some shops see ticket size dip slightly as throughput rises because techs become more transactional. Watch the average and protect it with upsell training, not by slowing back down.

Before you can fix it, name what is causing it. In our experience working with field-service shops on this exact problem, the windshield time problem is almost always one or more of the following four root causes.

The most common pattern: a tech starts the day in the north of the metro, drives 35 minutes south for the second call, drives 40 minutes east for the third, then comes back north for the fourth because that customer specifically asked for an afternoon window.

This happens when dispatch is reactive rather than zoned. Calls come in, they get slotted to whoever has an open hour, and the geography is an afterthought. Two or three reschedules later, you have a route that looks like spaghetti when you map it out.

The fix is to assign techs to geographic clusters. Tech A owns the north zone. Tech B owns the south. Tech C floats. Even rough zoning — quadrants of the metro — compresses drive time meaningfully because every job that comes into a zone is a candidate for the tech who is already in it.

Even within a single zone, the order of jobs matters. A tech doing five jobs in the same zone can still rack up an extra hour of windshield time if the sequence is wrong — last job at the far end of the zone, drives back across to get home, no buffer for the third job slipping.

The fix is to sequence based on a traveling-salesman-aware route, not on the order the calls came in. Modern dispatch software handles this — give it the day's stops and it solves for shortest route. The shops still printing out a list of calls in arrival order and handing it to the tech are leaving 15 to 25 minutes a day on the table per tech, just from sequencing.

The classic "we will be there between 8 a.m. and 4 p.m." appointment window is the enemy of route optimization. When every slot is an all-day slot, you cannot sequence the day tightly because the customer expects you when you arrive, and you cannot promise the next customer a time because you do not know when you will leave.

Moving to two-hour appointment windows does three things at once. It forces tighter scheduling on the back end. It signals to customers that you are a tighter operation, which raises perceived quality and tolerance for higher prices. And it dramatically reduces no-shows and missed calls, because customers do not have to take an entire day off work — they plan around a known two-hour block.

The shops that pull this off do it with realistic windows. Not 30-minute windows that get broken every day. Two-hour windows you can actually hit. The discipline is in the dispatch tool calibrating travel time honestly.

Plumbing leak. Heat out in winter. Refrigeration down at a restaurant. Emergency calls are real revenue, but if you handle them by yanking your nearest tech off their route and dropping them on the emergency, you have just broken three other appointments and added an hour of drive time on the back end as the tech tries to catch up.

The shops that handle this well do one of two things. They keep a dedicated emergency-response tech who runs a lighter pre-scheduled load and absorbs emergencies as they come in. Or they use dispatch software that re-optimizes the day in real time when an emergency comes in — re-sequencing the remaining jobs and notifying affected customers of revised windows automatically. The worst version is dispatchers manually shuffling the schedule in a calendar tool while the phone is ringing. That is where the windshield time creeps back in.

If you can only make one change this quarter, here is the order we would push for, based on what we have seen move the needle fastest at small and mid-sized service shops.

Draw four to six zones on a map of your service area. Assign primary techs to each zone. Default new bookings to the zone tech unless the schedule forces an override. This is the single change that pays back fastest because it requires no software — a paper map and a dispatcher decision is enough — and it compresses the worst windshield offenders immediately.

Within a week or two you will see drive time per tech drop measurably. You will also see a side benefit: techs start to know their zones, their regular customers, and the building quirks. First-time-fix rates rise because the same tech keeps seeing the same equipment.

Move from 4-hour or all-day windows to 2-hour windows on at least your residential book. Be honest with your dispatch tool about travel time so the windows are hittable. Train your CSRs to set the expectation that the customer needs to be home for the window, not just somewhere reachable.

Two-hour windows do double duty. They compress the dispatcher's options enough to force tighter routing, and they raise customer satisfaction because the customer is not blocked out for an entire day. Most shops that make this switch see no-show rates fall and tip/review scores rise alongside the windshield time drop.

If you are still printing out the list of jobs and asking the tech to figure out the order, this is the easiest upgrade you can make. Dispatch software that solves the traveling salesman problem across the day's stops will trim 10 to 25 minutes per tech per day from sequencing alone.

The upgrade matters most when the dispatcher is shuffling things on the fly — the system re-solves the route every time a job is added, cancelled, or extends. Without that, your dispatcher is doing optimization math in their head while the phone rings.

One of the silent windshield-time killers is the mid-day trip back to the warehouse or supply house for a part the tech could have anticipated. The fix is structural: capture enough information at booking time — make, model, symptom, age of equipment — that the tech knows what they are walking into and what they are likely to need.

The best shops we have seen pair this with truck-stock discipline. The truck carries a high-frequency parts kit calibrated to the work the tech actually does in their zone. The booking captures the symptom-to-likely-parts mapping. The tech rolls with what they need on board and pulls the rare parts via a runner or a same-day depot drop.

Get this right and a meaningful chunk of "return to base for parts" drive time disappears.

No-shows are wasted slots. A wasted slot is a job's worth of windshield time plus zero revenue. Confirmation flows — automated text and email 24 hours out, with an easy reply-to-confirm or reply-to-reschedule — typically cut no-show rates by half.

The ROI is not abstract. A no-show on a tech doing five jobs a day is 20 percent of that day's revenue. If your no-show rate is 8 percent and you cut it to 4 percent, you have effectively recovered 4 percent of total revenue at zero marginal cost.

You can take the first two steps — zoning and tighter windows — with a whiteboard and discipline. Steps three through five start to require software that does specific things. Here is the short list of what the dispatch tool needs to handle for windshield time to keep falling.

Deelo's [Field Service app](/apps/field-service) handles the dispatch, scheduling, and mobile work-order side of this. Zone assignment, two-hour windows, route sequencing, drag-and-drop reschedule, mobile job completion, customer confirmation flows.

The [Fleet app](/apps/fleet) handles real-time truck location and route history, so you can audit windshield time at the end of the week and see whose routes got out of hand. It also feeds GPS data back into dispatch decisions in real time, so the "who is closest" question takes a glance, not a call.

Where it gets interesting is the [AI Assistant](/apps/assistant). When a tech marks a job complete on the mobile app, the assistant can automatically re-evaluate the rest of their day, look at open jobs in their zone, and surface the best next job to slot in if there is room. It can also flag when a customer's confirmation is overdue, when a tech is running long enough that the next window is going to slip, or when a same-day cancellation has opened a slot that a backlog customer would happily take.

This is the layer that turns a static schedule into a self-healing one. The dispatcher does not have to be watching the map all day. The assistant pings them when intervention is needed.

And because Field Service, Fleet, and the assistant all run on the same customer record and the same job record, there is nothing to integrate. The data the assistant uses to re-optimize the day is the same data the tech is updating in the mobile app. No Zaps. No webhooks to break.

Here is the order we would run this in. Most shops can complete this in a single quarter, with measurable results inside the first month.

Before you change anything, you need a number. Pull GPS data from your fleet tracker or your dispatch software for the last 30 days. For each tech, calculate the percentage of their on-clock time spent driving between job sites — not commute, not lunch, not parts runs. Just job-to-job transit.

If you do not have GPS, run a one-week manual measurement. Have each tech log the time they leave each job and arrive at the next. Even a rough estimate gives you a baseline to beat. Most shops are surprised by what the number is. The ones who think they are at 20 percent are usually at 32. The ones who think they are at 30 are sometimes at 40.

Pick the number you are going to push to. Twelve to 18 percent is the target zone. Eighteen percent is a reasonable first-quarter goal if you are starting north of 30.

Map your service area. Carve it into four to six zones based on actual job density, not just neat geographic boundaries. Assign primary techs to zones. Communicate the assignments to dispatch and to the techs themselves — this is not just a back-end change, it is something the team needs to buy into.

Keep one or two techs as floaters who can cover cross-zone overflow and emergencies. The floaters absorb the variability so the zone techs can run dense, optimized days.

Move your residential book from 4-hour windows to 2-hour windows. Update your CSR scripts and your booking page. Be honest about what is hittable in each zone — if the south zone genuinely has more traffic and longer drive times, do not promise the same windows you promise in the more compact downtown zone.

Measure on-time arrival rates the first two weeks closely. The point is not to over-promise. If you are hitting fewer than 90 percent of windows in week three, widen them back to 3 hours and tighten again as routing improves.

If you are not already on dispatch software that auto-sequences the day's jobs, this is the week to switch. Pick a tool that handles the items in the checklist above. Run it in parallel with your existing process for a few days, validate the routes, then cut over.

This is also the week to add customer confirmation automation — a text 24 hours out with a tap-to-confirm. Most field service platforms have this built in; if yours does not, it is one of the highest-ROI integrations you can add.

Pull the windshield time number again at the 30-day mark. You should see a measurable drop — typically 5 to 10 percentage points from the changes above. If you have not, the most common culprit is dispatch falling back into reactive habits. The schedule starts the day looking optimized, then a cancellation comes in, then an emergency, and by 2 p.m. the routes have unravelled.

Hold a 15-minute weekly review with dispatch. Look at the windshield time number by tech. Look at the worst route of the week and ask why. The shops that hold the gains are the ones that make this a Monday-morning ritual until it is muscle memory.

Once you are sustainably in the 18 to 22 percent range, push harder. The 12 to 18 percent shops are not doing anything magical — they are doing the same playbook with more discipline and with all the dispatch automation actually working.

Cutting windshield time looks like a routing exercise. It pays off as a margin exercise. The extra job per tech per day is the most visible benefit, but there are three more that show up over the following quarters.

First, customer satisfaction rises. Tighter windows, fewer reschedules, more on-time arrivals — all of it shows up in reviews and repeat rates. Shops that move to two-hour windows often see review scores rise a half-star within a quarter.

Second, technician retention rises. Techs hate driving more than they hate working. A day with six on-site jobs feels productive. A day with four jobs and three hours of drive time feels like wasted shift. The shops with the lowest windshield time also tend to have the lowest tech turnover, and tech turnover is one of the most expensive line items in field service.

Third, you can raise prices without losing trust. A shop that hits a two-hour window is perceived as more professional than one that does not. That perception underwrites a price premium of 5 to 15 percent in most markets we have seen. The premium falls straight to gross profit.

None of this requires growing the team or buying more trucks. It requires looking at the time in the truck as a number you can move, not a fixed cost of doing business. Move the number. The revenue follows.