How to Write an SOP Your Team Will Actually Follow

When the same customer question keeps landing on your desk, you probably have a task that needs documenting. Maybe the closing supervisor knows how to reconcile the till, but the weekend team calls her every Saturday. Or two people handle the same online order in slightly different ways, and the mistake doesn’t show up until a customer arrives.

A standard operating procedure (SOP) gives the next person enough information to complete that recurring task correctly. For a small business, a useful SOP can be a single page. Start with one task that causes delays or repeat questions, watch someone perform it, and write what they actually do. Then check whether another employee can follow it.

Choose one job with a clear beginning and end

“Handle customer orders” is a whole area of work. “Prepare a paid online order for pickup” is a manageable procedure. The second has a recognizable starting point, a person responsible, and a result you can check.

Pick a task that happens often enough to justify documenting, or one where a mistake is particularly costly. In a small shop, that might be opening the register, accepting a return, preparing pickup orders, or handing a completed job to billing. Start with a process employees already perform. Writing instructions for a process you haven’t figured out yet tends to preserve the confusion.

Before drafting, decide when this particular SOP applies. For pickup orders, the trigger might be an order marked paid and ready for preparation. Deliveries, unpaid reservations, and custom orders may follow other instructions. Put those limits in the document so employees can tell when to use it.

Watch the work before writing the steps

Ask someone who regularly performs the task to walk you through an actual job. Pay attention to the small decisions they make without thinking about them. Which record do they open? How do they check quantities? What tells them an order is safe to hand over? What happens when an item is missing?

Observe one normal example and ask about a recent exception. If possible, have the employee explain the reason for each check. You might discover that the team compares the order to a printed packing slip, but nobody has decided whether the slip or the software record is authoritative when the two disagree.

Resolve those decisions before writing the SOP. A procedure cannot reliably guide someone through a disagreement that management hasn’t settled.

Use a short SOP structure

You don’t need a complicated form. For most routine office, shop, and service tasks, these fields are enough to make a procedure usable:

Field	What to record
Task and owner	Name the job and the person who maintains the instructions.
When it applies	Define the starting event and any situations outside its scope.
Before you begin	List the records, materials, tools, and permissions the employee needs.
Steps	Write the actions in the order they’re performed, including checks and handoffs.
Exceptions	Say when to stop and whom to contact if the normal steps cannot be completed.
Done means	Give a result another person can verify.
Version and location	Identify the current copy, owner, and date of the last material change.

These are suggested operating fields, not a universal compliance form. Hazardous work, regulated records, and industry-specific procedures may require additional controls or approvals.

Write actions someone can actually follow

Imagine a neighborhood shop preparing prepaid online orders for collection. A weak instruction says, “Process the order carefully and notify the customer.” It leaves the next employee to decide what “carefully” means.

Here’s a more useful version of that task:

1. Open the order record and confirm the payment and pickup method shown there.
2. Locate the items on the order and compare the item names and quantities with the picking list.
3. If an item is missing, damaged, or different from the record, mark the order on hold and ask the shift manager to resolve it. Do not substitute an item without authorization.
4. Pack the items and label the package with the order reference. Avoid exposing unnecessary customer details on the outside.
5. Update the order status to ready for pickup only after the contents match the record.
6. Send the customer the approved pickup notification.

The specific status labels will depend on your system. Use the ones employees actually see. If the process includes an action on a particular screen, a screenshot can save several sentences, as long as the screenshot is maintained when the interface changes.

Notice that the exception appears at the point where it matters. The employee can stop a faulty handoff before sending a false “ready” message. The procedure should also state who has authority to approve a substitution and how that decision is recorded.

Define what finished looks like

A series of checked steps is helpful, but the person taking over the work still needs to know whether the result is correct. For the pickup example, completion means the package matches the paid order, the record shows the right status, and the customer has received the agreed notification. An unresolved missing item keeps the order on hold.

Write the completion check in the terms the business already uses. If the bookkeeper needs a file at the end of a weekly billing run, name that file and where it’s saved. If the next technician needs an approved job description, identify where they can find it and whose approval is required.

Keep sensitive information out of public or broadly shared SOPs. A procedure can tell employees where to enter a bank detail or customer identifier without repeating that data in a screenshot or example.

Test the draft with another employee

Give the draft to someone familiar with the workplace who hasn’t performed that exact task recently. Provide access to the tools and let them follow the steps without coaching. Ask them to talk through any decision they cannot make from the instructions.

Watch one routine case and one common exception. In the shop example, the routine test is a complete order. The exception is an order with a missing item. The SOP passes when the employee prepares the normal order accurately and puts the incomplete one on hold with the correct handoff, without having to guess.

If they ask a question the document doesn’t answer, repair the underlying instruction and retest that step. If a step is slow because the employee cannot access the correct screen, the fix may be an access change. Longer instructions won’t solve that.

For processes involving workplace hazards, follow the training and authorization requirements that apply to the job. The Occupational Safety and Health Administration’s small-business resources can help employers identify the relevant standards and training obligations.

Put the SOP where people will use it

When introducing a new or revised SOP, give staff time to practice the exceptions. Our process-training guide covers the rollout.

The final SOP should live somewhere the team can find during work, such as a clearly named folder, the relevant job system, or a posted instruction at the workstation. Avoid sending the only copy through a chat message and assuming people will find it a month later.

Name one person responsible for updating the procedure. A dated version and a simple change note help prevent two employees from following different instructions. Tell affected employees what changed, then replace obsolete printed copies or links.

Review the SOP when the underlying work changes: a new booking system, an altered approval limit, a recurring error, or a new handoff. You can also schedule a check for frequently used, high-impact procedures. There is no reason to invent a universal monthly review requirement for every one-page instruction.

If you have dozens of documents, see our guide to process documentation for small businesses for a way to organize ownership, handoffs, and updates across the whole collection.

Copy this one-page SOP starter

Prefer to generate a procedure from your own details? Use the interactive SOP template to build, copy, and save one without starting from a blank page.

Use the text below as the beginning of your first procedure. Fill it out while you observe the task, then test it before making it official.

If your instructions become too detailed for one page, decide whether a separate work instruction or checklist would be easier to use. Keep the detail closest to the person who needs it during the task.

Back to Operations