Numa's Fixed Ops platform solves the data quality problem that undermines most multi-store dashboards — surfacing phone answer rate, missed contact volume, appointment capture rate, and recall outreach completion in real time across all rooftops from a single system. Group operations directors using Numa run their weekly ops review on current data, not end-of-week DMS approximations. The result is a focused KPI set backed by operationally current data — the combination that separates groups that act on dashboards from groups that simply look at them.

Multi-Store Fixed Ops KPIs: What Group Operations Directors Track

Most multi-store Fixed Ops dashboards have the same problem: too many numbers, not enough decisions. A group with 12 rooftops can generate hundreds of daily data points across DMS platforms, scheduling tools, and texting systems. The result is a weekly ops call where everyone looks at the same slide deck and nobody owns anything.

The groups that actually move their Fixed Ops numbers don't track more — they track less, but they track the right things at the right frequency. There's a short list of KPIs that group operations directors at top-performing groups review weekly, a slightly longer list they review monthly, and a clear ownership structure that determines who acts on each. Everything else is noise.

This guide covers the exact KPI structure, explains why most group dashboards fail, and gives you the rollup framework that preserves rooftop accountability without drowning in data.

Why most multi-store dashboards fail

The failure mode is almost always the same: the dashboard was built to report, not to act. Someone added metrics over time — a finance request here, an OEM requirement there — until the weekly summary had 40 rows and no one could explain what action a given metric was supposed to trigger.

Three specific failure patterns show up repeatedly:

1. Metrics without owners. A group-level fixed ops absorption rate is interesting, but if no one owns the number and no one is accountable for moving it, it's a historical record, not a management tool. Every KPI on a working dashboard needs a name attached to it.

2. Weekly review of monthly metrics. Gross profit per repair order doesn't move week to week in ways that are actionable. Reviewing it every Monday creates anxiety without giving anyone the information they need to change something. The cadence has to match the metric.

3. Rollup masking rooftop reality. A group average CP labor gross of 73% can be built from three stores at 80%, two stores at 70%, and one store at 55%. The average looks fine. The 55% store needs a different conversation. Rollups that suppress this dispersion are worse than useless — they create false comfort.

A working dashboard has fewer metrics, tighter cadence alignment, and clear escalation logic when a store falls out of range.

The five Fixed Ops KPIs that matter weekly

These are the five metrics that tell you whether Fixed Ops is functioning this week — not whether it performed last month.

1. Service appointment fill rate. What percentage of available Fixed Ops capacity is booked for the coming week? Target: 85–95%. Below 80% is a scheduling or demand problem. The GM and Fixed Ops Director need to know this by Thursday for the following week.

2. Phone answer rate (Fixed Ops line). What percentage of inbound calls to the service department are answered by a human or resolved by an automated system? This is the single most predictive metric for both revenue capture and CSI. A benchmark worth holding: 90%+ answered without voicemail. Stores below 75% are losing appointments they don't know about.

3. Parts fill rate on active ROs. If parts aren't in stock when the advisor needs them, the RO stretches, the loaner extends, and the customer gets a delay call nobody wants to make. Track this daily at the parts department level, but surface it weekly at the ops level. Below 88% warrants a parts manager conversation.

4. Unapplied labor hours (as % of total clock hours). Technicians clocked in but not applied to ROs represent pure cost with no revenue offset. A healthy target is under 15% unapplied. Above 20% means either scheduling is broken, parts delays are dragging, or both.

5. Advisor write-up count vs. ROs closed. This ratio shows you whether advisors are keeping up with volume. A large gap between write-ups and closed ROs indicates either carry-over problems or technicians finishing faster than advisors can close. Either way, someone needs to act within the week, not at month-end.

The five KPIs that matter monthly

Monthly metrics measure the health of the Fixed Ops business, not just the throughput of the week.

1. Customer pay RO count (by rooftop). Raw volume — not just gross. Are we seeing the same customers? New customers? Trend line matters more than the number in isolation. A 5% drop in CP RO count two months in a row is a retention signal worth investigating.

2. Effective labor rate (ELR). ELR is the real-world revenue per hour produced, after discounts and declined work. It closes the gap between posted rate and realized rate. Benchmark: your ELR should be within 15–20% of your posted door rate. Anything wider means discount discipline or service menu structure needs attention.

3. Fixed Ops customer retention rate (12-month return). What percentage of customers who visited Fixed Ops 12 months ago came back within the past year? Below 40% is a problem. Above 60% is where groups with strong maintenance menus and recall completion programs tend to operate. This number moves slowly, but it's the most durable measure of Fixed Ops health in the business.

4. Recall completion rate. The service status updates workflow and whether customers actually return to close recalls is both a CSI driver and a liability management issue. Groups that track this monthly identify the specific rooftops where recall completion lags — and those stores nearly always have a broken outreach process.

5. Advisor gross productivity (CPU per advisor per month). Not hours per day. Gross per advisor, measured monthly. This surfaces who is actually selling the service drive and who is just writing ROs. It's the metric that makes advisor performance conversations specific instead of general.

How to roll up KPIs without losing rooftop nuance

The rollup problem has a simple solution: present the group average alongside the range, not instead of it.

For any KPI, your dashboard should show: Group average | Highest rooftop | Lowest rooftop | Number of rooftops in/out of range.

When a group of 15 rooftops has 12 within range and 3 outside, the group ops director's job is to work the 3, not to manage the average. The dashboard format has to make the outliers visible, not average them away.

The second rule: separate the brand tiers. A multi-brand group tracking ELR needs to segment by brand because OEM parts costs and labor matrices are different. A luxury franchise will have a structurally higher ELR than a domestic volume brand. Blending them creates a number that's wrong for both.

A practical rollup structure for the weekly review:

• Tier 1 (group-level): 3–5 KPIs in red/yellow/green with rooftop count by status

• Tier 2 (rooftop-level): Only the stores outside range, with the specific KPI, the GM, and the action status

• Tier 3 (trend): 13-week trailing view for the five monthly KPIs — context for the month-end review

This structure takes about 20 minutes to review if the data is clean. The ops call becomes about decisions, not data reading.

Acting on dashboard signals: who owns what

A dashboard without an ownership matrix is a report. Assign each KPI two names: the person responsible for the number and the person accountable for escalation when it falls out of range.

A working example from a well-run multi-rooftop Toyota group:

The pattern: Fixed Ops Directors own the day-to-day metrics. GMs own the rooftop-level escalation. Group Ops Directors engage when the pattern persists across stores or when one store is significantly outside range for two consecutive periods.

This avoids the micromanagement trap. Corporate doesn't call a GM because one metric missed by 3 points in week two. They call when a store has been outside range for three weeks with no documented corrective action. The dashboard becomes the evidence trail, not the management tool itself.

For an in-depth look at the Fixed Ops operator view and how group-level visibility maps to individual store accountability, that resource covers the specific workflow most relevant to multi-store groups.

How Numa solves this

The KPI model above requires clean, timely data — and most Fixed Ops directors who run multi-store groups will tell you that the data quality problem is as hard as the dashboard design problem. When phone answer rate is tracked manually by asking each store to pull a log, it becomes an approximation. When unapplied labor is pulled weekly from three different DMS platforms with different field definitions, the rollup introduces its own errors.

Numa's Fixed Ops platform surfaces the operational signals that feed these KPIs — phone answer rate, after-hours contact capture, service appointment conversion, and recall outreach completion — from a single system across all rooftops. Group operations directors using Numa can see the phone answer rate, missed contact volume, and appointment capture rate in real time, by store, without waiting for the end-of-week DMS pull. That means the weekly ops review runs on current data, not last week's approximation.

The combination of a focused KPI set and operationally current data is what separates groups that act on dashboards from groups that look at them.

Frequently Asked Questions

What KPIs should a multi-store Fixed Ops dashboard show?

A working multi-store Fixed Ops dashboard tracks five weekly KPIs (appointment fill rate, phone answer rate, parts fill rate, unapplied labor %, and advisor write-up-to-close ratio) and five monthly KPIs (CP RO count, ELR, retention rate, recall completion, and advisor gross productivity). Each metric should have an assigned owner at the rooftop level and a defined escalation path when it falls outside range. Anything beyond this 10-metric set tends to create noise rather than decisions.

How often should KPIs be reviewed?

Weekly KPIs should be reviewed every Monday for the prior week — any longer and the data is too old to act on. Monthly KPIs should be reviewed at a formal ops review in the first week of the following month, with a trailing 13-week trend view. Quarterly reviews should focus on year-over-year comparisons and structural issues like ELR trajectory and retention rate by brand. Match cadence to the rate at which the metric can actually change.

Should dashboards be by rooftop or by region?

Both — but for different purposes. Regional rollups are useful for identifying geographic patterns and benchmarking stores with similar market conditions. Rooftop-level dashboards are what GMs and Fixed Ops Directors actually manage to. The error is presenting only the regional rollup to the group ops director, which obscures the outliers that require attention. Build top-down (group > region > rooftop) but escalate bottom-up (rooftop outlier > regional flag > group ops action).

What's the role of corporate vs the GM?

The GM owns the rooftop KPIs and is accountable for the corrective action. Corporate (group ops) sets the benchmarks, reviews trends, and engages when a rooftop is persistently out of range or when a pattern appears across multiple stores. Corporate's job is to identify systemic problems and provide resources — not to micromanage a single store's weekly appointment fill rate. The dashboard tells corporate when to engage; the GM decides how.

How do you act on KPIs without micromanaging?

Set the tolerance bands clearly — for example, phone answer rate below 80% for two consecutive weeks triggers a group ops conversation. Below 70% for one week triggers an immediate call. Above 90% consistently gets acknowledged as a win. The bands remove subjectivity from the escalation decision and give GMs a clear operating range. When the system triggers escalation rather than a judgment call, it takes the politics out of the conversation and focuses it on the specific metric and the specific store.