This guide explains how to write SOPs that help your virtual assistant (VA) handle more work efficiently, even if you have no prior experience writing process documents.
Why SOPs Are Important When You Hire a VA?
Without SOPs:
- Your virtual assistant asks repeated questions
- You explain the same task multiple times
- Output quality is inconsistent
- You are required for most decisions
- Your virtual assistant cannot work independently
SOPs define clear steps for tasks. This ensures consistent execution. For founders working with virtual assistants, this allows work to scale without constant involvement.
What Makes a Good SOP for Virtual Assistants?
A virtual assistant works remotely and may be in a different time zone. They cannot ask questions in real time. The SOP must answer common questions in advance.
An effective SOP for a virtual assistant includes:
- Clear instructions without relying on prior context
Explain both the task and the reason behind it - Visual elements
Use screenshots, recordings, or annotated images to show steps - Defined decision logic
Specify actions based on different inputs or situations - Documented access details
Include logins, tool locations, folder paths, and naming rules - Error handling steps
Explain what to do when a task cannot be completed as expected
The SOP should allow the virtual assistant to complete tasks without needing clarification.
The 5-Step Framework for Writing Your First VA SOP
You don't need a degree in process management. You need a system. Here's the exact framework that takes you from blank page to working SOP in under two hours.
This framework helps you create an SOP in under two hours.
Step 1: Select a task
Start with a task that:
- Occurs at least weekly
- Takes more than 30 minutes
- Affects revenue or customer satisfaction
- Has clear success criteria
Examples include email management, social media posting, CRM updates, or invoice processing.
Calendar management is also a suitable task. It is repetitive, time-consuming, and affects daily operations.
Step 2: Record the task
Do not rely on memory. Important steps may be missed.
Instead:
- Use a screen recording tool such as Loom or Scribe, or use your phone recorder
- Perform the task while recording
- Explain each step and the reason for it during the recording
- Save the recording
This recording will be used to create the SOP document.
Step 3: Build the SOP Structure
Here's the template format that has worked for Wishup customers.
**SOP Title**: [Specific Task Name]
**Last Updated**: [Date]
**Estimated Time**: [How long this should take]
**Tools Needed**: [List of software, logins, access requirements]
**Purpose**: [One sentence: why this task matters]
**Steps**:
1. [Action verb + specific instruction + screenshot if relevant]
2. [Include decision points: "If X happens, then Y"]
3. [Continue through completion]
**Quality Checklist**:
- [ ] [What to verify before submitting]
- [ ] [What good output looks like]
**What to Do When Something Goes Wrong**:
- Problem: [Common issue]
Solution: [Exact steps to fix]
**Resources**:
- Link to template: [URL]
- Example of completed work: [URL]
- Who to contact if stuck: [Your backup person]
Use your recording to fill in each section. Watch it once, write down every step in order, then watch it again to catch the nuances.
Step 4: Test It With Your VA
Have your VA:
- Follow the SOP exactly as written
- Note every moment of confusion
- Record their attempt (if possible)
- Report back on what was missing
You'll discover gaps immediately. Maybe you forgot to mention which folder to save files in. Maybe your screenshot is from the old interface. Maybe your decision tree needs a third branch.
Iterate. The SOP isn't done until your VA can complete the task independently with zero questions.
Step 5: Set a Review Cadence
SOPs expire. Tools update. Processes evolve. Clients change preferences.
Set calendar reminders:
- Monthly review: For high-frequency tasks
- Quarterly review: For medium-frequency tasks
- Annual review: For low-frequency tasks
The fastest way to make an SOP useless is to let it go stale. Continuous improvement frameworks like Lean and Kaizen often start by reviewing existing SOPs to identify bottlenecks, redundant steps, or opportunities to enhance productivity.
The 6 Tools That Make SOP Creation Actually Easy
For Screen Recording & Visual Capture
Loom: Record your screen while you talk through a process. Free plan includes 25 videos up to 5 minutes each. Perfect for the "watch me do it once" approach. Your VA can replay at their own pace, pause, rewind.
Scribe: Automatically generates step-by-step guides with screenshots as you perform a task. It's like having a documentation assistant watching over your shoulder. Great for software-heavy processes.
For SOP Storage & Management
Trainual: Built specifically for documenting processes and training. Includes 400+ templates, completion tracking, and role-based assignments. Starts at $249/month for up to 25 users. Trainual's 400+ employee training templates give your team a starting point for every role, process, and policy.
Process Street: Combines SOP documentation with workflow automation. Every SOP becomes an interactive checklist. Process Street fixes documentation by turning your documentation into interactive, role-based training modules with built-in tests and progress tracking. Starts around $100/month.
Notion: The Swiss Army knife. Not SOP-specific, but incredibly flexible and free for individuals. Great if you're bootstrapping and need one place for SOPs, project management, and notes.
For the Budget-Conscious Founder
Google Docs + Google Drive: Free, familiar, accessible from anywhere. Create a shared folder structure, use templates, embed images directly. Not fancy, but it works. Pair it with Loom for recordings and you have a complete system for $0.
The tool doesn't matter as much as the habit. Start with what you already have. Upgrade when friction appears, not before.
10 Ready-to-Use SOP Templates for Virtual Assistants
Copy these, customize them, and hand them to your VA tomorrow.
Template 1: Email Management & Response Protocol
**SOP: Email Management & Client Response**
**Estimated Time**: 2 hours daily (AM and PM review)
**Tools**: Gmail, Canned Responses, Client CRM
**Purpose**: Ensure no client email goes unanswered beyond 4 business hours
**Morning Routine (9-10 AM)**:
1. Review inbox (screenshot: show inbox view)
2. Flag emails requiring founder input (star + label "Needs Review")
3. Respond to routine inquiries using canned responses:
- Pricing questions → Use template "Pricing Information v2"
- Meeting requests → Check calendar, propose 3 times using Calendly link
- General FAQs → Use knowledge base answers in [Link to Doc]
4. Move completed emails to "Processed" folder
5. Update CRM with any client communication notes
**Decision Tree**:
- If email is complaint → Flag as urgent, notify founder via Slack immediately
- If email requests refund → Forward to [email protected] + founder
- If email is spam → Archive immediately
- If email tone is unclear → Flag for review, don't respond
**Quality Check**:
- [ ] Zero emails in inbox unmarked after review session
- [ ] All client questions answered or flagged for escalation
- [ ] CRM updated with communication notes
- [ ] Response tone matches company voice guide [Link]
**Common Issues**:
Problem: Client asks about feature we don't offer
Solution: Use template "Feature Request Response" + log request in [Feature Request Sheet]
Template 2: Social Media Content Scheduling
**SOP: Weekly Social Media Scheduling**
**Estimated Time**: 3 hours weekly (Monday mornings)
**Tools**: Buffer/Hootsuite, Canva, Content Calendar
**Purpose**: Maintain consistent social presence without daily intervention
**Weekly Workflow**:
1. Open Content Calendar [Link to Google Sheet]
2. Review approved posts for the upcoming week (Row highlights in green = approved)
3. For each approved post:
- Download images from [Asset Folder]
- Resize for platform requirements using Canva templates [Link]
- Write caption using approved copy (Column D in sheet)
- Schedule in Buffer for optimal times:
* LinkedIn: Tuesday/Wednesday 10 AM EST
* Twitter: Daily 9 AM, 3 PM EST
* Instagram: Monday/Thursday 7 PM EST
4. Add hashtags from [Hashtag Bank] (max 3 for LinkedIn, 10 for Instagram)
5. Mark as "Scheduled" in Content Calendar (Column F)
6. Screenshot Buffer queue, send to founder in weekly summary
**Quality Checklist**:
- [ ] All images meet platform specs (check Buffer preview)
- [ ] No typos in captions (use Grammarly before scheduling)
- [ ] UTM parameters added to all links (use [UTM Builder])
- [ ] Week fully scheduled by Monday 11 AM EST
**What to Do When**:
- Content Calendar is empty → Notify founder Thursday prior week
- Image quality is poor → Flag in Content Calendar, don't schedule
- Link is broken → Replace with working link OR mark row yellow for founder review
Template 3: Calendar Management & Meeting Coordination
**SOP: Calendar Management & Meeting Booking**
**Estimated Time**: 30 min daily + as needed
**Tools**: Google Calendar, Calendly, Zoom
**Purpose**: Optimize founder's time, eliminate double-booking, prep for all meetings
**Daily Calendar Review (8 AM)**:
1. Review next 48 hours in Google Calendar
2. Ensure all meetings have:
- Zoom link (if virtual)
- Address + parking info (if in-person)
- Attendee confirmation (check email)
- Meeting prep doc attached [Link to template]
3. Send founder morning brief via Slack:
"Calendar today: [List meetings with 1-line context each]"
**New Meeting Request Process**:
1. Check email for meeting requests
2. Cross-reference founder's [Meeting Priority Matrix]
- Priority A (VIP clients/investors) → Book within 48 hours
- Priority B (Partners/prospects) → Book within 1 week
- Priority C (Vendors/general) → Book 2+ weeks out
3. Check calendar conflicts:
- Respect 30-min buffer between meetings (minimum)
- No meetings before 9 AM or after 5 PM unless marked "Flexible" in matrix
- Block lunch 12:30-1:30 PM daily
4. Send Calendly link with 3 available slots
5. Once confirmed:
- Add to calendar with clear title: "[Meeting Type] - [Person Name] - [Company]"
- Create meeting prep doc [Template link]
- Add Zoom link if virtual
- Send calendar invite to all attendees
**Meeting Prep (24 hours before)**:
1. Pull relevant info:
- Client history from CRM
- Previous meeting notes from [Folder]
- Any pending action items
2. Populate prep doc template
3. Share in Slack channel #meeting-prep
**Decision Logic**:
- If double-booking occurs → Move Priority C meeting, notify all parties
- If meeting request is vague → Reply requesting clarification on purpose/duration
- If VIP requests time outside normal hours → Flag to founder, don't auto-decline
**Quality Standards**:
- [ ] Zero scheduling conflicts
- [ ] All meetings have prep docs 24 hours in advance
- [ ] Attendees receive calendar invites within 4 hours of confirmation
Template 4: Invoice Processing & Payment Follow-up
**SOP: Invoice Processing & Payment Tracking**
**Estimated Time**: 1 hour weekly (Fridays)
**Tools**: QuickBooks/FreshBooks, Invoice Tracker [Google Sheet], Email
**Purpose**: Ensure timely payment, maintain cash flow, reduce outstanding receivables
**Weekly Process (Every Friday 2-3 PM)**:
1. Open [Invoice Tracker Sheet]
2. Review "Outstanding" tab for invoices 7+ days old
3. For each invoice in 7-14 day window:
- Send gentle reminder: Use template "Payment Reminder - First"
- Update tracker with "Reminder Sent" + date in Column G
4. For invoices 15-30 days old:
- Send firmer follow-up: Use template "Payment Reminder - Second"
- CC founder on email
- Update tracker
5. For invoices 30+ days old:
- Flag for founder review (Column H = "ESCALATE")
- Don't send additional emails without approval
**New Invoice Creation**:
1. Receive completed work notification from team
2. Verify deliverables match project scope [Link to project folder]
3. Create invoice in QuickBooks using template for client type:
- Retainer clients → Template A
- Project-based → Template B
- One-time → Template C
4. Include:
- Detailed line items
- Payment terms (Net 30)
- Preferred payment methods
- Any applicable late fees
5. Export PDF, save to [Invoice Archive Folder] with naming: YYYY-MM-DD_ClientName_InvoiceNumber.pdf
6. Send to client + add to Invoice Tracker
7. Set reminder in calendar for 7-day follow-up
**Payment Received**:
1. Mark invoice "PAID" in tracker + add payment date
2. Move row to "Paid" tab
3. Send client receipt + thank you (Template: "Payment Confirmation")
4. Update financial dashboard [Link]
**Red Flags**:
- Invoice returned/questioned → Forward to founder immediately
- Payment method fails → Send payment link alternatives within 24 hours
- Client requests payment plan → Flag for founder, don't approve terms independently
**Quality Metrics**:
- [ ] 95%+ of invoices paid within 30 days
- [ ] Zero invoices sent without verification
- [ ] Tracker updated same day as any status change
Template 5: CRM Data Entry & Lead Management
**SOP: CRM Lead Data Entry & Qualification**
**Estimated Time**: 1 hour daily
**Tools**: HubSpot/Salesforce, Lead Capture Form, LinkedIn
**Purpose**: Ensure all leads are logged, enriched, and ready for sales follow-up
**Daily Lead Processing (Morning)**:
1. Export new leads from [Form/Website] submitted in last 24 hours
2. For each lead:
- Create new contact in CRM
- Populate required fields:
* Full name
* Email (verify format)
* Company
* Title
* Phone (if provided)
* Lead source (website/event/referral)
- Enrich data:
* Find LinkedIn profile → add URL to CRM
* Check company website → add company size, industry
* Google company → look for recent news/funding (add to notes)
3. Score lead using qualification matrix [Link]:
- Budget indicators (company size, industry, job title)
- Timing (form responses about timeline)
- Authority (decision-maker title)
- Assign score: Hot (8-10), Warm (5-7), Cold (1-4)
4. Route appropriately:
- Hot leads → Assign to founder, send Slack alert immediately
- Warm leads → Assign to sales queue
- Cold leads → Add to nurture sequence
**Lead Follow-up Tracking**:
1. Check CRM for leads marked "Awaiting Follow-up"
2. If 48 hours passed since last contact:
- Send reminder to assigned sales rep via CRM task
3. If 7 days passed without response:
- Flag for founder review
**Data Quality Rules**:
- No duplicate entries (check email before creating new contact)
- All company names capitalized consistently
- All required fields filled before lead is marked "Qualified"
- Notes field includes: lead source detail + any special context
**When to Escalate**:
- Lead requests immediate call → Notify sales team via Slack, mark urgent
- Lead mentions competitor → Add note, flag for founder
- Lead data incomplete after enrichment attempt → Mark "Needs Review" for sales to complete
**Quality Standards**:
- [ ] 100% of leads processed within 24 hours of submission
- [ ] Zero duplicate contacts created
- [ ] All Hot leads escalated same-day
- [ ] Enrichment data added to 90%+ of leads
Template 6: Customer Support Ticket Management
**SOP: Customer Support Ticket Response & Escalation**
**Estimated Time**: 3 hours daily (spread across AM/PM)
**Tools**: Zendesk/Freshdesk, Knowledge Base, Slack
**Purpose**: Resolve customer issues quickly while maintaining brand voice and satisfaction
**Ticket Triage (Check every 4 hours)**:
1. Log into support dashboard
2. Sort by: Unassigned → Oldest first
3. Categorize each new ticket:
- **Bug/Technical Issue** → Label "Tech", assign to dev team, note repro steps
- **Billing Question** → Label "Billing", assign to finance
- **How-to/Feature Question** → Label "Product", handle yourself
- **Complaint/Escalation** → Label "Urgent", flag founder immediately
4. Set priority:
- Critical (service down, payment issue) → Respond within 1 hour
- High (feature not working) → Respond within 4 hours
- Normal (questions, requests) → Respond within 24 hours
**Response Protocol**:
1. Open ticket, read full history
2. Check if answer exists in Knowledge Base [Link]
3. If yes:
- Personalize response using customer's name
- Summarize solution in simple terms
- Link to relevant KB article
- Ask if they need additional help
- Use template: "How-to Response"
4. If no:
- Research answer (check product docs, ask dev team in Slack)
- Draft response
- Review against Brand Voice Guide [Link]
- Add new answer to Knowledge Base for future
- Send response
5. Mark ticket status:
- "Solved" if fully answered
- "Pending" if waiting on customer
- "On-hold" if waiting on internal team
**Escalation Criteria** (Flag immediately):
- Customer threatens to cancel
- Customer mentions competitor
- Issue affects multiple users
- Bug causes data loss
- Request for refund over $X
- Customer is VIP account [Check list: Link]
**Quality Standards**:
- [ ] No ticket goes 24+ hours without response
- [ ] Brand voice maintained (friendly, helpful, concise)
- [ ] Ticket properly categorized and assigned
- [ ] Knowledge Base updated with new answers
- [ ] Customer satisfaction score maintained above 90%
**Canned Responses to Use**:
- Template 1: "First Response - General"
- Template 2: "How-to Answer"
- Template 3: "Escalation to Team"
- Template 4: "Issue Resolved"
- Template 5: "Follow-up After 48 Hours"
**Never Say**:
- "I don't know" → Instead: "Let me find that answer for you"
- "That's not my department" → Instead: "I'll connect you with the right team"
- "It's working fine for me" → Instead: "Let's troubleshoot this together"
Copy these templates, edit the bracketed placeholders with your specific tools/processes, and you're 80% done.
Common SOP Mistakes (And How to Avoid Them)
Mistake 1: Writing from memory instead of observing
You will miss steps. Record the task first. Create the SOP from the recording.
Mistake 2: Assuming missing context
You know the reason behind steps. Your virtual assistant does not. Include the reason for each step so they can handle variations.
Mistake 3: Making the SOP too long
Long documents are hard to use. Keep it concise and easy to scan using headings, bullet points, and visuals.
Mistake 4: No version control
Multiple versions create confusion. Add a date to each SOP and record what changed.
Mistake 5: Not updating the SOP
Processes and tools change. Review and update the SOP regularly.
Mistake 6: Skipping testing
The SOP may seem clear to you. Test it with someone unfamiliar with the task. Identify and fix unclear steps.
Mistake 7: No error handling
Define actions for common issues. Include steps for cases where tasks fail or inputs are missing.
How to Scale Your SOP System Without Burning Out?
You've written your first SOP. Great. But you have 47 more tasks to document. Here's how to scale without drowning:
Start with the pain: Document the tasks that hurt most when they're done wrong. Revenue-critical tasks, customer-facing tasks, tasks you explain multiple times per week.
Batch your documentation: Block one afternoon per week for SOP creation. Protect this time. Document 2-3 processes per session.
Use the 80/20 rule: Your SOP doesn't need to cover every possible edge case on day one. Document the happy path first. Add edge cases as they come up.
Make your VA co-author: After they've done a task 3-5 times, have them update the SOP with what was unclear or what they learned. They'll catch things you missed.
Create SOP templates for similar tasks: If you're documenting five different client onboarding processes, create one master template and customize it five times. Don't start from scratch each time.
Set a documentation trigger: Every time you explain a task more than once, that's your signal to document it. If you're explaining it, you'll explain it again.
Implementing SOPs in a small business setting can significantly enhance operational efficiency by standardizing processes. Get something written. Make it better over time.
Using Obsidian and an LLM to Create Multiple SOPs:
Use Obsidian to store all SOPs as structured markdown files in one folder. Create a standard template with sections such as steps, decision logic, access details, and error handling. Record tasks, then use an LLM like ChatGPT to convert the recording transcript into a clean SOP using your template. Ask the LLM to simplify language, remove ambiguity, and format for scanning. Save the output in Obsidian, link related SOPs, and update files as processes change.
What to Do Once Your SOPs Are Written?
Documentation isn't the finish line. It's the starting line.
Make them accessible: Your SOPs are worthless if your VA can't find them. Create a clear folder structure, either on Obsidian, Notion or on Google Drive. Everything in one searchable place.
Train your VA to use them: Walk through 2-3 SOPs together. Show them how to navigate, how to interpret screenshots, how to use decision trees. Make them comfortable with the system.
Create a feedback loop: Add a "Was this SOP helpful?" checkbox at the end of each document. Ask your VA to flag unclear sections. Schedule monthly SOP review meetings.
Track compliance: Not in a micromanaging way, but in a "are these actually being followed" way. If output quality improves, your SOPs are working. If not, they need refinement.
Build on the foundation: Once basic tasks are documented, start documenting more complex workflows. Client onboarding. Product launches. Crisis management. Your SOP library becomes your operational backbone.
Hire faster: When your next VA starts, you have a training library ready. SOPs enhance operational efficiency by streamlining processes and utilizing resources effectively, which can lead to increased profitability. Their ramp time drops from weeks to days.
The Bottom Line
When SOPs are in place, your virtual assistant can complete tasks without repeated questions. Decisions do not depend on you because the SOP includes clear logic. Output becomes consistent because the expected result is defined. Work continues across time zones without delays. Onboarding new virtual assistants becomes faster because they can follow existing SOPs.
Virtual assistants can reduce operating costs, but only if tasks are clearly documented. Start with one task, document it, and assign it. Improve the SOP based on usage. Repeat this process to build a complete system.
