Fill the board before a slow truck costs you the day
A dispatch dashboard pulls capacity, job status, and technician location data into one live view so operations managers and dispatchers can route smarter, fill gaps before they cost revenue, and stop finding out about idle techs at end of day.
The problem
A tech sat idle for two hours. Nobody knew until 4 pm.
It happens more than anyone wants to admit. A job finishes early, the tech sits in a parking lot waiting for a call that never comes, and by the time the dispatcher realizes the gap, the afternoon is gone. The root cause is not poor dispatching: it is that nobody had a real-time view of where the day actually stood. A dispatch dashboard for contractors is built to make that gap visible before it turns into lost revenue.
Dispatch KPIs: what good, watch, and poor look like
A dispatch dashboard is only as useful as the metrics it surfaces. The five signals below are the ones dispatchers and operations managers check first. Targets vary by trade, season, market, and team size.
- Tech utilization rateTime on revenue-generating jobs divided by total available hours. Tracks wasted drive and idle time.Good
- Current
- 88%
- Target
- 85%+
- On-time arrival rateJobs where the tech arrived within the promised window. Low scores correlate with cancelled calls and poor reviews.Watch
- Current
- 79%
- Target
- 85%+
- Unfilled capacity todayBookable time with no job assigned. Each slot is an hour of labor cost with no revenue attached.Poor
- Current
- 3 open slots
- Target
- 0–1
- Callback / revisit rateJobs requiring a return visit for the same issue. High callback rate signals first-call-resolution or parts-availability problems.Poor
- Current
- 4.2%
- Target
- < 3%
- Same-day job completion rateJobs closed the same day they were scheduled. Strong completion rate means fewer overnight open jobs clogging tomorrow's board.Good
- Current
- 91%
- Target
- 90%+
| Metric | Current | Target | Status |
|---|---|---|---|
| Tech utilization rateTime on revenue-generating jobs divided by total available hours. Tracks wasted drive and idle time. | 88% | 85%+ | Good |
| On-time arrival rateJobs where the tech arrived within the promised window. Low scores correlate with cancelled calls and poor reviews. | 79% | 85%+ | Watch |
| Unfilled capacity todayBookable time with no job assigned. Each slot is an hour of labor cost with no revenue attached. | 3 open slots | 0–1 | Poor |
| Callback / revisit rateJobs requiring a return visit for the same issue. High callback rate signals first-call-resolution or parts-availability problems. | 4.2% | < 3% | Poor |
| Same-day job completion rateJobs closed the same day they were scheduled. Strong completion rate means fewer overnight open jobs clogging tomorrow's board. | 91% | 90%+ | Good |
Info
Coaching moment
When unfilled capacity hits three or more open slots before noon, the right move is not to wait for CSRs to fill the board organically. A dispatcher with a live capacity view can flag open slots to the call-center team in real time so incoming calls get routed to the nearest available tech, turning dead time into booked revenue the same morning.
What a dispatch dashboard looks like in datacube
This is the kind of board an operations manager or lead dispatcher keeps open all day, and can also push to an office TV for the whole dispatch team to reference without opening the CRM.
Figures are illustrative. Datacube builds the dispatch board around your CRM (ServiceTitan, Workiz, Housecall Pro, and similar), your team structure, and how your company defines utilization and capacity.
Dispatch review cadence: what to check and when
| When | What the dispatcher checks | Decision it enables |
|---|---|---|
| Morning standup (7–8 am) | Capacity for the day, carryover open jobs, tech availability and drive time | Pre-load techs with jobs near their first stop; flag any skills mismatches before the first call |
| Mid-morning check (10–11 am) | Unfilled slots, early job completions, on-time arrival rate so far | Reassign open slots to techs who finished early; alert CSR team to fill gaps before noon rush |
| Afternoon (1–2 pm) | Jobs still in progress vs completed, callbacks reported today, tech utilization trend | Prioritize same-day completion of near-done jobs; escalate multiple callbacks to the ops manager |
| End of day wrap (4–5 pm) | Final utilization, open overnight jobs, daily callback count, on-time arrival rate for the day | Set up tomorrow's board: assign carryover jobs, flag techs with 2+ callbacks for a skills review |
| Weekly ops review | Utilization by tech, callback rate by tech and by job type, on-time trend, open capacity days | Identify routing patterns that waste drive time; adjust tech territories or zone assignments |
How an operations manager coaches dispatch performance from the dashboard
01 Start with capacity, not busyness
A board that shows jobs in progress can still hide three techs with open afternoon slots. The dispatch dashboard separates jobs running from capacity available so a manager sees both signals at the same time, not sequentially.
02 Flag idle techs before the window closes
When a tech completes a job 40 minutes ahead of schedule, the dashboard surfaces that as open capacity immediately. The dispatcher can then route a same-day request from the nearest open call rather than leaving the tech in a queue.
03 Trace callbacks to their source
Two or more callbacks from the same tech in a week is a pattern, not bad luck. The dashboard lets an operations manager pull the job history and identify whether the issue is a skill gap, a parts problem, or a diagnostic miss, so coaching is targeted, not general.
04 Use on-time arrival to audit routing, not punish techs
A consistent on-time arrival problem in a specific zip code or time window usually signals a routing or drive-time estimation issue, not a motivated-tech problem. A real-time view lets operations leaders see the pattern and correct it before it becomes a review problem.
05 Set a utilization goal and put it on the TV
When the whole team can see utilization in real time on the office TV, dispatchers self-correct between coaching sessions. A 3% lift in utilization across a team of ten techs can mean several additional revenue-generating jobs per week without adding headcount.
Warning
Common mistake
Measuring dispatch performance on completed-job count alone. A dispatcher who keeps 12 techs busy with low-margin tune-ups looks great on job count but misses on revenue per tech. The dispatch dashboard surfaces job type, average ticket, and utilization together so a manager can see whether a busy board is also a profitable one.
What home-service dispatch teams track in datacube
Live capacity board
See available, assigned, and in-progress slots per tech in real time, not after the fact. Dispatchers can fill open slots the same morning they appear.
Tech utilization by day and week
Track time on revenue-generating jobs versus total available hours per technician. Spot low-utilization techs before month end.
Callback and revisit tracking
See callbacks per tech and per job type as they happen. Two revisits in three days from the same tech surface immediately for a coaching conversation.
On-time arrival rate
Track on-time arrivals across the team and by individual tech. Use the data to audit routing and drive-time estimates, not just performance scores.
Office TV display
Push the dispatch board to any 55-inch-plus TV in the office so the whole team can see utilization, open capacity, and today's job count without opening the CRM.
Utilization goals and leaderboards
Set a daily or weekly utilization goal by team or by individual tech. Run a contest for the highest on-time rate or lowest callback rate. Datacube ships contest management with every board that has a leaderboard.
The short version
- Dispatch dashboards close the gap between what the CRM shows and what is actually happening in the field, right now.
- Tech utilization, open capacity, on-time arrival, and callback rate are the four signals that separate a profitable dispatch day from a busy-but-losing one.
- Real-time visibility lets dispatchers fill idle time the same morning it appears, not at the end-of-day debrief.
- Datacube builds the dispatch board around your CRM and your team's definitions of capacity, utilization, and callbacks, not a generic template.
Dispatch dashboard FAQs
See your dispatch board, built for your operation
Bring your current CRM and dispatching setup and we will show you what a real-time dispatch KPI dashboard looks like for your team: live capacity, utilization by tech, callbacks as they happen, and a board your whole operations team can coach from.
Keep exploring
Related
Go deeper
