There is a moment in every growing virtual assistant business where the owner realizes the bottleneck is their own head. You have more work than hours, you know you should hand something off, and you cannot, because the only place the process exists is in your memory. Writing SOPs is how you get it out of your head and into something a contractor can follow. Most guides on how to write SOPs for a virtual assistant business stop at “record a Loom and write the steps,” which is the right idea and not enough, because a recording of you doing a task fast is not a document someone new can follow.
I have spent time on the operations side of virtual assistant and BPO work, and I have watched owners try to delegate off half-written procedures. It goes the same way every time: the contractor does it wrong, the owner concludes delegation does not work, and they take the task back. The problem was almost never the contractor. It was an SOP that assumed knowledge the writer forgot they had. Here is how to write one that actually transfers.
Table of contents
Open Table of contents
Write the SOP the second time you do a task
The best moment to write an SOP is not when you are drowning and desperate to delegate. It is the second time you do a repeatable task, while it is fresh and you still remember which parts are fiddly. The first time, you are figuring it out. The second time, you notice you are repeating yourself, and that is the signal to capture it.
Waiting until you are overwhelmed produces rushed, thin procedures, which are the ones contractors cannot follow, which sends you right back to doing everything yourself. Writing them a little earlier, when the task is calm, is what makes handing it off possible later. This is a close cousin of which SOPs a VA business needs first, which covers the procedures worth capturing before anything else.
Do it, then document it, then have someone else test it
The method that works has three parts, and most people only do the first two.
Do the task while capturing it. Record your screen while you perform the task the way you normally would, talking through what you are doing and, crucially, why. The why is what separates a checklist from a real SOP, because it lets the contractor make the right call when reality does not match the steps exactly.
Write the steps in order, plainly. Turn the recording into written steps someone can follow without watching a video. Number them, keep each step to one action, and add a screenshot where a word picture is not enough. Write for someone who has never seen the task, because they have not.
Then, and this is the part almost everyone skips, have someone else follow it before you rely on it. Hand the draft to a contractor or even a friend and watch where they get stuck, guess, or ask a question. Every place they stumble is a gap you could not see because you already know the answer. Fix those gaps and the SOP is finally done. An SOP you wrote and never tested is a guess about what is clear.
The knowledge you forgot you have
The single reason SOPs fail to transfer is expert blindness: you have done the task so many times that whole decisions have become invisible to you, so you leave them out. You write “update the client’s report,” and in your head that includes checking the date range, pulling from the right source, and flagging anything unusual, but none of that made it onto the page because it no longer feels like a step to you. It feels like breathing.
The test-it-with-someone-else step exists precisely to catch this. When a contractor stops and asks “which report?” or “pull it from where?”, they are showing you a decision you make automatically and never wrote down. Those invisible decisions are where delegation breaks, and surfacing them is the whole point of writing the SOP well.
What a usable SOP contains
A procedure a contractor can actually follow has a predictable shape. Use the same structure every time so both you and your team know what to expect:
- A title that names the task plainly
- When to do it: the trigger or schedule
- What you need first: the tools, logins, and access
- The steps, numbered, one action each, with the reasoning where a choice is involved
- What done looks like: the definition of a correct result, which most SOPs leave out
- What to do when something is off: the common exception and who to ask
That “what done looks like” line is the one people forget and the one that matters most. Steps tell the contractor what to do; the definition of done tells them whether they did it right, which is what lets them work without checking with you on every task.
Building and maintaining a whole library of these is exactly what the VA Business Owner Full System is for. It includes the hiring and contractor onboarding process, the contractor agreement, and the operational documents an owner needs to delegate, written so the procedures a contractor follows are already in the right shape. You adapt them to your business rather than inventing the format under pressure.
Keep them alive
An SOP is not a monument. The moment you change how you do a task and do not update the document, the SOP becomes worse than useless, because it now teaches the wrong thing confidently. Build a small habit of updating a procedure when the process changes, and let the contractor who runs a task own its SOP, suggesting fixes when reality drifts from the page. A living procedure that matches how the work actually happens is the only kind worth keeping.
Writing SOPs well is what turns a VA who does everything into an owner who has a business that can run without them in the room. It is slow the first few times and it compounds fast, because every procedure you document is a task you never have to personally hold again. That is the whole point of writing them, and it is a core part of moving from doing the work to owning the systems.
Frequently asked questions
When should I write an SOP for my VA business? The second time you do a repeatable task, while it is fresh and you remember the fiddly parts. Waiting until you are overwhelmed produces thin procedures that contractors cannot follow.
What makes an SOP a contractor can actually follow? Steps written for someone who has never seen the task, the reasoning behind choices, and a clear definition of what a correct result looks like. Then test it by having someone else follow it before you rely on it.
Why do my SOPs not work when I hand them off? Usually expert blindness: you leave out decisions you make automatically and no longer notice. Having someone else follow the draft surfaces those invisible steps so you can write them in.
Where should I store my VA business SOPs? Anywhere your team will reliably open, like a single shared Google Drive folder. The tool matters far less than whether the procedure is specific enough to follow and kept up to date.