Numa operates as the standardization layer for Fixed Ops communication and customer experience across multi-rooftop dealer groups. The Operator dashboard gives corporate a unified, near-real-time view of communication cadence compliance — inbound response time, proactive update rate, and first-contact resolution rate — broken down by rooftop, without manual reporting from the stores. For groups building or rebuilding their Fixed Ops standardization program, Numa handles the hardest layer to standardize — customer communication cadence — while leaving operational execution to each rooftop.

How to Standardize Fixed Ops Across Multiple Rooftops

Every multi-rooftop group hits the same friction when corporate tries to standardize Fixed Ops: the rooftop GMs who've been running their operations independently for years push back. Not always loudly. Sometimes it's quiet non-compliance — nodding in the planning meeting, then continuing business as usual. The result is a group that looks standardized on paper and operates inconsistently in practice.

The standardization challenge isn't really about standards. It's about what you're trying to standardize, and who owns execution. Corporate can mandate a KPI dashboard or a communication cadence. Corporate cannot mandate the specific way a service advisor builds rapport with a customer who just got bad news about their repair cost. When standardization efforts try to own both, they fail on both.

The multi-rooftop groups that have solved this problem share a common framework: they standardize the operating system — the inputs, cadences, and measurements that make performance visible and comparable across rooftops — and they leave execution decisions to the rooftop. The group sets the floor. The rooftop decides the ceiling.

This piece lays out the framework in operational terms: what to standardize centrally, what not to touch, how to roll out without triggering the resistance that kills most standardization programs, and how to measure whether it's working.

Why Most Fixed Ops Standardization Efforts Stall

Standardization programs at dealer groups tend to fail in one of three ways:

They try to standardize everything. A corporate Fixed Ops initiative that covers everything from RO write-up process to customer greeting scripts to parts reorder thresholds collapses under its own complexity. Rooftop GMs and Fixed Ops Directors have too many things to change simultaneously, compliance monitoring becomes impossible, and the initiative fragments within 90 days.

They standardize outputs without standardizing inputs. Setting a group-wide target for CSI scores or effective labor rate (ELR) without standardizing the operational processes that produce those outcomes is target-setting, not standardization. Rooftops hit the target or they don't, but corporate has no visibility into why — and no lever to pull when a rooftop underperforms.

They generate compliance theater. The rooftop produces the required reports, uses the required language in check-ins, and hits the numbers that are easy to hit while operating exactly as before on the metrics that aren't being measured. This is especially common when the standardization initiative came from above without rooftop buy-in.

The underlying issue in all three failure modes is the same: standardization is being applied to the wrong layer. Corporate is trying to control execution when its actual leverage is in the operating system.

A multi-rooftop Chrysler Dodge Jeep Ram group in the Midwest went through two failed standardization attempts before identifying the pattern. The third attempt succeeded because it explicitly defined what was being standardized at the group level and what was being left to each rooftop. That clarity resolved most of the resistance before rollout began.

The Three Things That Should Be Standardized Centrally

1. The measurement system. Every rooftop should be measuring the same KPIs, on the same cadence, using the same definitions. This sounds obvious and is frequently wrong in practice. If one rooftop measures ELR on customer-pay only and another measures it on total RO volume, the numbers aren't comparable and the group-level view is meaningless. If one rooftop reports CSI scores weekly and another reports monthly, performance visibility is inconsistent.

The specific KPIs that belong in a group-standard measurement system: ELR, Fixed Ops absorption rate, CSI (by OEM methodology), first-contact resolution rate on inbound communications, and advisor productivity (ROs per advisor per day). These are the metrics that tell you whether a rooftop's Fixed Ops operation is healthy — and they're meaningless unless they're measured identically across locations.

2. The customer communication standards. How the group communicates with customers during the Fixed Ops process should be standardized: when customers are contacted after check-in, what the status update cadence looks like, what the minimum requirements are for inbound response time. These standards protect the brand and protect CSI scores at a group level. A customer who had a great experience at one rooftop and a poor communication experience at another forms a view of the group, not just the location.

This doesn't mean the messages are scripted identically. It means the cadence and timing are standard: every customer receives a proactive update within X hours of check-in, every inbound text gets a response within Y minutes, every missed call gets a follow-up within Z minutes. The "how" is up to the rooftop; the "when" is group standard.

See how multi-rooftop groups standardize communication cadences across locations for a detailed breakdown of the measurement and reporting infrastructure that makes this workable.

3. The escalation framework. When does a Fixed Ops problem escalate from the rooftop to corporate? What constitutes a heat case that requires group-level visibility? What CSI score threshold triggers a formal support engagement? Defining this framework centrally prevents the situation where corporate finds out about a persistently underperforming rooftop from an OEM performance review rather than from its own reporting.

The Three Things That Shouldn't Be Standardized

1. Advisor workflow and customer interaction style. The specific way a Fixed Ops Director runs their morning meeting, the way an advisor writes up a RO, the customer conversation style on the service drive — these are rooftop execution decisions. Standardizing them creates friction without creating value. The customer experience standard (what customers receive) can be consistent without the execution style (how advisors deliver it) being identical.

2. Marketing and local promotional cadences. A rooftop serving a rural market with a loyal customer base operates differently from an urban rooftop competing against three other same-brand dealers within 20 miles. Group-level marketing standards make sense for brand consistency; local promotional timing and offer structure should remain a rooftop decision.

3. Staffing mix and lane configuration. The ratio of advisors to technicians, the use of express versus appointment-only lanes, the scheduling of BDC support — these decisions are made based on local market conditions, physical facility constraints, and rooftop volume patterns that corporate doesn't have the ground-level visibility to manage. Standardizing staffing structure at the group level typically produces rooftops that are misconfigured for their actual volume and market.

The principle here is consistent: standardize what makes performance visible and comparable. Leave what makes execution effective to the people who can see the floor.

How to Roll Out Without Triggering Rooftop Pushback

The resistance that kills most standardization programs is predictable and preventable. Rooftop GMs and Fixed Ops Directors push back when they believe:

• Corporate is adding reporting burden without adding value to their operation

• The standards being imposed don't reflect the reality of running their specific store

• Compliance will be used to punish them rather than support them

Addressing each of these directly before rollout:

On reporting burden: If the standardization initiative requires new data entry or new reporting that doesn't already exist, explain exactly what automation or tooling change will handle the collection. Rooftop teams should not be doing manual work to feed a corporate dashboard.

On rooftop-specific conditions: Run a discovery phase before announcing standards. Spend time with the Fixed Ops Director at each rooftop — or a representative sample — and explicitly ask what their operation looks like that would be complicated by specific proposed standards. You will find real exceptions. Incorporating them before rollout prevents post-rollout workarounds.

On punitive framing: The rollout communication should explicitly describe what corporate does when a rooftop is underperforming against group standards. "We identify it and send support resources" lands very differently than what many GMs assume: "We identify it and put the GM on notice." If the former is true, say it clearly and demonstrate it early in the rollout by actually sending support to the first underperformer you identify.

A multi-rooftop Toyota group in the Southeast ran this rollout sequence over 14 weeks: four-week discovery phase, four-week co-design phase with rooftop Fixed Ops Directors, four-week pilot at two stores, then full rollout with refinements incorporated. Adoption rate at 90 days was materially higher than their previous standardization attempts — specifically because the discovery and co-design phases created rooftop ownership of the standards rather than resistance to them.

Measuring Standardization Effectiveness

Standardization is working when you can see performance variation across rooftops and understand why it exists. The failure mode is a reporting system that shows uniformity because rooftops are reporting what corporate wants to see, not what's actually happening.

The metrics that reveal whether standardization is real:

Cross-rooftop KPI variance. Once standards are in place, what is the variance across rooftops on each standardized KPI? Some variance is expected — rooftops have different markets, volumes, and facility constraints. What you're watching for is whether variance is narrowing over time, and whether the rooftops that are outlying have explanations that make sense.

Inbound response time compliance. If a group standard requires inbound texts to be answered within five minutes, what is the actual average response time by rooftop? This is a leading indicator of communication standard compliance that can be measured automatically rather than relying on self-reporting.

CSI score variance. Are CSI scores converging across rooftops over time? Persistent outliers at the low end — especially when they're not explained by market-level factors — indicate either that the standard isn't being followed or that the standard isn't the right lever for that rooftop's specific problem.

For the group-level view, how Fixed Ops groups use a unified communication dashboard to compare rooftop performance details what this measurement infrastructure looks like in practice.

How Numa Solves This

Numa operates at the group level as a standardization layer for Fixed Ops communication and customer experience standards. Across multiple rooftops, Numa gives corporate operations a unified view of communication cadence compliance — inbound response time, proactive update rate, first-contact resolution rate — without requiring rooftop-level data entry or manual reporting.

The Operator dashboard shows group-level performance alongside individual rooftop breakdowns. When a rooftop is underperforming against group communication standards, corporate can see it in the same dashboard where they're reviewing CSI trends — and they can see it in near real time, not in a monthly report. Rooftop Fixed Ops Directors get the same visibility into their own performance, so there are no surprises in the group review.

For multi-rooftop groups that are in the process of building or rebuilding their Fixed Ops standardization program, Numa's communication layer handles one of the hardest parts to standardize — the customer communication cadence — while leaving operational execution to the rooftop. That's the balance that makes standardization sustainable rather than theatrical.

Frequently Asked Questions

What's the right balance between group standards and rooftop autonomy?

A useful rule: standardize everything that makes performance visible and comparable across rooftops. Leave everything that makes execution effective to the rooftop. In practice, this means KPI definitions, measurement cadences, customer communication standards, and escalation frameworks belong to the group. Staffing mix, workflow design, advisor interaction style, and local promotional timing belong to the rooftop. When corporate tries to own execution decisions, it typically produces compliance theater — rooftops hit the metrics that are measured while ignoring the underlying intent.

How do you measure standardization compliance?

The most reliable compliance signals are system-generated rather than self-reported: inbound response time data from your communication platform, proactive update rate from your outbound messaging system, CSI scores from OEM reporting. Self-reported compliance data is unreliable under a punitive accountability framework. Build your measurement system from data that requires no manual entry at the rooftop level.

What KPIs should be standardized first?

Start with the three that have the clearest definitions and the most direct connection to business outcomes: ELR, CSI score (by OEM methodology), and inbound response time. These three give you a meaningful picture of Fixed Ops health without creating measurement complexity. Once these are standardized and consistently tracked, add Fixed Ops absorption rate and advisor productivity. Build the measurement system incrementally rather than standardizing twelve KPIs simultaneously.

How long does Fixed Ops standardization typically take?

Expect 12–18 months from rollout to meaningful compliance and consistent measurement. The 90-day mark is when you'll see whether adoption is real or superficial — rooftops that are genuinely running the new standards show it in their KPI data; rooftops running compliance theater show flat numbers with clean reports. Full embedding — where the standards are simply how the operation runs rather than a program being followed — typically takes two to three performance review cycles.

What's the role of corporate vs the rooftop GM?

Corporate owns the operating system: what is measured, when it's reviewed, what triggers an escalation, and what support resources are available to underperforming rooftops. The rooftop GM owns execution: how the lane is run, how advisors are managed, how the communication standards are achieved. When corporate tries to own execution, it creates the resistance and non-compliance that kills standardization programs. When corporate clearly owns only the operating system and demonstrates value by making performance visible and providing support, GMs tend to engage rather than resist.