Updated May 23, 2026
Key Takeaways
- An SOP is only useful if a VA can complete the task from it without asking a single clarifying question - that is the test to apply before finalizing any procedure.
- Build SOPs by recording yourself doing the task first, then transcribing the steps - this method produces better procedures than writing from memory.
- Numbered steps outperform paragraphs because they are scannable, followable, and easier to update when one step changes.
- Each SOP should include a common errors section - this converts your past correction conversations into documented guidance.
- Stealth Agents dedicated full-time VAs start at $10/hr - they execute SOPs well when the procedures are complete, but an SOP library is yours to build.
SOPs are the operational backbone of a VA relationship. Without them, delegation is fragile - dependent on memory, verbal clarification, and your availability. With them, a VA can complete any documented task correctly without interrupting you.
The problem is that most SOPs get written poorly and go unused. This guide covers how to write SOPs that VAs actually follow.
What Makes a VA SOP Useful
A useful SOP passes one test: a VA who has never done the task before can complete it correctly from the written procedure alone, without asking any questions.
This is a high bar. Most SOPs fail it because:
- Steps are at the wrong level of detail (too high-level to follow, or too buried in context to act on)
- Tools and access requirements are not listed upfront
- The expected output is not described - the VA does not know what "done correctly" looks like
- Common errors are not addressed
An SOP that fails this test is not a bad draft - it is an incomplete one. The completion step is having the VA attempt the task from the SOP and noting every question they ask.
The SOP Template
Use this structure for every VA SOP:
SOP Title: [Specific task name]
Owner: [Who manages this SOP]
Last updated: [Date]
Version: [1.0, 1.1, etc.]
1. Purpose (1-2 sentences)
What this task achieves and why it matters.
Example: This SOP covers the process for triaging the business inbox each morning so that urgent client messages are handled within two hours and routine messages are batched for afternoon processing.
2. When to Run
When this task is performed and by whom.
Example: Every weekday by 9 AM ET. Performed by the executive VA.
3. Tools and Access Required
List every tool, system, and credential needed. Include links to the tools and any notes about access level.
Example:
- Gmail (delegated access to main@businessname.com - credentials in 1Password > VA Shared vault)
- Notion (task log - link: notion.so/businessname/task-log)
- Slack (to send escalation messages - #escalations channel)
4. Step-by-Step Instructions
Numbered. Specific. Actionable.
Example:
- Log in to main@businessname.com via Gmail.
- Sort inbox by unread messages, oldest first.
- For each unread email: read the subject and first two sentences to categorize.
- Apply labels: URGENT (response needed today), REVIEW (needs my attention but not today), INFO (no response needed), VENDOR (vendor communication).
- For every URGENT email: draft a reply using the relevant template from Notion > Email Templates. Add draft subject: "DRAFT - [client name]" and move to Drafts folder.
- For every REVIEW email: add a task in Asana: "Review email from [sender] re: [subject]" due today.
- For every INFO or VENDOR email: archive immediately.
- At end of triage: send me a Slack message in #daily-updates: "Inbox triage complete. Urgent: [X] drafts ready for review. Review tasks: [X] added to Asana."
5. Expected Output
What does a correctly completed task look like?
Example: All emails labeled, urgent drafts in Drafts folder, daily-updates Slack message sent, Asana tasks created for any REVIEW items. Zero unread emails remaining in inbox.
6. Common Errors
What mistakes happen on this task and how to avoid or fix them.
Example:
- Mislabeling an URGENT as REVIEW: if in doubt, default to URGENT. I can downgrade; I cannot un-miss an urgent message.
- Drafting a reply for INFO emails: INFO items do not need drafts. Archive them.
- Forgetting the Slack update: the update is required even if there are zero urgent items.
7. Escalation
When to stop and contact you, and how.
Example: If you are unsure how to categorize a message, or if you receive a message that appears to be a legal notice, complaint, or dispute, do not archive or label it. Send it to me immediately in Slack DM.
How to Build Your SOP Library
Step 1: List Every Recurring Task
Start by listing every task you want to delegate. Do not filter by complexity or frequency yet - get everything on a list. Common categories:
- Email management tasks
- Scheduling and calendar tasks
- Research tasks
- Reporting and data tasks
- Client communication tasks
- Vendor coordination tasks
- Social media tasks
Step 2: Prioritize by Frequency and Delegation Readiness
Rank the list by: (1) how often the task recurs and (2) how ready you are to delegate it today. Start with high-frequency, ready-to-delegate tasks. You are building SOPs to unblock delegation, not to document everything simultaneously.
Step 3: Record Before You Write
For each priority task, record yourself doing it - screen recording with narration (Loom works well). Talk through every step as you do it, including the judgment calls. "I label this one URGENT because the client has a deadline tomorrow" is exactly the context that belongs in an SOP but never makes it into a written procedure drafted from memory.
After recording, transcribe the steps into the SOP template. Fill in the common errors and escalation sections from memory of past problems.
Step 4: Pilot the SOP
Have the VA attempt the task from the written SOP alone. No verbal explanation - just the document. Note every question the VA asks. Each question is a gap in the SOP. Add the answer to the relevant section.
After one successful pilot run with no questions, the SOP is complete.
Step 5: Maintain and Update
SOPs go stale when tools change, processes evolve, or you discover better approaches. Assign the VA as a co-owner who flags when a step is outdated. Review every SOP once per quarter - take 15 minutes to skim through your active SOPs and verify they still reflect reality.
FAQ
Q: How long should an SOP be?
A: As long as it needs to be and no longer. Simple recurring tasks (archive emails by label, update a CRM field) might need five numbered steps. Complex tasks (prepare a monthly financial summary from multiple sources) might need fifteen steps with screenshots. Length is determined by task complexity, not by convention.
Q: Should I use screenshots in SOPs?
A: For tasks involving specific UI navigation (clicking through a CRM, using a specific software feature), screenshots reduce ambiguity significantly. For tasks that are primarily written or judgment-based (drafting emails, triaging tickets), screenshots add less value. Use them where they eliminate a potential confusion point.
Q: Can the VA help write SOPs?
A: Yes, and they often should. After the VA has done a task several times, ask them to write a draft SOP from their experience. Review and correct the draft. This produces more accurate procedures than you writing from memory, and builds the VA's documentation habit.
Q: What if a task involves judgment that is hard to document?
A: Document the judgment criteria explicitly. "If the client has an active project in the CRM, treat as URGENT. If not, treat as REVIEW" is a judgment rule that can be written. For genuinely subjective tasks, document the examples - "here are three past instances where I labeled it X and why." Examples are often more useful than abstract rules.
An SOP library is a business asset that outlasts any individual VA relationship. If the VA leaves, your next hire onboards in days rather than weeks. Stealth Agents dedicated full-time VAs start at $10/hr and execute documented procedures reliably - the SOPs are yours to build, but the investment pays for itself within the first month.