The 8 KPIs Every Multi-Location Business Should Track Weekly

With one location, you can feel how the business is doing. You're there. You see the busy days, the unhappy customer, the employee who's struggling.

With two or more, you can't. By the time a problem at another site reaches you, it's usually been going on for weeks. The cure is a short list of numbers every location reports every week, so you can see which sites are doing well and which need you, without having to be everywhere at once.

Here are the eight key performance indicators (KPIs) that matter most for a multi-location service business, how to calculate them, and how to review them in 30 minutes a week.

Why Weekly, and Why Only Eight

Weekly is fast enough to catch problems while they're small, and slow enough that the numbers mean something. Daily numbers bounce around too much; monthly numbers arrive too late.

Eight is enough to cover money, customers, operations, and people, and few enough that site managers will actually report them every Friday. Every extra KPI is one more reason a report arrives late or not at all.

The 8 KPIs

Money

1. Revenue vs. target What it is: Total sales invoiced for the week, compared with that site's own target. Why it matters: It's the first sign a site is growing, stalling, or slipping. Give each site its own target. A new location or a smaller market shouldn't be measured against your flagship.

2. Labor cost % What it is: The week's wages and payroll costs divided by the week's revenue. Why it matters: For most service businesses, labour is the biggest cost. When this number creeps up, it usually means scheduling hasn't kept pace with demand, or jobs are taking longer than they should. The healthy range varies widely by industry, so set your target from your own best-run weeks.

Customers

3. Customer satisfaction What it is: The average rating from this week's customer surveys (for example, out of 10). Why it matters: It's your early warning for lost customers. A drop at one site, while others hold steady, almost always points to something specific to that location: a staffing change, a process shortcut, or a manager stretched too thin.

4. Complaints and callbacks What it is: Complaints received, plus return visits needed to fix work. Why it matters: Callbacks are expensive twice over. You pay for the repeat visit and risk losing the customer. A rising count often shows up before satisfaction scores fall.

Operations

5. On-time completion % What it is: Jobs or orders finished by the promised time, divided by all jobs completed. Why it matters: Customers remember lateness more than almost anything else. This KPI also shows when a site is running out of capacity, since late jobs usually start piling up before you need to hire.

6. Jobs completed What it is: The number of jobs, orders, or appointments completed in the week. Why it matters: It's the volume behind the revenue. If revenue is flat but jobs are up, your average job value is falling, and you'll want to know why.

People

7. Open roles What it is: Positions currently unfilled at the site. Why it matters: An open role today is overtime, burnout, and slower service next month. Tracking it weekly keeps recruiting moving instead of stalling.

8. Safety incidents What it is: Injuries or near-misses reported this week. Why it matters: The target is zero, and any incident deserves a same-week conversation. A site where near-misses aren't being reported isn't necessarily safer. It may just be less honest.

The Roll-Up Mistake Most Owners Make

When you combine locations into a company total, some KPIs add up and some don't.

Counts add up. Revenue, jobs completed, complaints, open roles, and safety incidents can simply be summed across sites.

Percentages don't. Here's why. Say Site A had $60,000 in revenue and a labor cost of 30%. Site B had $20,000 in revenue and a labor cost of 45%. Average the two percentages and you get 37.5%. But the true company figure is:

($18,000 + $9,000) ÷ $80,000 = 33.75%

The simple average overstates your labor cost by nearly four points, because it treats the small site as if it were as big as the large one. For percentages like labor cost, weight each site by its revenue. For scores like customer satisfaction, where every site's customers matter equally, a simple average is fine.

There's one more trap: if a site hasn't reported yet, don't count it as zero. Leave it out of the company target for that week. Otherwise a late report looks like a sales collapse.

Setting a Target for Each Site

A KPI without a target is just a number. For every KPI, decide three things.

The target. Start from each site's recent performance, not from hope. Take the average of its last three good months as a baseline, then decide how much better you want it to be. A new location should have its own, lower revenue target for its first year, rising as it builds a customer base.

Which direction is better. Revenue and on-time completion should go up; labor cost, complaints, and incidents should go down. It sounds obvious, but writing it down stops arguments about whether a change is good news.

A watch zone. Decide how far from target still counts as "keep an eye on it" rather than "act now." For example, revenue within 10% of target might be amber, and anything further below is red. Watch zones keep you from overreacting to a slightly soft week while still catching real problems.

When to Change Your KPIs

These eight are a strong starting point, but your business isn't everyone's. Swap a KPI out when:

• Nobody acts on it. If a number has never changed a decision, it's taking up space.

• It's always green. A KPI that every site hits every week isn't telling you anything. Raise the target or replace it.

• You've found a better early warning. If you notice that average job value drops two weeks before revenue does, track that instead.

Change your KPIs at the start of a quarter, not mid-month, and keep the definitions identical across every site. Comparisons between locations only work when everyone measures the same thing the same way.

A 30-Minute Weekly Review

Numbers only help if someone acts on them. Hold the same short review every Monday:

1. Check who reported. Chase any missing site first. A dashboard with gaps can't be trusted.

2. Look at the company picture. Which of the eight KPIs are on target, which are close, and which are off?

3. Rank the sites. Which location has the most KPIs off target this week? Start there.

4. Look at the trend, not just the week. Compare each site with its own previous four weeks. One bad week is noise; three in a row is a pattern.

5. Agree on actions. For anything off target, decide what happens, who owns it, and by when. Write it down.

6. Check last week's actions. Were they done? Did they work?

The last two steps are what turn a report into management. Without them, you're just watching numbers change.

Make It Easier on Your Site Managers

Tracking only works if reporting is painless. Three things help:

• One simple form, the same at every site, submitted by the same day and time each week

• A written definition for every KPI, so "on time" means the same thing in every location

• Feedback that flows back. When managers see their numbers used, and their wins noticed, reports start arriving on time.

See Every Location on One Screen

Our Multi-Site KPI Dashboard, part of the Multi-Site Operational Toolkit, does all of this in Excel:

• Up to 12 locations and 10 KPIs of your choice, each with a target, a watch zone, and a written definition

• Company totals calculated the right way: counts summed, percentages weighted by revenue, and missing reports left out of the target

• A site league table and a colour-coded comparison of every site against every KPI

• Thirteen-week trends, a site-by-site drill-down, and a record of who has and hasn't reported

• An action log that flags overdue follow-ups

• Site managers enter one row a week. The dashboard does the rest.