Ask a business owner whether they have SOPs and you’ll usually get one of two answers. Either they say “not yet,” or they say yes and then admit nobody has opened the folder since they made it. I’ve been on both sides of that. When I started Virtual Assist USA in 2008, most of our processes lived in my head, and the rest lived in old email threads that only I knew how to find.
SOPs for scaling are a different animal from the checklist you write so a new hire can cover your inbox for a week. Once more than a few people are doing the same work, the procedure has to survive turnover, growth and the fact that you won’t be in the room. That changes how you write them, who owns them and where they live.
Why Most SOPs Never Get Used
Most SOPs fail for the same reason: they were written once, by the person who already knew how to do the job, as a one-time project. They skip the steps that feel obvious to the author, they go stale the first time a tool changes, and nobody is responsible for fixing them. After a while the team learns that the document is wrong, so they ask a coworker instead, and the SOP becomes decoration.
The fix is to treat your procedures as part of how the business runs. When people use a procedure in their daily work, they notice what’s wrong with it and it gets corrected, while one sitting in a folder goes out of date.
Which Processes to Document First
Don’t try to document the whole company at once. Start with the work that meets three tests: it happens often, more than one person touches it, and mistakes cost you money or a client’s trust.
For most small businesses, that list looks something like this: onboarding a new client, sending and following up on invoices, scheduling and confirming appointments, handling a refund or billing dispute, and the weekly reporting someone pulls together on Friday afternoon. If a new person has asked you how to do it twice, it belongs on the list.
If you’re the person the whole team comes to with these questions, you’re probably the bottleneck, and our post on the executive bandwidth problem is worth a read before you start.
What a Useful SOP Includes
The Trigger and the Finish Line
Start each procedure with what kicks it off and what “done” looks like. “When a signed proposal comes back in DocuSign” is a trigger. “The client has a welcome email, a kickoff call on the calendar and a folder in Google Drive with their contract inside” is a finish line. Without those two pieces, people start at different points and stop when they feel finished, which is how a client ends up with a welcome email and no kickoff call.
The Steps, Written for Someone Who Has Never Done It
Write the steps for a smart person who has never worked at your company. Name the tool, the folder, the template and the person to copy. “Send the invoice” leaves too much open. “Create the invoice in QuickBooks using the Monthly Retainer template, attach the timesheet PDF from the client’s Drive folder, and email it from billing@ with the account manager copied” leaves almost nothing open.
A short screen recording next to the written steps helps a lot, especially for anything inside software. People skim text, but they’ll watch a three-minute video of someone doing the task.
The Judgment Calls
This is the part that matters most as you grow. What should someone do when the client’s card declines? When is it fine to extend a deadline, and when does it need a manager’s approval? Write down the decisions that come up, who makes them, and what the default is when that person isn’t available. That’s how you stop being the answer to every question.
Give Each SOP an Owner
Each procedure needs one named person who keeps it accurate. That person doesn’t have to write it or do the task, but when something changes, it’s their job to update the document. Without an owner, nobody updates the document, and it drifts out of date within a few months.
At our company, the people closest to the work own the procedures for that work. They’re the first to notice when a step stops making sense, and they have the most reason to fix it.
Where Your SOPs Should Live
Put your procedures where your team already works. If your team lives in Google Drive, keep them in a shared Drive folder with a simple naming system. If you run projects in Asana, ClickUp or Monday, link the SOP directly inside the recurring task so it’s one click away when someone needs it.
What you want to avoid is a library nobody visits. When the procedure shows up inside the task, people read it, and when it’s buried three clicks deep in a wiki, they ask a coworker instead.
Keep Them Current Without Making It a Project
Set a review rhythm and keep it light. Once a quarter, each owner opens their procedures, checks them against how the work is done today and fixes whatever has drifted. It usually takes less than an hour. Add a “last reviewed” date at the top so your team can tell at a glance whether to trust it.
The other habit worth building is to update the SOP the moment someone finds a gap. If a new team member gets stuck and has to ask, the answer goes into the document that same day. Over time, your procedures get better precisely because people are using them.
If you’re bringing on support for the first time, you don’t need a full system before you start. Our guide to onboarding a virtual assistant in seven days covers the simple version, and you can use AI to draft your first workflows so you aren’t starting from a blank page.
FAQs
What are SOPs for scaling a business?
They’re standard operating procedures written so that a growing team can do recurring work the same way without relying on the owner. Compared with a quick checklist, they include who owns the process, what triggers it, what done looks like and how to handle the common exceptions.
How do I write SOPs for my small business?
Start with the processes that happen often, involve more than one person and cost you when they go wrong. Write each one for someone who has never done the task, name the specific tools and templates, and add a short screen recording for anything done inside software.
How many SOPs does a small business need?
Fewer than you think to start. Five to ten procedures covering client onboarding, billing, scheduling and your most common customer requests will handle most of the day-to-day questions. Add more as new roles and services come online.
How often should SOPs be updated?
Review them once a quarter, and update them immediately whenever someone finds a step that’s wrong or missing. A “last reviewed” date at the top of each document tells your team whether it can be trusted.
Who should own a company’s SOPs?
Give each procedure one owner, ideally the person closest to the work. They don’t have to perform the task themselves, but they’re responsible for keeping the document accurate when tools, people or policies change.
Need Help Building Systems That Scale?
If your processes still live in your head or in a folder nobody opens, we can help you sort out what to document, who should own it and how to keep it current as you grow. Take a look at our business consulting and advisory services to see how we work with growing companies on operations.
