Transformation Advisory & Execution · Viewpoint
The dealer is where variance is measured. It is not always where it is caused.
A network scorecard reveals where performance differs. Management still has to identify the cause, find who controls it, and test whether an intervention works.
Contents
Dealer standards define the expected process. They do not explain why comparable dealers perform differently, which organisation controls the cause or whether an intervention worked. Because performance is measured at the dealership, upstream constraints can be recorded as dealer underperformance.
Dealer networks are measured constantly. Standards audits, scorecards, field visits, sales targets, customer-experience measures and increasingly detailed dashboards all show where performance differs. More measurement does not by itself produce a better management decision.
The missing step can be diagnosis. A dealership may be below the network average in lead conversion, service retention or stock turns. Before prescribing training or another process standard, the importer has to establish whether the difference is driven by customer demand, product allocation, local capability, upstream policy, system timing or the way the measure is calculated.
Those causes require different owners and different actions. Consistent standards are valuable, but compliance and performance answer different questions.
Do not prescribe a dealer-level intervention until you know whether the constraint sits at the dealership, the importer, the OEM, a shared system or in the measure itself.
Some gaps need correction, not diagnosis
Some requirements are non-negotiable. A failed safety control, legal obligation, authorised-repair condition or customer-data rule requires prompt correction and verification. The cause can still be investigated, but the breach must not be treated as an acceptable performance variation. The diagnostic method below concerns differences in commercial and operational performance, including where a dealer follows the documented standard yet underperforms.
Standards describe the expected process. But they dont heal and Variances are still important.
A standard can specify how quickly a lead should be handled, which steps must occur during service reception or how an ageing vehicle is escalated. An audit can show whether the steps were followed. Neither establishes that non-compliance caused a commercial outcome.
A dealer may follow the enquiry process correctly but receive a very different mix of leads from another site. A workshop may meet reception standards but struggle to retain customers because parts are unavailable or technician capacity is constrained. A dealer may have unusually old stock because allocations and local demand diverged months before the field visit.
What explains the difference, and which part of the operating system can change it?
First, compare like with like
A raw network ranking can confuse opportunity with execution. Territory potential, customer mix, model availability, sales channel, workshop throughput and local competition all affect outcomes. Comparison is useful only when those differences are visible and the underlying metric has one definition across the network.
This does not require an elaborate statistical model for every field decision. It requires discipline about the denominator, the comparison group and the time period. A lead-to-sale rate is hard to interpret if one site counts all digital enquiries and another counts only qualified customer conversations. Service retention can mislead if the eligible vehicle population, vehicle age or fleet mix differs materially.
Start with the spread of results among genuinely comparable outlets rather than the national average. Where a fair comparison is impossible, say so rather than presenting a ranking as evidence of management failure.
Then separate the causes into five layers
A practical first diagnosis should test five possible sources of variance:
Market and demand. Territory potential, customer composition, product-market fit, competitor activity and local demand patterns.
Commercial design. Stock allocation, price and incentive mechanics, lead routing, financial offers and targets. These are set above the dealership, often months before the result is measured.
Dealer capability and execution. Staffing, leadership, appointment handling, selling or service routines, and the quality of local follow-through.
Shared operating infrastructure. DMS and CRM interfaces, parts availability, warranty authorisation, customer identity and escalations between organisations.
Measurement. Inconsistent definitions, incomplete records, lagging data, attribution errors or indicators that reward the wrong behaviour.
The five layers are a working diagnostic, not a claim that every problem has one clean root cause. Layers interact. The purpose is to avoid prescribing a dealership action for a constraint the dealership cannot control.
A variance hypothesis is more useful than an action list
Consider an illustrative example. Two otherwise comparable service outlets have materially different rates of completing promised work on time. The standard response is more service-adviser training. A stronger first step is to test the mechanism: do delays begin in appointment booking, work authorisation, technician allocation, parts replenishment or customer approval?
Each explanation points to different evidence and a different owner. If work waits for centrally controlled warranty decisions, the importer or OEM must change the escalation route. If workshop jobs consistently exceed planned capacity, the local operator may need a scheduling or staffing intervention. If the recorded completion metric mixes different types of job, the first fix is the definition.
The field visit should end with a hypothesis that could be proved wrong, the evidence needed to test it, one accountable intervention owner and the expected sign of improvement. Ten activities with no causal explanation do not yet make a performance plan.
Do not copy the top dealer until the mechanism is visible
Rankings are good at finding questions and poor at giving transfer instructions. The top site may benefit from territory, product mix, a legacy customer base, spare capacity or one individual whose practice is not embedded in the business.
Before rolling a practice out, establish which behaviour changed which result, under which conditions, and whether it holds when the person, period or site changes. Transfer then means changing a routine, role, tool or decision rule. Circulating a best-practice presentation rarely changes any of them.
Make the intervention part of the management rhythm
The next step is a routine that connects diagnosis to action. A useful dealer-performance review can be organised around five questions:
What is the variance? Identify the outcome, the comparable group, the time period and any data-quality limitation.
What are the leading explanations? Test market, local, upstream and measurement causes before selecting an intervention.
Who can change it? Assign the issue to the dealer, importer, OEM or shared process owner with actual decision rights.
What change will be tested? Specify one intervention, the operating behaviour it should change and a realistic test window.
What would disprove the hypothesis? Name the leading operational measure and the downstream outcome, and review both rather than marking the action complete.
This changes the job of network field teams. Their value moves from checking compliance and distributing a centrally prepared improvement list to distinguishing causes, securing cross-functional decisions and testing whether interventions travel from one outlet to another. That requires comparable data before the visit, and the authority to leave a site without prescribing a local action when the evidence points upstream.
The importer cannot diagnose away its own responsibility
The most expensive misdiagnosis is classifying every gap as dealer execution because that is where it is measured. The point of observation and the point of causation are often different. Allocation, targets, lead routing, warranty decisions and system interfaces are set above the dealer, and their effects surface in the dealer's numbers.
at.Pointe's published importer-transformation case (at.Pointe engagement, anonymised) describes this pattern. Importer, market and retail processes had grown separately, management data could not always be trusted enough to drive action, and systems did not connect cleanly. The redesign introduced common KPI definitions so that dealer and importer teams worked from a shared performance logic, with escalation routines designed around it. The case shows that upstream operating design shapes dealer results. It does not show that any particular diagnostic method improves profit.
An effective network-performance system therefore needs an escalation route for causes that require importer or OEM changes. Without one, field teams can identify a problem accurately and still have no authority to solve it.
The management decision
Standards remain necessary. They set minimum operating expectations, protect the customer promise and make processes repeatable. The next improvement may not be a thicker standards manual or another network dashboard.
It is more likely to be a better way to compare outlets, investigate why they differ and direct management effort to the organisation that can change the outcome. That is how a network moves from seeing variance to managing it.
Related at.Pointe reading
- Dealer problems often start at the importerAn anonymised at.Pointe engagement examining importer operating structures behind recurring dealer symptoms.
- Regional autonomy does not remove regional managementHow regional oversight and clear decision rights can support local operating accountability.
- Importer & Distribution TransformationRelated capability and case context from at.Pointe.
Evidence boundary
This viewpoint builds on the published anonymised at.Pointe importer-transformation case, which describes fragmented importer, market and retail processes, shared performance logic and a transformation roadmap. The five-layer diagnostic, variance-hypothesis method and proposed management review are at.Pointe operating propositions rather than independently validated outcome measures.
No quantified improvements, causal profitability results or client-identifying details are claimed. Examples are illustrative, not descriptions of specific dealerships.
