The monthly ops review has all seven KPIs on the slide, blended into one company-wide number, and every one of them is green. Nobody in the room can say which location is actually dragging the average down — or whether one location is quietly masking for two others that are worse. That’s the real problem with cleaning company KPIs across locations: the average is doing exactly what it’s built to do — hiding the one location that’s actually failing.
Take direct payroll as a percentage of revenue. Across MaidCentral’s customer base it’s run close to 41–42% recently — a reasonable number to feel fine about, blended. But the average is the least interesting number here. The leak lives in the spread: one location running at 35% and another at 49% produces the same company-wide 42% as three locations all running an even, unremarkable 42% — and those are two entirely different businesses to manage.
Averages absorb outliers by design. That’s what an average is for — and it’s exactly why a single blended KPI can look healthy while one location is actively losing money underneath it.
A number with no assigned owner isn’t a KPI. It’s a slide. If nobody at the location or crew level is accountable for a metric moving, the metric is decoration with a review schedule attached.
Governance without granularity doesn’t catch anything. Reviewing seven company-wide numbers monthly feels like oversight. It’s oversight of the average — the thing that actually needs catching is the location quietly diverging from it.
See where your own locations diverge.
Break one KPI out by location and find out if your average is telling the truth.
Cleaning company KPIs across locations: the real question isn’t which ones. It’s who owns each one, where.
The Growth-tier version of this problem is visibility: get the numbers in one place so you can see them at all. At this scale, the numbers are usually already visible — dashboards exist, reports get sent. The governance version of the problem is sharper: does anyone own the number at the level where it’s actually produced, or does it only exist as a company-wide roll-up that nobody below the ops review has to answer for? A KPI that’s tracked but not owned at the location level isn’t governed. It’s just reported.
From gut instinct to a company that trains on its own data
Bright Side Services crossed the million-dollar mark after years of running on referrals, effort, and Michelle Krueger’s own instinct for what was working. In-home estimates still drove the sales process. Absenteeism sat at 33%. Payroll was manual. Too much of the business ran on what only Michelle carried in her head — including, when COVID hit staffing hard, whether to keep going at all.
Bright Side Services — crossed $1M, survived a full staff replacement, still moving. Before: gut-feel decisions, in-home estimates driving sales, 33% absenteeism, and a business too dependent on what only Michelle knew. After: absenteeism down to 8.53%, average bill per clean up 10% ($184 → $202), and when Michelle replaced her entire office team mid-growth, the business kept going.
“Before stronger systems and data, decisions were often made from gut instinct. Now I can see what is happening, train from data, and identify problems more objectively.”
— Michelle Krueger, Owner, Bright Side Services
Read that sequence again: see, train, identify. In that order. Not “identify, then see” — the visibility came first, and only once it existed could the business start training itself on its own results instead of Michelle’s memory of what usually worked.
What if it breaks?
Nothing about this asks a location manager to give up judgment, and nothing about it replaces the relationship a good manager has with their crews. The numbers don’t run the location — they tell you where to look, the same way they always would have if you’d had the time to check every location yourself, every week. Most companies phase this in one metric at a time, starting with whatever’s easiest to prove out — usually payroll percentage or absenteeism — rather than overhauling the whole review process in one quarter. The review meeting doesn’t get bigger. It gets sharper about which location it’s actually talking about.
What not fixing this costs, three years out
The company that keeps reviewing blended averages doesn’t fail dramatically — it just keeps making decisions for the average location, which is to say, for a location that doesn’t exist. The best-run location subsidizes the worst one in the numbers, so the worst one never gets the attention it needs and the best one never gets credited for what it’s actually doing. Three years on, that’s not a crisis. It’s a company where every decision has been made slightly wrong for slightly too long, and where the fix — when it finally happens — costs more than it would have at year one, because the gap between locations had three years to compound instead of one quarter.
Where this actually lives in the system
Role-based access is part of the platform — which is what makes it possible for a location’s own numbers to be visible to the people who actually run that location, rather than existing only as a company-wide roll-up nobody there ever sees broken out. Exactly how far that visibility extends, and whether a single cross-location view consolidates automatically, depends on how your accounts are structured — Satellite Offices versus Branches changes what’s available out of the box, so that’s worth confirming directly with your account team rather than assuming either way. What doesn’t depend on account structure: the same seven numbers, defined the same way, at every location, so “our payroll percentage” means the same thing whether it’s said about location one or location four — that consistency is the whole point of tracking cleaning company KPIs across locations in the first place.
The changed Monday meeting
The ops review still has the same seven numbers. What’s different is that each one has a location attached, a name attached, and a question attached — not “how’s payroll company-wide” but “why is location three’s payroll four points above the other two, and what’s the plan by next review.” The decision gets made in the room, not three weeks later after someone finally pulls the location-level report by hand.
Questions Operators at Scale Ask
How many locations before this actually matters?
It matters at two. The math that hides a struggling location inside a healthy average works exactly the same whether you’re averaging two locations or twelve — it just gets harder to catch by eye as the number of locations grows.
Doesn’t breaking out variance just create more reports to review?
The opposite, done right — one report with location-level breakdown replaces the practice of pulling the same seven numbers by hand for each location separately when something feels off. The governance is in the definition being consistent, not in the volume of reporting.
Will this create competition or blame between location managers?
That’s a framing choice more than a data one — the same variance data can be used to rank people or to find out where a location needs support before its numbers get worse. Companies that get value from this treat a diverging location as an early flag, not a scorecard.
How did one company actually make this transition?
Bright Side Services did it while replacing its entire office team mid-growth — the systems that had already replaced gut instinct with visibility were exactly what let the business keep running through a change that would have been much harder to survive on memory and referrals alone.
Earlier in the journey? → Cleaning Business KPIs: The 7 Numbers That Actually Show You’re in Control — the Growth-tier version of this question, for a single-location or single-team operation.
Bring your KPI review deck.
A working session built around your actual multi-location numbers — not a feature tour.
