How to Write an SOP for Your Small Business: A Simple Template
A standard operating procedure, or SOP, explains how a recurring task should be completed. For a small business, the most useful SOP is one someone can follow during the work, with enough context to make the right decisions and enough detail to check the result.
You do not need to document the entire business before improving one handover. Start with a task that repeats, causes questions or keeps coming back with corrections. A short, tested checklist can be more valuable than a long manual nobody opens.
Choose one process with a clear beginning and end
“Marketing” is too broad for a first SOP. “Prepare a newsletter draft from an approved campaign brief” is a manageable process. It starts when the brief is approved and ends when the draft is ready for review.
Other good candidates include acknowledging a new enquiry, preparing a weekly report, uploading a product from approved information or creating a client folder. Choose work you can demonstrate and verify.
Write down the problem the SOP should solve. It might be inconsistent file names, missed links, unclear approvals or repeated questions about where information lives. That helps keep the document focused.
Understand what an SOP should contain
A policy sets a rule or expectation. A procedure explains how to perform the work, while a process describes how activities connect. Business.gov.au’s guide to policies, procedures and processes provides a useful reference for these distinctions.
For your working SOP, include the steps and the relevant rules together where the person needs them. If a publishing approval is mandatory, put it next to the publishing step rather than leaving it buried in a separate document.
A simple SOP template
Title: name the task in plain language.
Purpose: explain why the process exists.
Trigger: state what starts the work.
Owner: identify who performs it and who approves exceptions.
Inputs: link to current source information, assets and examples.
Steps: list the actions in the order they occur.
Checks: define how to verify the output.
Exceptions: explain when to stop and escalate.
Completion: state where the result is recorded.
Maintenance: name the document owner and review date.
The template can live in your existing document or project system. The important part is that people know which version is current and can reach it while doing the task.
Capture the task while it is actually being performed
Work through a real example and note the decisions you make. Include the points that are obvious to you because you have done the task many times. Those are often the details a new assistant cannot infer.
If you use a screen recording, keep it focused on one process and avoid exposing unrelated customer data. Pair the recording with a written checklist so people do not have to replay the entire video to find one step.
Use screenshots only where they clarify the action. Interface images become outdated, so describe the purpose of the step as well as the location of the button.
Write actions that can be observed
“Check the report” leaves too much room for interpretation. “Confirm the date range, compare the total with the source export and flag any missing values” explains what the check involves.
Similarly, “make sure the email is good” can become “check the offer wording against the approved brief, test every button, review the mobile preview and confirm the audience exclusions”. A person can demonstrate whether those checks happened.
Keep each step short. If a step contains several unrelated decisions, break it into smaller actions or link to a separate process.
Worked example: weekly project update
Purpose: give the business owner a reliable view of current work, blockers and decisions.
Trigger: the weekly review deadline.
Inputs: current project tracker, team updates and decision log.
Review tasks due this week and next week.
Confirm that completed tasks have a linked output or verification note.
Ask owners for missing updates rather than assuming a status.
List blockers with the affected task, owner and next action.
Separate decisions needed from information-only updates.
Prepare a summary of completed work, upcoming priorities and risks.
Send the summary through the agreed channel by the review deadline.
Record new decisions in the tracker after the review.
Quality check: each priority has an owner and a date; each blocker has a next action; each completed item has evidence.
Exception: if a critical deadline is at risk, raise it as soon as identified instead of waiting for the weekly summary.
This is an illustrative example. Adapt the review timing and escalation rules to your business rather than copying them without discussion.
Test the SOP with someone who did not write it
Ask another person to follow the document on a small, low-risk task. Watch for missing inputs, unclear language and decisions that still require a guess.
Do not fix every question verbally and leave the document unchanged. Update the SOP so the next person benefits from the same clarification. Testing is how the document becomes a working tool.
Also test exceptions. What should happen if an asset is missing, a link fails or the approval owner is unavailable? A process that only covers the ideal path can fall apart at the first delay.
Keep the document current
Give each SOP an owner and a review trigger. Review after a tool change, a recurring error or a meaningful change in scope. A calendar reminder can help, but it should not be the only reason to update the document.
Record the current version and keep outdated copies out of the main working folder. When you change a critical step, tell the people who use it and confirm they understand the change.
Look at whether the SOP reduces repeated questions and rework. If it is too detailed to use, simplify it. If people still have to guess at a decision, add the missing context.
Frequently asked questions
How long should an SOP be?
Long enough to complete and verify the task, and short enough to use during the work. A straightforward process may need one page; a complex process may need linked sections.
Can a virtual assistant write SOPs for me?
A VA can document a demonstrated process and test it with you. The business owner or responsible specialist should confirm rules and decisions that require their authority.
Make your next handover easier
Use the VA onboarding checklist to connect documentation with access and review. If your processes need practical organisation, talk to VAmazing about systems and business operations support.
