Drive time is the largest cost in a pest control business that nobody puts on an invoice. A technician who spends two and a half hours a day in the truck is costing you roughly a third of a billable day, every day, forever.
Getting an hour of that back is worth more than almost any price increase you could push through. Here is how.
Work out what your drive time is actually costing
Before optimising anything, measure it, because the number is usually worse than the guess.
Take last week. For each technician, add up total hours on the clock and total hours actually on site treating. The difference, minus lunch and admin, is drive.
A worked example. A technician works 8 hours, completes 9 stops averaging 35 minutes on site. That is 5.25 hours of work and roughly 2.25 hours of driving and parking. At a $95 hourly cost — the method for calculating yours is in how much to charge for pest control — those 2.25 hours cost $214 a day, or around $53,000 a year for one truck.
Cut it by 40 minutes a day and you have freed roughly $21,000 a year of capacity per technician, or room for two more stops a day without hiring anyone.
Cluster by day of week, not by customer convenience
This is the single highest-impact change and it is free.
Most small operators schedule recurring visits whenever the customer prefers, which scatters a day across the whole service area. Instead, divide your territory into zones and assign each zone a day.
- Monday — north zone
- Tuesday — east zone
- Wednesday — central and commercial
- Thursday — south zone
- Friday — west zone, plus overflow and callbacks
Then when you sell a quarterly plan to a house in the north zone, it goes on a Monday. Not because Monday suits the customer best, but because every other north-zone visit is also on Monday.
Sell it as a feature rather than apologising for it: "We're in your neighbourhood on Mondays, so we'll always be with you on a Monday." Customers accept this readily, and it converts a scattered day into a dense one.
Keep one day — Friday here — deliberately loose for the work you cannot plan: callbacks, re-services and emergencies. Protecting the planned days from interruption is most of the value.
Sequence the stops properly once they are clustered
Clustering gets you to the right part of town. Sequencing decides how much you drive inside it.
Humans are bad at this. The instinct is to order stops north to south, or in the order they were booked, and both reliably produce a route that crosses itself two or three times. A nine-stop day has 362,880 possible orders; nobody is finding the good one by eye.
The practical rules if you are doing it manually:
- Start at the edge furthest from home and work back, so the last stop is closest to where you finish
- Never cross a highway, river or railway twice — handle everything on one side before crossing
- Group tight pockets — four stops in one subdivision are one stop with walking between them
- Put the time-sensitive jobs where they fit the geography, not at the start by default
This is exactly the kind of problem software should solve. PestShift optimises the stop order within a technician's day and sets arrival times along with it, leaves appointments the customer was promised a time for where they are, and warns if the technician assigned does not hold the license category the job requires. What it does not do is move jobs between technicians automatically — you decide who gets what, and then each day gets optimised.
Protect the promised times
The limit on any optimisation is the promises you have already made.
Some jobs genuinely have a fixed window: a commercial kitchen that can only be treated before opening, a customer who took a morning off work, a tenant who has to let you in. If the optimiser moves those, you have traded drive time for a missed appointment, which costs far more.
So mark them. Every scheduling system worth using needs a way to say "this one does not move", and then build the flexible stops around the fixed ones. In practice a typical day has two or three anchored jobs and six or seven that can go anywhere, which is plenty of freedom to work with.
Stop booking jobs that break the route
The best routing decision happens at the point of sale, not at dispatch.
When a prospect calls from forty minutes outside your cluster, that account consumes an extra hour and a half of unbillable time on every single visit for as long as they are a customer. At quarterly service, that is six hours a year of driving for roughly $460 of revenue.
You have three honest options: decline it, price it to cover the drive, or put it on the one day you are already in that direction and only accept more work there as the cluster grows.
The thing not to do is take it at standard price because the schedule looked empty that week. The emptiness is temporary; the account is not. This is why how to build a recurring pest control route treats geography as the primary filter when adding customers.
Cut the time at each stop, not just between them
Routing saves minutes between jobs. Preparation saves them at the door.
Arrive knowing the property. Gate codes, dog, where the crawlspace access is, what was applied last visit and what the customer complained about. A technician who has to phone the office for a gate code has lost ten minutes and some credibility.
Load the truck once. A technician who returns to the shop mid-route for a product has wasted an hour. Pack for the whole day's work, which requires knowing the day's work the night before.
Finish the paperwork at the stop. The application record has to be made anyway — see pesticide application record keeping — and doing it at the truck takes two minutes, while reconstructing nine of them at 8pm takes an hour and produces worse records.
PestShift gives each technician a day view with their stops in driving order, the gate codes and property notes, and what was used last time, with the chemical record captured on the job rather than afterwards.
Review the route monthly, not never
Routes decay. Customers cancel, new ones join, and the clean zones you drew in March have holes in them by September.
Once a month, look at each day and ask two questions: are there stops that no longer belong to this day's zone, and are there pockets thin enough to merge into a neighbouring day? Moving six accounts between days once a quarter keeps the whole structure tight.
This is also when thin neighbourhoods reveal themselves, and a thin neighbourhood is a marketing target rather than a problem — the argument for door-knocking the streets around existing customers in pest control marketing ideas.
What good looks like
For a residential route in a reasonably dense suburb, a technician doing general pest maintenance should be completing nine to twelve stops a day with drive time under 90 minutes total. If you are at seven stops and three hours of driving, the problem is almost always scatter, not speed.
Fix the clustering first, sequence second, and the per-stop preparation third. In that order, because no amount of clever sequencing rescues a day with stops in four different towns.
PestShift handles the day-level routing, the recurring plans that feed it and the records that come out of it, starting at $49 a month for one technician. See pricing.