How to Write an SOP: A Step-by-Step Guide With Examples

Don't try to document the whole company. Start with processes that are repeated often, are error-prone, or depend on one person's memory. A quick way to choose is to list your recurring tasks and mark each one on three questions:

• Would a mistake here cost money, customers or compliance trouble?
• Does only one person know how to do it?
• Do new hires need to learn it in their first month?

Two or three yeses put a process at the top of the list. Write five SOPs in the first month, not fifty. Consistent use of a few beats a library nobody opens.

Use the same skeleton for every SOP so people know where to look:

1. Title and purpose. One sentence on what the procedure achieves.
2. Owner and last reviewed date. One named owner responsible for keeping it current.
3. When to use it. The trigger that starts the procedure.
4. Roles. Who does which part.
5. Tools and access needed. Systems, logins, forms, and supplies.
6. Steps. Numbered, one action per step, starting with a verb.
7. Decision points. "If X, go to step 6. If Y, stop and call the manager."
8. Done means. How to tell the task is finished correctly.
9. Common problems. Two or three known snags and their fixes.

Keep it to one or two pages. If a procedure needs more, split it into two connected SOPs.

Here's a compact SOP for processing a customer refund at a small online shop.

• Purpose: Refund eligible orders correctly and record the reason.
• Trigger: A customer requests a refund by email or through the help form.
• Roles: Support agent (does steps 1 to 4); manager (approves anything outside policy).

1. Open the order and confirm the purchase date and payment method.
2. Check the refund policy. If the order is inside the window and the item is eligible, go to step 3. If not, send the declined-refund template and stop.
3. Issue the refund through the payment system, using the original payment method.
4. Log the refund with a reason code in the support tracker.
5. Send the confirmation template, including the expected timing.

Done means: the refund appears in the payment system, the tracker is updated and the customer has a confirmation.

The steps are short and start with verbs. The decision point is explicit, and the exit is clear.

Most SOPs fail in the writing, not the idea. These habits help:

• Watch, don't guess. Sit with the person who does the task and write what they actually do. Steps written from memory skip the things experts do without thinking.
• One action per step. "Open the order and check the address and update the status" is three steps.
• Say where things are. Name the exact screen, folder or button rather than "the usual place".
• Use screenshots or short recordings for tool-heavy steps, and keep the text steps too, so the SOP is searchable.
• Write for the newest person. Avoid internal shorthand, or define it once.
• Cut explanation you don't need. Put the why in the purpose line and keep the steps lean.

Then have someone who's never done the task follow it while you watch silently. Every place they hesitate is a step to fix.

An outdated SOP is worse than none, because people trust it. Build in upkeep:

• One owner per SOP. A named person, not a department.
• A review date. Twice a year is enough for most; sooner for anything tied to software that changes often.
• A quick update path. Anyone who finds an error should be able to flag it in a minute, with a comment or a form.
• Retirement. When a process is gone, archive the SOP so it doesn't confuse anyone.

A useful habit is to tie updates to events. Whenever a process changes, a tool is replaced, or a new hire says "that step doesn't work anymore", the owner updates the SOP within the week.

Start with whatever your team will actually open. A shared folder with a consistent naming scheme is fine for a dozen SOPs. Beyond that, choose a category of tool. Process Street turns an SOP into a runnable checklist that assigns steps and due dates each time a process starts, which suits repeat work like onboarding. Trainual suits teams that want SOPs bundled with training, quizzes and role playbooks for new hires. For a direct comparison, see checklist and training tool comparison and the guide to SOP management with Trainual or Process Street.

For more examples, browse the SOP examples for a professional services firm, and pair your SOPs with a written hiring process so new people are trained on them from day one.