If your best staff member went on leave for two weeks, would work carry on as normal, or would customers start to notice? In many SMEs the key processes exist only in one or two people’s heads. A standard operating procedure (SOP) is a written, step-by-step guide to how a task is done in your business. This article covers the signs that you need SOPs, which processes to document first, and a five-step method for writing procedures that staff will actually use.
Signs you need SOPs
- Every new hire is trained differently, depending on who teaches them.
- The same mistakes keep recurring: wrong quotes, missed follow-ups, stock errors.
- Staff check with you before doing almost anything.
- Quality varies between staff, shifts or branches.
- You cannot take a week off without your phone ringing.
What SOPs give you
- Consistency: customers get the same result, whoever serves them.
- Faster training: new staff become productive sooner.
- Less dependence on you: you can delegate with confidence.
- Easier improvement: you cannot improve a process nobody has written down.
- A more valuable business: buyers, investors and banks prefer a business that runs without the owner in every decision.
Which processes to document first
Start with three, not thirty. Choose processes that happen often, affect customers or cash, and depend on one person. Common first choices:
- Order to delivery: from quotation to order, delivery and invoice.
- Getting paid: invoicing, reminders and following up late payers.
- New staff onboarding: everything a new hire needs in the first two weeks.
Good next choices are purchasing and stock receiving, handling complaints, and month-end closing.
How to write a good SOP in five steps
- Watch the work. Sit with the person who does the task best and note every step as they do it.
- Map the flow. Draw it on one page: where it starts, each step, any decisions, and where it ends.
- Write short instructions. One action per line, starting with a verb: “Check the PO number”, “Send the quotation by email”.
- Add the details that cause mistakes. Who does it, which system, deadlines, templates and screenshots.
- Test it. Ask someone new to follow the SOP without help. Wherever they get stuck, fix the wording.
Keep your SOPs alive
An SOP that nobody updates soon becomes wrong, and then nobody trusts it.
- Give each SOP an owner.
- Review it every 6 to 12 months, or whenever a system or supplier changes.
- Keep it where staff actually look: a shared folder, or printed at the workstation.
- Keep it short. If an SOP runs past two pages, split it.
The most common mistake is writing SOPs from memory in an office. Procedures written that way miss the small steps that matter most, which is why the best SOPs come from observing the work itself.
Key takeaways
- Document the three processes that are frequent, customer-facing or cash-related, and dependent on one person.
- Write from observation, not memory, and test every SOP on someone unfamiliar with the task.
- Give each SOP an owner and a review date, or it will drift out of date within a year.
Let us document it for you
Our SOP Development (RM2,500) maps three of your core processes, turns them into written step-by-step SOPs with process maps (Word and PDF), and walks your staff through them. Additional SOPs can be added at RM600 each. Book your SOP project