Oasis Intelligence
How to turn a due list into a routed week
The fastest route for one technician is the last decision, not the first. The bigger savings come from putting each due visit on the right day and with the right technician before anyone reorders stops. Here is a practical method for pest control and other recurring service teams, and what to measure so you know it worked.
Why route optimization often disappoints
Most field service tools now advertise route optimization. Read their help pages and a pattern appears: the optimizer reorders the stops already assigned to one technician on one day. Housecall Pro's help center says its drive-time optimization does not reschedule jobs to different days or change which technician a job is assigned to. Jobber's team has said its route optimization cannot yet be customized by technician or skill, and owners on its community forum describe routes that look right on a map but not on the road.
That matters because the expensive decisions happen earlier. If a stop sits on Tuesday while its neighbors are all on Thursday, no amount of reordering Tuesday removes the extra miles. Owners feel this as a planning problem rather than a routing problem: one pest operator on Jobber's forum described about five hours to route roughly 70 recurring accounts, and a PestPac reviewer wrote that routing was bad enough to need a full-time employee.
What a poorly built week costs
An illustrative example, with the assumptions shown so you can swap in your own numbers:
- Technician pay: the median pest control worker earns $21.75 an hour, according to the US Bureau of Labor Statistics. With payroll costs, assume about $28 an hour.
- Vehicle cost: the IRS 2026 standard mileage rate is 72.5 cents a mile.
- Waste: 20 extra minutes and 8 extra miles per technician-day is about $15 a day, or roughly $3,800 per technician per year over 250 working days.
- For ten technicians, that is about $38,000 a year in labor and vehicle cost, before counting the extra stops that time could have covered.
Treat published claims of 20 to 40 percent fuel savings with caution; they rarely show their baseline. Measure your own instead, as described below.
A six-step method
- Build the due list with windows, not dates. For each recurring customer, record the earliest and latest acceptable service date from their cadence and agreement. A quarterly customer due on the 15th might be fine anywhere from the 8th to the 22nd. Windows are what give you room to plan.
- Pin the anchors first: customers with fixed time windows, locked appointments, access or pet requirements tied to one technician, and jobs that need a specific license. Everything else flexes around them.
- Choose the day before the order. Group due work by area and assign areas to days, so each technician's day covers one tight cluster. This step usually saves more drive time than reordering ever will.
- Assign technicians by capacity and skill, then order stops by real road travel time, not straight-line distance. Leave a small buffer for overruns rather than filling every minute.
- Keep routes stable. Customers like a consistent day and technicians learn their routes. Lock the next 24 hours except for emergencies, make changes one to two days out expensive, and allow bigger moves only a week or more ahead.
- Repair disruptions locally. When a cancellation, a call-out or rain hits, rebuild only the affected days instead of the whole month, and compare every option against leaving things as they are.
A worked example
Take an illustrative pest control company with six technicians and about 600 quarterly customers, so roughly 200 visits fall due each month, about ten a working day.
Built the usual way, the office books visits close to each customer's due date and the routing tool reorders each technician's day. The result looks tidy on each day's map, but the same neighborhood gets visited on four different days by three different technicians.
Built with the method above, the planner first sees that 38 of this month's visits sit in one area with service windows that overlap. Assigning that area to two consecutive days and one technician removes three separate trips across town. The quarterly customers there all stay inside their windows, and two of them move by only three days. Reordering stops happens last, inside days that already make sense.
The point is not the specific numbers, which are illustrative. It is the order of decisions: windows, anchors, days, technicians, then stops.
What to measure each week
- Drive minutes per stop, from GPS or your routing tool.
- Stops completed per technician-day.
- Share of due visits completed inside their service window.
- Dispatcher hours spent building and repairing the schedule.
- Visits moved after they were confirmed, a measure of schedule churn.
Record a two-week baseline before changing anything. Without one, you will not know whether a new method or tool helped.
Common mistakes
- Booking each visit on its exact due date. It feels precise and destroys route density.
- Re-optimizing everything every night. Customers lose their usual day, technicians lose their routes, and churn rises.
- Using straight-line distance. Rivers, highways and school zones make map distance a poor guide to drive time.
- Filling every minute. A day with no slack turns one long service into a late afternoon for every customer after it.
- Judging a tool by its demo. Judge it by drive minutes per stop and dispatcher hours against your own baseline.
Where software helps, and where it does not
Software is good at the arithmetic: travel times, capacity, skills and service windows across hundreds of stops. It is bad at what nobody has written down, like the customer who must be first because of the dog. Any tool you use should show why it suggests a move, in minutes and miles, and let a person approve it. A schedule that rearranges itself without asking erodes the trust of customers and technicians alike.
How SwiftSched approaches it
SwiftSched is built around this method. It keeps recurring visits that are due in view, helps find the right day and technician for each one, and suggests a route with the estimated driving time. Every suggestion waits for a person's approval, and existing bookings stay put unless you move them. If you want to measure this on your own routes, a free leak review starts with your due list and a two-week baseline.
Sources
Questions owners ask first
What is the difference between route optimization and schedule planning?
Route optimization orders the stops already on one technician's day. Schedule planning decides which day and which technician each stop belongs to. Planning usually has the larger effect on drive time and capacity.
How much drive time can better routing save?
It depends on your route density and how routes are built today, so measure it. Record drive minutes per stop for two weeks, change one thing, and compare. Published percentages rarely show their baseline.
Should every recurring customer keep a fixed service day?
Keep fixed days by default because they help customers and technicians, and allow a change inside the customer's service window when it clearly saves time.
Do I need new software to do this?
Not to start. Steps one to three work with a spreadsheet and a map. Software pays off when you have more stops than a person can comfortably balance, or when a dispatcher spends hours each week rebuilding routes.