How to write SOPs for a service business: a practical guide

An SOP, or standard operating procedure, is a written set of steps for doing a specific task the same way every time. In a service business, SOPs cover things like checking in a new patient, preparing a vehicle inspection report, closing out a cleaning job, opening the salon in the morning, processing a new client's paperwork or handling a refund request.

Good SOPs do three jobs. They keep quality consistent across people and shifts. They make training faster, because a new hire has something to follow instead of shadowing for weeks. And they make improvement possible, because you cannot fix a process nobody has written down.

Do not start by trying to document everything. That project stalls in a few weeks. Start with the processes where mistakes cost you the most, then add more over time.

Ask your team and look at your records. The right first SOPs usually reveal themselves quickly.

• Which tasks cause the most customer complaints or redos?
• Which tasks generate the most "how do I..." questions from staff?
• Which tasks only one person knows how to do?
• Which tasks touch money, compliance or safety?
• Which tasks do new hires get wrong in their first month?
• Which tasks happen rarely enough that people forget the steps (year-end close, annual renewals, seasonal shutdowns)?

The answer depends on your industry, but the first SOPs usually sit at the points where the customer experience is made or broken.

Writing from memory leaves out steps. The person who does the task every day skips over things that feel obvious to them, which are exactly the things a new hire does not know. Capture the process as it actually happens.

Pick the method that fits the task.

• Computer tasks: record the screen with narration using Loom, Scribe, Tango or the built-in recorder on Windows or Mac. Scribe and Tango generate step screenshots automatically.
• Hands-on tasks: film a phone video of the task, with the person talking through what they are doing and why
• Short tasks: have the person do it while someone else types each step as it happens
• Judgment-heavy tasks: record a short interview asking "what do you look for?" and "what would make you stop?"
• Capture variations: ask what changes for a first-time customer, a large job or a rush order

Turn the recording into a short document. Use the same template for every SOP so people know where to look. Most SOPs fit on one or two pages. If an SOP gets long, split it into smaller ones.

A practical template has these parts.

• Title: an action, such as "Check in a new patient" or "Close out a residential cleaning job"
• Purpose: one sentence on why the task matters
• Owner: the role responsible, not a person's name
• When: the trigger that starts the task
• Tools and materials: software, forms, supplies
• Steps: numbered, one action per step, starting with a verb
• Check: how to confirm the task was done right
• If something goes wrong: who to contact and what to do
• Last updated: date and who updated it

Detailed enough that a trained new hire can complete the task correctly without asking, and no more. Write for the person who knows the job but not your way of doing it. A licensed stylist does not need instructions on how to apply color. They do need to know where your business records formulas and how you want rebooking handled at checkout.

Use these writing rules to keep steps clear.

• Start each step with a verb: "Open," "Confirm," "Photograph," "Send"
• One action per step
• Use the exact names of buttons, fields and forms
• Add a screenshot or photo where a step is easy to get wrong
• Put warnings right before the step they apply to
• Use specific numbers: "within 15 minutes," not "promptly"
• Mark decision points clearly: "If the customer declines, go to step 9"

Here is a short example showing how the template looks in practice. Adapt the steps to your shop management system.

• Purpose: record the vehicle's condition and the customer's concern accurately so the technician can diagnose it and disputes are avoided
• Owner: service advisor. Trigger: customer arrives for a scheduled or walk-in appointment.
• 1. Greet the customer and confirm name, phone and vehicle in the shop management system.
• 2. Ask the customer to describe the concern in their own words and type it into the repair order exactly.
• 3. Ask when it happens (cold start, highway speed, braking) and record the answer.
• 4. Walk around the vehicle with the customer and photograph all four sides and any existing damage.
• 5. Record mileage and fuel level from the dashboard, with a photo.
• 6. Confirm the best contact method for estimate approval and note it.
• 7. Give the expected time for a call with findings.
• Check: repair order has concern, conditions, photos, mileage and contact method before the keys go to the technician.

Before publishing, have someone who does not usually do the task follow the SOP exactly. Watch where they hesitate, ask questions or do something different. Each of those spots needs a clearer step.

Then have the expert review it for accuracy. This two-person check catches both missing steps and wrong ones.

• Choose a tester who knows the general job but not this exact task
• Ask them to follow the steps literally and say out loud what they are doing
• Note every pause, question or workaround
• Rewrite those steps, then test once more with a different person

Use both, for different moments. The full SOP explains the purpose, the steps, the decision points and what to do when something goes wrong. It is what people read when they are learning a task or when something unusual happens. The checklist is the short version used while doing the work, with just the steps and checks.

A cleaning crew does not open a two-page document in a client's kitchen. They follow a room-by-room checklist on a phone or a laminated card, and the full SOP lives in the shared folder for training. A med spa front desk might follow a short check-in checklist inside the booking system, with a link to the full SOP for insurance questions. Write the full SOP first, then cut it down to the checklist, so both stay in sync.

An SOP nobody can find does not help. Store them in one place, organize them by role or area and link them from the tools people use during the task.

Common choices include Google Drive or SharePoint folders with a simple index, Notion or Confluence wikis, and dedicated tools like Trainual, Process Street or Whale that add assignments and sign-offs. The right choice is the one your team will open.

• One home for all SOPs, with a search or index
• Folders or tags by role and by area (front desk, service, billing)
• Links to SOPs from inside your booking, CRM or job management tool where possible
• Printed or laminated checklists for hands-on tasks at the workstation
• Read-only for most staff, editable by named owners
• New hire onboarding includes the SOPs for their role

Calendar-based reviews tend to get skipped. Review an SOP when something changes or when there is evidence it is not working. Name an owner for each SOP who is responsible for updating it.

Monvell documents processes and writes SOPs as part of our operations and consulting work, often alongside automation, since a clearly written process is also the starting point for deciding what to automate.

• A tool, form or system used in the process changes
• The same mistake happens twice
• A new hire asks the same question more than once
• A customer complaint traces back to the process
• A service, price or policy changes
• A regulation or license requirement changes

People follow SOPs that make their job easier and that they helped write. Involve the people who do the work in recording and testing each SOP, and explain the reason behind each important step.

Build SOPs into training and quality checks. A manager reviewing a completed job against the SOP's check section, and a new hire signing off that they have read and practiced each SOP for their role, both reinforce the habit without turning it into paperwork.

Most SOP projects fail in familiar ways. Watch for these from the start.

• Trying to document every process at once, then stalling
• Writing from memory instead of watching the task
• Long paragraphs instead of numbered steps
• Naming a person as owner instead of a role, so SOPs break when people leave
• Storing SOPs in a folder nobody opens
• Never updating them after a tool or policy change, until staff stop trusting them
• Writing SOPs as rules handed down, without the team's input

Use this list for each new SOP.

• The process was chosen because it causes mistakes, questions or risk
• It was recorded while someone did the real task
• It follows the standard template: purpose, owner, trigger, tools, steps, check
• Each step starts with a verb and covers one action
• Someone who did not write it tested it
• An expert reviewed it for accuracy
• It is stored in the shared location and linked from the tools used
• It has a named owner and a last-updated date