SOP Template: A Free Standard Operating Procedure Template for Service Businesses

What is an SOP in business?

An SOP, or standard operating procedure, is a written set of steps for doing one task the same way every time. It answers four questions: what the task is, who owns it, when it happens and exactly how to do it.

In a service business, SOPs cover the work that repeats every day or every week:

• Answering a new lead and booking the first appointment
• Dispatching a crew or technician
• Closing out a job and sending the invoice
• Onboarding a new team member
• Handling a customer complaint
• Running the weekly team meeting

When these steps live only in the owner's head, every question comes back to the owner. When they live in an SOP, the team can run the work without you. That is the whole point.

SOP vs. playbook vs. checklist

People use these words loosely, so here is how we use them:

• SOP: the steps for one task. "How we book a new customer."
• Checklist: a short list inside an SOP that confirms nothing was skipped.
• Playbook: a collection of SOPs for one part of the business. "The sales playbook" might hold 8 to 12 SOPs.

Start with SOPs. A playbook is just your SOPs, organized. If you want a ready-made structure for the playbook itself, see our free tools for service business owners.

The free SOP template

Copy everything inside the box. Each field has a short note on what goes there. Delete the notes when you fill it in.

STANDARD OPERATING PROCEDURE

1. SOP NAME
   [Verb + task. Example: "Book a new customer appointment"]

2. SOP ID AND VERSION
   ID: [Department code + number. Example: SALES-003]
   Version: [1.0]
   Last updated: [Date]
   Next review: [Date, 90 days out]

3. OWNER
   Owner (keeps this SOP current): [Role, not a person's name]
   Approved by: [Role]

4. PURPOSE
   [One or two sentences. Why this task matters and what goes
   wrong when it is done badly.]

5. SCOPE
   Applies to: [Who does this task]
   Starts when: [The trigger. Example: "A new lead comes in"]
   Ends when: [The finish line. Example: "Appointment is on the
   calendar and the customer has a confirmation"]
   Does not cover: [Related tasks that have their own SOP]

6. TOOLS AND ACCESS NEEDED
   [Software, logins, forms, scripts, equipment]

7. DEFINITIONS
   [Any term a new hire would not know]

8. STEPS
   Step | Action (start with a verb) | Who | Time limit | Notes
   1    |                            |     |            |
   2    |                            |     |            |
   3    |                            |     |            |
   [Keep each step to one action. Add a screenshot or short
   screen recording link where it helps.]

9. DECISION POINTS
   If [situation], then [what to do].
   If [situation], then [what to do].

10. QUALITY CHECKLIST
   [ ] [Thing that must be true when the task is done]
   [ ] [Thing that must be true when the task is done]
   [ ] [Thing that must be true when the task is done]

11. WHAT GOOD LOOKS LIKE (THE NUMBER)
   Measure: [Example: "Leads booked within 24 hours"]
   Target: [Example: "90 percent or better"]
   Where it is tracked: [Scorecard, report or dashboard]

12. WHEN TO ESCALATE
   Escalate to: [Role]
   Escalate when: [Clear trigger]

13. RELATED SOPS
   [Links to the SOPs that come before and after this one]

14. CHANGE LOG
   Date | Version | What changed | Changed by

That is the full standard operating procedure template. Fourteen sections looks like a lot, but most SOPs fill sections 4 to 7 in a few lines each. The steps, decision points and checklist are where the real work is.

A filled SOP example: booking a new customer

Here is the template filled in for a task almost every service business has. Use it as a model for your own.

1. SOP NAME: Book a new customer appointment
2. ID: SALES-003 | Version 1.2 | Last updated: Oct 1 | Next review: Jan 1
3. OWNER: Customer Service Lead | Approved by: Operations Manager
4. PURPOSE: New leads go cold fast. Booking them the same day keeps
   our close rate up and stops leads from calling a competitor.
5. SCOPE: Applies to all customer service reps.
   Starts when: A call, web form or text comes in from a new lead.
   Ends when: The appointment is booked in the scheduling software and
   the customer has a text and email confirmation.
   Does not cover: Rescheduling (see SALES-004).
6. TOOLS: CRM, scheduling software, call script v3, service area list.
7. DEFINITIONS: "Hot lead" = needs service within 48 hours.
8. STEPS:
   1. Answer or return the lead within 5 minutes during business hours.
   2. Confirm name, address, phone, email and the problem.
   3. Check the address against the service area list.
   4. Ask the 3 qualifying questions in the call script.
   5. Offer the two soonest open slots.
   6. Book the slot in the scheduling software and tag the lead source.
   7. Send the confirmation text and email from the CRM.
   8. Add notes the technician needs before arrival.
9. DECISION POINTS:
   If the address is outside the service area, use the referral script.
   If it is a hot lead and no slot is open in 48 hours, escalate.
10. CHECKLIST:
   [ ] Lead source tagged
   [ ] Confirmation sent
   [ ] Technician notes added
11. THE NUMBER: Leads booked within 24 hours. Target: 90 percent.
    Tracked on the weekly sales scorecard.
12. ESCALATE: To the Operations Manager when a hot lead cannot be
    booked within 48 hours.
13. RELATED: SALES-002 (Lead intake), SALES-004 (Rescheduling)
14. CHANGE LOG: Oct 1, v1.2, added step 8, Operations Manager

Notice what makes it work. Every step starts with a verb. Each step is one action. There is a number at the end so you can tell whether the SOP is being followed without watching anyone.

How to write an SOP in 6 steps

The template is the easy part. Writing SOPs your team actually follows takes a simple process.

1. Pick the task that interrupts you most

Do not start by writing SOPs for everything. Start with the task that brings the most questions to your desk. If you are not sure which one that is, our guide to stopping being the bottleneck in your business walks through how to find it.

2. Record the task while someone does it

The fastest way to write an SOP is not to write it. Have the person who does the task best walk through it while you record the screen or take notes. Write down every click, call and decision. You will catch steps the expert does without thinking.

3. Turn the recording into steps

Fill in section 8 of the template. Rules for good steps:

• Start each step with a verb: "Send," "Check," "Book."
• One action per step. If a step has "and" in it, split it.
• Add a screenshot for any step that happens inside software.
• Keep the whole SOP to one or two pages. Longer than that, and it is two SOPs.

4. Add the decisions and the number

Most SOPs fail at the exceptions, not the normal path. List the two or three situations where people get stuck and say what to do. Then add one number that shows whether the task is being done right.

5. Test it with someone new

Hand the SOP to someone who has never done the task. Watch them follow it without help. Every time they stop or ask a question, the SOP has a gap. Fix it and test again.

6. Set an owner and a review date

An SOP without an owner goes stale in months. Give each SOP an owner by role, and review it every 90 days or whenever the process changes. Log the change in section 14.

Why most SOPs fail (and how to keep yours alive)

Plenty of businesses have a shared drive full of SOPs nobody opens. It usually comes down to one of these:

• Nobody owns them. The owner wrote them once and moved on.
• They are too long. A 12-page document will not get read on a job site.
• They are not tied to a number. If no one checks results, no one checks the SOP.
• They live in the wrong place. Keep SOPs where the work happens, in the tools your team already opens every day.
• No one is accountable for using them. Writing SOPs is a project. Running the business on them is a job.

That last point is the one owners miss. Someone has to own the system: notice when a step is skipped, update the SOP when the process changes and train new hires on it. In larger companies, that is the operations manager or COO. In many businesses with 5 to 250 team members, it is still the owner, which is why the SOPs never stick. If you are weighing whether it is time to hand that job off, read our guide on how to hire an operations manager.

SOPs for service businesses: where to start

If you run a home services company or another service business, these are the first ten SOPs we would write, in order:

1. New lead intake and booking
2. Job scheduling and dispatch
3. Job closeout and invoicing
4. Collecting payment and following up on unpaid invoices
5. Customer complaint handling
6. Requesting reviews after a job
7. New hire onboarding
8. Weekly team meeting
9. Weekly scorecard update
10. Purchasing and inventory restock

The first four protect your cash. The next two protect your reputation. The last four keep the team running without you. For more on how this looks in trades and field service companies, see operations for home services businesses.

How Edge builds SOPs with EdgeOS

At Edge, SOPs are one part of EdgeOS, the operating system our full-time Operations Manager installs inside your business. Your Operations Manager documents your core processes as SOPs and playbooks, ties each one to a number on your company scorecard and keeps them current as the business changes.

The difference is ownership. Your Operations Manager does not hand you a folder of documents and leave. They run the business on those SOPs every day, train your team on them and update them when something breaks, so the systems keep working after the first draft is done.

If you want SOPs that your team actually follows, and someone who owns them full time, we can show you how it works.

Book a Call