Writing SOPs so the business runs without you

What an SOP is, and what it is not

A standard operating procedure is a short, written description of how a recurring task is done in your company: who does it, when it starts, the steps, and what finished looks like. It is not a policy manual, a training course or a list of everything that could go wrong. The best SOPs in service companies fit on one page and get used daily because they answer the question a new person would otherwise ask the owner.

The test of a good SOP is simple. Could someone who started this week follow it on a Saturday, with nobody to call, and get a result you would accept? If not, it needs more steps or fewer words.

Why turnover makes SOPs urgent

Even in roles that are not growing, people leave and must be replaced. BLS projects about 105,100 openings a year for receptionists despite declining employment, mostly to replace workers who leave^[2]. For janitors and building cleaners, it projects about 321,800 openings a year^[3]. For HVAC mechanics and installers, about 40,600 openings a year against roughly 440,900 jobs^[1].

Every one of those openings is a new person learning how your company answers the phone, books a job and closes an invoice. Without written procedures, each new hire learns from whoever sits next to them, habits drift, and the owner becomes the only reliable source of truth. That is exactly the dependence that keeps owners on the tools and lowers a company's value.

Which SOPs to write first

Start where errors cost customers or cash, and where the task happens many times a week. Leave rare and technical tasks for later; your experienced technicians already know them, and they change often.

A one-page format

• Title: the task in plain words, such as 'Booking a repair call'.
• Trigger: what starts the procedure, such as 'a customer calls or submits a web request for repair'.
• Owner: the role responsible, not a person's name.
• Tools: the software screens, scripts or forms used.
• Steps: numbered, one action each, written as instructions.
• Done when: the observable result, such as 'job is in the schedule with address, problem description and confirmed arrival window, and the customer has a confirmation'.
• Exceptions: the two or three situations that need a different path, and who to escalate to.
• Last reviewed: date and reviewer.

Worked example: the call-answering SOP

Phones deserve the first SOP because consistency there is rare. In a Harvard Business Review audit of how companies handled web leads, 23% never responded at all^[4]. Most small contractors are not that bad on the phone, but most have no written standard either.

1. Answer with the company greeting and your first name within three rings during business hours.
2. If calls are recorded, play or say the recording notice; some states, such as Florida, require consent from all parties^[5].
3. Ask the safety question first for urgent trades: any gas smell, sparking, flooding or no heat with vulnerable people in the home.
4. Capture name, callback number, service address with ZIP code, the problem in the caller's words, and equipment age if known.
5. Search the customer record before creating a new one, to avoid duplicates.
6. Offer two arrival windows from the schedule, confirm one, and read back the details.
7. State the service-call policy as written in the price book; do not improvise prices.
8. Send the confirmation and log the call outcome: booked, message, quote requested or not a fit.

Dispatch and invoicing in brief

The dispatch SOP should set the rules that dispatchers otherwise make up under pressure: which jobs go to which technicians by skill and license, how emergencies bump scheduled work, when to call a customer about a late arrival, and how to record a reschedule. Write the bump rules down. Disagreements about who gets the emergency call at 3 p.m. are a common source of friction between office and field.

The invoicing SOP should define when an invoice is created, who checks it, how payment is requested on site, and what happens on day 1, day 15 and day 30 if it is unpaid. Pair it with a weekly reconciliation step, so payments taken in the field match what reached the bank.

How to write them quickly

1. 01

   Record the best person doing the task

   Screen-record the office lead booking three calls, or film a technician doing a truck stock check, while they narrate.

2. 02

   Draft from the recording

   Turn the narration into numbered steps. AI transcription and drafting tools can do the first pass; the owner of the task edits it.

3. 03

   Test with someone new

   Ask a recent hire to follow the draft without help, and note every place they hesitate or ask a question.

4. 04

   Fix and publish

   Rewrite the confusing steps, add the missing exceptions and put the SOP where people work: in the field service software, a shared drive folder or printed at the desk.

5. 05

   Train against it

   Use the SOP in onboarding and in weekly huddles, so it becomes the reference people actually reach for.

Where SOPs should live

An SOP that takes three clicks and a password to find will not be used during a busy morning. Put each procedure where the task happens. Call-handling steps belong on the screen the office uses to book jobs, or printed beside the phone. Truck procedures belong in the field app or on a laminated card in the truck. Keep one master folder with every SOP and its review date, so you can see the whole set at a glance.

• Use one naming pattern, such as 'Office - Booking a repair call', so people can search.
• Store the current version only; archive old versions in a separate folder.
• Link SOPs from onboarding checklists, so new hires read them in order.
• Make sure technicians can open field SOPs offline.

Keeping SOPs alive

• Give each SOP an owner by role, responsible for keeping it accurate.
• Review the top five SOPs every quarter and the rest twice a year, and date each review.
• Change the SOP the same week the process changes, such as new software, a new price book or a new service.
• When a mistake happens, ask first whether the SOP was missing, unclear or not followed, and fix the right one.
• Retire SOPs nobody uses; an outdated procedure is worse than none.

Checklists for the field

Technicians resist long documents, and they are right to. For field work, turn the SOP into a short checklist built into the job: arrival steps, the safety checks for that trade, the photos to take before and after, and the items to confirm with the customer before leaving. A checklist the technician taps through on the job record also becomes evidence when a customer disputes what was done, and it shows the service manager which steps get skipped most often.

Example: a five-truck company documents the office

Example (fictional): Pinecrest Plumbing and Air had one office manager who knew everything. When she took two weeks of leave, bookings fell apart. The owner asked her to record herself answering calls, dispatching and invoicing for one week. A part-time assistant turned the recordings into six one-page SOPs, and a newly hired coordinator tested each one.

The test found eleven gaps, mostly unwritten rules about which technicians could do which jobs. Those became a skills table inside the dispatch SOP. The next time the office manager was out, the coordinator ran the schedule with two phone calls to the owner instead of twenty.

Common mistakes

• Writing a binder nobody opens instead of one-page procedures at the point of work.
• Documenting the ideal process instead of the real one, so staff ignore it.
• Leaving out exceptions, so people improvise exactly where errors are most expensive.
• Writing every SOP yourself; the people doing the work write better ones.
• Never reviewing them, so they drift out of date within a year.

SOPs pay off most when combined with getting the owner out of daily work; see owner time management and growing from 1 to 5 trucks.