Writing SOPs for a service business: getting the way you work out of your head

Which processes to document first

Do not try to document everything. Start with the tasks that meet at least one of these criteria:

• Happen often: the standard service visit, the phone intake, the estimate.
• Cost money when done wrong: pricing, chemical mixing, equipment shutdown, invoicing.
• Create complaints: the final walk-through, cleanup, arrival communication.
• Only the owner knows: anything that stops when the owner is sick or on vacation.

A typical first list for a service company has ten to fifteen processes. That is enough to change how the business runs.

The CLEAR method for writing SOPs

• C — Capture the process as it is done today by your best person.
• L — List the steps in order, short and specific.
• E — Evidence: define what proves each step was done, such as a photo, a checkbox or a reading.
• A — Assign an owner responsible for keeping the SOP current.
• R — Review it on a schedule and whenever a mistake repeats.

Capture: record the best way, not the ideal way

The fastest way to write an SOP is to watch your best technician do the task and record it. Film it on a phone, or have them talk through it while you take notes. Do not start from a blank page imagining how the task should be done in theory. You want the real process that already works, with the small tricks your best people use. Then fix what is inconsistent or unsafe.

List: steps a new hire can follow

Write each step as an action that starts with a verb: "Park on the street, not the driveway, unless the customer says otherwise." "Photograph the unit's data plate before starting." "Test the system for 10 minutes after the repair." Keep it to the essential steps. If a step needs judgment, give the rule of thumb and when to call the office. A good test: could someone with basic skills in your trade follow it on their first week without calling you?

Evidence: define what "done" looks like

Most quality problems are not caused by people skipping steps on purpose. They happen because "done" was never defined. For each critical step, say what proves it: a before and after photo uploaded to the job, a pressure reading recorded in the app, a checklist box ticked in front of the customer. Evidence makes the SOP checkable, and it protects the business when a customer disputes the work. See how to document a job for warranty claims.

Assign: every SOP has an owner

SOPs go stale when nobody is responsible for them. Assign each one to the person closest to the work: the lead technician owns the service visit SOP, the office manager owns intake and invoicing, the owner owns pricing. The owner of an SOP updates it when the process changes and trains others on it.

Review: update when things change or break

Review each SOP at least once a year, and immediately when a mistake repeats. A callback, a complaint or an injury is a signal to ask: was there an SOP, was it followed, and does it need to change? Over time, this turns every problem into a permanent improvement instead of a one-time lecture.

Format: checklists, videos and photos

Choose the format that fits how the task is done. On the job, a checklist in the field service app beats a document. For hands-on tasks, a short video is often clearer than text. For setup and quality standards, photos of "right" and "wrong" work well. Keep all SOPs in one place everyone can reach from a phone, such as a shared folder or your field service software, with a simple naming pattern: department, task, version.

Example: the arrival and walk-through SOP

• Text the customer when leaving the previous job, with the technician's name and photo.
• Park where it does not block the customer, and put on shoe covers before entering.
• Introduce yourself, confirm the problem in the customer's words and ask if anything else is going on.
• Inspect before quoting; photograph the problem.
• Explain the options and the price before starting any work.
• When done, show the customer the work, explain what was done and how to care for it.
• Clean the area and take after photos.
• Collect payment, and ask for the review with a direct link by text.

Eight steps, each checkable, and together they cover most of what causes complaints and missed revenue.

A one-page SOP template you can copy

• Title: department and task, for example "Field — Water heater replacement".
• Purpose: one sentence on why this matters to the customer and the business.
• Who does it: the role, not the person's name.
• When: the trigger that starts the task.
• Tools and materials: what must be on the truck.
• Steps: numbered, one action per line.
• Evidence: the photos, readings or checkboxes that prove it was done.
• When to call the office: the situations that need a decision.
• Owner and last review date.

Using the same template for every SOP makes them faster to write and easier to read. The team learns where to look for the answer.

Example: the phone intake SOP

The phone is where most jobs are won or lost, and it is usually the least documented process. A simple intake SOP: answer within three rings with the company name and your name; get the customer's name and address first, so you can call back if the line drops; ask what is happening in their words and how urgent it is; confirm the service area; offer two specific time windows instead of asking "when works for you?"; state the diagnostic or trip fee clearly; confirm by text with the technician's name. Recorded calls reviewed once a week against this checklist improve booking rates quickly. See phone scripts that book jobs.

A worked example: what SOPs are worth

A cleaning company with six crews has a 6% rate of "re-clean" callbacks, each costing about $90 in labor and travel. At 400 jobs a month, that is 24 callbacks and $2,160 a month, before counting the customers who quietly leave. The owner writes SOPs for the standard clean, the move-out clean and the final walk-through, with a photo checklist for kitchens and bathrooms. Suppose callbacks drop to 2.5%. That saves 14 callbacks, or about $1,260 a month, and probably keeps several recurring customers who would have left. Training time for new hires also falls, from three weeks of shadowing to about one week plus the checklists. These are illustrative numbers, but they show that SOPs pay for themselves in reduced rework alone.

Using SOPs in training

SOPs turn training from "follow Mike around for a month" into a structured plan: read or watch the SOP, see it done, do it with supervision, do it alone with the checklist, and get signed off. Each new hire has a list of SOPs to complete in the first 30, 60 and 90 days. This makes progress visible and makes it clear when someone is ready to work alone. See training a new technician for a full plan.

Getting the team to actually use them

SOPs fail when they are handed down as rules nobody asked for. Involve your best people in writing them, keep them short, and connect them to things the team cares about: fewer callbacks, fewer angry customers, faster jobs, clearer paths to promotion and bonuses. Refer to the SOP in every coaching conversation: "What does the SOP say here?" And follow them yourself. If the owner skips the checklist, so will everyone else.

SOPs and the owner's time

The biggest payoff of SOPs is often for the owner. Every documented process is one less question in the owner's phone and one less task only they can do. Businesses with clear SOPs can run for a week without the owner, can promote a lead technician to manager with confidence, and are worth more when the owner decides to sell, because a buyer is paying for a system, not a person. See the owner's time and selling your service business.

The first ten SOPs for most service businesses

• Answering the phone and booking the job.
• Giving an estimate and presenting options.
• Arrival and walk-through.
• The core service, one per main service line.
• Safety for the main equipment and chemicals.
• Truck stock and end-of-day restock.
• Job completion, photos and cleanup.
• Invoicing and collecting payment.
• Handling a complaint or a callback.
• Onboarding a new hire.

Common mistakes

• Writing long documents nobody reads.
• Describing an ideal process instead of the one that works.
• No definition of what "done" looks like.
• No owner and no review date, so SOPs go stale.
• Storing SOPs where the team cannot reach them from the field.
• Writing them without the people who do the work.
• The owner ignoring them.

A 30-day plan to start

• Week 1: list your recurring processes and pick the first five.
• Week 2: record your best person doing each one.
• Week 3: write each SOP as short steps with evidence, and assign an owner.
• Week 4: train the team on them and start using the checklists on every job.

Put the SOP review on the calendar the same way you schedule truck maintenance. A process that is written down, used on every job and reviewed when something goes wrong becomes the most valuable asset a small service business has, because it keeps working when people change.

After the first five, add one or two SOPs a month. In a year, the business runs on a system anyone can learn. Pair this with quality control for service crews to make sure the standards are kept.

Frequently asked questions

What SOPs should a service business write first?

Start with tasks that happen often, cost money when done wrong, create complaints or only the owner knows: phone intake, estimates, arrival and walk-through, the core service, safety, truck stock, job completion, invoicing, complaints and onboarding new hires.

How long should an SOP be?

Short enough to use on the job. Most field SOPs fit on one or two pages or in a three-minute video, with numbered steps, the evidence that proves each step was done and the situations that require calling the office.