FieldRoutes Route Optimization: What the Optimize Button Can and Cannot Fix
FieldRoutes can order a route and spread recurring work across days. When the result still disappoints, the cause usually sits in the rules and the route book it was given.
In short
FieldRoutes route optimization orders the stops on a route and, through Intelligent Routing, can spread recurring work across days by preferred technician, day or region. When the Optimize button disappoints, the cause is usually upstream: rules the optimizer never sees, gaps in the route book and promises that leave no room. Fix those inputs, choose a goal, then judge the result route by route.
- FieldRoutes optimization is real: it sequences routes and can bulk-schedule by preferred technician, day or region.
- An optimizer only respects rules that are in the data, so a skill nobody entered is a skill nobody enforces.
- Timed appointments and blocked days set the shape of a week before any optimizer runs.
- Fewer routes and the same routes, fuller, are different goals that produce different plans.
- Judge a plan per route against a normal week, not by how clean the map looks.
On our sales calls with FieldRoutes offices, the first real question is nearly always a version of this one: what do you do better than the optimizer we already pay for? Behind it there is usually an owner who pressed Optimize, looked at the result and went back to planning by hand. The disappointment is real. In my view, the algorithm is rarely the reason.
The part of PestRouting that reads FieldRoutes (formerly PestRoutes) is my responsibility, so I know the data that FieldRoutes route optimization works from in detail. PestRouting plans a week or a month of routes for one office under that office's own rules and writes the adopted plan back to FieldRoutes, which stays the system of record. Below is what that data tends to show when the button disappoints.
What FieldRoutes route optimization actually does
FieldRoutes describes two levels in its HomeShield case study. On a single route of 10 to 20 stops, optimization orders the stops to cut drive time. Across several routes, it can choose days, times and order from customer preferences and due dates. Intelligent Routing adds bulk scheduling, with work assigned by preferred technician, day or region.
That is a serious toolset, and most offices use some of it. In the PCT survey FieldRoutes cites in its route density article (Guide to Labor Savings, November 2024), 72% of pest control professionals said they already use software that optimizes routes, and 55% ranked route density first among ten productivity factors. Route software is that common, and density still tops the wish list. The tool on its own is not closing the gap.
Key insight: An optimizer can only work with the rules and the days it is given. When its result looks wrong, read it as a report on the input.
Five reasons the Optimize button disappoints
| What you see | Where the cause usually sits | What to check in FieldRoutes |
|---|---|---|
| A termite or commercial job goes to the wrong technician | Required skills or licenses were never entered | Skills on each service type and each technician |
| Stop order changes, drive time does not | Timed appointments pin the route | How many visits per route carry a Timed window |
| Work lands on a day nobody can really work | The route book says the day is open | Holiday routes, blocks, start addresses |
| The plan looks feasible and runs late by noon | Durations come from templates | Subscription durations against time on site |
| The map is cleaner, and the team hates it | Nobody chose the goal | Fewer routes, or the same routes with more work |
Rules the optimizer never sees
An optimizer enforces a skill only if the job requires it in the data and the technician holds it there. In one of our published results stories, skills had never been entered in FieldRoutes, so the first planning run let anyone take any job. Nobody had made a mistake. The rule lived in the dispatcher's head. Our guide to FieldRoutes skills and licenses covers how to get it into the data.
Preferred days have a similar gap. FieldRoutes holds one preferred day per subscription, so a customer who takes Tuesday or Thursday is stored with one of them. The other day is invisible to every tool that reads the field.
Promises that leave no room
Each FieldRoutes appointment carries an arrival window: anytime, AM, PM or Timed. A Timed visit fixes one point in the day, and two of them on opposite sides of a territory decide the route's shape before any sequencing starts. Google's documentation on routing with time windows treats each window as the only span in which a visit may happen, which is why a heavily timed route barely moves when you run it again. When a Timed window is worth that price is the subject of our piece on preferred time vs exact time.
Days that look open but are not
The route book also tells the optimizer who can work when. A holiday route that still takes bookings, a block over half a day or a technician with no start address each say something false about capacity. When PestRouting reads FieldRoutes, it treats a technician's day as off when none of their routes that day allows API scheduling. A route titled "Vacation" that still takes bookings gets planned like any other, because software reads the setting and ignores the title.
Durations from the template
Every visit carries a duration. When the subscription says 30 minutes and the job takes 45, the plan is feasible on screen and late by lunch. Our audits begin with a list of these gaps: visits with no recorded time, work that needs a skill nobody is on record as holding, visits the preferred technician did not do. Each gap gets one stated assumption, applied to both sides of the comparison.
A goal nobody chose
Some owners want fewer routes and a smaller labor bill. Others tell us every technician has to work every day, and they want the same routes, fuller. Both are legitimate, and they produce different plans. A pure mileage optimizer can leave one technician with almost nothing, which is useful to know and hard to dispatch. In PestRouting each office picks Territory, which gives every technician a compact area and shares the work within a set allowance, or Max efficiency, which builds the tightest routes and balances nothing.


Fix the inputs in this order
Pressing Optimize again on the same week teaches you nothing new. Work through the inputs instead, in this order:
- Write down the rules your dispatcher actually follows: preferred technician, preferred days, time windows, skills and licenses, areas, banned technicians. Mark each one as stored in FieldRoutes or kept in someone's memory.
- Move every remembered rule into the data, or into a planner that holds it. Territories are the rule most often missing, and our guide to territory management in FieldRoutes walks through them.
- Clean the route book for the next four weeks: closed routes, blocks, start addresses, inactive technicians.
- Count Timed appointments per route. If most routes carry several, change the booking habit before you judge any optimizer.
- Choose the goal: fewer routes, or the same routes with more production on each.
- Then optimize, and compare drive time, distance and production per route with a normal week of the same office.
How to tell the optimizer from the setup
Re-plan a month that already happened. Take one office with the same technicians, visits and rules, plan the month again, and compare it with what the team actually drove. If the re-plan is much better, the setup was holding the routes back. If it barely moves, the routes were already good, which is worth knowing too.
That is how our free audit works. The ranges we publish for better planning are 15 to 30% fewer miles per technician route, 10 to 25% less drive time per technician per day and 15 to 40% more production. In one published case, the same team produced 49% more per hour of work, with 23% fewer miles per stop and 15% less drive time per route.
Frequently asked questions
Does FieldRoutes have route optimization?
Yes. FieldRoutes orders the stops on a route to cut drive time, and its Intelligent Routing can bulk-schedule recurring work across days by preferred technician, day or region. What it can respect depends on the rules stored in your account.
Why does the FieldRoutes Optimize button barely change my routes?
Usually because the route was pinned before the button ran. Timed appointments, blocked hours and fixed technician assignments leave very few legal ways to drive the day, so a new run lands close to the old one. Count the Timed visits and check durations before blaming the algorithm.
Why does optimization send the wrong technician to a job?
Because the job's requirement is missing from the data. If the service type requires no skill, or the technician's license is not recorded, every technician looks eligible to the optimizer. Enter required skills on service types and the skills each technician holds first.
What does PestRouting do differently from FieldRoutes optimization?
PestRouting plans a whole week or month for one office at once and treats seven assignment rules as rules it may not break: preferred technicians, preferred times, preferred weekdays, required skills, a consistent technician, banned technicians and service areas. A stop it cannot place is listed with the reason instead of being forced onto a route, and adopting a plan writes it back to FieldRoutes.
Do I need to replace FieldRoutes to get better routes?
No. FieldRoutes stays the system of record for customers, subscriptions, billing and the schedule. A planner that connects to FieldRoutes reads that data, plans the routes and writes the adopted ones back, so the office and the technicians keep working in FieldRoutes.
Want to see your own routes re-planned under your own rules? Request a free route audit of one month of your routes.
Ran into a word you would define differently? The glossary says how we use every term on this page.

Written by
Ahmed Abd El DayemCo-Founder & CTO, PestRouting
Responsible for product, engineering and data security at PestRouting, including the route planner and the FieldRoutes integration.
Ahmed on LinkedInLiked this? Get the same analysis on your routes.
30 minutes. We listen first. Then you decide if a real audit makes sense. No pitch, no pressure.



