What Is an SOP? Examples and How to Write One
SOP guide

What Is an SOP? Examples and How to Write One

A standard operating procedure (SOP) is a documented set of steps for doing a task the same way every time. Here is what makes a good one, six real examples and how to write your first this week.

By David Jenyns, founder of SYSTEMology and systemHUB · Updated November 2026

What is a standard operating procedure (SOP)?

A standard operating procedure (SOP) is a documented set of steps that tells someone how to complete a specific task in your business.

Think of it like a recipe. It lists the steps and what the finished result should look like so the outcome is the same every time whoever does the work.

You will also hear them called processes, procedures, playbooks or systems. The label doesn’t matter. What matters is getting the knowledge out of people’s heads and into a format your team can use.

SOP, policy or process: what’s the difference?

Policy

What you do and why. For example: “We refund customers within 30 days.”

Process

The high-level workflow from start to finish, such as how a refund request moves through the business.

SOP

The step-by-step how. The detailed instructions someone follows to carry out the process within the policy.

Why it matters

Why SOPs matter

Could your business survive without you for three months? If the honest answer is no, it’s rarely because your team isn’t talented. It’s because everything they need to know lives in your head. SOPs are how you start building a business that runs without you.

 Consistency

Your team delivers the same quality every time, not just when you are watching. Nobody claims McDonald’s makes the world’s best hamburger but you know exactly what you will get at every location. Systems make that possible.

 Freedom

When processes are documented your team can handle things without interrupting you. Gary McMahon went from 100-hour weeks to a three-week holiday with his family after systemising Ecosystem Solutions and his profit rose about 80%.

Faster training

New people get up to speed in days instead of months. They follow the SOP instead of shadowing someone for weeks. (More in our guide to onboarding best practices.)

Fewer mistakes

A clear process means important steps don’t get missed. Lime Therapy, an allied health practice with 40 staff, systemised its invoicing and cut the time it takes tenfold.

A business worth more

Buyers don’t pay top dollar for a business that falls apart when the owner leaves. They pay for documented, repeatable systems. Your SOPs are what make your business a sellable asset.

What good looks like

5 essentials every SOP needs

A bad SOP collects dust in a shared drive. A good one gets used every day without you. After working with hundreds of businesses these are the five things that separate the two.

1. A defined trigger

Every SOP starts by answering one question: when does this process begin? A customer complaint, a new hire’s first day, a deadline each month. Make it explicit. Without a trigger the SOP has no natural entry point and nothing happens. The trigger is the on switch.

2. A stated purpose

A list of steps without context is just instructions. When your team knows what a process achieves and who it serves they make better decisions when things don’t go to plan. “This system ensures customers receive prompt refunds while keeping the financial records accurate” turns rule-followers into problem-solvers.

3. A definition of done

The steps end but the process doesn’t. Nobody knows if the task is finished or what happens next. State the endpoint: a record updated, a confirmation sent, another process triggered. Nobody should have to wonder whether they are done.

4. Written for a human

Write in conversational language from the point of view of the person doing the task. “Here’s how to handle a customer complaint” beats “Initiate the customer complaint resolution protocol.” Match the detail to the job: overview systems map the big picture (like an annual marketing plan) and how-to systems give step-by-step precision for tasks like processing an invoice. Document the 80% path first and add edge cases later.

5. Never more than one click away

The best SOP is useless if it’s buried in a shared drive. Link it from where the work happens: task cards, calendar invites for recurring processes, even QR codes near equipment. If finding the SOP takes more effort than asking you, your team will ask you.

See it in practice

6 real SOP examples

Here are six SOPs from six departments. Each one has a trigger, clear steps and an endpoint.

Sales

Following up on a new enquiry

Trigger: New lead comes in via website form or phone call.

  1. Log the enquiry in the CRM within 30 minutes
  2. Send the personalised “thanks for reaching out” email template
  3. Call the lead within 2 hours during business hours
  4. If there’s no answer, send a follow-up SMS
  5. Schedule a follow-up call for 48 hours later
  6. After the first conversation, update the CRM and move the lead to the right pipeline stage

Endpoint: The lead is either booked for a discovery call or marked as not qualified with a reason.

Operations

Onboarding a new client

Trigger: Client signs the agreement and makes the first payment.

  1. Send the welcome email with the onboarding questionnaire
  2. Create the client folder in the project management tool
  3. Schedule the kickoff call within 5 business days
  4. Assign the project lead and notify the team
  5. Complete the internal setup checklist (access, logins, templates)
  6. Run the kickoff call and document key decisions
  7. Send the kickoff summary and next steps within 24 hours

Endpoint: The client is fully set up, the team knows what to do and the first deliverable is scheduled. (More in building a client onboarding process.)

Finance

Processing a customer refund

Trigger: Approved refund request from the customer service team.

  1. Verify a team leader has approved the refund
  2. Open the original invoice in the accounting software
  3. Create a credit note against the invoice
  4. Process the refund to the original payment method
  5. Email the customer to confirm the refund and timeframe
  6. Update the CRM record with the refund and the reason

Endpoint: The refund is processed, the customer is notified and the records are updated.

HR

First day for a new team member

Trigger: The new hire’s start date.

  1. Prepare their workstation (computer, login credentials, phone)
  2. Send the welcome pack (handbook, org chart, first-week schedule)
  3. Manager greets them and does office introductions
  4. Walk through the employee handbook and key policies
  5. Set up system access (email, project management, internal tools)
  6. Assign a buddy for the first two weeks
  7. Schedule check-ins for end of day 1, end of week 1 and end of week 4

Endpoint: The new team member has everything they need and knows where to go for help.

Marketing

Publishing a social media post

Trigger: The content calendar says a post is due.

  1. Draft the post copy using the content brief
  2. Select or create the visual asset
  3. Submit it to the marketing lead for approval
  4. Schedule the post in the social media tool
  5. Monitor engagement for the first 2 hours
  6. Respond to any comments within 4 hours
  7. Log performance metrics at the end of the week

Endpoint: The post is live, engagement is monitored and results are tracked.

Customer service

Handling a customer complaint

Trigger: A complaint arrives by phone, email or social media.

  1. Acknowledge it within 2 hours and thank the customer for raising it
  2. Log it in the CRM with the customer’s details and what went wrong
  3. Ask clarifying questions until the issue is clear
  4. Offer the standard fix or escalate to a team leader if it falls outside the guidelines
  5. Confirm the resolution with the customer in writing
  6. Record the cause and add any lessons to the weekly review

Endpoint: The customer is satisfied, the complaint is closed in the CRM and the cause is logged.

That’s the pattern. Follow it and you can write an SOP for anything in your business. Want more? Here are 15 standard operating procedure examples across every department, each ready to copy and adapt.

Skip the blank page

systemHUB includes 100+ ready-made SOP templates across sales, marketing, operations, HR and finance. Copy one and customise it for your business.

Browse free SOP templates  Start your free trial
The method

How to write your first SOP

Most guides tell you to sit down and write every step from memory. Don’t. This is the method we have used with hundreds of businesses, from trades to professional services to allied health. The full framework is in the SYSTEMology book.

Watch: the system for creating systems, step by step (11 minutes).

  1. Pick one processNot ten. Not your whole department. Choose the one causing the most pain: the one that keeps interrupting you or where mistakes keep happening. Not sure? Look at your core departments (marketing, sales, operations, finance, HR and management) and find the most critical recurring task in each.
  2. Find your knowledgeable workerThe person who documents a process isn’t always the owner. It’s the person who does the work every day and does it well. They know the real steps, the shortcuts and the pitfalls you might miss. We call them the “knowledgeable worker.”
  3. Record, don’t writeDon’t sit at a blank document. Have your knowledgeable worker record themselves doing the task, with screen recording (Loom, Zoom or similar) for computer work and a phone camera for hands-on work. Ask them to narrate: “First I open this, then I click here.” You capture what actually happens, not what someone remembers. Ask why they do each step, note the decision points and record today’s process. You can optimise later.
  4. Turn the recording into a documentTranscribe it, then structure the transcript into clear numbered steps. AI speeds this up: feed the transcript into Process Pal (our free recording-to-SOP tool) and you get a first draft in minutes. Review it, because AI gives you speed and your team gives you accuracy. No recording? Describe the process in a few sentences and the free AI SOP generator drafts it for you. Documented SOPs are also where business process automation starts, because you can’t automate what nobody has written down.
  5. Test it with a real personHand the finished SOP to someone who hasn’t done the task and ask them to follow it step by step the next time it comes up. Where they get stuck or ask questions is your revision list. This test is non-negotiable.
  6. Store it where your team can find itPut every SOP in one central, searchable place, not scattered across email attachments, Google Docs and desktops. That’s the job SOP software is built for.
  7. Train, then trustDemonstrate the task using the SOP, do it together, then watch them do it alone. Repeat that last step until they can run it without help. Then step back and let the system do its job.
systemHUB, a central platform for SOPs and process documentation
systemHUB keeps every SOP in one searchable library.

Watch: turn a recording into a structured SOP using AI (9 minutes).

Want the deeper version? Our full guide on how to write an SOP covers the format that works and includes a worked example. When you’re ready to zoom out from single procedures to whole workflows, see how to document a business process.

Avoid these

Common mistakes when writing SOPs

Most SOP projects stall for the same few reasons.

Documenting everything at once

You don’t need 100 SOPs to start. You need one. Get it working, then move to the next. Momentum matters more than volume.

The owner writing every SOP

That defeats the purpose. You’re trying to free yourself from daily operations, not add a documentation job. Assign a Systems Champion or use your knowledgeable workers.

Waiting for perfection

Done beats perfect. A good-enough SOP your team uses today is worth more than a perfect one you finish someday. You can always improve it later.

Writing it from memory

Memory skips steps. Recording captures what actually happens. Always start from a recording.

Creating systems for systems’ sake

Before documenting anything, ask: will this help the business? If it won’t improve the customer experience, free up your team or reduce errors, pause. Documentation isn’t the goal.

Setting it and forgetting it

SOPs are living documents but don’t force updates on a schedule. Update them when they need it. Your team is your best early warning system if feedback is welcome.

Questions

Frequently asked questions

What does SOP stand for?

Standard operating procedure. It is a documented set of steps for completing a specific task or process in your business.

What does a good SOP look like?

It has a clear trigger, a stated purpose, numbered steps in plain language and a definition of done. Someone who has never done the task can follow it and get the right result.

How many SOPs does a business need?

Start with your Minimum Viable Systems: roughly seven critical processes per department across six core departments. That is about 42 systems to cover the essentials. Don't let the number overwhelm you. Start with one.

Who should write SOPs?

Not the business owner. The best approach is to have the person who does the work (the knowledgeable worker) record themselves doing the task, then have someone else structure that recording into a written document.

How long should an SOP be?

As long as it needs to be and no longer. A simple daily task might need five steps and a complex monthly process might need 20. Match the detail to the audience: a new hire needs more guidance than an experienced team member.

How often should SOPs be updated?

When they need it, not on a fixed schedule. Think of it like a flat tyre: you fix it when it happens, not at the next annual service. If a tool changes, a step changes or your team flags a gap, update the SOP then.

What is the difference between an SOP, a policy and a process?

A policy is what you do and why. A process is the high-level workflow. An SOP is the detailed, step-by-step how-to someone follows to carry out the process within the policy.

Start with one

You don’t need to systemise your entire business this week. Pick the one process causing you the most pain. Record it, document it and get your team using it. Once the first SOP works you’ll see what’s possible and the next one gets easier. Your SOPs, policies and onboarding together become your business brain.

Keep reading

Or browse all guides and the free AI SOP tools.

Start building your first SOP

Document how your business really runs in one central place your team and your AI can use.

14-day free trial. No credit card required.

Recent Posts