Numa’s AI Operating System gives group operations leadership a shared view of inbound contact volume, appointment booking pace, and BDC throughput across rooftops without requiring each store to operate identically. By handling after-hours and overflow inbound contacts at the BDC layer — the capacity constraint most groups face first — Numa allows Fixed Ops teams at each rooftop to focus on conversations requiring human judgment rather than volume. Numa’s operator dashboard provides the group-level visibility into Fixed Ops communication and scheduling metrics that group operations directors need to plan capacity across rooftops rather than just report it.

Fixed Ops Capacity Planning: A Framework for Multi-Store Groups

Most multi-store groups approach Fixed Ops capacity planning the same way: each rooftop manages its own bays, its own advisor headcount, and its own BDC. The group-level view is a rollup of individual store performance reports, not a planning instrument.

That approach works until it doesn’t. When one rooftop is at 95% bay utilization and turning customers away on Friday afternoons, and another rooftop 12 miles away has open bays and an advisor with capacity, the group is both losing revenue and failing customers — simultaneously, at the same time, in the same market.

The fixed constraint is the assumption that capacity is rooftop-local. It is not. For a multi-store group, Fixed Ops capacity is a portfolio that can be planned, allocated, and measured at the group level. The upside is in coordinating across rooftops to capture demand that individual stores cannot serve alone.

This framework covers the three capacity layers that matter, how to plan at the group level, how to reallocate across rooftops without triggering internal resistance, and how to measure utilization in a way that surfaces group-level opportunities rather than just individual store performance.

Why rooftop-level capacity planning hits a ceiling

Every Fixed Ops Director optimizes for their own store’s performance. That is rational behavior given how most groups measure accountability — P&L by rooftop, CSI by rooftop, Fixed Ops absorption by rooftop. When incentives are rooftop-local, capacity planning is rooftop-local.

The problem is that demand is not rooftop-local. Customers in a metro market are not exclusively loyal to one store in a group’s network. They have loyalty to the brand, to a specific advisor, and to convenience. When their preferred store is booked out two weeks, a meaningful percentage will schedule at a competitor before they will proactively call the next store in the same group — because they do not know the group network exists.

Rooftop-level planning also creates inconsistent utilization patterns that compound Fixed Ops cost. A store with one Fixed Ops Director who is strong at scheduling and communication will run 80–85% bay utilization. A store with a weaker planning process will run 60–65%. Both are paying similar fixed costs — building lease, equipment maintenance, base advisor compensation — but generating significantly different revenue per square foot.

The ceiling on rooftop-level planning is that optimization within a single store’s constraints still leaves group-level capacity on the table. The floor rises when the group plans as a system.

The three capacity layers: bay, advisor, BDC

Fixed Ops capacity is not one number. It is three interdependent layers, each with different constraints and different levers.

Bay capacity is the physical constraint: how many vehicles the Fixed Ops department can work on at one time, given the number of bays, their configuration (oil change bays vs. full-service bays vs. alignment bays), and the mix of work being performed. Bay utilization above 90% for sustained periods indicates demand exceeding physical capacity. Below 70% indicates either demand shortfall or scheduling inefficiency.

Bay capacity is the hardest layer to change quickly — adding bays requires capital investment and permitting. But it is also the easiest to misread. A store reporting 85% bay utilization may have peak-day utilization of 98% (turning customers away on Fridays) and mid-week utilization of 72% (paying fixed costs for idle bays on Wednesdays). Average utilization masks the distribution, which is where the planning problem actually lives.

Advisor capacity is the workflow constraint: how many ROs an advisor can manage per day given their workload, the complexity of jobs on their board, and the administrative time required for each RO. Industry benchmarks suggest that well-supported service advisors can manage 18–22 ROs per day in a steady-state environment. Advisors managing significantly above 22 ROs per day show quality degradation — write-up errors, missed follow-up on parts delays, and reduced customer communication quality.

Advisor capacity is more flexible than bay capacity. Cross-training, scheduling adjustments, and redistribution of administrative tasks (status calls, parts follow-up, appointment confirmations) can increase effective advisor capacity without adding headcount. Administrative task redistribution to AI or BDC is one lever; see the Fixed Ops AI tools overview for how this fits into a broader capacity model.

BDC capacity is the communication constraint: how much inbound and outbound contact volume the Fixed Ops BDC team can handle during staffed hours. BDC capacity is the layer most directly tied to the scheduling funnel — a BDC at capacity during peak morning hours will miss inbound calls, delay appointment confirmations, and slow the reminder cadence that drives show rates. BDC capacity is also the layer most amenable to AI augmentation, where the team handles complex conversations while AI handles volume.

The three layers interact. A Fixed Ops operation can have adequate bay capacity but low advisor capacity — resulting in bays sitting idle because advisors cannot take more ROs. Or adequate bay and advisor capacity but a BDC bottleneck that limits appointment flow. Group-level planning requires visibility into all three layers across all rooftops, not just the P&L summary.

How to plan capacity at the group level

Group-level Fixed Ops capacity planning requires three things most groups have not built: a consistent measurement framework across rooftops, a shared view of utilization data, and a decision process for reallocation.

Consistent measurement framework — To plan across rooftops, you need the same metrics calculated the same way at every store. Bay utilization, advisor throughput, BDC contact-to-appointment rate, and no-show rate should be defined and measured identically across the group. Stores using different DMS configurations, different appointment scheduling tools, or different BDC reporting formats make group-level comparison impossible. Standardize measurement before attempting group-level planning.

Demand forecasting by rooftop — Fixed Ops demand is predictable in pattern if not in exact volume. Seasonal demand curves, day-of-week patterns, and the relationship between vehicle age in a given market area and maintenance demand are all forecastable with 12 months of historical data. A group with 8 rooftops should be forecasting Fixed Ops demand for each rooftop 4–8 weeks out and comparing that forecast against current booking pace to identify supply-demand imbalances before they become customer experience problems.

Capacity sharing protocols — When one rooftop is projected to be booked out during a peak period, the group’s response should be a defined protocol, not an ad hoc decision. That protocol includes: how customers are offered scheduling at a sister store, which advisor or BDC team handles the transfer contact, and how the appointment is tracked across stores for commission and performance reporting purposes.

A 6-rooftop Honda group in the Mid-Atlantic region built a capacity sharing protocol after discovering that their highest-volume store was turning away approximately 40 appointment requests per week during peak periods. Two nearby stores in the same group had available capacity. The protocol moved 25–30 appointments per week to sister stores with minimal customer resistance when the transfer was handled proactively at the time of first contact.

Reallocating across rooftops without triggering pushback

The political challenge of group-level Fixed Ops capacity planning is that it requires rooftop Fixed Ops Directors to accept customers booked at another store — and to participate in a group system that may benefit the group but create uncertainty about individual store metrics.

The resistance is predictable. Fixed Ops Directors who are measured on rooftop P&L have no incentive to send customers to a sister store. BDC teams measured on appointments set at their store have no incentive to book customers elsewhere.

Solving this requires measurement adjustment before process adjustment. If the group allocates appointment-transfer revenue and performance credit to the originating rooftop, the incentive structure supports the new protocol rather than fighting it. Some groups use a simple rule: the rooftop that originates the customer relationship retains the customer relationship metric (CSI attribution, recall completion credit) regardless of where the RO is written.

The second factor is communication framing. A Fixed Ops Director being asked to “send customers away” will resist. The same Fixed Ops Director being told “we are capturing 40 appointments per week that would otherwise go to a competitor” responds differently. The framing is accurate — the alternative to the sister-store referral is a customer calling a third-party service center or a competitor dealership, not a customer patiently waiting for the store to open a slot.

Measuring capacity utilization

Group-level capacity utilization metrics should be reported weekly and reviewed at a group operations level monthly. The metrics that matter most:

Bay utilization by day of week and time of day — not just overall utilization. Identify where the demand spikes and where the capacity is idle. A store averaging 80% bay utilization with a Friday peak of 97% has a structural problem that the average disguises.

Advisor throughput by advisor — not just by store. Advisors significantly above or below the store median indicate either a training opportunity or a workload distribution problem that is not visible in aggregate numbers.

BDC contact-to-appointment rate by hour — not just by day. Missed inbound contacts during the 7–9 AM rush are not visible in daily totals. Hourly BDC contact data reveals the specific time windows where BDC capacity is the binding constraint on appointment flow.

No-show rate by store and by booking channel — identifying which channels and which stores have elevated no-show rates narrows the reminder cadence problem to the specific layer that needs intervention. For more on this, see the detailed framework in our service lead conversion rate analysis.

How Numa solves this

Numa‘s AI Operating System gives group operations leadership and Fixed Ops Directors a shared view of inbound contact volume, appointment booking pace, and BDC throughput across rooftops — without requiring each rooftop to operate identically.

The platform handles BDC capacity at the layer where groups most commonly face constraints: after-hours and overflow inbound contacts that fall outside staffed BDC hours at individual rooftops. For a multi-store group, this means the BDC capacity constraint is addressed by AI handling volume — so the Fixed Ops team at each rooftop handles the conversations that require human judgment, not just the ones that happen to reach a live person.

Numa’s operator dashboard provides the group-level visibility into Fixed Ops communication and scheduling metrics that group operations directors need to plan capacity across rooftops rather than just report it.

Frequently Asked Questions

Q1: How do you plan Fixed Ops capacity across multiple stores?

Start with consistent measurement: the same bay utilization, advisor throughput, and BDC metrics calculated identically at every store. Then build a demand forecast for each rooftop 4–8 weeks out, compare against current booking pace, and create protocols for redistributing demand to available capacity before individual stores hit their ceiling. Group-level planning requires standardized data before it can drive meaningful decisions.

Q2: What’s the right utilization rate for service bays?

Target 78–85% bay utilization as a sustained average, with peak-day utilization managed below 95% to preserve scheduling flexibility for urgent and same-day work. Above 90% sustained average, you are likely turning away demand. Below 70%, either demand is insufficient for the market area or scheduling is not capturing available demand. Measure utilization by day of week, not just as an overall monthly average.

Q3: How does capacity planning interact with CSI?

Directly. Overcapacity conditions — where advisors are managing more ROs than their workflow can support — drive write-up quality down, communication frequency down, and customer wait time up. All three are CSI drivers. Sustainable capacity utilization (78–85% bay, 18–22 ROs per advisor) produces better CSI outcomes than operations running at peak utilization with lower quality. Capacity planning is a CSI management tool, not just a revenue management tool.

Q4: Should capacity decisions be centralized or local?

Both, with clear ownership boundaries. Bay configuration, advisor headcount decisions, and capital investment in Fixed Ops are legitimately group-level decisions — the group’s balance sheet supports them. Scheduling, day-to-day workload distribution, and advisor-customer matching are legitimately local decisions — the rooftop Fixed Ops Director has the operational visibility. The mistake is leaving demand forecasting and cross-rooftop reallocation to individual store discretion, because the incentive structure does not support voluntary customer sharing.

Q5: How does AI affect capacity planning?

AI primarily affects BDC capacity — the communication constraint layer — by handling inbound and outbound volume that would otherwise require staffed hours. For multi-store groups, AI BDC allows consistent after-hours coverage across all rooftops without proportional headcount cost. This is most valuable for groups where individual rooftops have variable BDC staffing quality. AI does not directly affect bay capacity or advisor throughput, but by removing the communication bottleneck, it improves the accuracy of demand data available for group-level capacity planning.