If the process changes depending on who is working that day, you do not really have a process yet. You have tribal knowledge.
A lot of repair shops have good people and years of experience, but the operation still lives in somebody’s head. The advisor knows how they like to build an estimate. The manager knows how they handle a comeback. The owner knows what should happen when a customer declines work. Then one person is out, leaves the company, or moves to another location and the process changes overnight.
That is why SOPs matter. But the goal is not to create a giant manual nobody reads. The goal is to take the repeatable parts of the business and make them clear enough that people can be trained, managers can inspect execution, and the owner can know what good looks like without standing over everybody.
Start With the Processes That Affect Customers and Profit
Do not try to document every possible situation first. Start with the workflows that repeat every day and have the biggest impact on customer experience, gross profit, productivity, and consistency.
- Appointment preparation
- Customer greeting and walk-around
- Vehicle check-in
- Digital Vehicle Inspection
- Estimate building
- Preventive maintenance review
- Advisor inspection preparation
- Customer presentation
- Approvals and declines
- Parts ordering and returns
- Technician dispatch and workflow
- Quality control
- Vehicle delivery
- Declined work follow-up
- Manager repair-order review
Write the Process From the Actual Work
The best SOP usually comes from watching the job happen. Sit with the employee who performs it well. Follow the process from start to finish. Ask what decision they are making at each step, what information they need, what can go wrong, and what the next person in the workflow needs from them.
Then compare that to what the owner believes should happen. That gap is often where the real work starts.
Define the Trigger, Owner, Steps, and Finish Line
Every useful SOP should answer four simple questions.
- What triggers this process?
- Who owns it?
- What steps have to happen?
- How do we know the process is complete?
If nobody owns the process, people assume somebody else will handle it. If there is no clear finish line, the manager cannot verify whether it was completed correctly.
Keep the Language Simple Enough to Use at the Counter
An SOP should not sound like a legal document. Write it in the language your team actually uses. If an advisor has to stop and interpret a paragraph while a customer is waiting, the SOP is too complicated.
The best process is usually the clearest process the team can repeat under pressure.
Build the Handoff Between Technician and Advisor
Many shop problems do not happen because one person failed. They happen during a handoff. The technician finds the concern, but it never makes it to the estimate. The estimate is complete, but the inspection is not prepared for the customer. The advisor presents the work, but the decline is never documented for follow-up.
A strong SOP should define what the technician owes the advisor, what the advisor owes the customer, and what the manager verifies.
Use the DVI Process as an Example
- Technician completes the inspection according to shop standard
- Useful photos and measurements are included
- Good and bad vehicle conditions are documented
- Legitimate findings are identified clearly
- Required findings reach the estimate
- Advisor reviews and edits the inspection for customer-friendly language
- Edit Pencil is used where appropriate to make pictures easy to understand
- Available service history is reviewed where appropriate
- The inspection is sent at the right point in the process
- The complete recommendation is presented
- Approvals and declines are documented
Notice that the process does not stop when the technician clicks complete. The SOP follows the repair order all the way through customer communication.
Do Not Leave Preventive Maintenance to Memory
If your shop recommends preventive maintenance, define how the advisor identifies it. Mileage, vehicle condition, manufacturer recommendations, known history, and CARFAX or another available service history source may all matter. The point is consistency, not recommending the same service to every vehicle.
Turn Repeated Owner Decisions Into Standards
Every time the same question comes back to the owner, ask whether the business needs a clearer rule. How much authority does the manager have on a customer adjustment? When should a vehicle be rechecked? Who approves overtime? When does the owner need to be involved?
The owner should not have to keep making the same decision forever. Good SOPs turn repeated decisions into a system.
Train the SOP With Real Examples
Do not hand an employee a document and call that training. Walk through actual repair orders, actual inspections, actual customer conversations, and actual workflow examples. Let the employee practice the process and explain it back.
If the team can only repeat the words but cannot perform the process during a busy day, the training is not finished.
Managers Have to Inspect the Process
Once the standard exists, the manager needs a simple way to verify execution. That may mean reviewing a defined number of repair orders, checking DVI quality, confirming estimate completeness, watching workflow, or reviewing approvals and declines.
You cannot coach a process you never inspect.
Connect SOPs to a Scorecard
The SOP explains what should happen. The KPI helps show whether the process is producing the expected result.
- DVI completion and quality
- Estimate completeness
- ARO
- Technician productivity
- Effective labor rate
- Payroll percentage
- Approvals and declines
- Customer follow-up completion
If the KPI moves the wrong direction, inspect the related process before assuming the employee simply needs to work harder.
Make the SOP Easy to Find
A process nobody can find during the workday will not help much. Store SOPs where the team already works, organize them by role or workflow, use short checklists where appropriate, and keep the current version obvious.
Version Control Matters
Processes change. Software changes. Pricing changes. Roles change. When the SOP is updated, the old version should not keep circulating. Assign ownership for maintaining each important process and review the highest-impact SOPs on a regular cadence.
Build SOPs That Can Travel to the Next Store
For a multi-location owner, an SOP becomes even more valuable because it creates a common operating language. The customer experience, DVI standard, estimate process, manager review, and training method should not have to be reinvented at every location.
Your first store becomes much easier to duplicate when the things that make it work are documented, trainable, and verifiable.
Ask the Opening Question Again
If the process changes depending on who is working that day, do you really have a process? Or are your employees carrying the business around in their heads?
The goal is not to create more paperwork. The goal is to make the business less dependent on memory, personality, and owner involvement by turning the best way you know how to operate into something the team can repeat.