How to Create SOPs for a Small Business, Step by Step

Most advice on how to create SOPs for small business teams begins with a template. That is the wrong place to start. A standard operating procedure is only useful if the person doing the work can follow it on a busy day without phoning anyone, and a template knows nothing about how your business runs. This guide sets out the order we follow when writing SOPs with owner-led businesses: what to document first, how to capture it, how to write it, and how to make sure people use it.

Start with the processes that cost you most

You do not need a manual for everything. Begin with three to five processes, chosen with three filters: the process happens often, mistakes in it are expensive or visible to customers, and it currently depends on one person's memory. Common first candidates are order processing, customer onboarding, purchase approvals, the month-end close, opening and closing a store, and handling complaints.

Avoid starting with something rare and complicated, such as the annual audit. Your first SOPs should produce a visible improvement within weeks, so the team sees the point of the exercise.

Related: how to make your business run without you →

Capture the process as it actually runs

Do not write SOPs from behind a desk. Sit with the person who does the work, ideally while they do it, and note every step, including the workarounds nobody mentions in meetings. At each step ask three questions: what starts this, what do you need before you can do it, and what do you do when something is missing or wrong. The answers to the third question are where most of the useful content sits.

Record a short screen or phone walkthrough where it helps. Five minutes of video showing someone raise an invoice in your accounting software can replace pages of description, and it is easy to update when the screen changes.

Write it so a new hire can follow it

Good SOPs are short, specific and written for a role, not for the organisation as a whole. This structure works for most of them:

• Purpose: one line on why the process exists and what a good result looks like.
• Owner: the role accountable for it, and who covers when that person is away.
• Trigger: the event that starts it, such as a new order or the first working day of the month.
• Inputs: what must be ready before the first step.
• Steps: numbered, one action per step, each starting with a verb.
• Decision points: what to do if something specific happens, with the rule or limit spelled out.
• Output and check: what the finished result is and how someone confirms it is right.

Write in the language your team uses every day. If your floor staff work more comfortably in Kannada or Hindi, write the procedure in that language; a document people struggle to read will not be followed. Keep each SOP to a page or two. If it runs longer, you are probably describing two processes.

Where a step is a check rather than an action, turn it into a checklist. Checklists are the part of an SOP that people actually look at while they work.

Test the draft on someone new

Hand the draft to someone who has never done the process and ask them to follow it while the usual owner watches without helping. Every time they hesitate or ask a question, the SOP has a gap. Fix the gaps and run the test again. Two rounds are usually enough to turn a draft into something usable, and the person who tested it becomes your first backup for that process.

Roll it out and stay with it

Writing is the easier half. Adoption is where most SOP efforts fade. Brief the team in person, explain why the process changed, and keep the final version where the work happens: a shared drive, a pinned message, a printed sheet at the counter, or a checklist inside software you already use. For the first month, someone should check that the procedure is being followed and collect the points where it causes friction.

With one distribution client, we set inventory thresholds, automated reordering and put a new vendor management process in place, then spent 60 days with their operations team until the new habits held. Within eight months the team had the capacity to open two new locations. That is one client's result, not a forecast for yours, but the lesson carries: the documents mattered, and the 60 days are what made them stick.

Keep every SOP current

An SOP that is never updated becomes a document everyone knows to ignore. Give each one an owner and a review date, and revisit it whenever the tool, the team or the rule behind it changes. Keep a short version note at the top saying what changed and when. To get started this week:

• List every recurring process you can think of and mark the three that cause the most rework.
• Sit with the person who runs the first one and capture it step by step.
• Draft it using the structure above and test it on someone who has not done it before.
• Decide where it will live, who owns it and when it will next be reviewed.

Beyond Basics writes SOPs with owner-led businesses and stays through the rollout. We map how the work runs today, write procedures for the people who will use them, set up the checklists and trackers around them, and review them as the business changes. If you have tried writing SOPs before and they were not followed, that is usually where we start.

See our SOP writing and process consulting service →