How to Create SOPs for Your Virtual Assistant Using the 80/20 Method (Without Writing Documentation All Day)

You know you need SOPs for your VA. You have known this since the third time you answered the same question about the same process. You also know that writing documentation is not where you want to spend your Tuesday afternoon, or any afternoon. SOPs feel like a tax on expertise: the more you know how to do, the more you owe the documentation system. The 80/20 SOP Method resolves this tension entirely. You spend 20 minutes per process. The VA does most of the writing. You get documentation that actually reflects how your business runs, not an idealized version you drafted at a desk.

The method is called 80/20 because the labor split is approximately 80 percent VA, 20 percent you. You provide the source material, a recording of yourself doing the task, and your VA converts it into a draft. You review and correct. The result is an SOP that is complete, accurate, and written in a way that the person learning the process can actually follow.

Why Record-Then-Draft Is Superior to Writing-First

The standard approach to SOP creation is to sit down and write the SOP from memory or from notes. This approach has three structural problems that the 80/20 Method eliminates.

The curse of knowledge. When you write from memory, you omit steps that feel obvious because you’ve internalized them. You skip the decision points you make unconsciously. The resulting document is complete enough for someone who mostly knows the process, and useless to someone learning it from scratch. When a VA watches a recording and writes what they see, they include the steps that feel obvious to you because those steps are not yet obvious to them. The draft is more complete before you touch it.

Writing is slower than talking. Recording yourself doing the task takes 5 to 8 minutes. Writing the same content would take 30 to 45 minutes, and the written version would be less complete. The recording captures your actual workflow, the clicks, the pauses, the decisions, in real time. No translation is lost between the doing and the documenting.

You write one good draft; a VA can write the first draft faster. Your time is the scarce resource. The 80/20 Method preserves it. You spend 8 minutes recording and 10 minutes reviewing. The VA spends 30 to 60 minutes converting and drafting. The division of labor matches the value of the time on each side.

The Standard SOP Template Structure

Every SOP in your library should follow the same template. Consistency makes the library usable, your VA can navigate any SOP without reorienting to a new format each time. The standard six-section template:

Name. The exact name of the task or process, formatted consistently. Use title case. Example: “Client Invoice Generation, Monthly Cycle.”

Purpose. One to two sentences describing why this process exists and what it produces. “This SOP governs the monthly invoicing process for all retainer clients. Output is a sent invoice for each active client, filed in the Invoices folder and logged in the billing tracker.”

Trigger. The specific event or condition that initiates this process. “This process is triggered on the 28th of each month, or the first business day before if the 28th falls on a weekend.”

Steps. Numbered, sequential, imperative. Each step begins with an action verb. Each step covers exactly one action, not “log in and navigate to the billing section” but two separate steps: “Log in to [Tool]” and “Navigate to Billing > Invoices.” Screenshots can be embedded after steps where the visual state of the screen matters.

Edge Cases. A bulleted list of situations that deviate from the standard flow and what to do in each one. “If a client’s billing address has changed since last month, update the address in [Tool] before generating the invoice.” This section is where most SOPs fall short. Require at least two edge cases for every SOP, if your VA can only identify one, the process has not been examined carefully enough.

Output Standard. A description of what a correctly completed task looks like. “Invoice is sent to client’s billing email, a copy is filed in [Client Name] > Invoices > [Year], and the invoice number is entered in the billing tracker with status ‘Sent.’” Output Standards make verification possible without a meeting.

What Makes a Bad SOP

Too long. An SOP that takes more than five minutes to read will not be followed faithfully. If a process is genuinely complex, break it into sub-processes, each with its own SOP. A network of short SOPs is more navigable than one long document that attempts to cover everything.

Missing edge cases. The edge case section is not optional. The steps section covers the 80 percent, the normal, expected flow. The edge case section covers the 20 percent that causes 80 percent of the questions. A VA following an SOP that has no edge cases section will encounter an unexpected situation, stop, and message you. A VA following an SOP with a thorough edge case section will find the answer in the document and continue. That difference, multiplied across every process in your business, is the difference between a VA who runs independently and one who requires daily management.

Assuming shared context. “Log in to the usual account” is not a step. “Log in to [email address] using the password stored in LastPass under ‘Client Billing Tool’” is a step. SOPs written by experts frequently assume context that is not available to the person learning the process. The test is simple: can a competent professional who has never worked with you before follow this SOP to completion without asking a question? If not, it needs revision.

No output standard. Without an output standard, quality is subjective. Your VA thinks the task is complete; you think it’s 70 percent done. The disagreement is not about work ethic or capability, it is about the definition of “done” being implicit rather than written. Every SOP needs an explicit output standard.

Passive voice throughout. “The invoice should be sent” is ambiguous. Who sends it? By when? “Send the invoice to [client email] by 5pm on the trigger date” is actionable. Write every step in active, imperative voice. Subject is implicit: you, the person reading the SOP.

How to Build an SOP Library Over Time: Rolling Documentation

The largest SOP libraries are not built in documentation sprints. They are built through rolling documentation, a discipline where every VA interaction that involves a repeatable process generates a new SOP.

The trigger for rolling documentation is simple: any time you answer the same question twice, you owe the system an SOP. Any time you review your VA’s work and give the same piece of feedback for the second time, you owe the system an SOP. Any time a task takes longer than expected because your VA was navigating without documentation, you owe the system an SOP.

To operationalize rolling documentation, add one item to your weekly VA management routine: a five-minute review of the past week’s work. Ask two questions. First: were there any tasks this week where my VA had to ask a question they shouldn’t have needed to ask? Second: were there any tasks where my VA completed the work but I had to give substantive corrections? For each yes, schedule a 10-minute recording session in the following week to create the missing SOP.

Within 90 days of consistent rolling documentation, most VA-managed businesses have 20 to 40 SOPs covering the core recurring processes. At 40 SOPs, a new VA can be onboarded in roughly half the time of a business with no documentation. At 60 to 80 SOPs, the business can absorb a VA transition without meaningful disruption, the next person can learn from the library rather than from you.

Building Version Control Into Your SOP Library

SOPs decay. Processes change, tools update, standards evolve. An SOP written in January 2024 for a tool that released a major update in August 2024 is not just outdated, it is actively misleading. Build version control into your library from the start.

Every SOP file name includes the version number and date: “Client Invoice Generation, SOP, v1, 2024-01-15.” When an SOP is updated, the new version is saved as v2 with a new date. The old version is archived, not deleted, you may need to reference it if a process is rolled back or if an audit requires documentation of how a process was run at a specific point in time.

Require your VA to flag any SOP that contains a step they cannot complete as written because a tool or process has changed. That flag is a prompt to schedule a 10-minute recording session and generate v2. This feedback loop keeps the library accurate without requiring you to audit it proactively.

Your Next Step

Choose the single process that causes your VA the most friction right now, the one they ask you about most frequently, or the one where your review feedback is most repetitive. Open Loom. Record yourself doing the process at normal speed, narrating as you go. Send the link to your VA with the SOP template and a 24-hour deadline for the draft. Block 12 minutes on your calendar for tomorrow afternoon to review and finalize it. That one SOP, completed in two 10-minute sessions on your end, eliminates a recurring friction point and adds the first entry to your SOP library. Run the same process for a second task the following week. In 60 days, the library exists. In 90 days, it works.