Dispatcher on the phone at a weekly schedule grid of color-coded technician routes, handwritten notes beside the keyboard
Back to Blog
Scheduling & Dispatch
Saged Abd El Dayem, Co-Founder & CEO
7 min read
Published · Updated

Why Dispatch Is a Leadership Problem, Not Just a Scheduling Problem

Whoever owns the dispatch rules sets margin, customer experience and retention every day. How to tell a scheduling problem from a routing one, and the four decisions only leadership should make.

In short

Dispatch is a leadership problem because the rules behind it decide how much of every paid hour turns into service. Four decisions belong to leadership, not the desk: the routing goal, what may change and how close to the day, which customer rules are hard, and the numbers dispatch is judged on. Many problems that look like scheduling actually sit in routing, territory, capacity or those rules.

  • Ask who owns the dispatch rules, not who owns the calendar.
  • Fewer routes or fuller routes is an owner's decision, and it changes every plan.
  • Stops with no slot point to capacity; stops blocked by a conflict point to rules or data.
  • A dispatch number without a target and a reviewer will be ignored within a month.

Ask a pest control office who owns dispatch and you usually get a person's name. Ask who owns the rules that person enforces, and the room gets quiet. That gap is the problem. Dispatch touches profit, customer experience and technician retention every day, and when nobody owns its rules, the person at the desk invents them under pressure.

At PestRouting we build route planning on FieldRoutes (formerly PestRoutes) data, and every office we set up has to answer the same questions before the first plan runs: what the planner may move, which customer wishes are hard rules, and what a good route means for that business. None of those are scheduling questions. They are leadership decisions, and four of them should never be left to the desk.

Why dispatch sits between revenue and cost

Every dispatched day decides how much of the paid day turns into service. The Bureau of Labor Statistics puts the median pay of pest control workers at $21.75 an hour as of May 2025, and projects about 13,700 openings a year, so every technician hour is both expensive and hard to replace. FieldRoutes' 2025 industry survey of more than 1,000 pest control employees found that 89% of companies plan to raise technician wages this year.

Dispatch sits upstream of the numbers owners watch. Revenue per paid hour depends on how stops are grouped and ordered. Callbacks rise when the last stop of an overloaded day gets rushed or the wrong technician gets a licensed job. Customers judge the company on arrival windows and on seeing the same technician. Technicians judge it on whether their days are predictable.

Is it a scheduling problem or a routing problem?

"We have a scheduling problem" is one of the most common sentences in an owner's office, and often the wrong diagnosis. A full, chaotic calendar can come from five different layers: dispatch rules, capacity, territory, routing or the calendar itself. Hire another scheduler for a routing problem and the chaos stays.

QuestionIf the answer is yesThe fix lives in
Do stops stay unplaced even when routes are tight and well ordered?The team is out of hoursCapacity: hiring, or fewer promises per day
Are stops blocked by rules or data, such as a preferred technician who is off?The rules contradict each otherDispatch rules and subscription data
Do late finishes cluster on certain areas or technicians?Those areas are drawn wrong or overloadedTerritory
Are late finishes spread at random?Service times or stop order do not match realityRouting
Does overtime grow faster than the customer count?Efficiency is leaking, not capacityRouting and territory

PestRouting makes the first two questions visible on every plan. Stops the planner had but could not fit count as "no slot found", which means capacity. Stops a check removed before planning began show as "not planned due to conflict", each with its reason, such as a preferred technician who is off or a customer with no service address. The first list calls for hours. The second calls for a rule or a record to change.

Symptoms of leadership by default

  • Nobody can say what share of the paid day goes to driving.
  • Same-day requests are negotiated case by case between sales, the customer and whoever is at the desk.
  • Routes look different when the regular dispatcher is on vacation, because the rules live in one head.
  • The written schedule is a starting point that ends as a list of overrides.
  • Dispatch reports to the office manager, so the org chart treats it as administration.

FieldRoutes' own scheduling guide notes that technician availability is inconsistent due to time off and unexpected absences. An office that runs dispatch from memory feels every one of those absences twice.

The four dispatch decisions only leadership should own

The goal. Some owners want the same work on fewer routes. Others tell us on sales calls that every technician has to work every day, because a technician without a route earns nothing that day. Both are legitimate, and they produce different plans. In PestRouting the goal is a setting: Territory mode shares work fairly, balanced by production value, appointments, service time or paid working time, while Max efficiency builds the tightest routes and shows who is under-used. A separate choice decides which visits come first when the week is full: more visits, longer visits or higher-production visits.

What may change, and how close to the day. Leadership decides how far ahead routes freeze and what the planner may do with booked visits on later days. In PestRouting that lives in the office's Planner Rules, for example "Up to 2 days out: add nothing and move nothing."

Which customer wishes are hard rules. Preferred technicians, preferred weekdays, required licenses and service areas can each be switched on or off. A rule that is on is never broken, so each one should be on because the business decided it, not because nobody looked.

The scorecard. Which numbers dispatch is judged on, who reviews them and how often. Without that, quality drifts with whoever is at the desk.

The dispatcher should build the days. Leadership should write the rules the days are built from.

Dispatch KPIs you can defend

A KPI needs a definition, a target and someone who reviews it. PestRouting's Planning Quality tab uses four, with targets an office can start from.

KPIWhat it countsTarget
Stop AdherencePlanned stops completed at the same customer on the planned day85% or more
Route AdherencePlanned technician days on which that technician ran a route90% or more
On-Time RateCompleted stops reached within 10 minutes of the planned arrival80% or more
Work-Time OverrunHow far drive plus service time ran over the planned timeWithin 10% either way
PestRouting Planning Quality card with stop adherence, route adherence, on-time rate and work-time overrun against their targets
Planning Quality in PestRouting's Analytics compares what ran with what was planned, each figure against its target.

Add two money numbers from the field: the share of route time spent driving and production per paid hour. Which FieldRoutes reports feed the same picture is covered in the five FieldRoutes metrics that matter, and the full set lives in PestRouting Analytics.

A leadership cadence for dispatch

Review the scorecard weekly with the operations lead. Recalibrate lock times, exception limits and same-day caps monthly. Review territories and the recurring schedule quarterly. Most owners spend more time on receivables and the sales pipeline than on dispatch, even though dispatch decides whether that revenue can be served. The day-to-day habits that follow from good rules are in five FieldRoutes dispatch mistakes, and the wider case for rules over heroics is in building a company that can run without you.

Frequently asked questions

Should the owner be involved in daily dispatch decisions?

No. The owner should own the rules, the targets and the weekly review, and the dispatcher should build the days. An owner pulled into daily dispatch usually means the rules are not written down.

How do I know whether my scheduling problem is really a routing problem?

Check whether stops go unplaced even on well-ordered routes, whether late finishes cluster by area or are random, and whether overtime grows faster than customers. Unplaced stops on tight routes mean capacity; random late finishes and overtime outpacing growth point to routing.

Which dispatch KPIs should a pest control owner track?

Stop adherence, route adherence, on-time rate and work-time overrun show whether the plan held. Drive share of route time and production per paid hour show what the plan earned.

Who should the dispatcher report to?

Operations. Dispatch outcomes drive drive time, callbacks and finish times, so they belong with whoever owns operational performance, not with office administration.

What if an experienced dispatcher resists written rules?

Frame the work as writing down what already works. Experienced dispatchers carry real knowledge, and written rules keep it in the company when that person is out or leaves.

To see what your current rules do to a month of routes, our free route audit re-plans one month of your FieldRoutes routes under those 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:
Saged Abd El Dayem

Written by

Saged Abd El DayemCo-Founder & CEO, PestRouting

Responsible for strategy, sales and customer success at PestRouting, including the route audits for pest control companies on FieldRoutes.

Saged 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