How to Create SOPs for Your Virtual Assistant - Template and Examples Included

A virtual assistant without SOPs is like a GPS without a destination. They might move, but they will not end up where you need them.

Standard operating procedures are the single most important tool for getting consistent, high-quality work from your virtual assistant. Not training videos, not daily check-ins, not micromanagement. SOPs. Written, step-by-step instructions that remove guesswork and set a clear standard for what "done correctly" looks like.

This guide walks you through how to build SOPs that actually work, with a reusable template and real examples for the most common virtual assistant tasks. Whether you are onboarding your first VA or tightening up processes for an existing team, these templates will save you hours of back-and-forth.

See also: document your processes before hiring a VA, virtual assistant onboarding checklist, how to delegate effectively.

What Is an SOP and Why Does Your VA Need One?

A standard operating procedure is a documented set of instructions for completing a specific task. It tells your virtual assistant exactly what to do, in what order, using which tools, and what the expected outcome looks like.

Without SOPs, your VA relies on memory, assumptions, and guesswork. That leads to inconsistent output, repeated questions, and rework that costs you time and money. With SOPs, your VA operates independently and delivers results that match your expectations every single time.

The Business Case for SOPs

• Reduce training time by 60-70%: A new VA with well-written SOPs can be productive in days instead of weeks
• Eliminate repeat questions: The answer is in the SOP, not in your inbox
• Enable quality control: You can audit work against the documented standard
• Make scaling possible: Hire a second or third VA without personally training each one
• Protect against turnover: If your VA leaves, the replacement has everything they need on day one

SOPs are not bureaucratic overhead. They are the infrastructure that lets you delegate with confidence.

The SOP Template - Copy and Customize

Here is the universal template that works for virtually any virtual assistant task. Copy it, fill in the blanks, and you have a production-ready SOP.

Universal Virtual Assistant SOP Template

SOP Title: [Clear, specific name - e.g., "Daily Email Triage and Response"]

Version: 1.0

Last Updated: [Date]

Owner: [Your name - the person who approves changes]

Performed By: [VA name or role]

Purpose: [One sentence explaining why this task matters to the business]

Frequency: [Daily / Weekly / Monthly / As needed / Triggered by X event]

Estimated Time: [How long the task should take once the VA is trained]

Tools Required: [List every software tool, login, or access needed]

Prerequisites: [Anything that needs to happen before this task can start]

Steps:

1. [First specific action - include what to click, where to navigate, what to look for]
2. [Second action - be precise about inputs, outputs, and decisions]
3. [Continue with each step in order]
4. [For decision points, use "If X, then do Y. If Z, then do W" format]
5. [Final step - where to save/submit/report the completed work]

Quality Checklist:

• [First quality check]
• [Second quality check]
• [Final verification]

Common Mistakes to Avoid:

• [Mistake 1 and what to do instead]
• [Mistake 2 and what to do instead]

Escalation Rules: [When should the VA stop and ask you instead of proceeding?]

Examples: [Link to or include a sample of correctly completed work]

How to Write Effective SOPs - 7 Rules That Matter

Templates are only useful if you fill them in correctly. These seven rules will keep your SOPs clear, actionable, and genuinely helpful for your virtual assistant.

Rule 1 - Write for Someone Who Knows Nothing About the Task

The biggest SOP mistake is assuming context. Your VA may understand general concepts, but they do not know your specific tools, your naming conventions, your client preferences, or your definition of "good." Write as if explaining to a capable person who has never seen your business before.

Bad: "Update the CRM after each call."

Good: "After each client call, open HubSpot, navigate to the client's contact record, click 'Log Activity,' select 'Call' as the type, enter the date and duration, and paste the call summary from the notes template into the description field. Save the activity and verify it appears in the contact timeline."

Rule 2 - Use Screenshots and Screen Recordings

Text instructions work for simple tasks. For anything involving software navigation, include screenshots with arrows pointing to the exact buttons, fields, or menus. For complex workflows, record a 2-5 minute Loom video walking through the process.

A 3-minute screen recording can replace 2 pages of written instructions and is dramatically harder to misinterpret.

Rule 3 - Include Decision Trees for Judgment Calls

Many tasks involve decisions that seem obvious to you but are not obvious to your VA. Map these out explicitly.

Example decision tree for email triage:

• If the email is from a current client and mentions an issue: Label as "Client - Urgent," draft a response acknowledging receipt, and flag for your review
• If the email is from a current client with a routine question: Draft a response using Template B and send without review
• If the email is from a potential lead asking about pricing: Forward to [email protected] and label as "Lead - Hot"
• If the email is a newsletter, promotional, or automated notification: Archive immediately
• If you are unsure about the category: Label as "VA - Needs Review" and leave it in the inbox

Rule 4 - Specify the Output, Not Just the Process

Tell your VA what the finished product looks like. Include examples of completed work so they have a concrete reference point.

Bad: "Write a social media post about our new feature."

Good: "Write a LinkedIn post about our new feature. 150-200 words. Hook in the first line. Include one client benefit. End with a question to drive engagement. See the three example posts in our Social Media SOP folder for tone and format reference."

Rule 5 - Define What "Done" Means

Every SOP should end with a clear definition of completion. Where is the output saved? Who gets notified? What happens next?

• "Save the completed spreadsheet in Google Drive > Client Reports > [Month] folder"
• "Post a summary in the #completed-tasks Slack channel with the client name and task description"
• "Mark the Asana task as complete and tag me if any items required escalation"

Rule 6 - Include Escalation Triggers

Your VA needs to know when to stop and ask for help instead of guessing. Be specific about these boundaries.

Escalation triggers to include in every SOP:

• Any task that will take more than [X hours] longer than estimated
• Any communication from a VIP client (list the names)
• Any error message or system failure
• Any request that falls outside the documented process
• Any situation where the VA is less than 80% confident in the correct action

Rule 7 - Version and Review Regularly

SOPs are living documents. Processes change, tools get updated, and your VA will discover edge cases you did not anticipate. Add a version number and review date to every SOP. Schedule a monthly 15-minute review to update any procedures that have drifted.

Real SOP Examples for Common VA Tasks

Here are five complete SOP examples for the most commonly delegated virtual assistant tasks. Use these as starting points and customize them for your specific business.

Example 1 - Daily Email Management SOP

SOP Title: Daily Email Inbox Management

Purpose: Keep the inbox organized, ensure timely responses, and surface priority messages

Frequency: Twice daily (9:00 AM and 2:00 PM EST)

Estimated Time: 30-45 minutes per session

Tools Required: Gmail, Google Sheets (Email Tracking Log), Slack

Steps:

1. Log into Gmail using the shared workspace credentials stored in LastPass under "Company Gmail"
2. Start from the oldest unread email and work forward
3. For each email, classify using these categories:
   • Client - Urgent: Time-sensitive client request or complaint. Draft response, flag for owner review in Slack #email-review
   • Client - Routine: Standard client question or update. Draft response using the Client Response Templates doc. Send if the template fits exactly; flag for review if customization is needed
   • Lead - New: First contact from potential customer. Forward to [email protected] and log in the Lead Tracking Sheet
   • Internal: Team communication. Read and respond if action is required from VA role. Archive otherwise
   • Vendor/Subscription: Bills, receipts, service notifications. Forward invoices to [email protected] and archive
   • Spam/Promotional: Unsubscribe if recurring. Archive or delete
4. Log each processed email in the Email Tracking Google Sheet with columns: Date, Sender, Category, Action Taken, Follow-up Needed (Y/N)
5. Post a summary in Slack #email-review: "[Date] - [X] emails processed, [Y] flagged for review, [Z] leads forwarded"

Quality Checklist:

• Zero unread emails older than 4 hours in the inbox
• All flagged emails have a drafted response attached
• Email tracking log is updated for every processed message
• Slack summary posted after each session

Escalation Rules: Flag immediately if an email mentions legal action, a refund request over $500, or communication from anyone on the VIP Client List.

Example 2 - Social Media Scheduling SOP

SOP Title: Weekly Social Media Content Scheduling

Purpose: Maintain consistent social media presence across LinkedIn, Instagram, and Twitter

Frequency: Every Monday by 12:00 PM EST

Estimated Time: 2-3 hours

Tools Required: Buffer (scheduling), Canva (graphics), Google Drive (content calendar), Unsplash (stock photos)

Steps:

1. Open the Content Calendar in Google Drive > Marketing > Social Media > [Current Month]
2. Review the posts planned for the upcoming week (Monday through Friday)
3. For each post: a. Write copy following the Brand Voice Guide in Google Drive > Marketing > Brand Guidelines b. Create or select a visual using Canva. Use the "Social Media Templates" folder for branded templates c. For stock photos, use Unsplash only. Save downloaded images in Google Drive > Marketing > Social Media > Assets
4. Upload all posts to Buffer:
   • LinkedIn: Schedule for Tuesday, Wednesday, Thursday at 10:00 AM EST
   • Instagram: Schedule for Monday, Wednesday, Friday at 12:00 PM EST
   • Twitter: Schedule for Monday through Friday at 9:00 AM and 3:00 PM EST
5. Double-check every scheduled post for spelling, correct links, and proper image sizing
6. Take a screenshot of the Buffer queue showing the full week and paste it into the Content Calendar alongside the planned posts
7. Post in Slack #marketing: "Week of [date] - [X] posts scheduled across [platforms]. Queue screenshot in content calendar."

Quality Checklist:

• All planned posts are scheduled - no gaps in the weekly calendar
• Every post has a visual - no text-only posts
• All links are tested and working
• Copy matches brand voice guidelines
• Buffer queue screenshot saved to content calendar

Common Mistakes to Avoid:

• Do not schedule more than one post per platform per day unless the calendar specifically calls for it
• Do not use images with watermarks - only use properly licensed Unsplash photos or branded Canva templates
• Do not publish posts directly. Always schedule through Buffer for tracking

Example 3 - Monthly Bookkeeping Data Entry SOP

SOP Title: Monthly Expense Categorization and Data Entry

Purpose: Categorize business expenses for accurate financial reporting and tax preparation

Frequency: First week of each month (covers prior month)

Estimated Time: 3-4 hours

Tools Required: QuickBooks Online, Google Sheets (Expense Categories Reference), bank statement PDF

Steps:

1. Download the previous month's bank statement from the business checking account (Chase Business > Statements > Download PDF)
2. Open QuickBooks Online and navigate to Banking > Bank Transactions
3. For each transaction: a. Match the transaction description against the Expense Categories Reference sheet b. If the vendor is already in QuickBooks, verify the auto-category is correct c. If the vendor is new, look up the vendor type in the reference sheet and assign the correct category d. Add a memo with the business purpose if the transaction is over $100 or the purpose is not obvious from the vendor name
4. After categorizing all transactions, run the "Profit and Loss by Month" report in QuickBooks
5. Compare the total expenses against the previous month. If any category is more than 20% higher or lower than the previous month, note the variance in the Monthly Expense Notes column of the tracking sheet
6. Export the categorized transaction list as a CSV and save to Google Drive > Finance > [Year] > [Month] - Categorized Transactions
7. Post in Slack #finance: "Month] expenses categorized. [X] transactions processed. Variances noted: [list any categories with 20%+ change]."

Escalation Rules: Do not categorize transactions labeled as "Transfer," "Wire," or anything over $5,000. Flag these for owner review.

Example 4 - Customer Support Ticket Triage SOP

SOP Title: Daily Customer Support Ticket Triage

Purpose: Ensure every customer inquiry gets a timely first response and is routed to the right team member

Frequency: Three times daily (9:00 AM, 1:00 PM, 5:00 PM EST)

Estimated Time: 20-30 minutes per session

Tools Required: Zendesk, Knowledge Base (help.company.com), Slack

Steps:

1. Open Zendesk and filter tickets by "New" and "Open" status, sorted by oldest first
2. For each new ticket: a. Read the full customer message and any previous ticket history from the same email address b. Classify the ticket priority:
   • Urgent: Service is down, billing error, or security concern. Assign to Tier 2 immediately
   • High: Feature not working as expected but workaround exists. Respond with workaround and assign to Tier 2
   • Normal: How-to question, feature request, or general inquiry. Respond using Knowledge Base article if applicable
   • Low: Feedback, compliment, or non-actionable input. Respond with thank-you template and close c. Send the first response within the session. Use the response templates in Zendesk Macros. Customize the greeting with the customer's first name d. Tag the ticket with the correct category: billing, technical, feature-request, account, or general
3. Update the Ticket Triage Log (Google Sheets) with: Date, Ticket ID, Customer, Category, Priority, Action Taken
4. Post in Slack #support: "[Session time] triage complete. [X] new tickets, [Y] urgent, [Z] resolved on first response."

Escalation Rules: Any ticket mentioning data loss, account compromise, or threatening legal action goes to the owner immediately via Slack DM and email.

Example 5 - Calendar and Meeting Management SOP

SOP Title: Daily Calendar Management and Meeting Coordination

Purpose: Keep the executive calendar organized, prevent conflicts, and ensure every meeting has an agenda

Frequency: Daily at 8:00 AM EST and as needed for incoming requests

Estimated Time: 20-30 minutes for morning review, 5 minutes per ad-hoc request

Tools Required: Google Calendar, Calendly, Zoom, Slack, Google Docs (Meeting Notes Template)

Steps:

1. Open Google Calendar and review the next 48 hours of scheduled events
2. For each meeting today: a. Confirm the meeting has a video link (Zoom or Google Meet). Add one if missing b. Check that an agenda exists. If no agenda is attached, create one using the Meeting Agenda Template in Google Drive > Admin > Templates c. Send a reminder to external attendees 2 hours before the meeting (use the Meeting Reminder email template)
3. For scheduling requests that come in via email or Slack: a. Check calendar availability for the requested time window b. If the requester is an external contact, send them the Calendly booking link for the correct meeting type (15-min intro, 30-min discovery, 60-min strategy) c. If the requester is internal, book directly on the calendar and send a confirmation d. Never double-book. If a conflict exists, propose two alternative time slots
4. After each meeting concludes, create a Meeting Notes document using the template and share it with all attendees within 2 hours
5. Post the daily calendar summary in Slack #executive: "Today: [X] meetings. Prep needed for: [list any meetings missing agendas]. Tomorrow: [Y] meetings scheduled."

Quality Checklist:

• All meetings today have video links and agendas
• No scheduling conflicts in the next 7 days
• Meeting notes sent within 2 hours of each meeting
• Calendar summary posted by 8:30 AM

How to Organize Your SOP Library

Once you start writing SOPs, you need a system to keep them findable and up to date. Here is the folder structure used by businesses that successfully manage multiple virtual assistants.

Recommended Folder Structure

Company SOPs/
  Admin/
    Email Management SOP
    Calendar Management SOP
    Travel Booking SOP
    Document Filing SOP
  Marketing/
    Social Media Scheduling SOP
    Blog Publishing SOP
    Newsletter SOP
    Analytics Reporting SOP
  Finance/
    Expense Categorization SOP
    Invoice Processing SOP
    Accounts Receivable Follow-Up SOP
  Customer Support/
    Ticket Triage SOP
    Refund Processing SOP
    Review Response SOP
  Sales/
    Lead Qualification SOP
    CRM Data Entry SOP
    Follow-Up Sequence SOP
  Templates/
    SOP Blank Template
    Meeting Notes Template
    Email Response Templates
    Report Templates

SOP Naming Convention

Use a consistent naming format so anyone can find the right document quickly:

[Department] - [Task Name] - SOP v[Version]

Examples:

• Admin - Email Management - SOP v2.1
• Marketing - Social Media Scheduling - SOP v1.0
• Finance - Expense Categorization - SOP v1.3

Where to Store SOPs

Use a cloud-based tool that your VA can access from anywhere:

• Google Drive: Free, easy to share, version history built in. Best for most small businesses
• Notion: Great for teams that want a wiki-style knowledge base with linked SOPs
• Trainual: Purpose-built for SOPs and training. Worth the investment if you manage 3 or more VAs
• Loom + Google Docs: Combine video walkthroughs with written procedures for complex tasks

The tool matters less than the habit. Pick one location and put everything there. An SOP your VA cannot find is an SOP that does not exist.

How to Roll Out SOPs to Your Virtual Assistant

Writing SOPs is half the job. The other half is making sure your VA actually uses them and gives you feedback that improves them. Here is the rollout process.

Step 1 - Walk Through Together

Do not just send a link and expect your VA to figure it out. Schedule a 30-minute call for each major SOP. Walk through the procedure live, let them ask questions, and watch them complete the task once while you observe.

Step 2 - Trial Period With Review

Have your VA follow the SOP independently for one week. During this period, review their output daily. Note any steps that were confusing, skipped, or interpreted differently than intended.

Step 3 - Collect Feedback

Your VA is the best source of improvement ideas for your SOPs. After the trial week, ask:

• Which steps were unclear or confusing?
• Did you encounter any situations the SOP did not cover?
• Are any steps unnecessary or redundant?
• What would make this process faster?

Step 4 - Update and Finalize

Incorporate your VA's feedback, update the version number, and mark the SOP as "Active." Add a calendar reminder to review the SOP again in 30 days.

Common SOP Mistakes That Waste Your VA's Time

Avoid these pitfalls that make SOPs less effective:

Writing novel-length procedures: If an SOP is longer than 2 pages, break it into multiple SOPs. Long documents overwhelm VAs and make it hard to find specific steps.

Using vague language: Words like "appropriately," "as needed," and "use your judgment" are SOP killers. Replace every vague term with a specific rule or decision tree.

Forgetting to update after tool changes: If you switch from Mailchimp to ConvertKit, your email marketing SOP is now useless. Update SOPs the same day you change tools.

Not including examples: A visual example of the expected output is worth more than 500 words of description. Include screenshots, sample outputs, or links to correctly completed work.

Skipping the escalation rules: Without clear escalation guidelines, your VA will either bother you with every minor question or make decisions they should not be making. Define the boundaries clearly.

Getting Started Today

You do not need to write SOPs for every task before hiring a virtual assistant. Start with the three tasks you plan to delegate first. Use the template in this guide, follow the seven rules, and reference the examples for inspiration.

Most business owners find that writing their first three SOPs takes about 2-3 hours total. That upfront investment pays for itself within the first week of working with your VA, because instead of explaining the same things over and over, you hand them a document and they get to work.

Ready to hire a virtual assistant who will put your SOPs to work? Get started with a skilled VA today and see how proper documentation transforms delegation from frustrating to effortless. Our team at Stealth Agents matches you with experienced virtual assistants who thrive with well-documented processes.

See also: virtual assistant pricing breakdown, 15 tasks to delegate to a VA this week, VA skills checklist.