Multi-location rollup: what it means and why it matters for growing home-service companies
When you run more than one location, individual branch reports only tell you part of the story. A multi-location rollup combines every location into one consolidated view so an owner or GM can see the whole operation at a glance and still drill into any single branch.
Definition
A multi-location rollup is a single consolidated report or dashboard view that aggregates KPIs from every branch or location into one number, while still letting you break out any individual site.
In home services, a rollup answers the question every multi-location owner eventually asks: 'How are we doing across all locations right now?' Instead of opening five ServiceTitan reports or three QuickBooks accounts and manually combining the figures, a rollup pulls each location's revenue, job count, booking rate, labor percentage, and other key metrics into one view. The consolidated total appears at the top; click through or filter and you see the same metrics for Phoenix only, or Austin only, or any subset you choose.
The commercial page covering multi-location dashboard software is at /multi-location-reporting. This page stays on what the term means and how operators use it.
The problem a rollup solves
Picture a plumbing company that opened its third location last year. Each branch runs ServiceTitan. Each month the owner spends two to three hours copying revenue, job count, and conversion figures from three separate reports into a master spreadsheet, then formatting totals before the Monday leadership meeting. By the time the deck is ready the numbers are already a day or two stale. That is data chaos at the operations layer: the information exists, but it costs hours to assemble and arrives late.
A multi-location rollup replaces that process. When all locations feed into one analytics layer, the consolidated figures update as the day moves. The owner sees total booked revenue for the company at 10 a.m. and can immediately notice that Phoenix is running 30 percent behind its month-to-date target while Austin is ahead. That is an actionable signal, and it arrives before the problem compounds into a missed month.
What makes a rollup accurate vs. misleading
A rollup is only as trustworthy as the KPI definitions underneath it. If Phoenix counts a job as booked when the appointment is set and Austin counts it as booked only when a technician is dispatched, the consolidated booking number is not comparable across sites. The prerequisite for a meaningful multi-location rollup is data consolidation with standardized definitions: every branch measures the same thing in the same way before the numbers are summed.
Common inconsistencies that break rollups include: different CRM configurations by branch, revenue recognized at different stages of the job lifecycle, labor cost allocations that vary by region, and marketing spend tracked under different campaign names across locations. Fixing these before building a rollup is the foundation of reliable branch reporting.
Why this matters for home-service companies in particular
Home-service companies scale by replicating a model across markets, not by running a fundamentally different operation in each city. That means the same KPIs matter everywhere: booking rate, average ticket, revenue per technician, gross profit, and ROAS from local campaigns. A multi-location rollup lets leadership confirm that each new branch is performing to the model, not just surviving. Combined with real-time KPI tracking, a rollup shifts the ownership question from 'how did each location do last month?' to 'which location needs help today?'
Warning
Data visibility gap: when branch reports are all you have
If you can only see one location at a time, you are making company-level decisions from branch-level evidence. An HVAC operator with four locations who reviews each branch in separate tabs cannot immediately spot that two branches share the same capacity crunch on peak summer days, or that one market's lead conversion rate is dragging the company average down by eight points. That pattern only becomes visible at the rollup level, and by the time a monthly report surfaces it, the busy season is already over.
Who reads rollup data vs. branch-only data
| Role | Primary view | What they act on |
|---|---|---|
| Owner / CEO | Rollup: company-wide totals and trends | Allocate resources, spot underperforming markets, confirm growth trajectory |
| GM / VP of Operations | Rollup with branch drill-down | Compare branch KPIs, escalate gaps, coordinate cross-branch capacity |
| Branch / location manager | Single-branch view (their location) | Own their branch's booking rate, revenue, and team performance; compare to company target |
| Finance / controller | Rollup: consolidated P&L, COGS, and labor across all locations | Spot labor overruns, margin compression, or expense spikes in any market |
| Marketing leader | Rollup with market-level campaign breakdown | Compare ROAS and booked revenue by market, shift spend to highest-return locations |
| Technician / CSR | Their own branch or individual performance board | Personal KPIs: revenue, jobs completed, booking rate; they do not see other branches |
What a multi-location rollup board can look like
This is an illustrative example of how a datacube Live Stats board might surface company-wide and per-location KPIs in real time on an office TV or web view. Actual figures, layout, and metrics are configured to each company's data sources and goals.
Figures above are illustrative. A datacube rollup board is built to your company's actual data sources, branch structure, and KPI definitions.
Info
Owner takeaway: the rollup is not a summary, it is a diagnostic
Most owners want to know their top-line number fast. But the real value of a multi-location rollup is the first layer below the total: which branch is dragging and which is pulling ahead. That delta is where a conversation starts. If your rollup shows company revenue at goal but your booking rate is down 8 points in one market, you have a problem already forming inside an otherwise green number. A rollup that only shows the total is just a slower spreadsheet.
Multi-location rollup vs. related concepts
| Term | How it relates to multi-location rollup |
|---|---|
| Data consolidation | The process of pulling data from multiple sources into one place. Data consolidation is a prerequisite; the rollup is the output you see. |
| Branch reporting | Reports scoped to one location. Branch reporting is one slice; rollup reporting is all slices combined plus a total. |
| Rollup reporting | Synonymous with multi-location rollup in most trade contexts. The term 'rollup reporting' emphasizes the report format; 'multi-location rollup' emphasizes the scope. |
| KPI standardization | Defining each metric identically across branches so rollup math is apples-to-apples. Without it, the rollup total is meaningless. |
| Real-time KPI tracking | Updating dashboard data continuously through the day. A rollup paired with real-time tracking surfaces today's branch performance, not last week's. |
| Drill-down | Navigating from the rollup total into one branch, department, or technician. The rollup is the starting point; drill-down is the investigative step. |
Multi-location rollup FAQs
See how a rollup board looks in datacube
Datacube can consolidate revenue, job metrics, booking rate, and financial data from every location into one live board, with branch drill-down built in. See how it appears for a multi-location home-service company.
Keep exploring
Related
Go deeper