What KPIs should a multi-location operator track across all locations?

The core portfolio KPIs are revenue pacing vs. goal by location (month-to-date), booking rate by location, average ticket by location and by technician, gross margin by location (when connected to QuickBooks), technician utilization, and missed or abandoned call rate. The most important thing is that every location measures these the same way. One definition of 'average ticket' across eight locations is more valuable than eight slightly different metrics that cannot be compared.

How does a multi-location dashboard differ from each location's own board?

An individual location board shows the full operational detail for that team: CSR booking rates, individual tech performance, daily call volume, dispatch capacity. A portfolio rollup shows the operator the summary rows for every location side by side. In a datacube setup, the operator can see both: the portfolio view as the default, with a click through to any location's full board. The operator does not need to manage every detail, but needs to know which location to look at more closely.

How early in the month can a multi-location dashboard detect a problem?

With real-time data and a revenue-pacing view, a booking-rate or average-ticket problem is visible by day 5 to 8 of any month. That is when you have enough signal to distinguish a genuine underperformance from noise, and still have 60 to 70 percent of the month left to act. The operators who catch problems at day 8 and the ones who catch them at day 28 are often using the same CRM. The difference is whether the data is consolidated and displayed in real time or delivered in a weekly email.

Can datacube handle locations running different CRMs or field-service platforms?

Datacube is designed to consolidate data from 50+ sources, including different CRMs and field-service platforms across locations. When multiple locations are configured, datacube can pull from ServiceTitan at one location and Housecall Pro at another, standardize the KPI definitions, and display them side by side. The key is that your build process maps each source to a shared metric definition. This is part of the custom 4 to 6 week onboarding process, not a self-serve configuration.

What is the right meeting cadence for a multi-location operator?

A practical cadence for most operators: a five-minute daily scan of the portfolio rollup, a mid-week check-in on any locations showing a flag, a 30-minute Monday portfolio call with location managers (anchored to the live dashboard, not email reports), a 60-minute monthly portfolio review, and a quarterly location health assessment using trend data. The dashboard makes the daily scan possible without a phone call. The meeting time goes toward decisions, not toward data collection.

How do goals and contests work across multiple locations?

Datacube can run goals at the company level, at the location level, and at the individual level. Contests can span locations so a technician in location A is competing on the same leaderboard as a technician in location B. Goals show on-track in green and off-track in red on the dashboard. Contests ship with any datacube build that includes at least one leaderboard. For a multi-location operator, cross-location visibility is often the fastest way to raise the floor: a location manager who can see their team ranked third out of four locations has a different conversation with their techs than one who only sees their own numbers.

How is this playbook different from the franchise operator playbook?

The franchise operator playbook focuses specifically on the franchisee accountability model, royalty-fee reporting structures, and the data needs of a franchisor overseeing franchisees. This multi-location operator playbook is for an owner or executive who operates multiple locations they own directly, without a franchise structure. The dashboard architecture is similar, but the KPI priorities, accountability conversations, and operational interventions differ. If you run a franchise system, see the franchise operator dashboard playbook for a more specific operating model.

Does datacube require every location to be on the same CRM?

No. Because datacube is a visibility and analytics layer built on top of the tools your business already uses, it can connect to different data sources per location. A portfolio with locations on ServiceTitan and others on Workiz or Housecall Pro can still be consolidated into a single dashboard. Standardization happens at the KPI definition layer inside datacube, not by forcing your locations onto the same platform. The onboarding process maps each source to a consistent metric set.

Multi-location operator dashboard playbook

You run multiple locations, trade routes, or franchise markets. This playbook covers what to review, how often, and which KPIs separate a healthy location from one that needs attention before the month closes.

By Datacube content engineAutogeneratedJune 24, 2026

Role playbook

From location reports to a live portfolio view

Picture the before: Monday morning, three location managers email their weekly numbers, two in separate spreadsheet formats, one in a text summary. You stitch them together, spot that location three is running low on booked installs for the month, and send a message. By the time you get a reply it is Wednesday. The month is already compromised. The after: you open a single web dashboard at 7 a.m. Every location's booking rate, average ticket, technician utilization, and revenue-to-goal pacing is live and in the same format. Location three is flagged in red. You are on the phone by 7:05. That is what a multi-location operator dashboard playbook is actually about: shrinking the gap between a problem forming and the moment you can act on it.

The short version

Standardize KPI definitions across every location before you add dashboards. Revenue-per-job means nothing if location two counts accessories and location four does not.
Own portfolio-level booking rate, average ticket, revenue-to-goal pacing, and gross margin by location. Each one drives a different conversation with a different location manager.
Run a Monday morning portfolio check, a mid-week flag review, and a monthly trend call. Most location-level problems are visible in the first 10 days of the month if you are watching in real time.
The biggest portfolio risk is not a bad location. It is finding out a location is bad after the month ends, when the revenue is already gone.

Warning

Data visibility gap: the weekly report problem

Most multi-location operators receive data in the same delayed format: a weekly email, a shared spreadsheet, or a Friday call. By the time a lagging location appears in that report, the week is already over. A booking-rate dip that started Tuesday does not show up until the operator asks about it on Friday. In a month with 22 business days, that five-day lag costs you roughly a quarter of the window to correct it. Real-time portfolio visibility is not about more data. It is about compressing the gap between a problem forming and the moment you can redirect a location manager.

The KPIs a multi-location operator should own

These are the portfolio-level metrics that differentiate a healthy location from one drifting off pace. Status examples below are illustrative. Real targets vary by trade, market, season, and your business model. Set them against your own portfolio baseline.

Revenue-to-goal pacing by location (MTD)Decision: which location needs a demand-side push or a booking-rate conversation this week, not at month end.
Good
Current
Live by location
Target
On or ahead of pace by day 10
Booking rate by locationDecision: a location with half the booking rate of its sibling is leaking paid leads. That is a staffing or training conversation.
Watch
Current
Live comparison
Target
Consistent across locations
Average ticket by location and by techDecision: outlier lows often mean discounting, short-cutting the diagnostic, or skipping the membership offer.
Good
Current
By job type
Target
Within a defined band of the portfolio average
Gross margin by locationDecision: a location growing revenue but shrinking margin is building a profitability problem, not a success story.
Watch
Current
Connects to QuickBooks
Target
Profitable vs. revenue-chasing
Technician utilization by locationDecision: underutilized capacity at one location while another turns away calls is a dispatch coordination opportunity.
Good
Current
Jobs per day per tech
Target
Capacity used without overtime drag
Missed and abandoned calls by locationDecision: high missed calls during a campaign period means the ad spend is generating demand the location cannot capture.
Poor
Current
Live by day
Target
Minimize; compare vs. marketing spend

Metric	Current	Target	Status
Revenue-to-goal pacing by location (MTD)Decision: which location needs a demand-side push or a booking-rate conversation this week, not at month end.	Live by location	On or ahead of pace by day 10	Good
Booking rate by locationDecision: a location with half the booking rate of its sibling is leaking paid leads. That is a staffing or training conversation.	Live comparison	Consistent across locations	Watch
Average ticket by location and by techDecision: outlier lows often mean discounting, short-cutting the diagnostic, or skipping the membership offer.	By job type	Within a defined band of the portfolio average	Good
Gross margin by locationDecision: a location growing revenue but shrinking margin is building a profitability problem, not a success story.	Connects to QuickBooks	Profitable vs. revenue-chasing	Watch
Technician utilization by locationDecision: underutilized capacity at one location while another turns away calls is a dispatch coordination opportunity.	Jobs per day per tech	Capacity used without overtime drag	Good
Missed and abandoned calls by locationDecision: high missed calls during a campaign period means the ad spend is generating demand the location cannot capture.	Live by day	Minimize; compare vs. marketing spend	Poor

Location-by-location performance snapshot

Metric	Location A (strong)	Location B (on pace)	Location C (needs attention)	What it tells the operator
Revenue pacing (day 12 of 22)	58% of monthly goal	51% of monthly goal	31% of monthly goal	C is behind pace by roughly 20 points. At day 12, there is still time to intervene.
Booking rate (inbound calls)	68%	62%	44%	C's booking rate points to a training or staffing gap, not a demand problem. Conversations start here.
Average ticket	$520	$490	$310	C's low average ticket alongside low booking rate suggests both the CSR and tech layers need attention.
Missed calls (today)	3	7	18	C is burning ad spend on calls it cannot answer. That problem costs money twice: in the campaign and in the missed job.
Tech utilization	82%	76%	54%	If A has capacity constraints and C has idle trucks, there may be a shared-resource conversation to have.

Info

Quick example: HVAC portfolio heading into summer

An HVAC operator with four locations going into June knows summer demand will mask performance problems for three months. High call volume covers low booking rate. Full trucks hide inefficient dispatch. By October, when demand drops, a location that was quietly discounting all summer shows up with compressed margins and no reserve. The operator who ran a live portfolio dashboard in June saw the average-ticket gap at one location in week two, ran a coaching session that week, and protected the margin before summer demand inflated the revenue line. The one running weekly email reports found out in October.

Your daily, weekly, and monthly review cadence

01
Daily morning scan (5 minutes)
Open the portfolio rollup on web or mobile. Confirm each location's revenue pacing and booking rate against yesterday's close. Any location showing a red flag on either metric gets a message before 8 a.m. The goal is to see the drift before the location manager does, so your coaching is proactive instead of reactive.
02
Mid-week flag review (Tuesday/Wednesday)
Any location behind revenue pacing by more than five to eight points at the midpoint of the week needs a dedicated check. Is the booking rate low? Is the average ticket compressing? Are missed calls elevated? The dashboard tells you which question to ask. The location manager answers it.
03
Monday portfolio call (30 minutes)
Run a weekly portfolio call with each location manager, anchored to the same data each person can see in the dashboard. Review last week's revenue against goal, booking rate vs. portfolio average, and any outstanding coaching actions. Use the leaderboard view across locations to recognize what is working in the top performer and replicate it elsewhere.
04
Monthly portfolio review (1 hour)
Pull the full month's data across locations: revenue, gross margin, average ticket, booking rate, missed calls, and technician utilization trends. Compare each location's trajectory, not just its result. A location growing revenue with shrinking margin is a different problem than one that is flat but profitable. Connect to QuickBooks financial data when configured so the P+L view is in the same session as the operational view.
05
Quarterly location health assessment
Evaluate each location on the same standardized KPI set across the quarter. Use the trend view to flag structural problems vs. one-off months. Locations being considered for investment, additional headcount, or new market expansion should show at least two consecutive quarters of consistent KPI performance, not just revenue growth.

What a multi-location operator dashboard looks like

A portfolio rollup view accessible on web, with each location displayed as a row. Drill into any location for the full board. Set up on office TV screens at your HQ or regional office to keep the portfolio visible to leadership.

Dashboard preview

Figures are illustrative. A datacube multi-location operator dashboard is built around your locations, KPI definitions, CRM setup, and goals.

Goals, leaderboards, and contests across locations

Make healthy competition visible portfolio-wide

Where goals and contests create lift across a multi-location portfolio:

A shared leaderboard across locations for average ticket or booking rate creates peer pressure that is faster than a coaching call.
Location-vs-location contests during slow seasons give every team a visible target that is not just hitting a number on a spreadsheet.
Individual technician leaderboards visible across the portfolio let top performers self-identify. The location manager suddenly has data to support a promotion conversation.
Company-level and location-level goals in the same view let you see whether the portfolio goal is on track even when individual locations are mixed.

What a multi-location operator board needs to include

Standardized KPI definitions

Datacube builds your dashboards around a single, agreed definition for each KPI so location three counts revenue the same way location one does. You stop arguing about the numbers and start acting on them.

Location rollup with drill-down

A portfolio summary view for the operator, with one-click drill-down into any location's full board. No context-switching between systems or logins.

Real-time pacing vs. goal

Revenue, booking rate, and average ticket pacing against monthly goals in real time. You see a location going off track on day 8, not on day 28.

QuickBooks financial integration

When configured, datacube connects to QuickBooks so gross profit, COGS, labor percentage, and NOI by location sit on the same dashboard as your operational KPIs. No separate P+L pull required.

Cross-location leaderboards

Rank locations, teams, and individuals on shared metrics. Cross-location visibility drives accountability without requiring a new management layer.

Mobile and TV display

The portfolio dashboard is accessible on mobile so you can check pacing before a leadership call, and on the office TV at HQ so the team sees the portfolio position every day.

Multi-location operator dashboard FAQs

See your portfolio on one live board

Datacube builds a custom multi-location operator dashboard around your locations, your CRMs, and your KPI definitions, so you can spot a lagging location on day 8 instead of day 28.

Schedule a live demo Take the self-guided demo

Keep exploring

Operations managerA 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.

OwnerA practical guide for home-service and skilled-trades owners: the KPIs to hold on your screen every morning, the rhythm for reviewing them, and the questions your data should answer before you walk out of the office.

Private equity operatorA practical guide for PE operators who own home-service or skilled-trades portfolios: the KPIs that signal platform health, the cross-location review cadence, and how a real-time dashboard replaces the weekly variance-report chase.

Sales managerA practical operating rhythm for the person who owns revenue production in a home-service company. The KPIs to track by tech and by day, the questions to ask before the month slips away, and how a sales board turns individual numbers into team accountability.

Go deeper