Pro free for 30 days.No card.Start free →

How to Write SOPs People Actually Use: A Small Business Guide

A practical guide to writing standard operating procedures (SOPs) a small team will really follow: which tasks to document first, which format to pick, how to test a draft, and how to keep every procedure current.

By WorkBOS Content Desk7 min read
Cooks in hairnets working in a clean commercial kitchen with steel equipment (Photo by vitesca on Pixabay)
Photo: vitesca / Pixabay

Most small businesses run on what is in a few people's heads. The owner knows how to onboard a client, the office manager knows how to close the month, and one long-serving employee knows how to fix the thing that always breaks. It works until someone is sick, leaves, or the business grows past what one person can remember.

A standard operating procedure (SOP) is the fix: a written set of steps for a task you repeat. This guide shows how to write SOPs that people really open and follow, which is a different thing from writing SOPs that look impressive in a folder. It is practical, short on theory, and built for teams of 2 to 50.

What an SOP is, and what it is for

The US Environmental Protection Agency's guidance on preparing SOPs describes an SOP as written instructions for a routine or repetitive activity. Its stated benefits translate well to any business: less variation when staff change, easier training, a record of how work was done, and a ready-made checklist for anyone reviewing the work.

Which tasks deserve one

Do not document everything. Start with tasks that are:

  • Repeated often, such as invoicing, order handling, or opening and closing.
  • Costly when done wrong, such as refunds, payroll prep, or anything touching customer data.
  • Done by only one person, which is a single point of failure.
  • Handed between people, where steps are most often dropped.

A good first target is five to ten procedures. Resist the urge to write fifty.

Choose the right format

There is no required format. The EPA guidance says each organization should tailor the format to its own needs. In practice, three formats cover almost everything:

| Format | Best for | Example | |---|---|---| | Numbered steps | A sequence done the same way every time | Processing a refund | | Flowchart | Decisions with "if this, then that" branches | Handling a customer complaint | | Checklist | A short verification list used at a moment of work | Opening the shop |

The EPA guidance adds a useful warning: a checklist is a part of the SOP, not the whole SOP. Attach it to the procedure and say when to use it. The US Agency for Healthcare Research and Quality describes a checklist as a simple form for quickly recording data or required actions, and notes that consistency among the people filling it in matters most.

Write it so it is easy to follow

Use plain, short, active steps

The EPA guidance recommends concise, step-by-step wording in the active voice and present tense. In plain English: one action per step, starting with a verb.

  • Weak: "The refund should be processed by the manager when appropriate."
  • Strong: "Open the order. Click Refund. Enter the amount. Ask a manager to approve anything over $100."

Include the right sections

For an administrative or office procedure, the EPA lists the purpose, scope, a short summary, definitions, responsibilities, the procedure itself, any checklists, records to keep, and references. For a small business that comes down to a one-page template:

  1. Title and ID, for example "SOP-04 Refund a customer".
  2. Purpose: one sentence on why this exists.
  3. Who does it: the role, not a name.
  4. When it applies: the trigger.
  5. Steps: numbered, with screenshots or links where helpful.
  6. Warnings: what can go wrong, repeated at the step where it matters.
  7. Records: what to save and where.
  8. Owner and review date.

Mark warnings where they apply

The EPA guidance separates warnings (risk of injury) from cautions (risk of damaged equipment or invalid results) and repeats them at the critical step. Do the same. If a step can charge a customer twice or delete data, say so at that step, in bold, not in a footnote at the end.

Write it with the people who do the work

The EPA guidance says SOPs should be written by people who actually perform the task, with a team approach for complex processes. Owners who write SOPs alone usually describe how the work should happen, which is not how it does.

A simple writing method

  1. Watch the task once. Note each step as it really happens.
  2. Draft the steps with the person who does it.
  3. Test it. The guidance suggests testing by someone other than the writer. Hand it to a colleague who has not done the task and see where they stall.
  4. Fix the gaps, then approve it.
  5. Publish in one known place.

Approval

The EPA guidance suggests approval by the immediate supervisor plus a quality reviewer. In a small business, that is typically the process owner and you. Record who approved it and when.

Keep SOPs alive with version control

An SOP that is out of date is worse than none, because people follow it. The EPA guidance recommends re-approving an SOP whenever the process changes, reviewing periodically (every one to two years is its example), and archiving procedures you no longer use.

Light document control

  • Put the title or ID, revision number, date and "Page X of Y" on every page.
  • Keep a master list: number, title, version, issue date, author, status, location.
  • Archive old versions so nobody grabs them by accident.
  • Keep a read-only copy for staff so only the owner edits.

A review rhythm

Set a calendar reminder for each SOP's review date. Also review after any incident, any near miss, and any change to a tool you use. If a step changes every month, it may belong in a checklist or a short note rather than a formal SOP.

A starter SOP, step by step

Here is a short example for sending an invoice, to show the level of detail that works.

SOP-07 Send a client invoice

  1. Open the signed quote or project record and confirm the work is complete.
  2. Create the invoice from the quote. Do not retype amounts.
  3. Check client name, address, tax line and payment terms against the contract.
  4. Attach any agreed receipts or timesheets.
  5. Ask the owner to approve invoices over $5,000.
  6. Send the invoice and set a follow-up reminder for the due date.
  7. Save the sent copy to the client's folder.

Warning: Never edit an invoice after sending. Issue a credit note instead.

That is under 100 words and covers the whole task. Compare it with the typical three-page policy nobody reads.

Common mistakes

  • Writing for an auditor instead of the new hire. Write for the person doing the task on a busy Tuesday.
  • Too long. If a procedure runs past two pages, split it into smaller ones.
  • No owner. An SOP without a named owner and review date goes stale.
  • Hidden in the wrong place. If people cannot find it in under a minute, they will ask a colleague instead.
  • Never tested. The first real use should not be the first trial.
  • Documenting what should be fixed. If a process is clumsy, simplify it before writing it down.

How WorkBOS can help

Nothing here needs special software; a shared folder and a calendar are enough. If you already use WorkBOS, SOPs can live in the drives and office suite, so there is one place to find them. Tasks can carry the review reminders, and document signing is handy for recording that a team member has read a new version. The Academy has short lessons on setting up the pieces, and the docs explain each area. Plans start with a free tier, listed on the pricing page.

For related reading, see our guides on onboarding a new employee and client onboarding, both of which are far easier when the underlying steps are written down.

Frequently asked questions

Q: How long should an SOP be? A: As short as the task allows. Most small business SOPs fit on one page. If one runs beyond two pages, split it into separate procedures or move a repeated verification into an attached checklist.

Q: Who should write the SOPs? A: The people who do the work, with you reviewing. The EPA guidance recommends subject-matter experts who perform the task, and testing by someone other than the writer.

Q: How often should we review them? A: Review whenever the process or a tool changes, and at least once a year. The EPA guidance gives every one to two years as an example of a periodic review.

Q: Is a checklist the same as an SOP? A: No. A checklist is one tool inside the SOP. The SOP explains who does the task, when, and how; the checklist helps confirm nothing was skipped. See our quality control checklists guide for how to build one.

Q: Should we use video instead of text? A: Video helps for hands-on tasks, but it is hard to search and update. Keep the written steps as the main version and link a short video from it.

Sources are linked in the text above: US Environmental Protection Agency (Guidance for Preparing Standard Operating Procedures, EPA QA/G-6); Agency for Healthcare Research and Quality (checklist tool).

Run it all from one place

Projects, clients, finance, people and AI employees in one system. Start free, no card needed.

Start free →