Most business owners who complain that their VA does not follow processes have the same problem: the processes were never documented clearly enough to follow. A vague verbal explanation is not an SOP. A 40-page policy document no one reads is not an SOP either. A good SOP is specific, actionable, and short enough that a capable person can execute it without asking questions.
Here is how to create SOPs your VA will actually use.
What Makes an SOP Work
An effective SOP answers four questions:
- What is the task? The title and purpose, in one sentence.
- When does it happen? Trigger — what starts this process?
- How is it done? Step-by-step instructions, in order.
- What does done look like? The output or completion criteria.
If an SOP does not answer all four, it is not complete.
The Right Format for VA SOPs
Keep it simple. The formats that work best are:
Numbered step list — best for sequential processes (e.g., how to process a customer refund)
Checklist — best for recurring tasks with multiple independent items (e.g., weekly social media posting checklist)
Loom video + written summary — best for complex tools or visual workflows (record your screen while doing the task once, write the key steps below the video)
Decision tree — best for tasks with conditional logic (e.g., how to handle customer complaints based on severity)
Avoid long prose paragraphs. Your VA needs to be able to scan the SOP while working, not read it like an article.
Writing Your First SOPs: Where to Start
Do not try to document every process at once. Start with the three most frequent tasks and the three highest-risk tasks.
Most frequent: These are the processes your VA will do every day or every week. Even a small improvement in clarity here compounds quickly.
Highest risk: Customer-facing communication, financial transactions, and access to sensitive accounts. These need documented steps even if they happen rarely.
Quick SOP Capture Method
The fastest way to create an SOP is to do the task yourself while narrating:
- Open Loom (free screen recorder)
- Do the task from start to finish
- Narrate what you are doing and why at each step
- Share the Loom link in the SOP document, then write the key steps below it in 10–15 bullet points
A usable SOP for most tasks takes 20–30 minutes to create this way. You do not need a special template or tool.
SOP Structure Template
TASK: [Name of the task]
TRIGGER: [What starts this process — a customer email, a weekly schedule, a new order, etc.]
TOOLS NEEDED: [List of tools or accounts used]
OUTPUT: [What should exist when this is done — a sent email, a completed spreadsheet, a scheduled post]
STEPS:
1. [First action]
2. [Second action]
3. [Continue until done]
NOTES:
- [Any exceptions, edge cases, or things to watch for]
- [What to do if something goes wrong]
- [Where to get help or escalate]
Making SOPs Easy to Find and Use
The best SOP is useless if your VA cannot find it when they need it. Store SOPs in a shared workspace that is organized logically:
- Notion: Create a "Processes" database with categories and tags — easy to search and update
- Google Drive: A shared folder with clearly named documents works fine for small teams
- ClickUp, Asana, or Monday.com: If you use a project management tool, add SOPs as resources within the relevant tasks
Name documents clearly: "How to Process a Customer Refund" is better than "Refund Process v2 Final."
Getting Your VA to Actually Follow the SOP
There are two reasons VAs do not follow SOPs:
1. The SOP is unclear. If the instructions are ambiguous, your VA will fill gaps with their own judgment — which may not match yours. Review each SOP with your VA before they use it for the first time. Ask them to walk you through how they would complete the task using the SOP. This surfaces gaps.
2. The SOP is outdated. Nothing undermines trust in documentation faster than following a process step-by-step and having it not work because something changed. When your tools, workflows, or standards change, update the SOP immediately.
The SOP Review Rule
Every time you give your VA feedback — "that is not how I want that done" — that is an SOP gap. The feedback itself should trigger an update to the relevant document.
A living SOP library that reflects how you actually work is one of the most powerful assets in a VA relationship. It removes dependency on your constant supervision and lets your VA operate independently with confidence.
When to Create SOPs vs. When to Just Explain
Not every task needs a formal SOP. Use your judgment:
| Write an SOP | Just explain |
|---|---|
| Task done repeatedly | One-time or rare task |
| High stakes or customer-facing | Internal, low-risk |
| Multiple steps or decision points | Simple two-step action |
| Other VAs might need to learn it | Only this VA will do it |
Aim to have SOPs for the core 10–20 tasks that drive your business operations. Everything else can live in quick notes, training calls, or short email explanations.
The business owners with the best VA relationships are almost always the ones with the best process documentation. SOPs are the infrastructure that lets your VA operate independently — and they save you from having the same conversation over and over again.
See our guide on setting clear expectations with a new VA for how SOPs fit into the broader onboarding picture.