How to Write an SOP for a Small Business

A useful SOP should let another person complete a repeatable task correctly without relying on the process owner to fill in missing details.

1. Pick the right process

Do not begin by documenting everything. Start with work that is repeated, expensive to get wrong, difficult to delegate, or dependent on one person's memory.

• Lead intake and follow-up
• Customer onboarding
• Quoting, invoicing, or collections
• Employee onboarding
• Quality-control checks
• Recurring reporting or meetings

2. Define the outcome before the steps

Write one sentence describing what must be true when the SOP is complete. This becomes the completion standard and keeps the procedure focused on an outcome instead of a pile of actions.

3. Name the trigger and owner

Every SOP should answer two questions before the first step: what starts this process, and who is responsible for making sure it happens?

Trigger examples: a signed agreement, a new web form, an invoice due date, a completed job, or a confirmed employee start date.

Owner: use a role rather than a person's name when possible so the SOP survives staffing changes.

4. List the required inputs

Document the information, tools, files, permissions, approvals, or templates needed before the work begins. Missing inputs are a common reason employees stop following an SOP and ask for help instead.

5. Write the normal path in numbered steps

Each step should contain an action that can be observed or verified. Avoid vague instructions such as “handle the request,” “follow up as needed,” or “make sure everything is correct.”

6. Add decision points and exceptions

A numbered list only describes the happy path. Good SOPs also explain when the normal procedure stops, who can make a judgment call, and what must be escalated.

• What if required information is missing?
• What if the customer requests something outside policy?
• What if the system is unavailable?
• What dollar amount or risk level requires approval?

7. Add a quality check

Explain how the operator verifies that the work is correct before closing the task. A quality check should be specific enough that two people would reach the same conclusion.

8. Define what “done” means

The completion standard is different from the final action. “Send the email” is an action. “The customer has been sent the approved confirmation and the next action is recorded” is a completion standard.

9. Test the SOP with someone else

Give the SOP to a person who understands the role but did not write the document. Watch where they hesitate, make assumptions, or ask questions. Those are gaps in the SOP.

10. Assign a review date

SOPs become unreliable when tools, owners, policies, or workflows change. Give each SOP a named owner and a review date so outdated instructions can be caught before they cause mistakes.

A simple SOP structure

For most small-business processes, this structure is enough:

1. SOP title
2. Owner
3. Purpose
4. Trigger
5. Required inputs
6. Procedure
7. Quality check
8. Completion standard
9. Exceptions and escalation
10. Related resources
11. Last reviewed

See complete examples

See seven practical small-business SOP examples, or start with the free copy-ready SOP template.

Building more than one SOP?

The Small Business SOP Builder Kit is designed for building a repeatable SOP library rather than writing each document from scratch.