Building a 10-minute weekly dispatcher review
Most owners under-manage their dispatcher because they don't have a structured way to review the role. Here's a 10-minute weekly meeting agenda that catches dispatch problems before they hit margins.
Dispatch is the single role with the highest leverage on weekly profitability in a small service business. A dispatcher who's good at their job adds 10-25% to weekly revenue through tighter scheduling, better skill matching, and faster responses to changes. A dispatcher who's not good loses the same amount, often invisibly.
Most owners under-manage their dispatcher, not because they don't care, but because they don't have a structured way to review the role. Here's a 10-minute weekly meeting that catches the problems early.
The agenda
Block 10 minutes every Friday afternoon. Open with: "Quick look at this week's numbers."
Then walk through these six items, ~90 seconds each:
1. Jobs completed vs jobs scheduled
Pull last week's numbers. How many jobs went on the calendar Monday morning? How many got completed by Friday close? The delta — rescheduled, no-shows, partial completions — is the dispatch friction number.
Healthy: 90%+ completion rate. Below 85%, dig into why.
2. Average response time on inbound calls
How long is the phone ringing before someone picks up? How long between voicemail and callback?
Healthy: <30 seconds for live calls during business hours. <2 hours for callbacks. Numbers above this are leaking leads.
3. Skill-match exceptions
How many jobs were assigned to techs without matching skill tags? Most platforms surface this as a warning when dispatch overrides; tally the count.
Healthy: 0-2 per week. Higher means either skill tagging is incomplete or dispatch is overriding for capacity reasons that need addressing.
4. Last-minute reassignments
How many jobs got reassigned within 24 hours of scheduled time? Each reassignment is friction — for the customer, for the original tech, for the new tech.
Healthy: Under 10% of weekly job volume. Higher indicates upstream scheduling issues (overbooking, no buffer time, skill mismatches surfacing late).
5. Customer complaints related to scheduling
Any complaints this week about wait times, missed appointments, late arrivals, or being rescheduled? Even one is worth understanding.
Pattern these — if late arrivals concentrate on Tuesdays, look at the Tuesday schedule. If rescheduling complaints concentrate on a specific tech, look at that tech's productivity numbers.
6. One thing that worked, one thing that didn't
Open-ended close. Ask the dispatcher: "What worked well this week?" and "What was hard?"
This surfaces operational friction that doesn't show up in the metrics. A dispatcher dealing with parts-supplier delays, frustrating customers, or unrealistic owner expectations needs to be able to flag it.
What to do with what you learn
Don't use these meetings as performance reviews. This is a working meeting to surface and fix issues, not an evaluation. The dispatcher should leave with specific action items, not feeling judged.
Track week-over-week trends. Single weeks fluctuate. The metric that matters is whether the trends are moving in the right direction over 4-8 weeks.
Tie improvements to systems, not just willpower. If response times are slow, the answer is usually a phone-routing change, not "answer faster." If skill-match exceptions are high, the answer is updating skill tags, not "stop overriding."
Share the wins. When the numbers move in the right direction, recognize it explicitly. Dispatchers do high-cognitive-load work that's mostly invisible when going well; the only visible signal is when things break. Counterbalance with explicit recognition.
What good looks like over time
Within 4-6 weeks of starting these meetings, most operations see:
- Job completion rate climbs 5-10 points
- Skill-match exception count drops by half or more
- Response times tighten 30-50%
- Customer complaint volume drops noticeably
The cumulative effect is meaningful — typically 8-15% revenue lift on the same crew, plus measurable improvement in customer satisfaction signals (Google reviews, repeat customer rate).
Ten minutes a week. Outsized return.
For more on the broader dispatch role and how to build it out as you grow, our HVAC dispatching best-practices guide walks through the role in depth.