A reporting dashboard open on a laptop screen
Back to Blog
Metrics & Audits
Saged Abd El Dayem, Co-Founder & CEO
9 min read
Published · Updated

FieldRoutes Reporting: 5 Pest Control KPIs Worth Tracking Every Week

FieldRoutes records what ran. Five ratios built from that data, each set next to the plan, tell a pest control owner whether the routes are getting better or quietly worse.

In short

FieldRoutes reporting tells you what happened: which visits were completed, by whom and for how much. Five KPIs built from that data show how the routes ran: production per paid hour, drive-time share, cost per stop, stop adherence and work-time overrun. Each one becomes a decision only when you compare it with what the plan said, week by week.

  • Totals grow with volume. A KPI is a ratio that stays comparable when the volume changes.
  • Compare every KPI with the plan, not with last month alone.
  • Visits closed without check-in and check-out times inflate drive-time share without any change in the routes.
  • Low on-time rates with routes that run over plan mean the service times are wrong, not the technicians.

FieldRoutes reporting tells you what happened: which appointments were completed, by which technician, at what price. That record is accurate. On its own it still cannot tell you whether the routes ran well, because completed stops, revenue and miles all rise when you simply have more work.

Five ratios built from the same data do tell you, and each one turns into a decision once you set it next to what the plan said. PestRouting's Analytics reads the actuals from FieldRoutes once technicians close their visits and puts them beside the adopted plan, day by day. You can build the same five in a spreadsheet. What matters is that the definitions stay fixed from week to week.

Why totals are not KPIs

A total grows with volume. If you served 12% more visits in May than in April, revenue, completed stops and miles all went up, and none of that says whether May was planned better. A KPI divides by something, such as paid hours or stops, so a bigger month and a smaller month stay comparable.

The second ingredient is a reference. Last month is a weak one, because it may have been bad too. The plan is a strong one: it says what the day should have looked like with the same visits, so the gap between plan and actual points at a cause.

KPIHow it is countedBetter when
Production per paid hourProduction value of completed visits divided by paid hoursHigher
Drive-time shareShare of route time spent driving rather than at customersLower
Cost per stopRoute costs divided by stopsLower
Stop adherenceShare of planned stops completed at the same customer on the planned day85% or more
Work-time overrunHow far drive plus service time ran over the planned time, on averageWithin 10% either way

1. Production per paid hour

Production value is what the completed visits earned at the price on the subscription or appointment. A no-show or a cancelled visit adds nothing. Paid hours depend on how you pay: from leaving the start location until getting back, from the first job to the last, or a mix. Pick the pay period you actually pay for and keep it, or the KPI moves every time someone changes the definition.

This is the money version of a question FieldRoutes asks in its own guide to pest control KPIs, which recommends a technician utilization rate above 70%. Utilization says how full the day was. Production per paid hour says what the full day was worth.

The floor is set by what an hour costs you. The BLS median pay for pest control workers is $21.75 an hour (May 2025), before benefits, the truck, materials and overhead. A route whose production per paid hour sits close to that number loses money however busy it looked.

2. Drive-time share

Drive-time share is the part of the route time spent driving rather than at customers. Read it together with distance per stop, because the pair separates two different problems:

  • Drive time above plan with distance on plan means the drive took longer than expected, often traffic or a slow start to the day.
  • Distance above plan means technicians drove a different order or different stops than the plan had.

Density is why this KPI deserves a weekly look. In a PCT survey that FieldRoutes cites in its article on route density, 55% of participants ranked increased route density first among ten productivity factors.

The data trap: visits without a recorded time

When a technician closes a visit without checking in and out, FieldRoutes holds no time for it. Those minutes vanish from the day, the day looks shorter, and driving takes a bigger share of it. A few such visits a day push drive-time share up without any change in the routes. Fix the habit in the field first: when technicians check in and out of every visit, the KPI starts measuring the routes instead of the paperwork.

Also compare an office with itself. A rural office drives more for the same work, so its drive-time share describes the geography rather than grading the dispatcher.

3. Cost per stop

Cost per stop divides what the routes cost by the stops on them. The route cost needs your own rates: a cost per route for each truck that goes out, per paid hour, per overtime hour and per mile. Without those rates the KPI is a guess, and with them it catches the problem production per paid hour can miss.

Cost per stop above plan while production is on plan usually means longer days. Look at drive-time share and work-time overrun next. Production below plan while cost is on plan usually means visits were planned and not done, which leads to the fourth KPI.

4. Stop adherence and the follow-up list

Stop adherence is the share of planned stops completed at the same customer on the planned day, by any technician. PestRouting rates it against a target of 85%. Its partner is route adherence, the share of planned technician days on which that technician actually ran a route, with a target of 90%.

Low stop adherence with high route adherence means technicians went out as planned and skipped stops. Low route adherence means planned technicians did not work, for example sick days nobody told the plan about.

The stops behind the number need a next step, so keep a list of every visit from the last seven days that was not completed, sorted by reason:

  • Awaiting first visit. The plan had it, and it sits on no route of that day. Reschedule it and check why.
  • No-show. The technician came and the customer was not there. Handle no-shows and cancellations with reminders and a fixed rebooking rule.
  • Cancelled. Confirm why and rebook.
  • Needed more time. The route ran, and the visit ended neither completed nor cancelled. Most often the day ran out, which points back at the plan.

5. Work-time overrun and on-time rate

Work-time overrun measures how far the routes' working time, drive plus service, ran over the planned time on average. Within 10% either way is healthy. On-time rate is the share of completed stops reached within 10 minutes of the planned arrival, with a target of 80%.

A low on-time rate together with a positive overrun means the plan expects visits or drives to be shorter than they are. The usual cause is service times on the subscriptions that no longer match the field. Coaching technicians to hurry does nothing for that. Correcting the times does, and it is also the first step to reduce overtime through route planning.

The Planning Quality tab in PestRouting Analytics with stop adherence, route adherence, on-time rate and work-time overrun, each against its target, with a daily chart under each tile
Planning quality in PestRouting: stop adherence, route adherence, on-time rate and work-time overrun, each rated against its target. The figures come from a demo office.

Read the five together

One KPI behind plan is a symptom. Two together usually name the cause:

What you seeLikely causeWhere to look
Drive time above plan, distance on planTraffic or late startsStart times and the first stop of the day
Distance above planTechnicians drove another order or other stopsThe day in plan versus actual
Production below plan, cost on planPlanned visits not doneThe follow-up list
Cost per stop above plan, production on planLonger daysDrive-time share and overrun
Low on-time rate, positive overrunService times too short in the planTime on site per service type

A weekly review in five steps

  1. Fix the period. Same office, last full week, compared with the plan for those days.
  2. Rate each KPI. On target, within tolerance when it is less than 15% worse than plan, or behind.
  3. Open the worst day. One day of plan versus actual on the map explains more than a month of averages.
  4. Clear the follow-up list. Every visit on it either gets a new date or a decision.
  5. Once a month, split by technician. An office average can hide one technician who always runs over and one who always finishes early.

Weekly KPIs track drift. When you need a baseline, meaning what the same visits would have cost under a better plan, a route audit on your FieldRoutes data answers that question once.

Frequently asked questions

What KPIs should a pest control company track?

Track production per paid hour, drive-time share, cost per stop, stop adherence and work-time overrun every week. Together they cover what the routes earned, what they cost, whether the plan was kept and whether the plan was realistic.

How do you calculate drive-time share for a technician?

Divide the time spent driving by the total route time, meaning driving plus time at customers. Count the drive to the first stop and home only if your pay period pays for it, and make sure visits have check-in and check-out times, or the share comes out too high.

What is a good on-time rate for pest control technicians?

Reaching 80% or more of completed stops within 10 minutes of the planned arrival is the target PestRouting rates against. If the rate is lower and routes also run over the planned time, the plan's service times are too short.

How often should pest control KPIs be reviewed?

Review them weekly against the plan and split them by technician once a month. Weekly is short enough to catch a drift before it becomes the normal week, and monthly by technician shows imbalances an office average hides.

Can PestRouting report on FieldRoutes data?

Yes. PestRouting reads completed visits from FieldRoutes and shows production, drive time, cost per stop, stop adherence, on-time rate and work-time overrun against the plan you adopted, with a seven-day follow-up list of visits that were not completed. See Analytics for what each view shows.

To get a baseline for these KPIs from your own month, start with the free route audit.

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