How to Write Standard Operating Procedures (SOPs) Your Team Will Actually Follow

In many small businesses, the most important knowledge lives in someone's head: how to open the shop, how to handle a refund, which supplier to call when the boiler part is late. That works until the person is ill, leaves or gets too busy to answer the fifth question of the day. Standard operating procedures, or SOPs, are written instructions for repeatable tasks. Done well, they make training faster, reduce mistakes, keep quality consistent and free the owner from being the only source of answers. Done badly, they become a thick manual that nobody opens. This guide shows how to write SOPs people use: which processes to document first, how to capture what really happens, a simple template, how to write clearly, how to test with a newcomer, where to store the documents and how to keep them current. As a bonus, the same documents make an excellent knowledge base for an AI assistant.

Step 1: Choose what to document first

Do not try to write everything. Start with processes that are frequent, risky or often asked about.

Pick five. Finishing five useful SOPs beats starting fifty.

Step 2: Capture how the work is really done

1. Ask the person who does the task best to walk you through it while you watch.
2. Write down every step, including the ones they do without thinking.
3. Note the tools used, the decisions made and what can go wrong.
4. Take screenshots or photos where they help.
5. Ask: what do new people usually get wrong?

Recording a screen or phone video while they work is a quick way to gather the details. You can turn it into text afterwards.

Step 3: Use a simple template

Keep to one page where possible. If a process needs more, split it into smaller SOPs and link them.

Step 4: Write clearly

• Start each step with a verb: 'Open', 'Check', 'Send'.
• One action per step.
• Use the words your team uses, and define any jargon.
• Say what good looks like: 'The receipt shows the refund amount and today's date.'
• Include exact wording for customer messages where consistency matters.
• Use short sentences and lists rather than paragraphs.
• Add a screenshot only if it clarifies.

Decisions need a rule. Instead of 'use judgement', write 'if the amount is under $50, approve it; if it is over, ask the manager'.

Step 5: Test it with a newcomer

The real test of an SOP is whether someone who has never done the task can follow it alone. Give the document to a new or unrelated team member and watch without helping. Note every place they hesitate or ask a question, then fix those steps. Repeat until they succeed. Most first drafts fail this test; that is normal and is exactly what the test is for.

Step 6: Store SOPs where people will find them

• Use one shared location, such as a shared drive or a wiki, with clear names.
• Organise by area: front desk, operations, finance.
• Make them searchable, and link them from the places where work happens.
• Keep a single current version; archive old ones instead of leaving copies around.
• Give access to the people who need it, and restrict who can edit.

If staff regularly ask the same questions, an internal assistant trained on your SOPs can answer them instantly. Crescelo's knowledge base can ingest documents and pages; test it in the playground. For customer-facing documents, see preparing your service menu and price list.

Step 7: Assign owners and review dates

A wrong SOP is worse than none, because people follow it confidently. Owners and review dates prevent slow decay.

Step 8: Train with SOPs, and use feedback

• Use SOPs as the training script for new hires and check off tasks as they are learned.
• Encourage staff to suggest improvements; they know where the steps are unclear.
• When a mistake happens, fix the SOP as well as the mistake.
• Celebrate updates so keeping documents current becomes a habit.

Common mistakes

• Writing documents no one asked for.
• Describing the ideal process rather than the real one.
• Long paragraphs instead of steps.
• No owner, so nothing is updated.
• Hiding them in a location no one checks.
• Never testing with a newcomer.

An example SOP

Notice how short it is. A new team member can follow it on their first day, and the manager can change the limit in one place when policy changes.

Rolling SOPs out to the team

1. Explain why: fewer interruptions, easier training and more consistent service.
2. Introduce one SOP at a time, and let people use it for a week before adding another.
3. Ask the team what is unclear and fix it straight away.
4. Name a champion for each area who keeps the documents current.
5. Review the set together every quarter and retire what is no longer used.

People follow procedures they helped shape. Involving the team in writing and improving them is the difference between a living system and a binder on a shelf.

Frequently asked questions

See how reducing repeated questions helps your team, the knowledge base feature, pricing and how to create a customer onboarding process.

Further reading

• Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.