Virtual Assistant SOP Templates: 5 Workflows You Can Delegate
It isn't easy to delegate.
Research shows that founders spend 36% time on administrative tasks, even though delegating this work is associated with higher revenue and growth. The problem is that 25% believe that it's “faster if I do it myself”
So, how do business owners take the messy tasks they do automatically, and turn them into steps their virtual assistant (VA) can reliably complete?
Creating a standard operating procedure (SOP) can help.
Start with the virtual assistant SOP template below, or jump straight to one of the five examples and adapt it to your business. Later in the guide, you’ll find tips from founders and VAs we interviewed, as well as what we learned from documenting and testing a workflow ourselves.
Quick answer: What is an SOP and what should it contain?
A virtual assistant SOP (standard operating procedure) is a written guide your VA follows to complete a recurring task the same way each time. It covers the goal and trigger, the tools and access needed, the steps with decision rules, and what finished looks like. A good SOP shares context including what your VA can do alone and when to ask you.
Copy this virtual assistant SOP template
When you’ve done a task dozens of times, it can be hard to know what someone else needs you to explain. Use the template below for a recurring task you want to hand over to your VA.
We’ve added prompts and examples to help you capture the steps, decisions, and exceptions your assistant may need to handle the task independently.
SOP: [Task name]
[Name the specific task you want done. For example: “Log this week’s receipts in the expense tracker.”]
Last reviewed: [Date] | Next review: [Date, or “when a tool or policy changes”]
SOP owner: [The person who reviews or revises this SOP]
Overview
Purpose: [In one sentence, explain why you do this task. Example: “To keep the expense tracker up to date.”]
Trigger & timing: [Say what starts the task and how often it’s done. Example: “Every Friday at 3 p.m., check for new receipts” or “When owner assigns the task in Asana.”]
Expected output: [Describe the end result. Example: Rather than “Expenses updated”, you could say “Every new receipt is logged with the date, vendor, amount, and category.”]
People
Task owner: [Name the person who makes business decisions about this task.]
Performed by: [VA’s name.]
Reviewer: [Optional field. Name the person who reviews the work, if anyone. You may opt for a temporary review period. Example: “Owner for the first two weeks.”]
Escalation contact: [Name who the VA should contact with questions, and where to reach them. Example: “Maya, Slack DM.”]
Tools and access
| Tool | Access needed | How to request access |
|---|---|---|
| [Name the tool.] | [Specify the access needed, such as view, edit, or admin.] | [Say who to ask and how.] |
Keep passwords and other credentials out of the SOP. Share access through a password manager or the tool's own invite.
Before you start
[List what the VA needs first: files, information, approvals or access. Example: "This week's receipts in the Receipts folder and edit access to the tracker."]
Steps
*[Write the steps below. The best way to write the steps is by performing the tasks and noting down the steps or recording yourself doing the task and using the recording to generate instructions.]*
- *[Describe the first action. Typically, start with a verb such as open, find, check, add, or send. Add a screenshot where it may make the step easier to follow.]*
- [Describe the next action. Add a screenshot or video link wherever seeing the screen helps.]
- [Continue adding steps until the task is complete.]
- [End with a step that confirms the action worked. Example: "Refresh the tracker and check the new rows are saved."]
Decisions and exceptions
[Start with the exceptions you already know. This section will expand and you will add more as your VA runs into them. As you build trust, you can also move decisions from "Owner" to "VA."]
| If this happens | Do this | Who decides |
|---|---|---|
| [A situation. Example: "A receipt is unreadable."] | [What the VA does. Example: "Ask the person who sent it for a clearer copy."] | [VA] |
| [An exception. Example: "A receipt is over $500."] | [Example: "Log it, flag the row and message the owner."] | [Owner] |
You may act without asking when: [Describe the decisions the VA can make independently. Example: "If a receipt is a duplicate, skip it and add a note in the tracker."]
Stop and ask when: [Describe situations that need the owner’s decision. Example: "A receipt is missing or the category isn't clear.”]
Never: [List actions your VA should never take, even if they seem helpful. Example: "Delete a row or change a past month's totals."]
Quality check
[Describe what the VA should check before marking the task complete. Make the checks specific enough to verify. Example: “Every receipt has a matching row, and the totals agree.”]
- [Check 1. Example: "Every receipt has a matching row."]
- [Check 2. Example: "The tracker total matches the receipts."]
- [Add a check for another mistake that happens often.]
Report completion
Where: [Say where the VA should report that the task is complete. Example: “#finance in Slack.”]
What to report:[Say what the VA should share when the task is complete. Example: “12 receipts added; 2 need review.”]
Deadline: [Say when the task should be completed or reported. Example: “By 5 p.m. every Friday.”]
Example and references
What good looks like: [Link to a past finished example. Example: "Last week's tab in the tracker."]
Visual guide: [Link to a recording or step-by-step guide of the task.]
Mistakes to avoid: [Describe an error that's easy to make on this task, or add a screenshot of it, so your VA knows to watch for it. Example: "Entering the date the card was charged. Use the date printed on the receipt."]
Update this SOP when
[List the changes that should prompt an update. This includes
- [A tool, policy, or workflow changes]
- [The assistant encounters a situation the SOP doesn’t cover]
Who edits it: [Owner / assistant with owner approval]
Once you’ve seen the blank template, it can help to see what those fields look like when they’re filled in. Below, we’ve used it for five common VA tasks: inbox triage, meeting scheduling, CRM updates, customer support routing, and publishing approved content.
Five virtual assistant SOP examples you can adapt
Each example below uses the same fictional business: Maya owns a six-person design studio, and Jordan is her VA. You can adapt these templates with your own names, tools, timings, and rules.
SOP for Inbox triage
Inbox triage means sorting incoming email so you only see what actually needs your attention.
When we asked VAs about the tasks that are hardest to hand over, they pointed out that inbox management often depends on the client’s preferences. A good SOP should clarify what they can archive, reply to, or forward to others, and what needs your attention.
As they learn your preferences, you can gradually let them draft replies and handle routine requests themselves.
SOP: Triage Maya’s email inbox
Trigger: Weekdays at [9:00 and 15:00].
Expected output: No unread messages, every message has one label, and a summary is posted for Maya.
Steps
Watch it done: [Link to a video or step-by-step guide of this task]
- Open the inbox and filter to unread messages.
- Give each message one label: Reply needed, Maya to review, FYI or Archive.
- Archive anything on the archive list once it’s labeled. The list covers newsletters, automated receipts and tool notifications.
- For Reply needed messages that match a saved reply, write a draft from the saved replies document. Leave it in Drafts.
- Star every “Maya to review” message.
- Post a summary in Slack: drafts waiting, starred messages, and anything urgent at the top.
Decisions and exceptions
| If this happens | Do this | Who decides |
|---|---|---|
| A client mentions a deadline today | Message Maya in Slack within [30 minutes] | VA |
| You aren’t sure which label fits | Use Maya to review | VA |
| Someone asks for a call | Follow the meeting scheduling SOP | VA |
| A message is from a lawyer or the tax office | Star it and flag it in the summary | Maya |
You may act without asking when: A message is on the archive list, or a saved reply fits it exactly.
Stop and ask when: A message mentions a payment or a complaint.
Never: Send a reply from Maya’s account [during the first month]. Delete a message.
Quality check
- The unread count is zero.
- Every message has exactly one label.
- Every draft is in Drafts, and nothing went out.
Report completion
Where: [#inbox in Slack]
What to report: Number of drafts waiting, number of starred messages, urgent items first.
Deadline: [By 9:30 and 15:30 daily].
2. SOP for meeting scheduling
Handing over calendar management lets your VA take care of the back and forth of scheduling without checking with you on every decision. They can find suitable times, send invites, resolve straightforward conflicts, and make sure you have the information you need before a meeting.
Your SOP should specify things like which hours you prefer for meetings, how much time to leave between calls, who gets priority when there is a conflict, and when your VA needs to check with you before confirming.
SOP: Schedule a meeting with Maya
Trigger: Someone asks to meet with Maya, by email or Slack.
Expected output: A calendar invite every attendee has accepted, with a video link and a one-line agenda.
Steps
Watch it done: [Link to a video or step-by-step guide of this task]
- Confirm who’s attending, how long the meeting is, and what it’s for.
- Find each attendee’s time zone. Check their email signature first, then ask if it’s missing.
- Check Maya’s calendar for open slots inside her meeting windows.
- Offer two slots, written in the attendee’s time zone with Maya’s in brackets.
- When they pick one, check the calendar again for conflicts.
- Send the invite. Title it “Studio x Company: Purpose” and add the video link and agenda.
- Reply in the thread to confirm the invite is sent.
Decisions and exceptions
| If this happens | Do this | Who decides |
|---|---|---|
| No open slot in the next [two weeks] | Send Maya the request and the first slot outside her windows | Maya |
| The attendee asks to reschedule a second time | Hand the thread to Maya | Maya |
| The meeting would fall before [9:00] or after [18:00] | Ask Maya first | Maya |
| An existing client asks for a [30-minute] check-in | Book it inside her windows | VA |
You may act without asking when: The attendee is an existing client and the meeting fits Maya’s windows.
Stop and ask when: The request is from someone new, or it needs more than [60 minutes].
Never: Move or cancel a meeting already on Maya’s calendar.
Maya’s meeting windows: [Tuesday to Thursday, 10:00 to 16:00 IST], with [15 minutes] between meetings.
Quality check
- The invite shows the right time in both time zones.
- The video link opens.
- Every attendee is on the invite.
Report completion
Where: Reply in the original email or Slack thread.
What to report: The confirmed date and time.
Deadline: [Within one business day of the request].
3. SOP for CRM update
Many VAs help small business owners and founders keep their CRM up to date. But simple instructions like “update the lead in the CRM” can leave a new VA with questions: Where is the record? Which field should I update? Which option should I choose? What if information is missing?
The SOP below shows how you can make those instructions explicit.
This process is also a good example of how some tasks are easier to show than explain. As one VA we spoke to pointed out, you can’t assume your VA already knows the tools you use or how you use them. That’s why, later in this article, we’ll take the same process a step further by recording the workflow and turning it into a visual SOP.
SOP: Update a contact in the CRM
Trigger: A contact sends new details, such as a job title or phone number, by email or signed form.
Expected output: One correct record with the new details saved and a note showing where they came from.
Before you start: Open the source email or form in another tab. Never update a contact from memory or a social media profile.
Steps
Watch it done: [PRODUCTION: Link to the Trails guide and narrated video of this task]
- Open the CRM and go to Contacts.
- Search by the contact’s email address. It’s the field least likely to be shared by two people.
- If nothing comes up, search by last name, then by company name.
- Check the results for duplicates. If more than one record could be this person, stop and follow the duplicate rule below.
- Open the record and compare each field you plan to change with the source.
- Update only the fields the source supports. Use the phone format [+country code, no spaces].
- Add a note: “Updated job title and phone. Source: email from Dana Okafor, 3 Oct 2026.”
- Save, refresh the page, and check every new value is still there.
- Mark the request done in the task tracker with a link to the record.
Decisions and exceptions
| If this happens | Do this | Who decides |
|---|---|---|
| Two records match | Don’t merge them. Send Maya both record links | Maya |
| No record exists | [Create a new contact with the source attached] | VA |
| The source conflicts with the record, such as a different company | Don’t overwrite. Add a note and ask Maya | Maya |
| A field is missing from the source | Leave the existing value | VA |
You may act without asking when: The source is an email from the contact or a signed form.
Stop and ask when: The source is secondhand, such as a colleague forwarding new details.
Never: Merge or delete records. Edit [deal value or account owner].
Quality check
- The refreshed record shows the new values.
- The source note is saved on the record.
- No duplicate record was created.
Report completion
Where: [The task tracker]
What to report: A link to the updated record.
Deadline: [Same business day].
4. SOP for support routing
For many small businesses, customer support is one of the tasks handed over to a VA. They can answer routine questions, triage incoming requests, and route issues to the right person.
Your SOP should explain which questions your VA can answer themselves, who handles billing or technical problems, and when to escalate a complaint. For example, can they answer a question about delivery times? What should they do if a customer requests a refund or reports that something isn’t working?
SOP: Route a customer support request
Trigger: A new message arrives in the support inbox.
Expected output: The customer has an approved reply, or the request is assigned to the right person with a note they can act on without rereading the thread.
Steps
Watch it done: [Link to a video or step-by-step guide of this task]
- Read the whole message and pick one type: How-to, Billing, Bug, Refund or Other.
- For How-to requests, check the approved help articles list for an answer.
- If an approved article answers it, draft a reply with the saved response and the article link.
- Otherwise, assign the request using the routing table below.
- Add an internal note: who the customer is, what they asked, what you checked, and what they need next.
- Tag the request with its type and check it shows in the assignee’s queue.
Routing table:
| Type | Route to |
|---|---|
| How-to, not covered by an article | [Support lead] |
| Billing | [Maya] |
| Bug | [Project lead for that client] |
| Refund | [Maya] |
Decisions and exceptions
| If this happens | Do this | Who decides |
|---|---|---|
| The message fits two types | Route by the first thing the customer asked | VA |
| The customer mentions a lawyer or a public review | Assign to Maya and mark it urgent | Maya |
| The customer asks to delete their data | Assign to Maya. Don’t reply | Maya |
You may act without asking when: An approved article fully answers a how-to question.
Stop and ask when: The answer depends on the customer’s account or contract.
Never: Promise a refund or a fix date.
Quality check
- Every new request has a type tag.
- Every assigned request has an internal note.
- Every draft reply links to an approved article.
Report completion
Where: [The help desk queue]
What to report: Nothing extra. The tag and note are the report.
Deadline: [First response within one business day].
4. Content publishing SOP
Content publishing is another repeatable task small businesses hand over to a VA. Once your content is written and approved, your VA can handle formatting, adding images and links, entering metadata, and scheduling publication.
The important part is making clear what “ready to publish” means. For example, should your VA fix a broken link themselves? What should they do if an image is missing? Can they correct a formatting problem, or should they send it back to the writer or editor?
The SOP below gives them a process to follow without having to ask you each time.
SOP: Publish an approved blog post
Trigger: A post is marked Approved in the content tracker.
Expected output: The post is live or scheduled, every link works, and the live URL is in the tracker.
Steps
Watch it done: [Link to a video or step-by-step guide of this task]
- Confirm the tracker shows who approved the post and when.
- Open the draft in the website’s editor.
- Check the featured image and image alt text are in place.
- Check the title, URL slug and meta description match the approved document.
- Preview the post on desktop and on mobile.
- Click every link in the preview and confirm it opens the right page.
- [Schedule the post for the approved date].
- Once it’s live, open the URL in a private browser window to confirm it loads.
- Paste the live URL into the tracker and mark it Published.
Decisions and exceptions
| If this happens | Do this | Who decides |
|---|---|---|
| No approval is recorded | Don’t publish. Ask the author who approved it | Maya |
| An image is missing | Don’t substitute a stock image. Ask the author for the file | Maya |
| A link is broken | Leave the post unpublished and send the author the link | Maya |
| A typo is obvious, such as a doubled word | Fix it and note it in the tracker | VA |
You may act without asking when: The fix is a typo that doesn’t change the meaning.
Stop and ask when: Anything in the post differs from the approved document.
Never: Publish a post that isn’t marked Approved. Edit a post that’s already live.
Who can approve a post: [Maya or the content lead].
Quality check
- The live URL loads in a private window.
- The title and meta description match the approved document.
- Every link opens the right page.
Report completion
Where: [The content tracker and #content in Slack]
What to report: The live URL.
Deadline: [By end of day on the publish date].
Virtual assistant SOP checklist and best practices
The five examples above give you a starting point, but copying the steps isn’t quite enough.
We spoke to founders who have delegated work and virtual assistants on the receiving end to understand where SOPs tend to fall short. What gets lost in the handoff? What leaves a VA guessing? And what helps them take over a task with fewer questions?
We distilled their advice into the checklist below:
Do
- Keep steps short and specific.
- State the expected outcome and deadlines
- Use screenshots and video demonstrations where helpful.
- Store SOPs in one central, easily accessible location.
- Review and update instructions whenever workflows change.
Don’t
- Overcomplicate procedures with unnecessary details.
- Assume your VA knows your tools or preferences.
- Leave important steps or exceptions undocumented.
- Leave outdated SOPs in circulation.
Before you hand it over, check:
- Do your VA’s logins work and do they have the access level the SOP lists?
- Do they know where to start without asking?
- Can they finish the task using only the SOP and the guide?
- Are common exceptions covered?
- Is it clear what your VA can decide?
- Is it clear when to escalate?
- Does your VA know how to report completion?
Salome, an ALX-certified Virtual Assistant we interviewed, sums it up: “SOPs help reduce guesswork, maintain consistency, and ensure tasks are completed to the client’s expectations.”
Should you use video or written SOPs for your VA?
Quick answer: For most tasks, the two work best together. Written steps are easier to scan, follow and update. A short screen recording shows where to click and how to move between tools, which is hard to put into words. A simple approach is to record the task once, turn it into written steps, and link the video at the top of the SOP so your VA can rewatch it when they need to.
The people we spoke to on both sides of the handoff explained why recordings help.
Salome said she finds screen recordings particularly helpful when a process involves several steps or depends on the client’s preferences. Examples include organizing an inbox, scheduling meetings, handling common customer inquiries, or using a CRM to track leads.
Jose Angelo, founder of Rebound SEO, had encountered the same problem from the other side of the handoff:
“I didn’t realize how much of the navigation needed to be explained until they started doing the work and I began getting a lot of questions. For me, the hard part was showing them how to use different products, tools, and features, and how to navigate those tools to achieve the outcome.”
He found that written instructions alone rarely helped his VAs. Instead, he would walk them through the process and keep a recording they could return to later.
So we put that approach to the test and noted how the process could flow.
Turn your workflow into an SOP
Remember the CRM update SOP from earlier? We recorded ourselves completing the task, using Trails to turn the recording into a visual, step-by-step guide.
Here’s how you can do the same with a workflow of your own:
Step 1: Record the task as you normally do it
Use a screen recorder such as Loom, Zoom or the one built into your computer to record the work as you do it. We used the Trails Chrome extension (it’s our software, so naturally it’s our favorite).
As you go about the work, it helps to talk through what you’re doing. You may say, for example, “I search by email first because names repeat.” That reasoning is often what your VA needs most.
Note: Many recording tools, including Loom, Zoom, and Trails, can transcribe what you say automatically, depending on the tool and your plan.
Step 2: Build the first draft
You can now edit the transcript, numbering the steps and adding screenshots wherever it helps. If you’re using Trails, this step is done for you: it splits the recording into steps, each with a screenshot and written instructions, and creates a narrated video of the same steps.
If you recorded somewhere else, you can upload the video to Trails, and its video to SOP feature will build the step-by-step guide from it.
Step 3: Review every step against the real task
Read the draft as if you'd never done the task, or have someone else read it. Fix any step text that describes the screen without saying what to do, such as “Contact record page.” Rewrite those as an action, such as “Open the contact’s record and click Edit.”
Blur or mask anything sensitive in the screenshots, such as real phone numbers, before you share it with your assistant.
Step 4: Share it with your assistant.
If you’re using trails, set the guide to Team access so your VA can view it, and link it from the written SOP. When the CRM changes, record the changed steps again and regenerate the video so both versions stay in step.
Step 5: Test the SOP before you hand it over
Ask your VA or someone who didn’t watch you perform the task to complete the task using only the SOP and the guide, without help from you. Each time they:
- ask a question
- make an assumption that turns out to be wrong
- can’t find something
- need an approval the SOP doesn’t mention
- produce something different from what you expected
you’ve found a missing instruction. Add it to the SOP and the guide. In Trails, you can record just the changed steps and regenerate the video, so the written steps and the video stay in sync.
Record your next handoff and turn it into an SOP with Trails
Pick something you’ve explained more than once this month and turn it into a guide in Trails.
Once your SOPs are ready, keep them up to date
After the handoff, it can help to keep a short “SOP notes” thread or doc where your VA writes down anything that didn’t match, such as a renamed button, a new field, a case the exceptions don’t cover, or a step that’s no longer needed.
Some ways to maintain your SOPs and keep your SOPs
- Review regularly: When you reach the SOP’s review date, go through the notes together and update the written steps. If you use Trails, you can re-record just the changed steps and regenerate the video, and its version history lets you restore an earlier version if needed.
- Date every update: Change the “Last reviewed” date each time, so you both know which version is current.
- Keep it together: Store every SOP in one shared folder your VA can reach, and name each one “[Task] SOP” so it’s easy to search.
- Link the guide: Put a link to the visual guide at the top of the written SOP, so your VA has both in one click.
A new assistant can work through them in order instead of shadowing you for a week. If your VA works across several tools, Trails Assistant can show the right guide inside the app they’re using, so they don’t have to go looking for it.
Stop being the bottleneck: Hand over your first task to your VA
At DEGY Entertainment, Michael Silver used to walk colleagues through processes on Zoom. A week later, someone would have forgotten a step, and he’d be explaining it again.
Now he documents tasks in Trails while he does them, pausing to fix anything that looks off instead of starting the recording over. He says his guides now take a third of the time to create, and new team members rarely need to ask: “With new folks, I send the link and they usually don’t even have questions.”
You can start the same way. Pick one task you’ve explained more than once, record it, and add the decisions your VA will need.
The first version won’t be perfect, and that’s fine. Your VA’s questions will show you what’s missing, and each round of fixes makes the next handoff a little easier. Over time, “it’s faster to do it myself” turns into “it’s already done.”
Copy the SOP template to get started, or record your next handoff with Trails.
Frequently asked questions
Which tasks should I document first for my VA?
It can help to start with tasks that come back every week and follow clear rules. Good first candidates are tasks that are:
- Recurring: You do them every day or every week.
- Rule-based: You can explain the decisions in a sentence or two.
- Waiting on you: They pile up when you’re busy.
- Easy to check: You can tell at a glance whether they were done right.
You might pick three to five for your VA’s first week. Tasks that depend on your relationships or judgment can wait until you’ve seen how your VA handles the rules you’ve written down.
What should a virtual assistant SOP include?
At minimum, it should cover what starts the task, the steps, what finished looks like, and what to do when something doesn’t fit. The part many SOPs miss is the decisions: what your VA can do on their own and when they should check with you. The template above includes a section for each of these.
Should the owner or the VA write the SOP?
Either can draft it. The owner supplies the business rules and approves the final version. One approach that works well is to record the task once, have your VA write it up from the recording, and then fill in the decisions and exceptions yourself before signing off.
Can AI help write a VA SOP?
Yes. AI can draft instructions from a recording, a transcript or your rough notes, which takes care of the slowest part of the job. You’ll still want to check each step against the real task and add the rules the source material doesn’t include, such as approval limits and who to escalate to. If you’d like to try it, Trails has an AI SOP generator. To see what finished guides look like, you can browse the Trails gallery.