How to Create SOPs for Your Virtual Assistant
See also: What Is a Virtual Assistant?, How to Hire a Virtual Assistant, How Much Does a Virtual Assistant Cost?
An SOP - Standard Operating Procedure - is a documented set of steps for completing a recurring task. For virtual assistant relationships, SOPs are the difference between spending 20 minutes explaining the same thing every week and having your VA run tasks correctly, consistently, without prompting.
Most business owners resist writing SOPs because they think it's time-consuming. A well-structured SOP for a typical VA task takes 15–30 minutes to write and saves that time every single week. Here's exactly how to do it.
Step 1: Identify Which Tasks Need an SOP
Not every task needs a formal SOP. One-off tasks or things your VA only does once don't need documentation. But any task that:
- Happens more than once
- Has a specific format or standard for the output
- Involves a sequence of steps that must be followed in order
- Has been done incorrectly in the past
- Would be hard to recover from if done wrong
...should have an SOP.
Start by listing your VA's recurring tasks. Inbox management, social media publishing, CRM updates, weekly reporting, invoice processing, appointment scheduling - these are all SOP candidates. Pick the three most important ones and start there.
Step 2: Document the Process While Doing It
The easiest way to write an SOP is to do the task yourself while narrating it step by step. Use a Loom recording and talk through each step as you do it, then have the recording transcribed (Rev.com or Otter.ai). Clean up the transcript into a numbered list.
Alternatively, screen-record yourself doing the task and write the steps from the recording. This approach is faster than writing from memory because the recording shows you exactly what you did - including the small steps you'd otherwise forget to mention.
The goal is to capture every decision point, not just the major steps. For an email management SOP, "check the inbox" is not a step. "Open the main inbox, check emails in the Primary tab, ignore Promotions and Social tabs" is a step.
Step 3: Write the SOP in a Consistent Format
Your SOPs should follow a consistent structure so your VA can scan them quickly:
Header: Task name, owner (who's responsible), frequency (daily / weekly / per occurrence), last updated date, and a link to any relevant templates or tools.
Purpose: One to two sentences on why this task matters and what success looks like.
Tools needed: Every platform, login, or resource required to complete the task.
Steps: Numbered list, written in plain imperative language ("Open," "Check," "Enter," "Click").
If/Then rules: For any decision the VA will need to make, spell it out explicitly.
Output: What the completed task looks like. Where to file it, who to notify, what to update.
Step 4: A Real SOP Example - Managing Your Email Inbox
Here's what a real inbox management SOP looks like:
Task: Daily Inbox Management Owner: VA Frequency: Daily, 9am ET Tools: Gmail (shared inbox access), HubSpot, Slack
Purpose: Keep the inbox at zero unread messages by EOD. All actionable emails should be replied to, forwarded, or escalated within 4 hours of receipt.
Steps:
- Log into the shared inbox at gmail.com using the credentials in LastPass.
- Filter by unread. Start with the oldest unread email.
- For each email, apply one of the following labels: "Reply Sent," "Awaiting Reply," "Escalate to [Owner]," or "Archive."
- If the email is a client inquiry: open the client record in HubSpot and check if they've inquired before. Reply using the New Inquiry template (linked in the Templates doc). Log the reply in HubSpot under "Last Contacted."
- If the email is a vendor invoice: forward to [accounting email] and apply the "Finance" label.
- If the email requires a decision only the owner can make: forward to owner via Slack message (not email) with a one-sentence summary: "Email from [Name] re: [Topic] - needs your decision."
- At end of day, send a Slack message to owner: "Inbox cleared. [X] emails processed. [X] escalated to you in Slack."
If/Then:
- If you're unsure whether to escalate: escalate. It's better to over-communicate.
- If an email is in a language other than English: paste into Google Translate, summarize in English, and escalate to owner.
This level of specificity means a new VA could follow this SOP without ever asking you a question.
Step 5: A Real SOP Example - Social Media Publishing
Task: Weekly LinkedIn Post Publishing Owner: VA Frequency: Every Monday and Thursday at 10am ET Tools: Buffer, Google Drive (content calendar), Canva
Steps:
- Open the content calendar in Google Drive (linked here). Go to the current week's tab.
- Find the post scheduled for today. Copy the caption text.
- Open the associated Canva graphic (linked in the calendar row). Download as PNG at 1080x1080.
- Open Buffer. Click "New Post" → LinkedIn.
- Paste the caption. Upload the PNG.
- Schedule for 10am ET on the correct date.
- Preview to confirm text is not cut off and graphic looks correct.
- Confirm scheduling. Go back to the calendar and mark the post as "Scheduled" in Column F.
Step 6: Store and Maintain Your SOPs
SOPs are only valuable if your VA can find them and they're kept up to date. Store all SOPs in a single location - a Notion database, a Google Drive folder, or a ClickUp doc. Use consistent naming: "[Task Name] SOP." Create a master index so your VA can search quickly.
Update SOPs whenever a process changes. If you switch from Gmail to Outlook, update every SOP that references Gmail the same day. Outdated SOPs are worse than no SOPs - they create false confidence and wrong outputs.
Common Mistakes to Avoid
Writing SOPs from memory instead of while doing the task. Memory skips steps you consider obvious. Do the task and document it in real time.
Making SOPs too high-level. "Check the email" is not a step. Be specific enough that someone unfamiliar with your business can follow the SOP correctly.
Not including if/then rules. Decision points are where tasks go wrong. Address them explicitly.
Never updating SOPs. A process that changes without the SOP being updated creates ongoing errors. Assign someone (your VA) to flag when an SOP seems out of date.
Creating SOPs but not organizing them. SOPs your VA can't find are SOPs that don't get used. Maintain a clean index.
Ready to Find Your Virtual Assistant?
Stealth Agents places virtual assistants who are experienced at following SOPs and who will proactively flag when documentation needs updating. Start building your operating system with the right person.
Find your process-ready VA at Stealth Agents