How to Write an SOP for a Small Business: A Template People Will Follow

The owner knows how to handle a refund. So does the longest-serving employee, although she does it a little differently. The new hire guesses. One day a refund is issued twice, and everyone agrees that "we need a procedure". The good news is that a procedure does not need to be a binder. Knowing how to write an SOP that fits on one page and reflects how the work is really done is enough.

What an SOP is for

A standard operating procedure describes how a recurring task is done, step by step. It exists to:

• Get consistent results, whoever does the task.
• Train new people faster.
• Reduce errors in tasks where a mistake costs money or customers.
• Free the owner. A written procedure can be delegated.
• Preserve knowledge when someone leaves.

It is not there to control every movement. Tasks that depend on judgement need guidelines, not a script.

Choose what to document

List your recurring tasks, then rank them by three questions:

1. How often is it done?
2. How many people do it?
3. How bad is a mistake?

Start with the five that score highest. For many small businesses these are: processing an order, handling a customer complaint, issuing an invoice, receiving stock, closing the day's cash and giving a refund.

A one-page template

Title. Name the task plainly: "Issuing a refund".

Purpose. One sentence on why the procedure exists.

When to use it. What triggers the procedure.

Who. The role that performs it and the role that approves, if any.

What you need. Tools, access, forms or information required before starting.

Steps. Numbered, one action per step.

Checks. How to confirm it was done correctly.

Exceptions. What to do in the common unusual cases, and who to ask.

Owner and date. Who maintains the procedure and when it was last reviewed.

Writing the steps

This is where most procedures succeed or fail.

• One action per step. "Open the order and check the payment status" is two steps.
• Start each step with a verb. Open, check, send, record.
• Be specific. "Send the confirmation message using the saved reply 'Order confirmed'" is better than "inform the customer".
• Include the decision points. "If the amount is above Rp 500,000, ask the manager for approval before continuing."
• Say where. Which screen, which folder, which form.
• Use the words the team uses.
• Add a screenshot or photo where a step is hard to describe.

Avoid vague words: "properly", "as needed", "appropriately". If a step needs judgement, say what to consider.

An example

Title: Issuing a refund

Purpose: To return money to a customer correctly and only once.

When: A customer requests a refund and the reason falls within the refund policy.

Who: Customer service performs. The manager approves amounts above Rp 500,000.

You need: The order number, proof of payment and access to the order system.

Steps:

1. Open the order and confirm that it was paid.
2. Check the refund log to confirm that this order has not already been refunded.
3. Confirm the reason against the refund policy.
4. If the amount is above Rp 500,000, send the request to the manager and wait for approval.
5. Record the refund in the order system with the reason.
6. Make the transfer to the account the payment came from.
7. Save the transfer proof to the order.
8. Send the customer the saved reply "Refund sent" with the proof.
9. Add the refund to the refund log.

Check: The order shows the status "Refunded" and the log has one entry for it.

Exceptions: If the original payment account is closed, ask the manager. If the customer requests a different account, ask for written confirmation first.

Nine steps, one page, and step two alone would have prevented the double refund.

Test it

A procedure written at a desk rarely survives contact with the real task.

1. Have the writer perform the task while following the document exactly.
2. Give it to someone who has never done the task. Watch without helping.
3. Note every hesitation and question.
4. Revise.

If a new person can complete the task correctly with only the page in front of them, the SOP works.

Make them easy to find

A procedure that cannot be found in thirty seconds will not be used.

• Keep them all in one shared place with a clear list.
• Name them consistently.
• Link the procedure where the work happens: in the task description, the chat channel or the system itself.
• Print the few that are used at a physical workstation.

Keep them alive

• Assign an owner to each procedure.
• Review at least once a year, and whenever the process, the tool or the policy changes.
• Update after mistakes. When something goes wrong, ask whether the procedure was unclear, missing or ignored.
• Invite corrections. The people doing the task know first when a step is out of date.
• Date every version.

An outdated procedure is worse than none, because people stop trusting all of them.

SOPs and AI assistants

Written procedures have a second use now. An AI assistant that answers customers or prepares work needs the same clarity a new employee does. A well-written refund policy and procedure can be given to the assistant as its instructions, with the approval steps kept for people. Vague procedures produce vague assistants.

Common mistakes

• Writing how the task should ideally be done, not how it is done.
• Trying to document everything at once.
• Long paragraphs in place of numbered steps.
• No decision points, so the first unusual case stops the reader.
• Stored where nobody looks.
• Written once and never updated.

Polynusa lets you keep procedures and policies in the workspace knowledge base, where the team can find them and where the AI assistant uses them as its source when drafting replies. See the pricing page.

Summary

Document the frequent, shared and risky tasks first. Use one page: purpose, trigger, who, what you need, numbered single-action steps, checks and exceptions. Test it on someone new, store it where the work happens, give it an owner and review it yearly.

FAQ

Which tasks should get an SOP first?

Start with tasks that are done often, done by more than one person, or costly when done wrong. Handling a new order, closing the cash register, issuing a refund and onboarding a customer are typical first candidates. Leave rare, low-risk tasks for later.

How long should an SOP be?

One page for most tasks. If a procedure needs more than about fifteen steps, split it into two procedures. A document nobody reads protects no one, and length is the main reason procedures go unread.

Who should write the SOP?

The person who does the task best, with a manager checking that it reflects how the business wants the task done. Then give the draft to someone who has never done the task and ask them to follow it. The places where they get stuck are the places to fix.