Guide · Operations

How to Write an SOP: A Step by Step Guide for Small Businesses

An SOP, a standard operating procedure, is the written version of how a task gets done in your business, written well enough that a new hire can do the task correctly without you standing behind them. Most small businesses run on knowledge that lives in two or three heads. That works until one of those heads is sick, on holiday, or resigning, and it is the reason the same mistakes repeat while the owner answers the same questions forever. This guide shows how to write an SOP properly: the structure, the process, a worked example, and the mistakes that turn most SOPs into documents nobody opens.

A checklist document with numbered steps, a pen, and a team following the same process, illustrating how to write an SOP for a small business.

We write these for a living. The operations behind this site run a remote team that grew from 30 to more than 200 people, and the only way that growth did not collapse into chaos was writing down how the work works, one procedure at a time.

What an SOP is, and what it is not

An SOP covers one recurring task, end to end: handling a refund, onboarding a client, publishing a product, closing the books each month. It is not a policy (policies say what the rules are), not a job description (those say who is responsible), and not a company handbook. An SOP answers one question: when this task needs doing, what exactly happens, in what order, to what standard?

The test of a good SOP is simple. Hand it to a competent person who has never done the task. If they complete the task to standard without asking you anything, the SOP works. If they stall, the document failed, not the reader.

The structure of an SOP that works

Every SOP we write uses the same skeleton, because a team that knows where each part lives reads faster and misses less.

  • Title and purpose: the task name, and one line on why it matters and when it runs.
  • Scope: who does this, and which cases it covers and does not cover.
  • Tools and access: every system, login, and permission needed, listed before step one.
  • The steps: numbered, one action per step, in the order the work actually happens.
  • Quality standard: what a finished job looks like, with an example where possible.
  • Exceptions: what to do when the normal path fails, and when to escalate instead of improvising.
  • Owner and review date: who keeps this document true, and when it gets checked next.

How to write an SOP in 7 steps

Step 1: pick the task that hurts most. Do not start by documenting everything. Start where errors cost money, where only one person knows how, or where you personally get interrupted most. One painful task, fixed, funds the habit.

Step 2: watch the task being done, by the person who does it best. Never write an SOP from your memory of how a task should go. Sit with the person who does it daily, watch a real run, and note what they actually do, including the small checks they perform without thinking. Those invisible checks are usually the difference between their results and everyone else's.

Step 3: draft the steps in plain language. One action per numbered step, short sentences, the exact names of buttons, screens, and fields. Write "Open the order, click Refund, choose Original payment method" instead of "process the refund appropriately". If a step needs a decision, write the rule for the decision, not "use your judgment".

Step 4: add the quality standard and an example. Steps alone produce technically completed tasks at wildly varying quality. State what good looks like: the finished output, the checks before it counts as done, and one real example of a job done right.

Step 5: test it with a fresh pair of eyes. Give the draft to someone who has never done the task, watch them follow it, and say nothing. Every place they pause, guess, or go wrong is a hole in the document. Fix the document, not the person. This step is the one everyone skips, and skipping it is why most SOP libraries fail.

Step 6: publish it where the work happens. An SOP buried in a drive folder nobody opens is a diary, not a system. Link it from the tool where the task starts: the help desk macro, the project template, the checklist the team already uses. One source of truth, edited in one place, never copied into five documents that drift apart.

Step 7: set the review rhythm. Processes change, tools change, and an outdated SOP is worse than none because it is confidently wrong. Every SOP gets an owner and a review date, quarterly for fast moving work. When the process changes, the SOP changes the same week, and that rule is what keeps the library alive.

A worked example: the shape of a support SOP

Here is the skeleton of a real style SOP, for answering a customer support ticket, with the middle steps compressed so you can see the shape:

  1. Purpose: every customer gets a correct, complete first answer within the team's response time target.
  2. Scope: support agents, all email and chat tickets. Billing disputes above the refund limit escalate under the exceptions section.
  3. Tools: help desk, CRM, order system, the macro library.
  4. Steps: read the full thread before touching anything; identify the one thing the customer is actually asking; check the order or account in the source system, never guess; answer using the matching macro as a base, then personalize the first and last lines; verify names, dates, and amounts against the record; set the ticket status and follow up date before sending.
  5. Quality standard: the customer could forward your reply to their boss without embarrassment, and a second agent reading the ticket knows exactly what happened.
  6. Exceptions: angry customer threatening public reviews, escalate to the team lead before replying. Suspected fraud, do not accuse, flag and escalate.

Notice what the example does not contain: no company history, no motivational paragraphs, no explanation of what customer support is. An SOP is a tool for the moment of work, and every line either helps the work or is cut.

The 5 mistakes that make SOPs useless

Writing them like essays. Long paragraphs hide the steps. If a reader has to mine a paragraph for the action, rewrite it as numbered steps.

Documenting the ideal instead of the real. An SOP for the process you wish you had will be ignored by the team running the process you actually have. Document reality first, improve it second, and update the document as the improvement lands.

Writing them yourself, alone, for other people's jobs. The person doing the task knows where the bodies are buried. Owners who dictate SOPs from above get documents that describe a company that does not exist.

No owner and no review date. Tools change quarterly. An unowned SOP library is accurate for about ninety days and fiction after that.

Trying to document everything at once. A fifty document launch overwhelms the team and dies. Ten procedures covering the ten most painful tasks, tested and used, beat two hundred untested ones. This is the same discipline behind deciding what to systematize first when a business is growing, which we cover in our guide to scaling a support team with data.

When the SOP work outgrows you

There is a point, usually somewhere past ten people, where keeping the operation documented and improving is a job in itself, and it lands on the owner at exactly the moment the owner has the least time for it. That is the work our operations management service exists to take over: documenting how your business runs, training the team on it, and keeping the system true as you grow. If you are not there yet, our breakdown of what a fractional operations manager costs shows the part time route. Either way, start with one SOP this week. The task that interrupted you twice today is the right one.

Frequently asked questions about writing SOPs

How long should an SOP be?

As long as the task requires and no longer. Most useful SOPs run one to three pages: a header, ten to thirty steps, a quality standard, and exceptions. If a document passes five pages, it is usually two procedures wearing one title, so split it.

What is the difference between an SOP and a checklist?

A checklist is the short, tick as you go version used during the work. An SOP is the full reference that explains the steps, the standards, and the exceptions. Good operations use both: the SOP is the source, and the checklist is the daily tool drawn from it.

Who should write a company's SOPs?

The person who does the task best drafts it, the owner or manager tests and approves it, and a named owner maintains it. Writing quality matters less than accuracy: a plainly written SOP that matches reality beats an elegant one that does not.

How often should SOPs be reviewed?

Quarterly for most, and immediately whenever the process, a tool, or a rule changes. Every SOP should carry its owner's name and its next review date on its face, so an expired document is visibly expired.

Do small businesses really need SOPs?

A two person business can survive without them. The moment a third person joins, or the owner wants a holiday without the phone ringing, written procedures stop being bureaucracy and start being the business's memory. The cheapest time to write them is before you desperately need them.

Free PDF download: SOP Template and Writing Checklist

A fill in SOP template plus the writing checklist that produces procedures people can actually follow.

Download the PDF

Want your operations documented, trained, and kept true?

Our operations management service does this work inside growing businesses: documenting how the work works, training the team on it, and keeping the system accurate as you scale. It is the same discipline we used to grow a remote support operation from 30 to more than 200 agents while handling 10,000 plus customer interactions a day.

Related: Operations management service · Fractional operations manager cost · Scaling a support team with data · 24/7 support vs business hours support

WhatsApp Us
WhatsApp Us Discuss Your Requirements