How to write standard operating procedures your crew will actually use

In most small service companies, the procedures live in the owner's head. That works until the owner is on a roof, on vacation, or trying to hire a third crew. Then every phone call, every quote and every job close-out depends on whether the person doing it happened to learn it the right way.

Standard operating procedures (SOPs) are the fix. Not a binder nobody opens, but short, specific instructions for the tasks your company does every day, written so a new hire can follow them and a veteran can check themselves against them. This guide covers which SOPs to write first, a format that works for field crews, how to write and test them, and how to keep them from going stale.

Which SOPs should you write first?

Do not try to document everything. Pick the tasks that score high on one of three tests:

• Frequency. Things done many times a day or week: answering the phone, booking a job, loading the truck, closing out a job.
• Cost of a mistake. Things that are expensive when done wrong: chemical mixing, ladder setup, quoting, collecting payment, locking up a customer's home.
• Handoffs. Places where work passes between people: office to crew, crew to billing, sales to scheduling. Most dropped balls happen at a handoff.

For a typical small service company, a good first five are:

1. New lead intake: answering calls, texts and web forms, and what to capture.
2. Quoting: what to measure, which photos to take, how to build and send the quote.
3. Job day: arrival, customer greeting, the work standard and the walkaround.
4. Job close-out: photos, cleanup, payment, notes and the next appointment.
5. End of day: vehicle, equipment, timesheets and tomorrow's schedule.

Write those five well and you will have covered most of what a new employee needs in the first month. Our guide to onboarding new field employees shows how SOPs fit into training.

A format that works on a phone

Field crews read SOPs standing in a driveway, on a phone, often with gloves on. Write for that.

• Title and purpose. One line on what the task is and why it matters. "Job close-out: so the customer sees a finished job, we get paid today, and the office knows what happened."
• When it applies. Which jobs, which roles.
• What you need. Tools, materials, apps, information.
• The steps. Numbered, one action each, starting with a verb. Ten steps is plenty; if you need thirty, split it into two SOPs.
• The standard. What "done right" looks like, with a photo if possible.
• Common mistakes. The two or three things people get wrong, from experience.
• Owner and review date. Who maintains it and when it was last checked.

Photos and short videos beat paragraphs. A thirty-second phone video of your best tech setting up a ladder on uneven ground teaches more than a page of text.

Example: a job close-out SOP

Notice what it does not say. It does not explain why customers matter or describe your values. It tells someone exactly what to do and what good looks like.

How to write an SOP in an afternoon

1. Watch your best person do the task. Not the owner's idea of how it should go; how it actually goes when it goes well. Record a video if they are willing.
2. Write the steps as they happen, in plain words. Ask "what do you check here?" at each point; the unspoken checks are what new people miss.
3. Cut it down. Remove anything obvious to any adult. Keep anything that is specific to your company or has caused a problem before.
4. Test it with someone new. Hand it to your newest employee and watch them follow it without help. Every place they hesitate or ask a question is a step you need to fix.
5. Publish it where the crew can find it in under ten seconds, and tell everyone it exists.

Use your crew's language. If everyone calls it "the wand" and the manual calls it "the extension lance," people will skim past it. Ask the people who do the work to review the draft; they will catch errors and they will be more likely to follow a procedure they helped write.

Where should SOPs live?

Wherever the work happens. For field crews that means on the phone, inside the tools they already open. Options, from simplest:

• A shared folder of short documents, organized by role, bookmarked on every work phone.
• Checklists inside your scheduling or job software, so the close-out steps appear on the job itself and have to be ticked off.
• Short videos in a private playlist, linked from the written steps.

The strongest option is building the SOP into the workflow so the software prompts each step. A required after photo before a job can be marked complete enforces the procedure better than any reminder. A custom CRM can attach checklists to job types, require photos or notes at close-out, and show the office which steps were skipped. More ideas: things to automate in a service business.

The office needs SOPs too. Phone intake is a good example: a written script for what to ask every caller and where to record it makes sure every lead gets the same treatment. See our phone answering tips for what that script should cover.

Keeping SOPs current and actually used

An SOP that describes how you worked two years ago is worse than none, because it teaches the wrong thing with authority. Three habits keep them alive:

• One owner per SOP. Usually the person who does the task most or leads that team. They update it when the process changes.
• Review on a schedule. Once a year at minimum, and whenever you change equipment, software, pricing or services. Slow season is the natural time.
• Update after mistakes. When a complaint, injury or callback traces back to a step, change the SOP that week. Our complaint handling guide explains how to find those patterns.

Use the SOPs in daily management, too. When a job goes wrong, ask "which step was missed, or is the step wrong?" rather than "who messed up?" That keeps the conversation on the process and makes people more willing to report problems.

Mistakes that make SOPs useless

• Writing for an auditor. Long paragraphs, legal phrasing and policy statements. Crews stop reading after the second sentence.
• Documenting the ideal instead of the real. If the SOP says the crew calls the customer from the shop at 7:30 and nobody ever does, either change the habit or change the document.
• Too many at once. Forty new procedures announced in one meeting will be ignored. Roll out two or three, coach them for a month, then add more.
• No consequence and no praise. If skipping the close-out photos changes nothing, people will skip them. Check a few jobs a week, and thank people by name when they get it right.
• Safety steps buried at the bottom. Put lockout, ladder and chemical steps first and mark them clearly. Our job site safety guide covers the basics.

Why written procedures pay off

Training gets faster, because new hires learn from the same checklist every time. Quality gets more consistent, because the standard does not depend on who is on the truck. The owner gets time back, because fewer questions reach them. And the business becomes worth more: a company whose operations are written down can run without the founder, which is exactly what a buyer is paying for. Our guide to selling a service business explains why that matters when the day comes.

Frequently asked questions