SOP Template for Small Business (Free Download) and How to Write SOPs Your Team Uses
Most small businesses already have SOPs. They live in the owner’s head, in a few old Word files nobody opens, and in the habits of the two staff who have been there longest. A good SOP template fixes the format problem in five minutes. The harder part is writing standard operating procedures your team actually opens, follows and keeps up to date.
Below is a free one-page SOP template you can download and use today, a filled-in example, and a practical method for how to write SOPs that stick. It is written for owner-led Australian businesses, including owners who want the business to run without them or plan to sell it in the next few years.
Key takeaways
- An SOP only has value if people use it. Short, step-by-step and easy to find beats long and thorough.
- Record yourself doing the task once, then turn the recording into steps. Do not write SOPs from memory at a desk.
- Give every SOP one owner and a review date, or it will be out of date within a year.
- Keep all SOPs in one searchable place. A shared drive full of loose files is where SOPs go to die.
- Start with the five processes that would break first if you disappeared for a month.
What is an SOP?
A standard operating procedure (SOP) is a written, step-by-step description of how one recurring task is done in your business: who does it, what starts it, which tools they use, and how they know it is finished. Quoting a job, onboarding a new customer, running payroll, closing out a job on site and chasing an overdue invoice are all good candidates.
An SOP is not a policy. A policy says what the rule is (“quotes over $20,000 need owner approval”). An SOP says how the work gets done, step by step, by whoever is doing it that day. You need far more SOPs than policies, and they are far more useful day to day.
What goes in a small business SOP template
Most templates online are built for large organisations with compliance teams. They have fifteen sections, approval signatures and a scope statement. In a business of five to fifty people, that length is the reason nobody reads them. Our SOP template keeps only the sections that earn their place:
| Section | What to write | Why it matters |
|---|---|---|
| SOP title | The task, in plain words. “Following up a sent quote”, not “Sales Process v2”. | People search for the task, not your document name. |
| Process owner | One named person. | If everyone owns it, nobody updates it. |
| Last reviewed | Date, plus the next review date. | Tells the reader whether to trust it. |
| Purpose | One or two sentences on why it exists and what good looks like. | Helps staff make sensible calls when something is not covered. |
| When this runs (trigger) | The event or time that starts it. | Stops tasks being forgotten because “nobody told me”. |
| Who does it | The role, plus a backup. | Holidays and sick days stop being a crisis. |
| Tools and logins needed | Software and files by name. Never passwords. | Shows what access a new person needs on day one. |
| Steps table | Step, who, how, done when. | The core of the SOP. “Done when” removes guesswork. |
| Exceptions and escalation | What can go wrong and who decides. | Stops every odd case landing back on you. |
| Related SOPs | What comes before and after. | Links single tasks into a whole process. |
| Version history | Date, who changed it, what changed. | Shows the SOP is alive and maintained. |
One note on the tools section. Write the name of the system (“Xero”, “the quoting spreadsheet in the Sales folder”), and point to your password manager for access. Passwords in SOPs end up in emails, printouts and old laptops.
How to write SOPs your team will actually use
Knowing how to write SOPs is less about writing skill and more about method. These six habits make the difference between a document library and a business that runs on its procedures.
1. Record yourself doing it once
Do not sit at a desk and try to remember how you quote a job. You will skip the steps you do on autopilot, which are usually the ones a new person gets wrong. Instead, the next time you do the task, record your screen and talk through what you are doing and why. Phone video works for anything physical. Ten minutes of recording captures more than an hour of writing from memory.
This is where AI earns its keep. A transcription tool plus an AI assistant can turn that recorded walkthrough into a draft SOP in minutes, already split into steps. You still need to check it and fix the details, but editing a draft is much faster than starting from a blank page.
2. Write it as steps, not paragraphs
Each step starts with a verb and does one thing: “Open the job in the CRM”, “Send the follow-up email using the Quote Follow-Up template”. If a step needs more than two lines, it is probably two steps. Add a screenshot only where the screen is genuinely confusing.
3. One owner per SOP
The owner is not necessarily the person who does the task. They are the person responsible for keeping the SOP accurate. When the software changes or the process improves, they update it. Pick the person closest to the work, not the most senior.
4. Put a review date on every SOP
Every six or twelve months is usually right. Put the review in the owner’s calendar or task list, not just on the document. A review can take five minutes: read it, check it still matches reality, update the date.
5. Store everything in one searchable place
Pick one home for your SOPs: a wiki, a shared drive with a clear folder structure, or your project management tool. The test is simple. Can a staff member find the right SOP in under thirty seconds by searching for the task? If not, they will ask you instead, and the SOP has failed.
6. Test it on someone who has never done the task
Hand the SOP to someone else and watch them follow it without help. Every question they ask is a missing step. Fix it, then you are done.
Which SOPs to write first
Owners who try to document everything at once usually stall after a dozen SOPs. A better approach is to start with the five processes that would break first if you vanished for a month. Ask yourself:
- Which tasks only I know how to do?
- Which tasks would cost us money or customers within two weeks if they stopped?
- Which questions do staff ask me most often?
For most small businesses, the first five land somewhere in this list: quoting and pricing, following up quotes and leads, onboarding a new customer, invoicing and chasing payment, and scheduling or job allocation. Write those, get them used, then move on. Our guide to reducing owner dependency walks through how to find these tasks systematically over two weeks.
Worked example: quote follow-up SOP
Here is the template filled in for a common process that often lives entirely with the owner. Notice how short it is.
SOP title: Following up a sent quote
Process owner: Sales coordinator
Last reviewed: 1st October 2026. Next review: 1st April 2027
Purpose: Every quote gets a fast, consistent follow-up so good jobs are not lost to silence. Done well, every quote ends as won, lost (with a reason) or parked with a date.
Trigger: A quote is sent from the quoting system.
Who does it: Sales coordinator. Backup: office manager.
Tools needed: CRM, quoting system, email templates folder, phone.
| Step | Who | How | Done when |
|---|---|---|---|
| 1. Create a follow-up task for 2 business days after sending | Sales coordinator | CRM task on the deal | Task exists with a due date |
| 2. Call the customer to check the quote arrived and answer questions | Sales coordinator | Phone, call notes in CRM | Call logged with outcome |
| 3. If no answer, send the follow-up email | Sales coordinator | “Quote Follow-Up 1” email template | Email sent and logged |
| 4. Second follow-up 5 business days later | Sales coordinator | Call, then “Quote Follow-Up 2” template | Logged in CRM |
| 5. Mark the deal won, lost or parked | Sales coordinator | CRM deal stage, loss reason field | No quote older than 14 days without a status |
Exceptions: Customer asks for a price change: send to the estimator, do not discount on the call. Quote over $20,000: owner makes the second call. Complaint during follow-up: log it and pass it to the office manager the same day.
Related SOPs: Preparing a quote. Booking a won job.
Once a process like this is written and running, steps 1, 3 and 4 are good candidates for automation in your CRM. Document first, then automate. Automating a process nobody has written down just makes the confusion faster.
Common SOP mistakes
- Writing for an auditor instead of a new starter. If a capable new hire cannot follow it on their first week, rewrite it.
- Documenting the ideal process, not the real one. Write what actually happens, then improve it. Staff ignore SOPs that describe a business they do not recognise.
- One giant operations manual. Nobody reads a 90-page manual. Short SOPs, one per task, linked together, get used.
- No owner and no review date. The SOP is right on the day you write it and slowly wrong after that.
- Writing them all yourself. If you write every SOP, the business still depends on you. Get the people doing the work to draft and own them.
Why SOPs matter for owner dependency and selling
SOPs make your week easier. They also matter a great deal if you plan to step back or sell. NAB Private Wealth found nearly half of Australian SME owners are over 50 and 22% are within five years of retirement age (NAB, Beyond the Business, May 2025). And Pitcher Partners’ Dealmakers 2026 study found succession planning is the top driver of mid-market deals, cited by 42% of respondents (Pitcher Partners, Dealmakers 2026). A lot of owner-led businesses will change hands over the next few years.
When a buyer looks at your business, one of the first questions is whether it will keep running after you leave. Documented, used SOPs are some of the clearest evidence they can find. Buyers and their advisers often ask staff how things are done, and compare the answer with the documents. Weak or missing documentation does not stop a sale, but it tends to show up as a longer required handover, more of the price paid as an earn-out, or terms that favour the buyer. Your broker and accountant can tell you how this plays out in your sector.
SOPs are one of the six things buyers check, alongside owner dependency, automation, management visibility, key people and transferability. If you are preparing to sell, our 24-month plan to prepare your business for sale shows where SOPs fit, and the operational due diligence checklist lists the documents buyers usually request.
FAQ
How long should an SOP be?
As short as it can be while still letting a new person do the task correctly. For most small business tasks, that is one page and five to fifteen steps. If it runs much longer, split it into separate SOPs and link them.
What is the best format for standard operating procedures?
For most small businesses, a simple step table with columns for the step, who does it, how and when it is done. Use a checklist for very simple routine tasks and a flowchart only where there are several decision points. Consistency matters more than format, so use the same SOP template for every process.
Can AI write SOPs for my business?
AI is good at turning a recorded walkthrough, a transcript or rough notes into a clean draft SOP. It cannot know how your business actually works unless you show it. Record the real process, let AI draft it, then have the person who does the task check and correct it.
How many SOPs does a small business need?
There is no fixed number. Start with the five processes that would break first without you, then add SOPs for any task that recurs and that more than one person needs to do. Many small businesses end up with somewhere between 20 and 60 over time.
Conclusion
A good SOP template gets you started. What makes SOPs work is the method: record the real process, write it as steps, give it one owner and a review date, store it where people will find it, and start with the five processes that depend most on you. Do that, and the business stops needing you for every answer.
If you want to see how much your business still runs through you, take the free Saleability Score. It takes about four minutes. Or see the seven areas we systemise, from sales and operations to finance and people.
