How to Write SOPs for a Virtual Assistant (Free Template)

To write SOPs for a virtual assistant, pick one recurring task, record yourself doing it once while talking it through, and have your assistant turn that recording into numbered written steps. Then add three things a recording cannot show: what done looks like, the decisions they can make alone, and what to do when something goes wrong. Test it by letting them run the task without you. That is the whole method, and the template below gives you the format.

What a virtual assistant SOP is (and is not)

An SOP, or standard operating procedure, is a short document that lets someone do a task the same way every time without asking you. For a virtual assistant it is usually one page per task: "Send and chase monthly invoices", "Prepare the Monday sales report", "Book travel for the founder".

It is not a training manual, a company wiki or a list of tips. A good SOP answers four questions:

1. What does done look like? The result, the deadline and the quality bar.
2. What are the steps? In order, with links to every tool and file.
3. What can they decide alone? And what needs your approval.
4. What if something breaks? The common exceptions and who to ask.

If your assistant can't answer those four from the document, it isn't finished yet.

Why SOPs matter more with a remote assistant

In an office, an unclear instruction gets fixed with a quick question across the desk. A remote assistant may be working while you are on calls, travelling or asleep. Every question they can't answer alone becomes a delay, or a guess.

SOPs also protect you. When the work lives in documents rather than in one person's head, holidays, sick days and replacements stop being emergencies. This is the same reason we recommend writing processes down in the first month of onboarding a remote employee.

Which tasks need an SOP first

You don't need an SOP for everything. Start with tasks that pass this test:

• They repeat at least weekly.
• They take more than 30 minutes each time.
• The steps are mostly the same each time.
• A mistake costs something: money, a customer or your reputation.

Good first candidates are invoicing, inbox triage, CRM updates, weekly reports, scheduling with outside contacts and order or refund processing. If you are still deciding what to hand over at all, start with our list of 25 tasks to delegate to a virtual assistant, then write SOPs for the top three.

One-off tasks and judgment-heavy work, such as negotiating with a supplier, don't need a full SOP. A short brief in the task card is enough.

How to write SOPs for a virtual assistant in 6 steps

1. Record the task once

Open a screen recorder (Loom, Zoom or the one built into your laptop) and do the task for real while explaining what you are doing and why. Say the parts you normally skip: "I always check this column first because the export sometimes duplicates rows." Five to fifteen minutes is typical.

Don't script it or redo it. A slightly messy recording of the real task is more useful than a polished one of an idealised version.

2. Have your assistant write the steps

Send the recording to your assistant and ask them to write the numbered steps in the template below. This does three things at once: it saves you the writing, it shows you whether they understood, and it produces the document in their words, which is the person who will use it.

Expect to correct the first draft. That is the point.

3. Add what done looks like

Recordings show the steps, not the standard. Add one or two sentences that define a finished result, with a number where you can:

• "Every overdue invoice gets a reminder by 11am on the 3rd of the month."
• "The report is in the shared folder by Monday 9am, with last week's numbers and a one-line note on anything that moved more than 10%."

4. Write the decision rules

This is the section most SOPs miss, and it is why assistants keep asking permission. Use three levels:

Level	Meaning	Example
Do it	Act and mention it in the daily update	Resend an invoice with a corrected address
Recommend	Prepare it, you approve	Offer a payment plan to a late client
Ask first	Stop and wait for you	Anything about pricing, contracts or legal

Move items up a level as trust builds. The same three levels work across your whole working relationship, as we describe in how to manage a virtual assistant.

5. List exceptions and where things live

Add the three or four things that go wrong most often and what to do about each. Then link every file, folder, template and tool the task uses. Never paste passwords into an SOP. Use a password manager, and for email use delegation: Gmail lets you add a delegate who can work in your inbox without knowing your password.

6. Test it, then lock it

Let your assistant run the task alone using only the SOP. Review the result before it goes out the first two or three times. Every question they had to ask is a gap: add the answer to the document. When a run goes through with no questions and no corrections, the SOP is done. Add a "last reviewed" date at the top.

Virtual assistant SOP template

Copy this into Google Docs, Notion or your task tool. One task per document.

SOP: [Task name]
Owner: [Assistant name]      Last reviewed: [date]
How often: [daily / weekly / monthly, day and time]
Time it takes: [minutes]
Recording: [link]

1. What done looks like
[One or two sentences. Include a deadline and a number.]

2. Before you start
- Access needed: [tools, with links]
- Files and templates: [links]

3. Steps
1. [Verb first. One action per step. Link the exact page.]
2.
3.

4. Decision rules
Do it: [list]
Recommend: [list]
Ask first: [list]

5. If something goes wrong
- [Problem]: [what to do]
- [Problem]: [what to do]
- Anything else: [who to ask, and how]

6. How to report it
[Where to log it, e.g. "One line in the end-of-day update".]

SOP example: chasing overdue invoices

Here is the template filled in for a common VA task, so you can see the level of detail that works.

• What done looks like: every invoice more than 7 days overdue gets a polite reminder by 11am on Tuesday, logged in the tracker.
• Steps: open the accounting tool's overdue report, filter to over 7 days, check the tracker for clients already chased this week, send the reminder template from the shared inbox, update the tracker with date and amount.
• Decision rules: Do it: send the first and second reminder. Recommend: a payment plan or a call from the founder after the second reminder. Ask first: pausing work for a client or mentioning late fees.
• If something goes wrong: the client says they already paid, so check the bank feed, then reply with what you found; the email bounces, so look up the billing contact in the CRM and note it on the board.
• How to report it: "Chased 5 invoices, $X total, 1 needs your call" in the daily update.

Notice that each step starts with a verb and names the exact place to click or look. That is what makes it usable without you.

Where to keep your SOPs

Tool	Good for	Watch out for
Google Docs or Word	Simple, everyone can edit	Hard to find once you have 30 or more
Notion	One linked library with search	Needs someone to keep it tidy
ClickUp, Asana or Trello	SOP attached to the recurring task	Content is spread across many cards
Screen recording only	Fast to make	Slow to scan, goes out of date quietly

Pick one home and link to it from the recurring task on your board. Whatever you choose, keep a simple index: task name, owner, how often, last reviewed.

Common mistakes when writing VA SOPs

• Writing it yourself from memory. You will skip steps you do on autopilot. Record first.
• Steps without a standard. "Send the report" doesn't say when, in what format or how good is good enough.
• No decision rules. Without them, your assistant either asks about everything or guesses.
• One giant document. A 12-page "operations manual" doesn't get read. One task, one page.
• Never updating it. Tools and prices change. An out-of-date SOP is worse than none, because it is followed confidently.

How to keep SOPs up to date

Make maintenance your assistant's job, not yours. Two rules are enough:

1. Whoever runs the task updates the SOP the same day a step changes, and notes it in the daily update.
2. Review one or two SOPs in each weekly check-in. Ask: is anything here wrong, slow or still dependent on you?

For tasks around your own inbox and calendar, the same approach turns into a rules sheet. Our guide to executive inbox management shows what that looks like in practice.

Get SOPs written with a dedicated VA

The biggest reason founders never write SOPs is time. A full-time assistant who records, drafts and maintains them as part of the job fixes that. A dedicated virtual assistant through Zenstack works only for you, during your hours, inside your tools, and builds your process library as they learn each task. If what you really need is someone running your inbox, calendar and priorities, look at a remote executive assistant instead.

We handle vetting, contracts, payroll and weekly check-ins, and if the fit is wrong in the first 30 days we replace them at no extra cost. Rates start at $12 an hour, about $1,920 a month full-time. See pricing, or tell us which tasks you want off your plate.