An open-plan office where several people work side by side at long desks
Back to Blog
Working With FieldRoutes
Ahmed Abd El Dayem, Co-Founder & CTO
8 min read
Published · Updated

5 FieldRoutes Dispatch Mistakes That Cost You Thousands Every Month

FieldRoutes gives dispatch fast tools: recommended routes, the Job Pool, Fill Routes and booking from the field. Five habits turn that speed into route debt, and each one has a fix.

In short

The expensive FieldRoutes dispatch mistakes happen before a route looks messy: promises made before dispatch sees the map, one queue for every kind of work, time windows handed out as a courtesy, exceptions that never expire, and days that end without a review. FieldRoutes books what each request asks for. Deciding which promises should exist is the dispatcher's job, and that is where the money is lost or kept.

  • A messy route is usually a symptom. The cost was created when the promise was made.
  • Recurring work, initials, reservices and one-time jobs need different rules, even on one board.
  • An exact-time window is capacity you spend, not a courtesy you give.
  • Every exception needs a reason, an owner and an end date, or it becomes the rule.
  • A short close-out review each day stops the same mistake from being paid for every week.

Most teams think FieldRoutes dispatch goes wrong when the route looks messy. It goes wrong earlier, at the moment a promise is made. A customer is offered the wrong day, a callback lands on a recurring route, an old exception survives one more month. By the time the board looks chaotic, the expensive decision is already made.

I call the result dispatch debt: future route damage created by today's promises, overrides and queue decisions. PestRouting plans routes on top of FieldRoutes data, and the limits on every plan we build were set when the appointments were booked: the day, the window, the technician. Five habits feed the debt. Each has a number you can watch.

Dispatch numberWhat it reveals
Exact-time shareHow much route flexibility is spent before anyone sequences the day
Same-day insertion rateHow often new work lands on a route that was already built
Cross-territory shareHow often a short-term request breaks who owns an area
Repeat override rateHow often dispatch fixes the same kind of failure twice
Open exception countHow many old notes and promises still shape today's routes

What FieldRoutes gives a dispatcher, and what it leaves to you

FieldRoutes (formerly PestRoutes) covers the mechanics of dispatch well. Its help center describes Recommended Routes, which suggests routes for a customer based on distance, with filters that match technician skills and hide routes over capacity, and a Job Pool that shows customers due for service and those closest to the customers already on a route. Fill Routes considers both existing appointments and jobs that are due when it builds routes. Since 2023, its mobile app lets technicians schedule appointments from the field.

That is a lot of speed. It also means a weak promise gets made faster, and by more people. FieldRoutes books what each request asks for. It does not decide which promises should exist, which work belongs on which route, or when an old exception should end. Those decisions are dispatch policy, and the five mistakes all sit there.

Mistake 1: letting booking promises outrun dispatch rules

In many offices, sales, CSRs or technicians make the promise first and dispatch is expected to make it work later. That is backwards. A route is shaped more by booking policy than by stop order. If the company promises whatever is asked for, dispatch inherits a problem no optimizer can solve.

The fix is a promise ladder that every person who books follows, including technicians booking from the field. Offer the area's day first, a preferred window second, an exact time only for a real requirement. A sold job should also reach scheduling route-ready, carrying:

  • the job type: recurring, initial, callback, one-time or commercial;
  • the scope and what the estimate found;
  • access details such as gate codes, pets and the contact on site;
  • the promise level the customer was actually given;
  • whether it needs a licensed specialist.

Without those, dispatch spends its morning doing investigation that belonged upstream.

Mistake 2: running one queue for every type of work

Recurring stops, initials, callbacks and one-time jobs behave differently. When they all compete in one queue, the loudest item wins instead of the right one.

FieldRoutes already holds the information to separate them. In PestRouting, an initial service of a subscription counts as Initial, an appointment booked with a reservice reason as Reservice, an appointment with no subscription as One-time service, and everything else as Recurring. Each kind gets its own rules: only a Recurring visit may change its day, while a booked callback or initial keeps its day and may only shift in time. A session can also plan just the recurring work and leave callbacks exactly where the office booked them.

Table of what may change about a booked visit in PestRouting under each scheduling mode, for recurring, one-time, reservice and initial visits
What the planner may change about a booked visit, by kind of work. Only recurring visits may move to another day, and only when the day's mode allows it. Callbacks, initials and one-time jobs keep their day.

Mistake 3: treating time windows as a courtesy

Dispatchers say yes to exact times because the call feels easier. A time window is a routing constraint, though, and every one narrows the ways a day can be ordered. Google's OR-Tools documentation on routing with time windows notes that the arrival window a vehicle can actually hit is usually smaller than the window the location allows. One exact time at 10:00 squeezes the stops on either side of it too.

Treat every exact appointment as capacity you are spending. Approve it for a real reason, and log the reason.

Exact times are not the mistake. Failing to tell them apart from preferred windows is. Our comparison of preferred time and exact time in FieldRoutes covers when each one fits.

Mistake 4: letting exceptions become permanent policy

An exception turns into a rule in three steps. Dispatch absorbs it once, then again, until it is "how we handle that customer." It becomes precedent, so the next request is easier to grant. Then the schedule itself is built around it, and the written rules stop describing the operation.

In FieldRoutes the leftovers are easy to find once you look: a preferred technician from an old territory, an appointment someone locked for one week and never unlocked, a holiday route that still takes bookings. PestRouting goes by what the data says, never by a name. A route that does not allow API scheduling reads as a day off. A route titled "Vacation" that still takes bookings gets planned like any other.

Treat exceptions like open tickets. Each needs a reason, an owner and an end date. If it has none of the three, it should not survive as a routing rule.

Mistake 5: ending the day without a learning loop

Many teams survive the day and move on, which guarantees a repeat. A fifteen-minute close-out each afternoon is enough: which overrides were avoidable, which jobs went into the wrong queue, which exact times did damage, which technicians were moved and why. Then change tomorrow's defaults to match.

The data helps. PestRouting's Follow-Up Visits list shows the last seven days of visits that did not happen, as No-show, Cancelled, Awaiting first visit or Needed more time, each with a suggested next step. Stop Adherence and On-Time Rate show whether planned stops were done on the planned day and on time.

Managing dispatch for 15 routes

At around 15 routes, one person can no longer hold every technician's licenses, preferred customers and days off in their head. The rules have to move out of the dispatcher's memory and into the system. A workable weekly rhythm looks like this:

  1. Plan next week in one pass, for example every Friday, from the subscriptions due and the technicians available.
  2. Freeze the next two days, so technicians know their routes and late changes need a reason.
  3. Keep same-day work in its own lane with a daily cap, as set out in our same-day request playbook.
  4. Run the close-out review daily and the dispatch numbers above weekly.

PestRouting can run the first two steps on a schedule. An automation can plan next week every Friday, and an office's Planner Rules can say "Up to 2 days out: add nothing and move nothing." In the route planner, preferred technicians, skills and service areas are rules a plan never breaks while their switches are on, and an adopted plan is written back to FieldRoutes. Who sets those rules is a leadership question, covered in why dispatch is a leadership problem.

Frequently asked questions

How does FieldRoutes support technician dispatching and mobile field operations?

FieldRoutes suggests routes for a customer by distance, filters them by technician skills and capacity, lists due customers in the Job Pool, builds routes with Fill Routes and lets technicians schedule from the field in its mobile app. It books what each request asks for, so the dispatch rules that decide which promises are made still have to come from the office.

How do I manage technician schedules and dispatch for 15 routes?

Plan the coming week in one pass, freeze the next two days, give same-day work its own capped lane and review the day every afternoon. At that size the rules for licenses, preferred technicians and days off need to live in the system, not in one dispatcher's memory.

What is dispatch debt?

Dispatch debt is the route damage that today's promises, overrides and queue decisions cause later. It shows up as cross-territory driving, exact-time pressure and repeated manual fixes on routes that were fine when they were first built.

Should every new appointment go straight onto a technician's route?

No. New work should first be checked against the route pattern, the kind of work and the capacity left. Some jobs belong in the Job Pool until they fit an area's day.

When should dispatch approve an exact-time appointment?

Approve it when a real requirement needs it, such as a commercial site's access hours or a customer who can only be home at one time. Log the reason so it can be reviewed later.

To see how much of your current schedule is held by promises nobody made, our free route audit re-plans one month of your FieldRoutes routes under your rules and compares it with how it ran.

Ran into a word you would define differently? The glossary says how we use every term on this page.

Share:
Ahmed Abd El Dayem

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 LinkedIn

Liked 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.

Related articles

View all articles