Auto Repair Shop SOPs: AI-Drafted Intake, Handover and Quality Steps

To write auto repair shop SOPs with AI, talk through one real job from key drop to handover, paste the rough notes into ChatGPT, Claude or Gemini, and ask for numbered steps, each with an owner, a trigger and evidence. Repeat for intake, quality check and handover, then test each draft with a technician on a live car.

Most downloadable SOP templates stop at a heading per step and an empty space where your shop's decisions belong. Those decisions are the real work, and AI cannot make them for you. What it does well is turn your spoken walkthrough into clean steps, ask the awkward questions you skipped, and format the result. What it must never supply are figures such as torque values, fluid specifications or service intervals. Those come from the manufacturer's service information, every time.

Follow me on Instagram@sagnikteaches

What a shop SOP has to decide that a template leaves blank

An SOP (standard operating procedure) is a one-page set of steps that lets a new starter do a job the way your best person does it. The six fields below separate a working procedure from a laminated wish. If your draft is missing one, the AI has filled the gap with something generic.

Connect on LinkedInSagnik Bhattacharya

Evidence and exceptions matter most in practice. Evidence lets you check a procedure was followed without standing over anyone. Exceptions stop people improvising badly at 5 pm on a Friday. When you prompt the AI, ask for all six by name and it will keep to them.

Subscribe on YouTube@sagnikteaches

Giving the AI your process: an interview, not a blank page

Typing "write me an intake SOP" gets you a plausible, generic procedure that belongs to nobody. Interview-style prompting extracts your process first. Open a chat with a free assistant (ChatGPT, Claude and Gemini all manage this; if you want the same shop rules applied each time, keep them in a Project in ChatGPT or Claude) and paste the prompt below. Keep customer names, phone numbers, number plates and vehicle identification numbers out of anything you type. Consumer chat plans carry a model-training switch in their privacy settings, so check it, and leave personal details out regardless.

You are helping a small auto repair shop write standard operating procedures (SOPs).
Interview me about ONE moment in the job: [vehicle intake / quality check / handover].
Rules:
1. Ask one question at a time and wait for my answer.
2. Cover: what triggers the step, who does it, what they check or say, what proves it was done,
   what happens when it cannot be done, and how long it should take.
3. Ask for one recent example of this step going wrong.
4. After 8 to 10 questions, stop and write "Ready to draft".
5. Never suggest technical values (torque, pressures, fluid types, intervals).
   If a step needs one, write [CHECK: manufacturer source].
6. Do not ask for customer names, phone numbers, plates or VINs.

Answer the way you would explain it to a new starter, in short sentences. Voice typing on a phone is fine. A typical exchange runs like this (illustrative):

AI: When a customer hands over the keys, what is the first thing the advisor does?
You: Opens a repair order and writes the number on a key tag.
AI: What happens if the customer is in a hurry and does not want a walk-round?
You: We still do the photos, they can wait at the counter. Photos take a minute.
AI: Can you give me one recent example where intake went wrong?
You: A bumper scuff nobody wrote down, and the customer said we did it.

That last answer is gold. A real failure tells the AI which step needs evidence and tells you which stop point to write. When the questions dry up, send the drafting prompt.

Using only what I told you above, write the SOP in this layout:
Title / Purpose (one sentence) / Owner (a role) / Trigger / Target time /
Steps (table: number, who, action, evidence) / Stop points (what to do when a step
cannot be done, and who decides) / Records kept / Version and review date.
Each step is one action starting with a verb. Maximum 12 steps.
Mark anything you assumed with [ASSUMED] so I can confirm or delete it.
Do not add steps I did not describe.

The [ASSUMED] marker is the most useful line in that prompt. AI drafts add steps that sound sensible and that nobody in your shop performs, and a procedure full of steps people skip teaches them to skip the rest. Budget roughly 90 minutes per SOP (my estimate): 20 minutes talking, 15 prompting, 25 correcting, and 30 testing on the floor. The floor test is the one people skip.

SOP one: vehicle intake, from rough notes to the version on the wall

This example comes from a four-bay independent shop with one advisor (illustrative throughout). The owner's raw notes took ten minutes to type:

Customer comes in, we get the keys, write down what's wrong, quick look round the car for dents, mileage, tell them we'll call with a price before doing anything, they sign, keys on the board.

The AI's first draft ran to 14 steps and had three problems, all typical.

• It invented equipment. Step 9 said the customer signs on a signature pad. The shop has a printed repair order and a pen. The step became "customer signs the printed repair order".
• It added a step nobody does. "Verify the vehicle identification number against the registration document" sounded professional, but no one in the shop had ever done it. It was deleted, because one fictional step makes people doubt the real ones.
• It missed the owner's main worry. The notes said "a price before doing anything", but the draft never recorded an approved amount. Step 8 now writes the approved amount on the repair order, and nothing above it happens without a recorded yes.

After the corrections and a floor test with the advisor, the intake SOP looked like this. It takes about eight minutes at the counter, plus under two for photos.

Stop points for intake

If the customer will not sign, diagnosis only: the advisor phones the owner before any other work. If a car arrives through the key drop, steps 1 to 5 are completed first thing the next morning before the car moves, and the photos are taken at drop-off regardless. If the customer declines photos, the RO says "customer declined", and the advisor initials it. The complaint wording in step 3 is the part that most improves diagnosis, and it has its own tutorial on capturing the complaint clearly with an intake form.

Photo steps: what to shoot, when, and where the files live

Photos are the cheapest evidence a shop can collect, and the part of an SOP most likely to be quietly dropped. Keep the list short enough to take in under two minutes, name the files so they sort themselves, and make the photo step something the repair order cannot move past without.

A naming pattern such as RO1042-intake-dash.jpg means a search by repair order number finds everything. Take photos on a shop phone or tablet and upload them straight to the repair order or one shared folder per job, so nothing sits on personal phones. Treat the folders as customer records: number plates and vehicle identification numbers can point to an owner, and how long you keep photos is a question for your adviser, not the AI. Do not photograph customers or their belongings.

SOP two: the quality check, and the figure the AI made up

The second procedure is the one that protects the shop. Its owner is a second person: never the technician who did the work. In a three-person shop that can be the advisor or the owner after a short briefing. The AI's first draft contained a line telling the checker to tighten every wheel nut to one torque figure, as though it applied to every car. The owner spotted it because it was a number, and the rule that came out of it is the red-pen rule: any figure in an SOP that is not your own policy gets a named source or gets deleted. The final line reads "to the manufacturer's figure, from the service information for this vehicle".

The version the shop adopted takes around twelve minutes plus the road test:

1. Trigger. The technician marks the job complete and hands the repair order to the checker. Evidence: status "ready for check".
2. Match the work to the paperwork. Compare finished work with the approved lines, one by one. Anything extra needs a recorded approval; anything not done is marked "deferred" with the reason.
3. Look at the work area. Fasteners, clips, undertrays, connectors and caps are in place; no tools or rags left behind; no wet patches. Photograph it.
4. Check fluids and pressures against the right source. Use the manufacturer's information for this vehicle. Record "topped up" or "correct" per item.
5. Wheels. If any wheel came off, confirm nuts were tightened with a calibrated torque wrench to the manufacturer's figure, and tick it.
6. Start the engine and compare the dash with the intake photo. No warning light that was not there at arrival. If fault codes were read or cleared, the RO shows before and after.
7. Road test. Follow the shop's standard route, covering the original complaint conditions. Note the starting and finishing mileage; the difference should match the route.
8. Re-create the complaint. If it cannot be reproduced, write how you know it is fixed.
9. Leave the car as you found it. Seat and mirrors back where they were, floor mats in place, steering wheel and handles clean.
10. Sign off or fail. Initials and time if it passes. If it fails, write the reason in one line and return it to the technician. The check restarts at step 2.

Step 6 is the quiet winner. Because the intake dash photo exists, a "that light was not on before" argument stops being an argument. Before the SOP existed, the shop in this illustration had no way to settle one. In the first fortnight the checker failed 4 of 30 jobs: a missing undertray clip, an unrecorded extra repair, a paperwork mismatch, and a warning light that was not in the intake photo. Four fails out of 30 is not a verdict on the technicians. It is the check doing what it is for.

SOP three: handover at the counter, as a script

The handover is where good work can still end in a dispute, so this SOP is written as a short script. The advisor owns it, and it starts when the quality check has passed and the customer arrives.

1. Before the customer arrives. Invoice matched to the authorised work; quality check initialled; keys and old parts at the counter.
2. Hand keys only to the right person. The name on the repair order, or someone they have told you about.
3. Explain in three sentences. What was wrong, what was done, what to watch. Use the handover note below.
4. Show the evidence. Photos of the failed part on the phone or tablet; old parts if requested at intake.
5. Walk through the invoice. Authorised work, anything extra with the recorded approval, deferred work and the date you recommend doing it.
6. Walk to the car. Show the area worked on, confirm no warning lights, confirm mileage, and use the intake photos if anyone disputes a mark.
7. Take payment and give the invoice.
8. Ask one question before they leave: "Is there anything about the car that does not seem right?" Write the answer on the repair order.
9. Close the job. Set a follow-up for two days later and archive the photos.

Stop point: if the customer disputes something, the advisor does not argue at the counter. Note it, offer to re-inspect, and hand the decision to the owner. The handover note in step 3 is where AI earns its keep, because technicians write notes for themselves, not for customers. Here is a prompt with an illustrative result.

Turn these technician notes into three plain sentences for the customer: what we found,
what we did, what to keep an eye on. No jargon. Do not say the car is "safe", "perfect"
or "as new". Do not mention anything not in the notes.

Notes: front pads at wear limit, discs scored, replaced pads and discs both sides,
bled system, wheels torqued, road test ok, rear pads about half life, recheck at next service.

AI output (illustrative): We found the front brake pads worn to their limit and the discs scored, so we replaced the pads and discs on both sides and bled the brake system. We tightened the wheels, then road tested the car and the brakes performed as expected. The rear pads have about half their life left, so we recommend checking them at your next service.

It stayed inside the notes and avoided "safe", but "performed as expected" is still a claim the notes did not make. The notes said "road test ok", so the shop edited the sentence to "road tested the car with no issues found". That small edit is the habit to build: every AI sentence has to trace back to something a technician wrote. For updates sent while the car is still in the bay, see how garages use AI to send repair updates.

Training a new technician from the three SOPs

Once the SOPs are tested on real jobs, they become the skeleton of a first-week training plan. The new person does not read three documents and hope. They watch, do, and teach back, with the SOP in their hand each time.

AI helps with two parts of that plan. The first is a quick scenario quiz generated from the SOP itself. Paste the finished SOP and ask for eight questions that each test a step through a situation, not a definition, with a model answer and the SOP step it comes from. A typical question (illustrative): "The customer says the brakes only squeal when cold and wants to leave straight away. What do you record, and what do you still do before they go?" The model answer points to steps 3, 6 and 8. The second use is a role-play partner:

Play a customer arriving at an auto repair shop in a hurry, who does not want a walk-round.
I am the service advisor. Stay in character for six exchanges. Then step out of character and
tell me which steps of the intake SOP below I followed, skipped or handled well.
[paste SOP]

Ten minutes of that is a better rehearsal than reading, and the feedback is tied to the real steps. Treat the quiz as a conversation starter, not a test to pass; the sign-off still needs a human watching a real job. For turning SOPs into short modules, AI in employee training goes further.

Checking use after two weeks, then feeding in the comebacks

A written SOP and a followed SOP are different things. After two weeks, pull ten closed repair orders and count what the evidence column promises. Illustratively, 7 of 10 had all the intake photos and 9 of 10 had the approved amount. The temptation is to remind people harder. The better response is to ask why. Here the missing photo was nearly always the dash, because the ignition has to be on and the advisor had already gone back inside to finish the paperwork. Version 1.1 moved the photos into the walk-round, when the advisor is at the car anyway. The next fortnight it was 9 of 10.

The second feed is every comeback, which is a job that returns with the same complaint. Spend ten minutes per comeback with the AI. Remove names, then paste the notes and ask where the SOPs failed.

Here are anonymised notes from a comeback: [complaint, what we did, what the customer reported].
Here are our three SOPs: [paste]. Which step failed or was missing? Propose one specific change
to one SOP, in the same table layout, and say what evidence would show it worked.
Do not add steps unrelated to this comeback.

The AI proposes; you decide. A good outcome is one small edit, a new version date and a line in the change log. A bad outcome is five new steps, which is the AI covering every possibility. Reject that, and keep the SOPs short enough to be read.

Numbers and claims to keep out of a repair SOP

The red-pen rule from the quality check applies across all three procedures. Before anything goes on the wall, strike through the following, or give it a source.

• Technical values. Torque, pressures, fluid grades, intervals, capacities. These belong to the manufacturer's information for the specific vehicle, and a tool that reads fault codes does not change that; AI for fault codes and manuals explains where its limits sit.
• Safety promises to customers. "Safe to drive", "as good as new", "guaranteed". Describe the work and the checks done instead.
• Warranty terms. Quote your actual written terms, never an AI paraphrase.
• Legal statements. What you must tell customers about estimates, authorisation or records varies, so check with your adviser and write the result in your own words.
• Prices. They belong in the estimate, which has its own approach in building an estimate template with ChatGPT.

Once the three SOPs have survived a month on real jobs, the same method extends to the next routines: parts ordering, courtesy cars, warranty claims. The general technique is in how to write SOPs with AI; the shop-specific work, deciding where evidence lives and who signs, is what you have just done.

Questions owners ask before writing shop SOPs

Can AI supply torque figures or service intervals for my SOPs?

No. It cannot verify them, and a confident wrong number is worse than a blank. Tell the AI to write [CHECK: manufacturer source] wherever a figure would be needed, and delete that marker only when someone has looked the value up in the service information for the car on the ramp.

How long should a shop SOP be?

One page. If a procedure runs past about a dozen steps, split it by moment, such as intake, quality check and handover, instead of shrinking the type. A new starter should be able to follow it standing at the counter or the bay, so each step needs one action, one owner and one piece of evidence.

Where should the SOPs live so technicians actually use them?

Print a copy where the step happens: intake at the counter, quality check at the checker's bench, handover beside the key board. Keep the master in one shared folder or your shop software with a version date, and remove old copies whenever you update. If people have to search for it, it will not be used.

Can I use my shop management software's checklists instead of a document?

Yes, provided they hold the same decisions: owner, evidence and stop points. The software gives you timestamps and photo storage, while AI helps with the wording and the training material. Draft the SOP first, then copy the steps into the software's inspection or checklist feature so the two never disagree.

Further reads

• Should a Small Auto Repair Shop Use AI? A Decision Checklist — Decide whether AI belongs in your shop before you build on it.
• AI Service Reminders That Bring Garage Customers Back — Bring customers back after the handover, using the same consent notes.
• Best AI for Auto Mechanics: Estimates, Parts Research and Messages — Other jobs in the shop where AI saves real time.
• How to Create SOPs From Screen Recordings With AI — Capture a screen-based step, such as the estimate, by recording it.
• AI Receptionist for Mechanics: What It Costs Against Missed Calls — Fix the phone side of intake as well.
• Body Shop Quality Control Checklist: Post-Repair Checks With AI — Filled-in post-repair checks for panels, paint, electrics and photos, with sign-off rules and prompts that turn your own comebacks into a checklist.
• AI for Body Shops: Insurer Paperwork, Supplements and Job Notes — Where AI helps a collision repair shop with paperwork: photo captions, supplement requests, daily job notes and repair summaries, and what a person must sign.
• ChatGPT for Car Mechanics: Fault-Finding Help and Where It Stops — Where a garage can use ChatGPT for fault-finding triage and customer wording, six wrong-answer patterns to expect, and a one-page shop rule.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: no vendor facts are used; every figure in the examples is illustrative. Vehicle specifications must always come from the manufacturer's own service information.