If you’re running a high-volume field operation — drain cleaning, pest control, septic, dryer vent, or any trade dispatching 20+ jobs a day — revenue is a lagging indicator. By the time your monthly numbers tell you something went wrong, you’ve already lost the jobs, the hours, and the margin.
The dispatchers running the tightest operations don’t wait for the monthly P&L. They watch four numbers every single day. These aren’t vanity metrics. They’re the operational pulse of your business — and if any one of them moves in the wrong direction, you want to know before noon, not before payroll.
Here are the four KPIs that separate high-performing dispatch operations from ones that are slowly bleeding efficiency they can’t see.
1. Jobs Completed Per Tech Per Day
This is your most important number. Everything else in your operation — revenue, labor cost, customer satisfaction — flows from this one metric.
Jobs completed per tech per day tells you whether your techs are running at capacity or whether you have idle time baked into your schedule that nobody is talking about. For most high-volume trades, there’s a ceiling based on job type:
- Drain cleaning: 8–15 jobs per tech per day
- Dryer vent cleaning: 8–12 jobs per tech per day
- Pest control treatments: 7–12 stops per tech per day
- Septic pump-outs: 5–9 jobs per truck per day
If your techs are consistently coming in below the floor of their range, you have one of three problems: routing inefficiency, dispatch lag, or scheduling gaps. All three are fixable — but only if you’re watching the number daily.
What to do with it: Pull this number every morning for the previous day. If a tech ran 6 drain jobs when your average is 11, find out why before they go out again. Was it drive time? A job that ran long? An unassigned slot that sat empty until 10am?
2. Time-to-Dispatch
Time-to-dispatch measures how long it takes from the moment a customer calls to the moment a tech has the job on their phone and is en route.
In high-volume operations, this number matters more than most operators realize. Every minute of dispatch lag is a minute of potential idle time for the tech closest to the job. At 80 jobs a day across 12 techs, dispatch lag compounds fast.
The benchmark for well-run high-volume operations: under 90 seconds from inbound call to assigned job.
If your dispatcher is still texting job addresses, calling techs to confirm, and waiting for a “got it” reply before moving to the next job — your time-to-dispatch is probably 5–10 minutes per job. Across 80 jobs, that’s 400–800 minutes of dispatcher time that should be running at under 120 minutes total.
What to do with it: Time a sample of dispatches this week. Pick 10 inbound calls at random and clock the time from call answered to job assigned in your system. If you’re over 3 minutes consistently, your dispatch workflow needs to change — not your dispatcher.
3. Technician Utilization Rate
Utilization rate is the percentage of a tech’s working hours actually spent on jobs — not driving, not waiting, not sitting at the yard because the schedule had a gap.
The formula is simple:
Utilization % = (Hours on jobs ÷ Total hours on clock) × 100
For a high-volume operation running 8-hour shifts, a well-utilized tech should be on jobs or actively en route for 75–85% of their day. If you’re running below 65%, you have significant idle time baked into your operation — and you’re paying for it every day.
Low utilization usually traces back to one of three causes:
- Routing inefficiency — techs are driving past each other’s jobs
- Schedule gaps — unassigned jobs sitting in the queue while techs are free
- Long job durations — a job type that’s taking longer than your price book assumes
What to do with it: Calculate this weekly at minimum, daily if you can. The goal isn’t 100% — that’s unrealistic and ignores drive time. The goal is identifying which techs are consistently under 65% and why. One tech with a utilization problem is a coaching conversation. Three techs with the same problem is a routing or scheduling system problem.
4. Unassigned Job Rate at 9AM
This one is simple and devastating if you ignore it.
Pull your dispatch board at 9am every morning. Count the jobs that are unassigned. Divide by total jobs on the board. That’s your unassigned rate at 9am.
In a well-run high-volume operation, that number should be under 15% by 9am. Jobs sitting unassigned at the start of the day are jobs at risk — risk of being pushed to late afternoon, risk of a frustrated customer, risk of a tech with a gap in their morning schedule.
The unassigned rate at 9am is a direct measure of how well your previous-day dispatch preparation worked. High-performing operations pre-assign the next morning’s jobs before the day ends. Their dispatchers start the morning managing exceptions, not building the board from scratch.
What to do with it: Set a daily 9am check as a non-negotiable. If your unassigned rate is consistently above 20% at 9am, your end-of-day dispatch process needs a hard stop where the next morning’s board gets built before anyone goes home.
The Bigger Picture
These four numbers — jobs per tech per day, time-to-dispatch, utilization rate, and unassigned rate at 9am — form the operational dashboard that high-volume dispatch managers live by.
None of them require expensive analytics software. They require discipline, a dispatch system that makes the data visible, and the habit of looking at them every single day before the trucks roll.
The operations that scale from 5 techs to 20 without hiring a second dispatcher aren’t doing it with magic. They’re doing it by watching these numbers, identifying the gaps, and closing them one by one — before those gaps become habits.
That’s what operational control looks like in the trades. Not a dashboard with 40 metrics. Four numbers. Every morning. No exceptions.
Until next time,
-Sam
