Branch performance: definition, formula, and dashboard example

What is branch performance?

Branch performance is a location-level view of how well each office, territory, or market is executing against the business plan. For a home-service or skilled-trades company with two or more locations, it answers: which branch is on pace, which is slipping, and why? The KPI set varies by operator but almost always includes revenue, gross margin, job volume, booking rate, and average ticket, because those five numbers together tell you whether a branch is busy, profitable, and converting its demand.

The challenge is visibility. When each location runs through its own CRM login, its own QuickBooks file, or its own reporting tab, the owner or GM has to log into each system separately, pull numbers manually, reconcile the formats, and stitch together a picture that is already stale by the time it is done. That lag is where problems hide. A branch that is 12 percent under its revenue goal in week two is still recoverable. The same branch at month-end is a missed number.

A scenario: spotting the underperforming branch in real time

Imagine a multi-location HVAC company. On a single branch rollup the GM can see on a Tuesday morning that one branch is comfortably ahead of its monthly goal, another is on pace, and a third has fallen behind with its gross margin slipping from the prior month. Without a multi-branch view that pattern would not surface until the controller pulls the month-end P&Ls, weeks too late to act; with a live board the GM calls the lagging branch's manager the same morning, finds the cause (a tech out sick, demand spilling to a competitor), and adjusts dispatch to cover it. On a datacube board each location or business unit rolls up from the same KPI definitions, and in ServiceTitan the per-unit figures come from the Business Unit Performance report.

What goes into a branch performance scorecard

Core metrics to track per branch: revenue (MTD and YTD vs. goal), gross margin (to catch discount creep or labor cost spikes), jobs completed, booking rate (demand capture at the branch level), and average ticket (revenue quality). Operators with a service and install mix often add a capacity utilization rate per department at each branch.

Who owns branch performance and how often to review it

The owner or GM owns the cross-branch view. Branch managers own their own location's numbers and are accountable to the company targets. Review the composite across all branches daily at a high level (are any locations falling behind on pace?), weekly in a branch-manager call, and monthly in a full KPI review where you look at trend direction, not just month-to-date snapshots.

How to track branch performance in practice

Start by agreeing on a shared KPI definition across every branch. If Branch A counts jobs completed differently from Branch B (for example, one includes cancelled-same-day and the other does not), the comparison is meaningless. Standardize the definitions first, then build the rollup.

Data sources for multi-branch reporting

For teams using ServiceTitan or Housecall Pro, job revenue and booking data can be consolidated by location tag. For financial margin data, QuickBooks class or location tracking maps each expense and income line to a branch. When configured to pull from both, a branch performance board can show operational and financial KPIs in the same view, refreshed throughout the day instead of after month-end close.

Common mistakes that distort branch performance numbers

The most frequent distortions: (1) shared technicians attributed to the wrong branch, inflating one location's job count and deflating another's; (2) inter-branch job transfers that count as revenue at both branches; (3) overhead allocation inconsistency, where one branch is charged HQ costs and another is not, making margin comparisons misleading; (4) using different date ranges per branch when pulling reports manually. All four disappear when a single reporting layer pulls from the same data source with the same filters applied to every location.