CEO Executive AssistantStandard operating procedures are the infrastructure of operational consistency. For automotive CEOs managing one location or a group of fifteen, SOPs are what allow your business to perform at a consistent level regardless of who shows up to work on a given day, which manager is covering which store, or what market conditions you are navigating.
Most dealership groups have some SOPs in place. Very few have a complete, current, and actively enforced SOP library that covers every critical operational function. The gap between these two states is one of the primary drivers of performance variation across stores and one of the most addressable operational opportunities available to dealership CEOs.
What Makes an SOP Actually Useful
Before building or auditing your SOP library, it is worth being specific about what makes an SOP useful versus a document that exists but does not improve operations.
An effective SOP has five characteristics:
Specificity. Vague direction creates vague execution. An SOP that says “handle customer complaints professionally” is not an SOP. An effective SOP specifies exactly what to do, in what order, with what tools, to what standard.
Executability. The person responsible for following the SOP should be able to execute it without needing additional information or judgment beyond what the document provides. If every step requires interpretation, the SOP is not complete.
Measurability. Every SOP should describe what success looks like. This allows managers to verify compliance and gives employees a clear performance target.
Accessibility. SOPs that exist in a filing cabinet or a folder structure no one knows about are not useful. SOPs need to be findable and readable at the moment they are needed.
Currency. An SOP that does not reflect how your operations actually work today is worse than no SOP at all. It creates confusion and undermines the credibility of your documentation system.
The Core SOP Library for Automotive Dealerships
A complete SOP library for a dealership group covers every major operational function. Below are the domains that require SOP coverage, with specific examples of the critical procedures within each.
Sales Operations SOPs
Internet lead response protocol. Defines the steps, timing standards, and content requirements for responding to every internet lead source. Should specify maximum response time (typically under 10 minutes during business hours), required contact methods (call, email, text), and escalation procedures if initial contact fails.
Vehicle appraisal process. Defines the step-by-step procedure for appraising a trade vehicle, including who participates, what tools are used (such as vAuto or similar), what information must be gathered, and how the appraisal is presented to the customer.
Desking process. Specifies how deals are structured, presented, and negotiated, including what gross profit floors are in place, when management needs to be involved, and how the deal transitions to F&I.
Delivery process. Covers every step of vehicle delivery from paperwork completion through feature demonstration, customer documentation, and survey solicitation. Poor delivery processes are among the most common drivers of low CSI scores.
Customer follow-up cadence. Defines the post-sale and post-service follow-up process: when to contact, through what channel, with what content, and how to document the outreach in the CRM.
Fixed Operations SOPs
Service appointment scheduling. Defines how appointments are booked, what information is gathered, how the DMS is updated, and how appointment confirmations are communicated to customers.
Repair order write-up. Step-by-step process for advisor write-up, including required customer information, vehicle inspection protocol, initial documentation of customer concern, and DMS entry requirements.
Multi-point inspection (MPI) process. Defines the inspection procedure, documentation format, the process for presenting recommendations to the customer, and how declined services are tracked for future follow-up.
Warranty claim documentation. The specific documentation requirements for each OEM’s warranty system. This is one of the highest-risk SOP areas from a compliance and chargeback perspective.
Technician clock-in and time management. Defines how technicians log time, what constitutes billable vs. non-billable time, and how time-related discrepancies are handled.
Parts ordering and receiving. Covers the purchase order process, receiving inspection, inventory entry, and discrepancy documentation procedures.
F&I Operations SOPs
Menu presentation process. This is the single most critical F&I SOP from both a revenue and compliance perspective. Every deal should go through a documented menu presentation, and the SOP should specify exactly how that presentation is conducted and recorded.
Customer credit application handling. Defines how credit applications are received, processed, submitted to lenders, and stored in compliance with applicable privacy and data security requirements.
Deal jacket documentation. Specifies every document required in a complete deal jacket, in what order, and how long deal jackets must be retained.
Adverse action notification. The process for communicating to customers when their credit application is declined, including timing, method, and documentation requirements.
Compliance review process. The procedure for self-auditing F&I deals for compliance before month-end close, including who conducts the review and what is done when issues are identified.
Administrative and Compliance SOPs
Cash handling and reconciliation. Covers who can accept cash, how cash is counted and verified, how deposits are made, and how discrepancies are documented and investigated.
Title and licensing process. State-specific procedures for processing title and registration, which typically have hard deadlines that create significant risk if the process breaks down.
OEM compliance calendar management. Defines who is responsible for each OEM compliance requirement, the deadline, the documentation required, and the process for verifying completion.
Employee onboarding process. Covers every step from offer acceptance through completion of required training, system access provisioning, and 30/60/90-day check-in cadence.
Incident and complaint escalation. Defines what constitutes an escalation-worthy incident, who must be notified, in what timeframe, and how the incident is documented.
Building SOPs That Get Followed
Writing SOPs is the straightforward part. The harder challenge is building an organizational culture where SOPs are actually followed consistently. This requires deliberate management effort.
Make SOPs Accessible
Your SOP library should be organized, searchable, and available on every device employees use for work. Cloud-based document management tools like Microsoft SharePoint, Google Drive, or dealership-specific platforms like Dealertrack DMS integrations work well. The critical factor is that the right SOP is findable in under 30 seconds by any employee who needs it.
Train to the SOP, Not Around It
When training new employees, the SOP should be the training document. If trainers are using the SOP as a reference while doing it “their way,” the SOP is decorative. Build your training programs around your documented SOPs and use role-playing and observation to verify that training produces SOP-compliant execution.
Audit for Compliance
SOPs are only as valuable as their enforcement. Build regular audits into your operational rhythm: mystery shops for sales and service, deal jacket audits for F&I, cash handling spot checks, and process observation walkthroughs.
The purpose of audits is not punishment. It is identification of where the SOP is not working as designed, either because the process is flawed or because execution is inconsistent. Both are fixable with different interventions.
Update SOPs When Processes Change
Nothing erodes trust in an SOP system faster than SOPs that do not reflect current practice. Assign SOP ownership to specific roles and build SOP review into your quarterly operational cadence. When a significant process change is made, the SOP update should happen within 30 days, not eventually.
See our CEO business operations checklist for how SOPs fit into your monthly review cadence. See our dealership operations management guide for the broader operational framework.
Prioritizing SOPs in Multi-Store Groups
For dealership groups with multiple locations, SOP strategy requires an additional layer of thinking: which SOPs should be uniform across all stores and which should allow for local variation.
The rule of thumb is that SOPs covering compliance, financial controls, and customer-facing standards should be uniform across all stores. These are areas where inconsistency creates either regulatory risk or brand experience degradation.
SOPs covering sales tactics, service advisor scripts, and inventory pricing strategy may benefit from local market adaptation within defined guardrails. A store in a rural market operates differently from an urban store in a high-competition metro, and forcing identical tactics onto different market contexts can limit performance rather than improve it.
The practical approach is a two-tier SOP structure:
Group-wide mandatory SOPs: These apply to all stores, are version-controlled at the group level, and are not subject to local modification. F&I compliance, cash handling, OEM reporting, title processing, and data security fall into this category.
Location-adapted SOPs with guardrails: These are templates that stores can adapt within defined parameters. The group specifies the non-negotiable elements and allows stores to customize the execution details for their market.
Connecting SOPs to Compensation and Accountability
SOPs that are not tied to any accountability mechanism tend to atrophy. The most effective way to sustain SOP compliance is to connect it to the metrics that drive compensation.
If your sales advisors are compensated in part on customer satisfaction scores, and your delivery SOP is designed to produce high satisfaction scores, the incentive structure reinforces the desired behavior. If your service advisors are compensated on total service revenue, and your MPI SOP is designed to surface legitimate service recommendations, the compensation structure supports SOP execution.
Build your SOP library with this alignment in mind. For every SOP, ask: what is the measurable outcome this process is designed to produce, and is that outcome reflected in how we measure and reward performance?
Common SOP Failures and How to Prevent Them
The most common reasons SOP programs fail in dealership groups:
Too much at once. Groups that try to build and implement a complete SOP library simultaneously typically see adoption collapse under the weight of change. Build your SOP library incrementally, starting with the highest-risk and highest-impact areas.
No ownership. SOPs that no one owns get stale. Assign each SOP (or each domain) to a specific role with defined review responsibility.
Compliance without consequences. If deviation from SOPs never produces any consequence, the implied message is that SOPs are optional. Build a clear response protocol for SOP violations that is consistent and proportionate.
Management inconsistency. If GMs and department managers do not personally follow the SOPs they are supposed to enforce, front-line employees will not either. Leadership behavior is the most powerful signal in any organizational culture.
Conclusion
Standard operating procedures are among the most valuable and most underinvested assets in most dealership groups. When built correctly and enforced consistently, they are the mechanism through which operational excellence becomes a group-wide standard rather than a characteristic of individual high-performers. For automotive CEOs, the SOP library is not an administrative project. It is a competitive advantage that compounds over time as your organization internalizes the standards and your operations become genuinely, durably consistent.
Related Reading
For further context, explore Standard Operating Procedures: Insurance Company CEO Guide and Automation Tools for Insurance Company CEO Operations.