How to Write an SOP Your Virtual Assistant Can Actually Follow

What is an SOP for a virtual assistant, and why do you need one?

An SOP is a written set of steps for one repeatable task. It says who does the task, what starts it, which tools to use, and what a finished result looks like. It is not a policy manual. Think of it as the instruction sheet you would hand a capable stranger on their first morning.

A virtual assistant often works in a different time zone, so a quick question can cost half a day. So the SOP replaces that question. If you are still deciding whether to hire, start with the guide to hiring a virtual assistant in the Philippines.

The cost of unclear work is measurable. Asana’s 2023 Anatomy of Work Global Index found that knowledge workers spend 58% of their day on coordination instead of skilled work. Those workers also estimated that better processes could save them 4.9 hours per week. But that is a self-reported estimate, not a measured result.

Written checklists have a stronger record. In a 2009 study across eight hospitals, including one in Manila, a surgical safety checklist went with a drop in complications from 11.0% to 7.0% and in inpatient deaths from 1.5% to 0.8% (New England Journal of Medicine). However, it was a before-and-after study, not a controlled trial, and surgery is not e-commerce. Still, the narrow point holds: a short written list, used every time, catches misses that memory does not.

Which tasks need an SOP for a virtual assistant first?

Start with tasks that repeat, follow rules, and cost you something when they go wrong. A simple filter: if the task happens weekly or more often, and a mistake touches a customer, an invoice, or your data, write it down first. Order checks and ticket handling for an e-commerce virtual assistant are typical examples.

Task type	Write an SOP now?	Example
Repeats weekly or daily and follows clear rules	Yes, first	Checking new Shopify orders, tagging Gorgias tickets, updating HubSpot deal stages
Rare but costly when wrong	Yes, as a short checklist	Refunds above a set amount, price changes, bulk imports
Needs judgment or taste	Write guidelines and examples, not steps	Replying to an upset customer, choosing featured products
Still changing every week	Wait until it settles	A campaign you are still testing

However, judgment work still belongs with a person. For where AI helps and where it does not, see can AI replace your virtual assistant.

How do you write an SOP for a virtual assistant, step by step?

Use these eight steps. They work, for example, for a Shopify order check, a HubSpot data cleanup, or a weekly report.

Steps 1 to 4: capture the task

1. Name the outcome and the owner. Write one sentence, such as “Every new Shopify order over $200 is checked for address errors before it is fulfilled.” Add who does it, how often, and who covers when they are away.
2. Record yourself doing the task once. Use a screen recording with your voice on. Do not write from memory, because memory skips the steps you do without thinking, such as the filter you always apply first.
3. Turn the recording into numbered steps. Start each step with a verb, such as open, filter, copy, or tag. Keep to one action per step and use the exact name of the menu, field, or button.
4. Attach what the VA needs. Add links, the tool, the permission level, and any lookup table the VA will check against, such as a list of order tags and what each one means. Share logins through a password manager, never inside the document.

Steps 5 to 8: make it safe to follow

5. Write the decision rules. Use if-then lines: “If the address has no unit number, email the customer with template B. If the order total is over $500, stop and message me.” Add one stop-and-ask rule that says when to pause instead of guess.
6. Define done. List what finished work looks like, with one good example and one bad example. End the SOP with a short checklist the VA ticks before closing the task.
7. Test it with your VA. Ask them to follow it without your help and to note every point where they hesitate. Each hesitation is a missing step. Fix it, then run the test again.
8. Give it an owner, a version, and a review date. Put your name and the date at the top. Then review it every quarter, and any time a tool changes its screens.

What does a good SOP for a virtual assistant look like?

Here is a one-page template. Most tasks fit it, so you rarely need more.

Section	What goes in it
Title and owner	Task name, who owns the SOP, and the last review date
Purpose	One sentence on the outcome and why it matters
Trigger	What starts the task: a new order, a Monday morning, a ticket tag
Tools and access	Shopify, Gorgias, HubSpot, or Google Sheets, the permission level, and the password manager entry
Steps	Numbered actions, one per line, with a screenshot or a link to a short recording
Decision rules	If-then lines and the stop-and-ask rule
Definition of done	A checklist and one example of correct work
Escalation	Who to message, in which channel, and what to include
Change log	Date, what changed, and who approved it

Next, here is an example of the steps section for an order check. Swap in your own amounts, tags, and tools.

1. Open Shopify Admin, go to Orders, and filter by Unfulfilled.
2. Open each order over $200 and compare the shipping address with the billing address.
3. If they differ, add the tag review-address and post the order number in your team chat.
4. If they match, add the tag checked.
5. Tick the checklist and log the number of orders reviewed in the tracking sheet.

Should the SOP be text, a checklist, a video, or an automation?

Use the lightest format that still removes the questions.

Format	Best for	Weak spot
Written steps	Tasks with clear rules and many steps	Gets long, and goes stale when screens change
Checklist	Quality checks and high-risk tasks	Does not explain why, or what to do when something is unusual
Screen recording	Showing where to click inside a tool	Hard to search and hard to edit
Automation	Stable rules with the same input every time	Needs setup and monitoring, and breaks when the input changes

Most tasks work best with written steps, a short recording linked from step one, and a checklist at the end. After a task has run cleanly from the SOP for a few weeks, ask whether a tool should do it. A rule such as “tag every order over $500 and notify me” suits a Zapier or Make scenario with multi-step conditional routing, started by a Shopify webhook that sends a JSON payload. Two guides explain the pieces: what a webhook is, with a Shopify example and Zapier vs Make for Shopify. If you want the build done for you, see Zapier and Make automation and Shopify order automation.

What mistakes make an SOP for a virtual assistant fail?

• Written from memory. Skipped steps stay hidden until your VA gets stuck on them.
• No decision rules. Real tasks have exceptions, so without a rule a VA will guess or wait.
• No definition of done. The VA cannot tell whether the work is finished or correct.
• Too long. A 12-page document does not get opened, so keep one task per SOP.
• No owner and no date. An SOP nobody maintains drifts out of date as tools change.
• Written for yourself. Phrases such as “the usual tags” mean nothing to someone new, so name each tag.

How do you know an SOP is working?

Track four numbers for the first month, then adjust the SOP where they stall.

Metric	How to measure	Healthy sign
Questions per task	Count the help requests your VA sends	Falls each week
First-pass error rate	Tasks with mistakes found in review, divided by tasks reviewed	Falls toward zero
Rework time	Minutes you spend fixing finished work	Falls
Time per task	Average minutes to finish	Settles, then stays steady

These are the kind of numbers I track in my own work. From my resume: 95% fewer data-entry errors and about 40% better data reliability at Sales Fury, and 30% faster processing at Airbnb. But they are my results in those roles, not a promise for your account. To test a new VA on a real task before you hand over an SOP, try a trial task. To see where the hours actually go, read whether to use a time tracker with a remote VA.

Frequently asked questions

How long should an SOP be?

Keep it to one task and one to two pages. If the steps run past about 15 lines, split the task into two SOPs. A short document gets opened every time, and a long one gets skipped. Link a screen recording for anything that needs screenshots.

What is the difference between an SOP and a checklist?

An SOP explains how to do a task: the steps, the tools, and the decision rules. A checklist only confirms that each step was done. Use the SOP to teach the task and a checklist at the end to check the work. Also, high-risk tasks need both.

Should I use a video or written steps?

Use both for tool-heavy tasks. A short screen recording shows where to click, and written steps are easier to search, edit, and check against. If you can only make one, write the steps first. A recording is quick to add later, once the steps are stable.

Can AI write my SOP for me?

AI can turn a transcript of your recording into a clean first draft, which saves time. It cannot know your exceptions, the exact menu names in your tools, or your risk limits. Review every step, add the decision rules yourself, and test the draft with your VA before relying on it.

How often should I update an SOP?

Review it every quarter, and again whenever a tool changes its screens or your rules change. Put the review date and an owner at the top. Ask your VA to flag any step that no longer matches what they see, since they use the SOP more often than you do.

When should I turn an SOP into an automation?

Automate when the rules never change and the input is always the same, such as tagging orders over a set amount from a Shopify webhook. Keep tasks that need judgment with your VA. Run the SOP by hand for a few weeks first, so you know the rules are stable.

Sources

• Asana, “Anatomy of Work Global Index 2023” (press release, March 2023)
• Haynes AB et al., “A surgical safety checklist to reduce morbidity and mortality in a global population,” New England Journal of Medicine, 2009 (summary on PubMed Central)
• OHS Online, “Surgical Safety Checklist Drops Deaths, Complications,” January 2009