You built your business by figuring things out as you went, and that worked. But at some point, the way everything runs – every process, every step, every “here’s how we handle that” – ended up stored in exactly one place: your head. The moment you want to bring someone on to help, whether that’s a virtual assistant or a part-time contractor, that becomes a real problem. This article will walk you through how to create a Standard Operating Procedure – think of it as a written recipe for a repeating task in your business – so that anyone you bring on can do that task the way you want it done, without needing you to explain it from scratch every single time.
What an SOP Actually Is (and What It’s Not)
A Standard Operating Procedure – SOP for short – is simply a written record of how a specific, repeating task gets done in your business. Not a general description, but the actual steps, in the actual order, the way you specifically want them done. Think of it like a recipe: if you hand it to someone who has never cooked that dish before, they should be able to follow it and get the same result every time.
It is worth clearing something up right away: an SOP is not the same as a to-do list. A to-do list tells you what needs to happen. An SOP tells you how to make it happen, and why each step matters. That difference is what makes it actually useful for delegation.
Many small business owners assume SOPs are something only large companies with HR departments and operations managers need to worry about. The opposite is true. When you have a small team – or no team yet – there is even less room for tasks to be done inconsistently or for important steps to be missed. A solopreneur handing off their inbox management to a VA for the first time needs an SOP far more than a corporation with a dedicated training department does.
To make this concrete: an SOP is not a lengthy formal document that requires special software or a consultant to produce. It does not need to cover every possible situation or exception on the first try. A single page describing how you respond to a new client inquiry, or how you send your monthly invoices, already qualifies. Simple, specific, and written down – that is all it needs to be to start working for you.
Why Your Business Specifically Needs SOPs Right Now
If you have ever thought “it would take me longer to explain this than to just do it myself,” you have already identified exactly why SOPs matter. That feeling – reasonable as it is in the moment – is the single biggest reason business owners stay stuck doing tasks they should have handed off years ago. The explanation only takes too long once. After that, the SOP does the explaining for you.
Think about what actually happens when you try to bring someone on without any documented processes. You send a task, they do it differently than you expected, you spend time going back and forth, you end up redoing parts of it yourself, and you walk away thinking delegation does not work. But the problem was never the person – it was the absence of a clear standard for them to follow. That is what an SOP provides.
There is also a real financial cost to undocumented processes that is easy to overlook. Every time a task lands back on your desk because no one else knows how to handle it, that is time you are not spending on client relationships, on business development, on the partnerships and events that actually grow your revenue. Administrative tasks done repeatedly without a system quietly consume hours that could be used elsewhere.
For service businesses specifically – whether you are in construction, coaching, or running a foundation – the tasks that cause the most pain tend to be the same ones: bookkeeping entries that get done differently each month, client emails that go out with inconsistent information, invoices that are delayed because the process lives only in the owner’s head. These are exactly the tasks that a well-written SOP can lift off your plate for good.
And if control is a concern – which it is for most business owners, and understandably so – an SOP is actually how you protect it. You are not handing over control when you write an SOP. You are defining precisely what your standard looks like, so that whoever does the task is working to your specification, not guessing at it.
Before You Write Anything – The Task Brain Dump
Before you open a document and try to write an SOP, there is one thing worth doing first: getting everything out of your head and onto a page. This is not the SOP itself – it is just a list of every repeating task you currently handle personally in your business. No filtering, no organizing, just a full honest inventory.
Set a timer for 15 minutes and write down everything you do on a regular basis. To help jog your memory, think across these categories: client communication, invoicing and bookkeeping, scheduling and calendar management, social media and content posting, website updates, and file organization. If you do it more than once, write it down.
Once you have that list, look for what could be called a “delegation candidate” – a task that repeats on a schedule or trigger, follows a consistent set of steps, and does not require your personal expertise or relationships to complete. Sending a monthly invoice is a delegation candidate. Having a strategic conversation with a long-term client is not. The distinction matters because SOPs work best for tasks where the process is the point, not the judgment call.
From your list, pick one task to document first. The best starting point is either the task you have been meaning to delegate the longest, or the one that costs you the most time each week. Resist the urge to start with something complex. A task that takes under an hour to complete and happens on a predictable schedule – that is your ideal first SOP. Getting one finished builds the confidence and the habit before you move on to anything more involved.
The Anatomy of a Simple, Usable SOP
A good SOP does not need to be long, but it does need to include the right information. Here is what every SOP in your business should contain, explained in plain terms.
A specific task name. Not “invoicing” – that is too broad. Something like “Sending Monthly Invoices to Retainer Clients” tells whoever is reading it exactly which task this document is for, with no room for confusion.
A purpose statement. One or two sentences explaining why this task matters and what a successfully completed outcome looks like. For example: “This task ensures that all retainer clients receive their invoice by the first business day of each month, so that payments are received on time and cash flow stays predictable.”
Who is responsible. Write the role, not the name. “VA” or “admin support” rather than a person’s name. This keeps the SOP useful even as your team changes.
When it happens. The trigger or the schedule that kicks the task off. “Every last business day of the month” or “within two hours of receiving a new client inquiry” – specific enough that the person doing it never has to guess when to start.
What needs to be in place before starting. This is everything required to complete the task: logins, templates, files, tools, information from another person. Listing these upfront prevents the task from stalling halfway through because something was missing.
Step-by-step instructions. Written as if for someone who has never done this before – not because they are not capable, but because specificity prevents mistakes and eliminates the need for clarifying questions. More on how to write these steps in the next section.
Common mistakes and exceptions. The things that occasionally go wrong, the edge cases, the “oh, and one more thing” details that currently live only in your memory. This is where the real expertise gets captured.
Where the finished work goes. The exact folder, the file naming format, who gets notified when the task is complete. Without this, tasks get done but never quite land in the right place.
How to Write the Steps Without Overthinking It
The step-by-step section is where most people get stuck. They either write steps so general that they are useless, or they get paralyzed trying to make it perfect before they have even started. Neither approach helps. Here is a simpler way in.
The most effective method is called “do it and document it.” The next time you perform the task, record each step as you go. You can type notes in a separate window, speak into a voice memo on your phone, or record your screen while you narrate – whichever feels most natural. You are not writing a polished document yet. You are just capturing what you actually do, in the order you actually do it. The polish comes later.
When you write the steps themselves, start each one with a verb – an action word. Open, click, copy, paste, send, save, check, confirm, attach. This makes each step scannable and leaves no room for ambiguity. “Send the invoice” is not a usable step. “Open QuickBooks, locate the client account, select the current month’s invoice, confirm the amount matches the retainer agreement, and click Send” – that is a usable step. The standard to aim for is this: the person following your SOP should be able to complete the task without sending you a single question. If they would need to ask, the SOP needs more detail.
Some tasks involve conditions – situations where the next step depends on something else being true first. You do not need a complicated diagram to handle this. Simple “if/then” language works perfectly well. For example: “If the client has an outstanding balance from the previous month, add a note to the invoice before sending. If the balance is current, proceed directly to step eight.” Clear, readable, and easy to follow.
One final reminder: your first draft does not need to be perfect. It needs to be accurate and complete. Spelling, formatting, and polish can come after. Getting the real process documented correctly is the only goal the first time through.
The Tools You Can Use (That You Probably Already Have)
Good news: you do not need new software, a subscription to another platform, or any technical expertise to store and manage your SOPs. The tools you already use are almost certainly enough.
Google Docs or Microsoft Word are the simplest starting point and work well for the vast majority of small businesses. Create a shared folder – in Google Drive or a cloud storage service like Dropbox – organized into categories that match your business: Admin, Bookkeeping, Client Onboarding, Content, Website. Each SOP lives in its own document inside the relevant folder. That is a complete, functional SOP system.
Notion or ClickUp are worth considering if you already use one of these tools for managing your projects and tasks. Both allow you to store SOPs alongside your active work, which makes them easier to find and reference. That said, if you are not already using these tools, there is no reason to start just for SOPs.
Loom is a free screen recording tool that lets you record your screen and your voice at the same time. For tasks that are easier to show than describe – navigating a piece of software, for example, or walking through a multi-step website update – a Loom recording can serve as the SOP on its own, or sit alongside a written version as a reference. Your VA watches it once and knows exactly what to do.
The only rule that matters here is this: the best tool is the one you will actually use and that your VA or team member can easily access. A simple folder of Google Docs that everyone can find is more valuable than a sophisticated system that nobody opens.
How to Hand Off an SOP Without It Falling Apart
Writing the SOP is only half of the process. How you hand it off determines whether it actually works in practice.
The first time a task gets delegated, walk through the SOP together – share your screen, go through each step, and answer any questions that come up in real time. This does not need to be a long meeting. Ten to fifteen minutes is usually enough. After that walkthrough, step back and let the person run the task independently using the document.
Before they start, ask them to follow the SOP exactly as written and to flag anything that is confusing, missing, or unclear. This is called a “test run,” and it is how the SOP gets better – not a sign that it was written poorly. Every gap they find is a gap that would have otherwise turned into a question, a mistake, or a task landing back on your desk.
The most common mistake at this stage is jumping in to answer questions that the SOP should have already answered. When a question comes in, resist the urge to simply reply. Instead, update the SOP with the answer and then point the person to the updated document. After one or two rounds of this, the questions stop – because the document now contains everything they need.
Make sure the SOP also defines what “done” looks like. Where should the finished work be saved? What file name should it use? Who should be notified, and how, once the task is complete? Without these details, tasks get completed but not properly closed out, which creates its own set of follow-up work.
A well-written, properly handed-off SOP is what makes monthly check-ins and asynchronous communication – that is, communication that does not happen in real time, like email or task management messages – actually viable. When the process is documented, you do not need to be available to answer questions in the moment. The document handles that for you.
Keeping SOPs Current Without It Becoming Another Task
SOPs are only useful if they reflect how your business actually operates right now. A document that describes a process you changed six months ago is not just unhelpful – it actively causes confusion and erodes trust in the system you have built.
The simplest rule to adopt is this: any time a process changes, the SOP gets updated before the task runs again. Not after. If you update the SOP after the task has already been done the old way, you create a window where the documented process and the actual process do not match – and that is where mistakes happen.
Once a VA or team member is regularly running a task, make them responsible for flagging when the SOP needs updating. They are closest to the process and will notice first when something no longer matches reality. Build this into your expectations from the beginning: following the SOP and maintaining it are both part of the role.
Set aside 30 minutes once a quarter to review the SOPs that are in active use. Go through each one, confirm it still reflects the current process, and archive anything that is no longer relevant. This is not a large investment of time, and it keeps your documentation from quietly becoming outdated in the background.
Think of SOP maintenance as a sign that your business is growing and your systems are being used. The processes that need updating are the ones that are being run regularly – which is exactly where you want your business to be.
The Tools You Can Use (That You Probably Already Have)
Good news: you do not need new software, a subscription to another platform, or any technical expertise to store and manage your SOPs. The tools you already use are almost certainly enough.
Google Docs or Microsoft Word are the simplest starting point and work well for the vast majority of small businesses. Create a shared folder – in Google Drive or a cloud storage service like Dropbox – organized into categories that match your business: Admin, Bookkeeping, Client Onboarding, Content, Website. Each SOP lives in its own document inside the relevant folder. That is a complete, functional SOP system.
Notion or ClickUp are worth considering if you already use one of these tools for managing your projects and tasks. Both allow you to store SOPs alongside your active work, which makes them easier to find and reference. That said, if you are not already using these tools, there is no reason to start just for SOPs.
Loom is a free screen recording tool that lets you record your screen and your voice at the same time. For tasks that are easier to show than describe – navigating a piece of software, for example, or walking through a multi-step website update – a Loom recording can serve as the SOP on its own, or sit alongside a written version as a reference. Your VA watches it once and knows exactly what to do.
The only rule that matters here is this: the best tool is the one you will actually use and that your VA or team member can easily access. A simple folder of Google Docs that everyone can find is more valuable than a sophisticated system that nobody opens.
Summary
You do not need to have everything figured out before you start. You do not need a perfect template, a new tool, or a full afternoon blocked off in your calendar. You need one repeating task, 20 minutes the next time you do it, and the willingness to write down what you actually do – step by step, in plain language.
That document, however rough it looks on the first try, is your first SOP. It is the beginning of a business that does not depend entirely on you being present for every task. It is what makes real delegation possible – not the kind where you hand something off and it bounces back to you two days later, but the kind where it genuinely gets done, to your standard, without you having to manage every step.
Start small. Start with one task. And let the system build from there.
👉 Not sure which tasks to document first – or how to hand them off once you do? Book a free 30-minute discovery call and we will look at your business together, identify where your time is going, and figure out exactly where a virtual assistant could step in so you can step back.
Your business did not get built by doing everything at once. Getting the right support in place works the same way – one task, one system, one step at a time. Let’s find the right starting point for you.
