Learning how to write SOPs for a virtual assistant means turning what lives in your head into a written process the VA can follow alone. Record yourself doing the task once, have your VA draft the steps from that recording, then test it on someone new to the work. If they finish with no questions, your SOP works.
Last updated: 2026-06-17
You hired a virtual assistant to get time back. Instead, you spend your mornings answering the same setup questions over and over. That gap almost always comes from one thing: the work was never written down. A standard operating procedure (SOP, a documented step-by-step for a repeatable task) closes that gap. It lets your VA run the task the same way every time, without pinging you.
This guide gives you a real method to document processes for a VA, including the record-then-write technique that cuts your authoring time to almost nothing. You also get a template and a storage plan, plus a maintenance routine so your SOPs never go stale.
Why Most VA Relationships Stall Without SOPs
A VA can only be as good as the instructions you give them. When the instructions live in your head, every edge case becomes an interruption. You become the bottleneck you hired the VA to remove.
The data backs this up. Gallup found that only 12% of employees strongly agree their organization does a great job onboarding new hires. The other 88% are left to guess. A VA who guesses produces inconsistent work, and you end up redoing it.
Good documentation flips the math. Research from Brandon Hall Group shows that a strong onboarding process improves new-hire retention by 82% and productivity by over 70%. SOPs are the backbone of that process. They turn a fuzzy “figure it out” handoff into a clear set of repeatable steps.
There is a cost angle too. Two in five HR managers who do not capture onboarding information in a structured way spend three or more hours per new hire doing manual setup. Multiply that by every task you delegate, and the hours add up fast. An SOP pays that time back permanently.
The Fastest Way to Document a Process: Record, Then Have Your VA Write It
Here is the technique that saves you the most time. Do not sit down and type out a procedure from scratch. You will forget steps, and it will feel like homework.
Instead, do the task while recording your screen with a tool like Loom. Narrate as you go. Say what you click and why you click it. Then show what “done” actually looks like. A five-minute task takes five minutes to capture.
Then send that recording to your VA and ask them to write the SOP from it. This does three useful things at once. Your VA learns the task deeply by transcribing it. You get a draft without typing a word. And the language ends up in the VA’s own words, which makes it easier for them to follow later.
Review their draft, fill any gaps, then approve it. You have just converted a task that only you knew how to do into a documented process, and your VA owns it.
What a Virtual Assistant SOP Should Include
A good SOP answers every question before the VA has to ask. Skip a section and you invite an interruption. Use this structure for each procedure.
| SOP Section | What It Covers | Example |
|---|---|---|
| Title and purpose | What the task is and why it matters | “Weekly invoice reconciliation: keeps AR accurate” |
| Trigger | When to start the task | “Every Monday by 10 a.m. ET” |
| Tools and access | Logins, software, and permissions needed | QuickBooks, shared inbox, Stripe dashboard |
| Step-by-step instructions | Numbered actions with screenshots or a Loom link | 1. Open QuickBooks. 2. Pull last week’s invoices. |
| Definition of done | What a finished task looks like | “All invoices matched, exceptions flagged in Slack” |
| Edge cases | What to do when something is off | “If an invoice has no match, tag the owner” |
| Escalation path | Who to contact and when | “Stuck more than 15 minutes? Message me directly” |
Keep each SOP to one task. A document that tries to cover “everything about billing” becomes unusable. One task, one SOP, every time.
Which Processes to Document First
You cannot document everything at once, and you should not try. Start where the payoff is highest. Prioritize tasks by two factors: how often they repeat, and how often you currently get interrupted about them.
High-frequency, high-interruption tasks go first. Think inbox triage, calendar management, or the recurring reports you rebuild every week. These are the tasks eating your week. Documenting them buys back the most time.
Next, document anything that breaks badly when done wrong. Client communication and payment handling fall here. The cost of a mistake is high, so a written standard protects you.
Leave one-off or rare tasks for last. If you do something once a quarter, a quick Loom is often enough; a full SOP can wait. For a fuller picture of what to hand off in the first place, see our guide on what a virtual assistant can do for your business, which maps tasks worth delegating.
Where to Store SOPs So Your VA Actually Uses Them
An SOP nobody can find is an SOP nobody follows. Storage matters as much as the writing. Pick one central home and put every procedure there.
Your options range from simple to structured:
- Shared doc folder (Google Drive, Notion): cheap, fast, fine for a small library.
- Dedicated SOP tool (Trainual, Whale, Scribe): built for process docs, with versioning and search.
- Project tool wiki (ClickUp, Asana): keeps SOPs next to the work they describe.
Whatever you pick, follow two rules. Give every SOP a clear, searchable title so your VA finds it in seconds. And link the SOP directly inside the recurring task or checklist, so it sits right where the work happens. If you want help structuring a clean handoff system around these documents, our team covers it across the virtual assistants resource library.
How to Keep SOPs Current Without It Becoming a Chore
SOPs rot. Tools change and processes evolve, so a stale document becomes worse than none because it teaches the wrong steps. Build a light maintenance habit so this never bites you.
Make your VA the owner of the library. When they spot a step that no longer matches reality, they update it and note the change. You review, not author. This is the single biggest shift that keeps documentation alive.
Add a “last reviewed” date to every SOP and set a quarterly check. Spend twenty minutes per quarter scanning for anything broken. That small recurring cost beats discovering, mid-crisis, that your billing SOP points to software you stopped using a year ago.
When a managed nearshore provider handles your VAs, this upkeep is built into the model. Documented process is treated as part of the job, not an afterthought. RAM BPO’s onboarding process gets a team operational in 7-10 business days.
Frequently Asked Questions
How do I write an SOP for my virtual assistant?
Record yourself doing the task on screen while you narrate each step. Send the recording to your VA and have them write the procedure from it. Review their draft, then add any missing detail before you approve it. Test the final version by handing it to someone unfamiliar with the task to confirm it works without your help.
What should a virtual assistant SOP include?
Every SOP needs a clear title and purpose, plus the trigger that starts the task and the tools required. Add numbered step-by-step instructions with screenshots. Include a definition of what “done” means, the common edge cases, and an escalation path. Cover those, and your VA can finish the task without interrupting you.
Which processes should I document first for a VA?
Start with tasks that repeat often and cause the most interruptions, like inbox triage or calendar management. Next, document anything costly when done wrong, such as client communication or payment handling. Save rare, one-off tasks for last, since a quick recording usually covers them well enough.
What’s the fastest way to document a process for a VA?
Do not write from scratch. Screen-record yourself completing the task with a tool like Loom, narrating as you go, then have your VA draft the written SOP from that recording. You skip the typing while your VA learns by transcribing, and the procedure lands in language they will actually follow later.
How do I keep my SOPs up to date?
Make your VA the owner of the SOP library so they update documents the moment a step changes. You review rather than author. Add a “last reviewed” date to each SOP and run a short quarterly check, spending around twenty minutes scanning for any outdated tools or broken steps.
Where should I store my VA’s SOPs?
Keep every SOP in one central, searchable home. That can be a shared Google Drive or Notion folder, a dedicated tool like Trainual or Scribe, or your project tool’s wiki. Give each document a clear title and link it directly inside the recurring task, so the instructions sit exactly where the work happens.
Key Takeaways
- Write SOPs by recording the task first and having your VA draft the steps from the recording, which saves your time and deepens their understanding.
- Every SOP needs a purpose, a trigger, tools, numbered steps, a definition of done, edge cases, and an escalation path.
- Document high-frequency, high-interruption tasks first; save rare one-offs for last.
- Store all SOPs in one searchable place and link each one inside the task it describes.
- Hand library ownership to your VA and run a quick quarterly review so documents never go stale.
Strong SOPs are what let a virtual assistant work without you hovering. If building and maintaining that documentation feels like one more job you do not have time for, that is exactly what a managed nearshore partner removes. RAM BPO provides college-educated, English-speaking VAs inside a fully managed model, so process documentation and upkeep come standard. To see how the pieces fit together, start with our guide to nearshore outsourcing and reach out when you are ready to delegate for real.
Related Reading: How to Delegate as a Business Owner Without Losing Control.
