If you want a virtual assistant to do great work without constant supervision, you need Standard Operating Procedures — SOPs. These documented step-by-step guides are the difference between a VA who needs to ask a question every 30 minutes and one who works independently and gets things right the first time.
SOPs sound bureaucratic. In practice, they're liberating. When your processes are documented, you can delegate confidently, onboard new help quickly, and catch errors before they become habits. Your business stops depending on memory and starts running on systems.
This guide walks you through exactly how to create SOPs that your virtual assistant will actually use.
What a Good SOP Looks Like
Before you start writing, understand what you're aiming for. A good SOP is not a vague summary of a task. It's a precise, sequential set of instructions that someone unfamiliar with the task could follow and produce a correct result.
A useful SOP includes:
- Title and task description: What is this SOP for, and in what context is it used?
- Who performs it: Which role is responsible for this task?
- When it's performed: Daily, weekly, on trigger, on request?
- Step-by-step instructions: Numbered, specific, with no assumed knowledge
- Tools or resources required: Links to relevant platforms, templates, login guidance
- Expected output: What does a successfully completed task look like?
- Common errors and how to avoid them: Anticipate the mistakes that happen most often
"An SOP isn't finished when the process is documented. It's finished when someone else can complete the task correctly without asking you a single question."
A two-page Google Doc with numbered steps and a few screenshots is more useful than a beautifully formatted 20-page manual no one reads. Clarity beats comprehensiveness.
Step 1: Identify Which Tasks Need SOPs First
You don't need an SOP for every task your VA performs — at least not immediately. Prioritize the ones where errors are costly, where the task is complex, or where you find yourself re-explaining the same thing repeatedly.
Start with:
- High-frequency tasks: Things your VA does daily or weekly — inbox management, social media posting, calendar scheduling
- High-stakes tasks: Things where a mistake has real consequences — sending emails to clients, processing payments, publishing content
- Tasks you hate re-explaining: Anything you've described more than twice
| Priority Level | Criteria | Examples |
|---|---|---|
| High | Frequent + high stakes | Client email responses, invoice creation |
| Medium | Frequent but lower stakes | Research tasks, report formatting |
| Low | Infrequent but complex | Quarterly reporting, annual audits |
Once you have this list, work through it systematically — but don't try to document everything before your VA starts. One or two well-written SOPs for the most important tasks are better than ten rushed ones.
Step 2: Document the Process as You Do It
The fastest way to write an SOP is to capture the process while you perform it yourself. Here's how:
Record a Loom video. Walk through the task while narrating your steps. This takes the same amount of time as doing the task normally, and the video itself can be the SOP or the basis for a written one.
Use a screen recording with voiceover. Tools like Loom, Screencastify, or even QuickTime make this easy. Your VA watches the video to understand the process.
Take screenshots at each step. For tasks that involve navigating software, screenshots annotated with arrows and labels are far more effective than written instructions alone. Tools like Snagit or even simple markup in Preview work fine.
Write the steps as you go. If you prefer text, open a Google Doc and type each step in sequence while you complete the task. Don't try to write it from memory afterward — the details that seem obvious to you will be missing.
Step 3: Write the SOP in Your VA's Language
You know this task better than almost anyone. That expertise is also a liability when writing documentation, because it leads you to skip steps that feel obvious to you but aren't obvious to someone learning the process for the first time.
A few writing principles:
- Start with a verb. Every step should begin with an action word: "Click," "Copy," "Navigate to," "Enter," "Open."
- One action per step. Don't combine two actions in one step — it makes it easy to miss one.
- Avoid jargon unless defined. If you use an acronym or internal term, explain it the first time it appears.
- Add "what good looks like." Include a screenshot or description of the expected result after key steps, so your VA knows whether they've done it correctly.
- Note exceptions. "If X happens, do Y instead" — these edge cases are where most errors occur.
After writing, test the SOP. Have someone unfamiliar with the task attempt to complete it using only your instructions. Note every point where they get confused. Fix those points. Repeat until confusion-free.
Step 4: Organize SOPs So They're Actually Used
An SOP that no one can find is useless. Create a central, shared library where all documentation lives. Options include:
- A shared Google Drive folder organized by category (Admin, Social Media, Client Work, Finance)
- A Notion workspace with a sidebar index
- A ClickUp or Asana project set up as a knowledge base
Give your VA a clear map to this library on day one. Make it part of the onboarding process to read through the relevant SOPs before starting work.
Include the SOP link in your project management tool next to each recurring task. When your VA sees "Publish weekly blog post" on their task list, the SOP for that task should be one click away.
For a full onboarding framework that integrates SOPs from day one, see how to train and onboard a virtual assistant.
Step 5: Keep SOPs Current
Processes change. Software gets updated. Your standards evolve. An SOP based on an outdated version of a tool is worse than no SOP — it actively misleads.
Build SOP maintenance into your workflow:
- Review all SOPs quarterly for accuracy
- When a process changes, update the SOP the same week — not eventually
- Ask your VA to flag any step that no longer matches reality
- Date-stamp your SOPs so you can tell when each was last reviewed
The VA who uses your SOPs daily will often notice when a step is outdated before you do. Encourage them to flag issues and suggest improvements. Over time, your documentation library becomes a living asset that grows more valuable with each revision.
For perspective on how effective delegation structures support your VA's work, see how to delegate tasks to your virtual assistant.
Well-built SOPs are one of the highest-leverage things you can create for your business. They let your virtual assistant work faster, make fewer errors, and operate without constant check-ins — which is the whole point.
If you're ready to put these systems to work with a high-quality VA, Stealth Agents provides vetted virtual assistants who are trained to follow documented processes and integrate smoothly into structured workflows. Visit their website to find the right fit for your business.