How to Write a Virtual Assistant SOP That Actually Gets Followed

The most common reason virtual assistant relationships fail is not a hiring mistake - it is poor documentation. A capable VA cannot perform well without clear instructions. Writing a standard operating procedure (SOP) is the single most important thing you can do before handing any task to a VA. This guide explains how to write a virtual assistant SOP that is specific enough to be followed, clear enough to reduce questions, and practical enough to be maintained over time.

What a VA SOP Actually Is

A standard operating procedure is a written document that describes exactly how to complete a specific task - step by step, with enough context that someone unfamiliar with the task can complete it correctly without asking for help.

A VA SOP is not:

• A general description of what you want done ("handle customer inquiries professionally")
• A list of goals or principles ("be responsive and friendly")
• A lengthy manual that no one reads

A VA SOP is:

• A step-by-step process document covering a specific task
• Written at the level of the person who has never done it before
• Short enough to read in under five minutes for most tasks
• Specific enough to remove ambiguity on common decision points

The test of a good SOP is simple: can someone who has never done this task follow it and get an acceptable result? If the answer is yes, it is ready to use.

The Five-Part SOP Structure

A practical VA SOP has five components:

1. Task name and purpose - What is this SOP for, and why does it matter? Example: "New client inquiry response - to ensure every inquiry receives a professional response within 20 minutes during business hours."

2. Trigger - What starts this process? Example: "Triggered when a new message arrives in the website contact form inbox or Instagram DMs."

3. Step-by-step instructions - The actual process, numbered, with specific actions. Example:

• Step 1: Check the inquiry for the client's name and question type (pricing, availability, general)
• Step 2: Select the correct response template from [link to template folder]
• Step 3: Personalize the template by inserting the client's name and addressing their specific question
• Step 4: Send the response and log the inquiry in the CRM with today's date, the client name, and the response template used

4. Decision rules - What does the VA do when something is outside the normal case? Example: "If the inquiry mentions a complaint or refund request, forward to [owner email] with the subject line 'Escalation: [client name]' and do not respond until you receive guidance."

5. Examples - One or two examples of the completed task done correctly.

This structure covers most recurring tasks completely. It takes fifteen to thirty minutes to write one SOP properly.

Start With Your Five Biggest Time Drains

You do not need to document every process before you start delegating. Start with the five tasks that consume the most time in your week. Common starting points:

• Email response management
• Appointment booking and confirmation
• Social media content scheduling
• Invoice generation
• Data entry or research tasks

Write one SOP per task. Hand the task to your VA with the SOP and a request to flag anything that was unclear after they complete it the first time. Update the SOP based on their feedback. Within a week, the task runs independently.

Most business owners find that once they start writing SOPs, the process becomes faster and the value is immediately obvious. A Stealth Agents VA starting at $10/hr who has clear SOPs from week one will reach independent operation in days, not months.

How to Write Steps That Are Actually Specific Enough

The most common SOP failure is steps that are too vague to follow. "Send the client an update" is not a step. "Go to the CRM, find the client's record, copy the email address, open Gmail, write a subject line using the format 'Your [service name] appointment on [date]', paste in the confirmation template, and click send" is a step.

When writing each step, ask yourself: "If I handed this to someone who has never used this tool or done this task, would they know exactly what to do?" If the answer is no, add more detail.

Specific decision rules are equally important. Every task has edge cases. Anticipate the most common ones and write explicit instructions for handling them. "If the calendar shows no availability this week, offer the next available slot within seven days. If the client requests something sooner, reply with [specific message] and escalate to [name]."

Screen Recordings as SOPs

For tasks involving software - entering data, navigating a CRM, scheduling in a calendar tool - a screen recording is often more effective than written instructions. A five-minute recording of you completing the task, with narration, gives your VA everything they need to replicate it exactly.

Tools like Loom make recording and sharing these walkthrough videos simple. Pair a Loom recording with a short written checklist and you have an SOP that covers both the visual process and the key decision points in written form.

Maintaining SOPs Over Time

SOPs become stale when processes change and no one updates the documentation. Assign your VA the responsibility of flagging when a step in an SOP no longer matches the current process. Review all SOPs quarterly or when a major tool or workflow change happens.

A living SOP library that stays current is worth more than a comprehensive but outdated document collection. Keep it simple, keep it maintained, and use it as the primary onboarding tool every time a new VA joins.

FAQ

Q: How long should a VA SOP be?

A: Most SOPs for recurring administrative tasks should be one to two pages, or a five to ten minute screen recording. Longer documents get skipped. If a task requires a very long SOP, it is usually better to break it into multiple shorter SOPs - one for each phase of the task.

Q: Should I write SOPs before hiring a VA or after?

A: Writing even three to five basic SOPs before your VA starts significantly speeds up onboarding. You do not need a complete library - just the key tasks you plan to hand off in the first two weeks. Your VA can help you document additional processes over time as they learn your business.

Q: What if my tasks are too variable for a fixed SOP?

A: All tasks have a repeatable core even when the specifics vary. Write an SOP for the decision framework - "when X is true, do A; when Y is true, do B; when neither, escalate to me" - rather than trying to document every possible case. This gives your VA a clear path for handling variability without needing to ask on every edge case.

Q: Can a VA help write their own SOPs?

A: Yes. After completing a task several times, a VA often writes clearer documentation than the original process owner because they experienced the gaps firsthand. Have your VA draft SOPs for their own recurring tasks after the first two weeks, then review and approve. This creates better documentation faster and builds the VA's ownership of the processes they manage.

A well-written virtual assistant SOP is the foundation of a productive VA relationship. It reduces your management time, improves your VA's confidence, and creates the consistent output you need to actually trust and expand delegation. Stealth Agents provides full-time dedicated VAs starting at $10/hr - paired with a straightforward onboarding process that makes SOP-based delegation work from week one.