What is the difference between dispatching and scheduling in a home-service business?

Scheduling is the upstream step where a CSR or booking system assigns a time window and tech to a customer request. Dispatching is the real-time management of those assignments through the day as jobs move, techs run long or short, emergencies come in, and customers cancel. A dispatcher's dashboard is less about who is on the calendar and more about whether the live board is producing completed jobs and capturing revenue as the day unfolds.

What KPIs should a dispatcher track daily?

The most decision-relevant KPIs for a dispatcher are capacity utilization by tech and zone, job-completion rate for the day, same-day reschedule rate, average drive time per job, and callback or return-trip rate by tech. Revenue per dispatched job is the number that connects routing decisions to business outcomes, so it belongs on the daily board even if it is reviewed in more detail weekly.

What is capacity utilization for a field-service dispatcher?

Capacity utilization is the share of available tech hours that are assigned to booked jobs on a given day. If you have 10 techs each with an 8-hour shift, you have 80 hours of capacity. If those techs are scheduled for 64 hours of jobs, utilization is 80%. High utilization is good up to a point: over-scheduling leaves no room for emergencies or jobs that run long, which drives same-day reschedules and callbacks. The target range varies by trade, season, and how you handle emergency calls.

How does a dispatcher dashboard help reduce callbacks?

Callbacks happen when a job is not completed correctly the first time, often because the wrong tech was routed to a job type outside their skill set. A dispatcher dashboard that shows tech job-type history and completion rates alongside open capacity makes it easier to route by skill, not just by proximity or availability. Over time, tracking callback rate by tech surfaces patterns that the service manager can address with training before they become a recurring cost.

How does dispatch coordinate with the call center on same-day demand?

The most common breakdown between dispatch and the call center is when CSRs keep booking jobs into a day where capacity is already committed. A shared live view of capacity utilization and open slots lets the call center see in real time whether dispatch can absorb another booking before they confirm it. When connected, a datacube dashboard can be configured to show the call center and dispatch the same capacity picture so both teams are making decisions off the same data.

What data sources feed a dispatcher dashboard?

Typically your field-service CRM (such as ServiceTitan, Workiz, or Housecall Pro) for job assignments, tech status, completion data, and job types. Drive time and zone data can come from the same source. When connected, datacube is designed to consolidate these into a live dispatch board so capacity utilization, completion rate, and callback patterns are in one view instead of spread across your CRM reporting tabs.

How is this dispatcher playbook different from the operations manager playbook?

The dispatcher playbook is about real-time routing and same-day capacity decisions: which truck goes where, right now. The operations manager playbook covers the broader execution layer including hiring pace, department performance, and longer-horizon process issues. Dispatch feeds the ops manager the field-level data that informs those bigger decisions. Both roles benefit from shared visibility, but they are asking different questions from the same board.

Dispatcher dashboard playbook

A practical operating guide for the person routing jobs and managing field capacity in a home-service business. What to watch at the start of each day, which KPIs to own, and how a live dispatch board turns a chaotic schedule into a profitable one.

By Datacube content engineAutogeneratedJune 24, 2026

Role playbook

The dispatcher's job is not filling slots. It is protecting same-day revenue.

At 8am on a Tuesday the board looks manageable. By 10am a tech calls out sick, two jobs reschedule, and a new emergency HVAC call comes in from a zip code already outside the morning route. In the next 20 minutes a dispatcher either finds the right truck for the right job and keeps the day on track, or the revenue walks. That is the job. It is not scheduling software. It is judgment under pressure, and the difference between a dispatcher who guesses and one who decides is whether they have the right numbers in front of them. This playbook covers the KPIs, the daily rhythm, and the dispatcher dashboard that makes those judgment calls faster and cleaner.

The short version

Own capacity utilization, job-completion rate, average drive time, same-day reschedule rate, and revenue per dispatched job. Each one points to a routing decision, not just a number.
Check the board at open, midday, and close. The biggest wins and the biggest leaks both happen inside the day.
A live dispatch board on the office TV or a shared web view makes capacity visible to the whole ops team, which reduces the phone tag between dispatch, service, and the field.
The costliest dispatch error is not a missed booking. It is the wrong tech on the wrong job type, which shows up as a callback or a low-ticket close.

The KPIs a dispatcher should own

Every KPI below is connected to a decision you make before the truck rolls. Status indicators show example directions only. Set real targets against your own baseline because they vary by trade, season, market, and how your routes are structured.

Capacity utilization (by tech and department)Decision: which techs have room for an add-on or emergency call right now.
Good
Current
Live, by tech
Target
Keep above your utilization floor, not just filled
Job-completion rate (same day)Decision: which rollovers need a priority slot tomorrow before the customer cancels.
Watch
Current
% of booked jobs completed
Target
Minimize rollovers
Average drive time per jobDecision: whether tomorrow's routes need rebalancing by zone to cut windshield time.
Watch
Current
Minutes per run
Target
Geographic clustering benchmark
Same-day reschedule rateDecision: whether reschedules come from customer cancels, tech issues, or scheduling gaps the CSR owns.
Poor
Current
% of jobs rescheduled day-of
Target
Low and stable
Revenue per dispatched jobDecision: are the right techs (by skill and ticket average) going to the highest-value jobs?
Good
Current
By job type and tech
Target
Track the high-ticket mix
Callback and return-trip rateDecision: which tech or job type generates repeat trips and what the root cause is.
Poor
Current
% of jobs that return
Target
Minimize per tech

Metric	Current	Target	Status
Capacity utilization (by tech and department)Decision: which techs have room for an add-on or emergency call right now.	Live, by tech	Keep above your utilization floor, not just filled	Good
Job-completion rate (same day)Decision: which rollovers need a priority slot tomorrow before the customer cancels.	% of booked jobs completed	Minimize rollovers	Watch
Average drive time per jobDecision: whether tomorrow's routes need rebalancing by zone to cut windshield time.	Minutes per run	Geographic clustering benchmark	Watch
Same-day reschedule rateDecision: whether reschedules come from customer cancels, tech issues, or scheduling gaps the CSR owns.	% of jobs rescheduled day-of	Low and stable	Poor
Revenue per dispatched jobDecision: are the right techs (by skill and ticket average) going to the highest-value jobs?	By job type and tech	Track the high-ticket mix	Good
Callback and return-trip rateDecision: which tech or job type generates repeat trips and what the root cause is.	% of jobs that return	Minimize per tech	Poor

Dispatcher review cadence: what to check and when

Check point	What to review	Action if something is off
Open of day (before first truck rolls)	Capacity by tech, route clustering, any carryover jobs from yesterday, and early emergency calls already in queue	Reassign carryovers first, tighten route geography, flag any understaffed zones before the call volume peaks
Midday capacity check (live board)	Completion pace vs. open slots, any techs finishing early with room for an add-on, rescheduled jobs that freed up time	Slot inbound emergency calls into newly opened capacity; avoid letting finished techs sit idle while call center has bookings queued
Close of day (before final debrief)	Jobs completed vs. booked, open rollovers, same-day reschedule count, and any unplaced emergency calls	Slot tomorrow's first priority jobs now, document rollover reasons, and pass reschedule patterns to the ops manager before the board resets
Weekly trend review (with ops manager or GM)	Capacity utilization trend, average drive time by zone, callback rate by tech, and reschedule-vs-completion ratio	Adjust zone assignments, flag techs with elevated callbacks, surface route inefficiencies to the service manager for coaching
Monthly ops review (with leadership)	Revenue per dispatched job by tech, capacity fill rate vs. call volume, and seasonal demand patterns	Inform hiring and training decisions, reset route structures for the next season, and align capacity targets with the marketing plan

How to run the day off your dispatch board

01
Morning setup (10 minutes before the first dispatch)
Open the live dispatch board. Sort by tech, zone, and job type. Carryovers from yesterday get a slot first. Then look at the gap between your booked job count and your available tech hours. If the gap is more than two jobs, flag the call center now so they can manage intake accordingly.
02
Routing decisions (ongoing through the morning)
Match job type to tech skill before filling slots by proximity. An HVAC replacement job going to a maintenance tech because they are closest is a recipe for a callback. Check the revenue-per-dispatched-job history by tech when a high-value job comes in. When connected to your CRM, a datacube dispatch board can surface tech job-type history alongside the open slot.
03
Midday capacity reset (5 minutes around peak)
At midday check which techs are ahead of pace and which are behind. A tech finishing two jobs early is idle capacity. A tech still on job one at noon may need a reassignment before the afternoon queue gets too full. Emergency calls that come in during the midday window slot best into the next opening within their zone, not into the first available tech regardless of location.
04
End-of-day close and tomorrow setup
Count the rollovers, note the reason for each, and slot them into tomorrow's board before it resets. Same-day reschedules that came from tech issues versus customer cancels tell different stories: one is a staffing signal, the other is a demand pattern. Record both. Share the completion and capacity numbers with the ops manager before sign-off.
05
Weekly check-in with the service manager
Bring the drive-time trend, callback rate by tech, and any zone where you consistently run low on capacity. This is the meeting where dispatch and service align on whether the routing structure is serving the job mix, not just filling the calendar.

What a dispatcher dashboard looks like

A live dispatch board designed to show capacity, job status, and routing signals in one view. Built for web or mobile so you can check it without leaving the board or chasing the field on the phone.

Dashboard preview

Figures are illustrative. A datacube dispatcher dashboard is built around your tech roster, job types, zones, and goals.

Info

Coaching moment: the wrong tech on the right job

Capacity utilization looks fine on paper, but callback rate climbs when a tech without the right skill set is routed to a job type above their experience level. Filling slots is easy. Routing the right skill to the right job requires seeing both the open capacity and the tech's job-type history in the same view. When a dispatcher can see that one tech consistently generates callbacks on replacement jobs while another converts them cleanly, that is a routing and training signal, not just a scheduling note. Pass those patterns to the service manager with the numbers, not just an anecdote.

Goals, leaderboards, and visibility

Make capacity and performance visible to the whole team

Where a live dispatch board changes team behavior:

A shared capacity view on the office TV reduces the phone calls from techs asking if there is more work available.
Tech-level job-completion and callback data lets the service manager coach on specific patterns instead of general impressions.
Daily capacity-utilization goals give dispatch a clear success metric beyond 'the day went okay'.
When marketing runs a campaign that spikes call volume, dispatch needs to see the incoming capacity demand alongside the existing board, not hear about it secondhand.

Warning

When to escalate same-day, not next week

Three things should never wait for the weekly review. A tech out sick with no coverage for their afternoon jobs is a same-hour capacity problem: the ops manager needs to know now so they can pull from another department or call for backup. A same-day reschedule rate spiking mid-morning during a marketing campaign means the CSR team is booking jobs that dispatch cannot fulfill, and both teams need to see that together before more jobs get booked. And a callback from yesterday's job that generates a new dispatch today is costing you double labor on a margin-negative run: flag it to the service manager before the truck rolls again.

Dispatcher dashboard playbook FAQs

See your live capacity on one dispatch board

Datacube builds a custom dispatcher dashboard around your tech roster, job types, zones, and routing goals, so you can make field decisions off today's numbers instead of a spreadsheet that was already wrong by 9am.

Schedule a live demo Take the self-guided demo

Keep exploring

Franchise operatorA practical operating framework for the person responsible for performance across multiple franchise locations in a home-service network. Which KPIs to own, how to structure your review cadence, and how a franchise operator dashboard gives you a consistent view across every location you oversee.

General managerA field-tested operating rhythm for the GM who bridges owner strategy and day-to-day execution. Which KPIs to own, how to run daily standups and weekly reviews off live data, and what your general manager dashboard should surface before a problem becomes a month-end surprise.

Install managerA field-execution operating guide for the person who runs installs in a home-service business. The KPIs to own daily, the review cadence that keeps crews on schedule, and the install board that replaces morning guesswork with real numbers.

Marketing managerA before-and-after guide for the marketing leader at a home-service company. What you should see in your dashboard every day, which KPIs you actually own, and how to stop defending ad spend to the owner when the data is already right in front of you.

Go deeper