How to Write SOPs Your VA Will Follow (Without Spending Weeks on It)
You blocked out a Saturday to finally write some SOPs. By 4pm you'd written two. One of them was eleven pages long.
On Monday morning your VA sent a message: "Quick question about the welcome email. Which template do I use for VIP clients?"
The answer wasn't in either SOP. So you answered it in whatsapp, like you always do, and the Saturday went into a folder nobody has opened since.
If that sounds familiar, the fix is a different way of writing them. Below is the method I use with clients. You capture the task once while you do it, an AI prompt turns it into a clear, structured SOP, and your VA tests it before it's called finished.
Why most SOPs don't get followed
Most SOPs are written by the person who already knows how to do the task and assumes your VA has a whole lot of business context they simply don’t have. When you've done something a hundred times, half the steps feel too obvious to write down, and those are the steps your VA gets stuck on.
The other reasons I see most often:
They're written in one big push and never updated, so they drift out of date within months.
They're too long to use mid-task. Nobody scrolls through eleven pages to find step 14.
They only cover the smooth version. Nothing tells your VA what to do when the payment fails or the client replies with a question.
They live somewhere your VA doesn't look, so the answer exists but asking via a DM is faster.
In my corporate career in quality systems, a procedure was judged on one thing: could the person doing the work follow it and get the same result every time without needing to ask any questions? That's the standard for your SOPs too. The test is whether your VA can use it at 9am on a Tuesday while you're on a client call and can't be interrupted.
How to write SOPs for your VA in 6 steps
Start with the tasks that interrupt you most
Record the task once (I like to use ‘Snipping Tool’ to record my screen)
Get a transcript
Format it into an SOP with an AI prompt
Check it, then test it with your VA
Store it in an easy to access location where the work happens
Step 1: Start with the tasks that interrupt you most
Don't try to document your whole business. Pick the three to five tasks that pull you back in most often. Look for tasks that:
Happen every week (or more)
Your VA asks about repeatedly
Get redone because they weren't done "your way"
Affect what a client sees, like welcome emails, invoices and follow-ups
Those are the SOPs that give you time back first.
Step 2: Record the task once
You have two options. Pick whichever suits the task and how you think best.
Option 1: Do the task and screen record it. Use Loom or the Snipping Tool's screen recorder. Talk through what you're doing as you go.
Option 2: Talk it through in a voice note. Open a voice note app and explain the task from start to finish, as if you were training someone sitting next to you. This works well for tasks that aren't on a screen, and you can do it on a walk.
Whichever you choose, say why as well as what. "I always check whether they're on the VIP package first, because VIP clients get a different template" is the sentence your VA needs, and it's the one you'd never think to write down.
Also talk through:
What starts the task, and how often it happens
The tools, templates and links you use
What "done properly" looks like
The mistakes people make, and what you'd want to hear about straight away
Step 3: Get a transcript
Loom creates a transcript for every recording. Most voice note apps can transcribe too, or you can run the audio through a transcription tool. Don't tidy it up. The "ums" and tangents are fine, because the prompt in the next step sorts them out.
Step 4: Format it into an SOP with an AI prompt
Paste your transcript into ChatGPT, Claude or your AI tool of choice with this prompt. It turns a rambling transcript into an SOP with the same seven sections every time, so your VA always knows where to look.
Step 5: Check it, then test it with your VA
Read the SOP before it goes anywhere. AI is good at structure and will occasionally misread what you meant, so check:
The standard. If your VA followed every step, would the result meet your standard?
The decisions. Does it cover the moments where the task changes? A different package, a failed payment, a client who doesn't reply.
The questions list. Answer anything the prompt flagged as missing, and add it to the SOP.
Then hand it over. The next time the task comes up, your VA follows the SOP. Every question they ask is a gap. Answer it by updating the SOP first, then send them the link.
The rule that keeps this working: if you answer the same question twice, the answer belongs in the SOP.
Step 6: Store it where the work happens
Keep every SOP in one place, whether that's a Google Drive folder, Notion or your project management tool. Number and name them the same way (for example, "SOP 4: Send welcome pack") so they're easy to find.
Better still, link the SOP inside the recurring task itself. When your VA opens "Send welcome pack" in ClickUp or Asana, the SOP is right there.
Give each SOP an owner and a "last updated" date. When something changes, the SOP changes with it.
The SOP layout your VA can follow
Every SOP uses the same seven sections and a checklist. Your VA learns the layout once, then knows where to find the answer in any SOP you give them.
1. Purpose
2. When This Is Done
3. Tools Required
4. Step-by-Step Instructions
5. Quality Standard
6. Common Errors to Avoid
7. Escalation Rule
8. Task Checklist
Recordings or written SOPs?
Both, used for different jobs.
A screen recording or voice note is the fastest way to capture a process. It's how you get the knowledge out of your head.
As the thing your VA works from, a recording falls short. It's hard to scan when you need step 6. It's hard to update, because one changed button means re-recording the whole thing. And it hides the decision points somewhere in minute four.
Record to capture, use the written SOP to work from, and link the recording at the bottom of the SOP for anyone who wants to watch it.
Common SOP mistakes that cost you time
Documenting the whole business at once. You'll burn out by SOP number six. Start with the tasks that interrupt you most.
Handing the SOP writing to your VA. You get their version of the task. Capture it yourself and let the prompt do the formatting.
Writing SOPs for a process you're about to change. Fix the process first, then document it.
Documenting how you wish it worked. Record what happens now. Improve it once it's on paper.
Answering questions in DMs instead of in the SOP. The answer disappears into a thread and you'll be asked again.
Treating SOPs as finished. They're working documents. If no one has updated one in a year, it's probably wrong.
When writing SOPs isn't enough
SOPs capture how a task is done. They work well when the process behind them is sound.
If your bigger issue is that nobody's sure how client onboarding should run, or every client gets a slightly different experience depending on the week, documenting it will lock in the mess. That's design work, and it comes before the SOPs. I wrote more about this in VA vs OBM vs Systems Specialist: Which One Should You Hire First?.
If you're not sure which tasks to document first, the free VA Priority Planner will help you sort what to hand over and in what order.
If you'd rather have the processes designed and documented properly, with your VA trained on them, that's what we do together in Build Your Dream Team.
