Operations manager dashboard playbook
A field-tested operating rhythm for the person who keeps every department running in a home-service business. Which KPIs to own, how to run your daily and weekly reviews, and what your operations dashboard should show so you stop finding out about problems at month end.
Role playbook
The ops manager's morning, before and after a dashboard
Before a unified dashboard: you open ServiceTitan, QuickBooks, the dispatch board, and a shared spreadsheet. You Slack the dispatcher about today's capacity, text a service tech about a callback from yesterday, and pull a weekly report that is already 48 hours stale. By 9 a.m. you have partial information about four departments and a list of questions no one has answered yet. After: one board loads on your screen. You see field capacity at 84%, three open callbacks from yesterday flagged red, install completions tracking five jobs behind goal for the month, and a technician whose average ticket dropped 22% this week. You know where to spend the next hour before the morning standup. The operations manager dashboard playbook is about building that second morning, not just buying software.
The short version
- The ops manager's job is cross-department coordination: field capacity, schedule adherence, job completion rates, and escalation routing all live with you, not in any single department silo.
- Daily reviews take 10 minutes if the board is built right. Weekly reviews drive accountability. Monthly reviews move targets. None of these happen well off a stale spreadsheet.
- The most expensive ops problem is usually invisible: capacity that looks full on paper but leaks through callbacks, incomplete jobs, and same-day cancellations that never get rebooked.
- An ops dashboard does not replace the dispatcher, the service manager, or the install lead. It gives you a common set of numbers so every conversation starts from fact, not assumption.
KPIs the operations manager should own
These are cross-department metrics only the ops manager has visibility into all at once. Status examples below are illustrative. Targets vary by trade, team size, season, and market, so calibrate against your own baseline before setting goals.
- Field capacity utilization (by department)Decision: where to pull in same-day bookings or shift overflow between service, install, and maintenance.Watch
- Current
- Live by day
- Target
- Track against scheduled vs. fillable slots
- Job completion rate (same-day close)Decision: which techs need support closing jobs on-site vs. returning for a second visit.Good
- Current
- By tech and department
- Target
- Push toward same-visit close on service calls
- Callback and return-visit rateDecision: whether callbacks cluster on a technician (training), a job type (parts), or a time of year (seasonal demand).Poor
- Current
- Daily count
- Target
- As low as quality work allows
- Schedule adherence (dispatch fill rate)Decision: route density, same-day add-ons, and whether dispatch has the signal to reallocate mid-day.Good
- Current
- By hour and by route
- Target
- Filled routes, minimum dead miles
- Same-day cancellation and reschedule rateDecision: which cancellations are recoverable and who follows up before end of shift.Watch
- Current
- Daily
- Target
- Flag and rebook within the same day where possible
- Average ticket by department (MTD vs. goal)Decision: whether a dip is a pricing issue, a job-mix shift, or a technician coaching opportunity.Watch
- Current
- By department
- Target
- Track against department-level goal, not just company average
| Metric | Current | Target | Status |
|---|---|---|---|
| Field capacity utilization (by department)Decision: where to pull in same-day bookings or shift overflow between service, install, and maintenance. | Live by day | Track against scheduled vs. fillable slots | Watch |
| Job completion rate (same-day close)Decision: which techs need support closing jobs on-site vs. returning for a second visit. | By tech and department | Push toward same-visit close on service calls | Good |
| Callback and return-visit rateDecision: whether callbacks cluster on a technician (training), a job type (parts), or a time of year (seasonal demand). | Daily count | As low as quality work allows | Poor |
| Schedule adherence (dispatch fill rate)Decision: route density, same-day add-ons, and whether dispatch has the signal to reallocate mid-day. | By hour and by route | Filled routes, minimum dead miles | Good |
| Same-day cancellation and reschedule rateDecision: which cancellations are recoverable and who follows up before end of shift. | Daily | Flag and rebook within the same day where possible | Watch |
| Average ticket by department (MTD vs. goal)Decision: whether a dip is a pricing issue, a job-mix shift, or a technician coaching opportunity. | By department | Track against department-level goal, not just company average | Watch |
Warning
Ops manager blind spot: the capacity that looks full but is not
A schedule that reads 90% booked is not the same as 90% productive capacity. Same-day cancellations that sit open, jobs that run long and push the afternoon route, callbacks from last week that the system still counts as complete revenue, and install jobs technically on the board but waiting on parts: all of these inflate your apparent utilization. If your ops dashboard only shows bookings, you are managing a plan, not a reality. The signal you need is completions, time-on-job, and open-callback counts side by side with the schedule fill.
Cross-department KPI ownership: what the ops manager watches vs. what the department lead owns
| KPI | Ops manager watches | Department lead owns | When the ops manager steps in |
|---|---|---|---|
| Field capacity utilization | Overall % across service, install, maintenance | Department-level routing decisions | Cross-department reallocation when one team is full and another is light |
| Job completion rate | MTD trend and outlier technicians | Individual tech coaching | When a technician's close rate drops and the service manager has not flagged it |
| Callback and return-visit rate | Company-wide pattern and cost | Root cause by tech and job type | When callbacks cluster on a crew or a job category that spans departments |
| Same-day cancellation rate | Volume and recovery rate each day | CSR and dispatcher follow-up | When open cancellations are not rebooked by midday and revenue is at risk |
| Average ticket by department | Trend vs. goal and vs. prior month | Pricing and upsell coaching | When a department-level dip is not being addressed and it is pulling company revenue below plan |
Daily, weekly, and monthly review cadence
01 Morning board check (10 minutes)
Before the standup, load the ops board and scan: field capacity for the day, open callbacks from yesterday, and any cancellations still unrebooked. These three numbers tell you where the day is fragile before a single truck rolls. If capacity is tight and callbacks are high, you know dispatch needs cover. If cancellations are open, you know who to follow up with before 10 a.m.
02 Daily standup (department leads, 15 minutes)
Run the standup from the ops board, not from memory. Service completions yesterday vs. goal. Install jobs on track vs. behind. Capacity for today with any same-day openings flagged. One red flag that needs a decision in the room, not later. The rule: if the number is on the board, the standup does not debate it, it acts on it.
03 Midday pulse (5 minutes)
A quick glance at the ops board around midday catches same-day cancellations that opened up but have not been rebooked, route delays that are compressing the afternoon schedule, and any technician running significantly long on a job. These are live problems with live fixes, not issues for tomorrow morning's standup.
04 Weekly ops review (department leads, 30–45 minutes)
Pull the week's performance on completion rate, callback rate, capacity utilization, and average ticket by department. Compare to the prior week and to the monthly goal pace. Identify one coaching priority per department and assign it before the meeting ends. If a trend is moving the wrong direction two weeks in a row, it is not a blip, it needs an owner.
05 Monthly targets and reset
Review the full month by department and company. Compare actual completions, callbacks, and average tickets against the goals set at the start of the month. Identify what changed, whether it was demand, staffing, a new install crew, or a pricing adjustment. Reset targets, adjust contests if you run them, and communicate the new baseline to the team before the next month starts, not after the first week.
What an operations manager dashboard looks like
This is the web view an ops manager opens at 7:45 a.m. before the standup. It consolidates field, dispatch, service, and install into one screen so the morning check takes 10 minutes, not an hour.
Figures are illustrative. A datacube operations manager dashboard is built around your departments, trade, data sources, and team structure.
Info
Coaching moment: the ops manager's role is not to fix everything
A common mistake ops managers make with a new dashboard is trying to personally resolve every red number on the board. That is not the job. The job is to see the number before the department lead misses it, ask the right question, and make sure the right person owns the fix with a deadline. The dashboard is your visibility layer. Your standup is the accountability mechanism. When a callback count spikes, the question is not 'how do I fix this' but 'who owns this, do they know, and what do they need from me to solve it today.' That is what makes the ops board a management tool, not just a reporting screen.
Goals, leaderboards, and accountability
How goals and contests support ops-level accountability
Where structured goals pay off for an operations manager:
- A department-level completion-rate goal makes a shared target visible to the whole install or service team, not just the manager.
- A callback-reduction contest across tech crews turns a lagging indicator into a behavior the team actively manages.
- Leaderboards by technician for average ticket and completion rate give the service manager a coaching tool without the ops manager having to run every one-on-one.
- Company-level and department-level goals on the ops board let you see at a glance whether you are pacing for the month or burning down the runway.
Operations manager dashboard FAQs
See every department on one ops board
Datacube builds a custom operations manager dashboard around your departments, data sources, and daily review rhythm so your morning standup starts with facts, not questions.
Keep exploring
Related
Go deeper
