You know that thing where a customer calls and asks about their repair, and the only person who knows the answer is you? Or when a new tech starts and you spend two weeks hovering over their shoulder because nothing is written down?

That's a shop without SOPs. And it's a shop that can't grow.

Standard operating procedures sound corporate and boring. They're not. They're the difference between a business that depends on you for every decision and one that runs when you take a week off.

What SOPs Actually Are (and Aren't)

An SOP is just a written answer to "how do we do this?" It's not a 40-page manual nobody reads. It's a clear, step-by-step process that any trained employee can follow to get a consistent result.

Good SOP: "When a customer drops off a device, do these 7 things in this order."

Bad SOP: A 3,000-word essay on the philosophy of customer intake.

Keep them short. Keep them specific. If your SOP takes longer to read than the task takes to do, it's too long.

The 5 SOPs Every Repair Shop Needs First

Don't try to document everything at once. Start with the processes that cause the most confusion, mistakes, or customer complaints.

1. Device Intake

This is where most shops lose money — through inconsistency at the front counter. One tech checks for physical damage, another doesn't. One asks about the passcode, another forgets. Then you're eating the cost of a cracked screen the customer swears "was already there."

Your intake SOP should cover:

Greeting and initial triage (what's wrong, when did it start)
Physical inspection checklist (document existing damage with photos)
Collecting customer info and contact preferences
Getting device credentials (passcodes, passwords, backup preferences)
Setting expectations on timeline and cost
Creating the ticket in your system
Handing the customer a receipt or sending a confirmation

Every device. Every time. No exceptions.

2. Diagnosis and Repair

This varies by device type, but the framework is universal:

Diagnose before quoting. Don't guess at the problem or the price.
Document findings in the ticket before starting work.
Get approval for any cost beyond the original estimate.
Test after repair — run through a standard checklist before marking complete.
Note what was done so the next tech doesn't have to reverse-engineer your work.

The goal isn't to tell experienced techs how to solder. It's to make sure the process around the repair is consistent — approvals, documentation, testing, communication.

3. Customer Communication

When does the customer hear from you? Most shops wing this, and customers fill the silence with anxiety.

Define the touchpoints:

Drop-off: Confirmation with estimated timeline
Diagnosis complete: What we found, what it'll cost, approval request
Repair in progress: Optional update for multi-day repairs
Ready for pickup: Notification with hours and payment info
Post-pickup: Follow-up (24–48 hours) to confirm everything's working

Automate what you can. But even manual communication works if it's consistent. The customer should never have to wonder what's happening with their device.

4. Quality Control

Nothing kills repeat business faster than a customer getting back a device that isn't actually fixed. Or worse — one with a new problem.

Pre-pickup QC checklist:

Does the original issue appear resolved?
Run a standard function test (screen, speakers, buttons, charging, connectivity)
Is the device clean? (Fingerprints, dust, smudges — presentation matters)
Are all screws in place, no gaps in the housing?
Does the ticket accurately reflect the work done?

This takes 3–5 minutes per device and prevents the 30-minute phone call when the customer finds a problem at home.

5. Closing and Payment

The last impression matters as much as the first.

Walk the customer through what was repaired
Show the device working (don't just hand it over)
Collect payment and provide an itemized receipt
Explain any warranty coverage
Ask for a review (yes, every time — make it part of the script)

How to Write an SOP That People Actually Follow

Here's where most shops go wrong: they write SOPs that read like legal documents and then wonder why nobody follows them.

Format that works:

Title — what this process is for
When to use it — the trigger (e.g., "Every time a customer drops off a device")
Steps — numbered, action-oriented, one thing per step
Notes — edge cases, tips, things that commonly go wrong

Keep the language conversational. Write it the way you'd explain it to a new hire standing next to you. If you catch yourself writing "pursuant to" or "in accordance with," start over.

One more thing: include the why behind critical steps. "Document existing damage with photos" is good. "Document existing damage with photos — because customers will claim we caused it" is better. People follow rules they understand.

Where to Store Your SOPs

The worst place: a binder on a shelf. The second worst place: a Google Doc nobody can find.

Your SOPs should be:

Accessible from the counter and the bench (digital, not paper)
Searchable (when a tech needs to check something mid-repair)
Version-controlled (so you know which version is current)
Easy to update (processes change — your SOPs should too)

A shared folder works. A wiki works. Your shop management software's notes section works. What doesn't work is making people hunt for the document.

When to Update SOPs

SOPs aren't write-once-forget-forever. Review them when:

A mistake keeps happening (the SOP probably has a gap)
You hire someone new (fresh eyes catch unclear steps)
You change tools or software
A customer complaint reveals a process failure
Every 6 months, even if nothing obvious changed

The best SOPs evolve. Version them (v1, v2, etc.) so everyone knows they're looking at the latest.

The Real Payoff

SOPs don't just help your team. They help you.

When your intake process is documented, you can hire a counter person without spending two weeks training them from scratch. When your QC checklist exists, you stop being the only person who checks work before it goes out. When your communication cadence is written down, customers get consistent updates whether you're in the shop or not.

That's how you go from "I can't take a day off" to "the shop runs fine without me." Which, by the way, is also how you go from one location to two.

Start Small

Don't spend a weekend writing 20 SOPs. Write one. The one that causes the most pain when it's done wrong.

For most shops, that's intake. Write it today. Train your team on it tomorrow. Refine it next week when you see what's unclear.

Then write the next one.

Six months from now, you'll have a shop that runs on systems instead of tribal knowledge. And you'll wonder why you didn't do it sooner.

TechsBox gives your team a consistent workflow for every repair — from intake to invoicing — so your SOPs are built into the software, not buried in a binder. Start your free trial →

How to Write SOPs for Your Repair Shop (So It Runs Without You)