SOPs and systems
The stranger test
Here's the question that separates task-doers from system-builders: if you disappeared tomorrow, could a stranger run your work from your documentation alone? For most VAs the honest answer is no — the process lives in their head, which means the client is renting their memory, not buying an asset. An SOP (standard operating procedure) is how you turn what you do into something the business owns. Paradoxically, documenting yourself makes you more valuable, not less: clients promote the VA who builds systems and hand the documented grunt work to someone cheaper — or to AI.
The anatomy of an SOP that works
Every SOP you write has six parts, in this order:
- Title + purpose — the task and why it exists ("Weekly invoice run — keeps cash flow visible and vendors paid on time")
- Trigger — what starts it: a date, an event, a request ("Every Friday" / "When a signed contract arrives")
- Tools and access — exactly what's needed: QuickBooks login, the shared Drive folder, the Slack channel
- Steps — numbered, one action per step, with a screenshot or 30-second Loom for anything visual
- Exceptions — what to do when it breaks ("If the amount differs from the PO by more than $50, stop and ask — never adjust it yourself")
- Owner + last updated — who maintains this doc and when it was last verified
The exceptions section is the one amateurs skip and seniors obsess over. Real processes break weekly. An SOP that only covers the happy path fails the stranger test the first time reality shows up.
One step, one action
Watch the difference. A bad step: "Send the invoices." A real SOP breaks that into what actually happens:
Granularity feels tedious while writing. It's the entire point. The stranger doesn't know that "the template" means the second one, or that big amounts are politically sensitive.
The process inventory: finding what to document
You can't systematize what you haven't named. The process inventory is a 20-minute exercise that surfaces every recurring task in your role:
- List everything you did in the last two weeks — small stuff included. Aim for 25+ items.
- Mark each one R (recurring) or O (one-off). Ignore the one-offs.
- Score each recurring task 1–5 on frequency and 1–5 on pain-if-done-wrong.
- Multiply. The top three scores are your first three SOPs.
SOPs are a career asset, not homework
Every SOP you write does three jobs. It makes your work survivable (you can take a sick day without the business wobbling). It makes you promotable (Jorel in Iloilo documented his founder's entire client-onboarding flow, then trained two new VAs to run it — he now manages both at $11/hr (~₱640/hr) while they execute). And it fills your portfolio: a well-written SOP with Loom walkthrough is the single most convincing artifact an admin VA can show a hiring manager, because it proves systems thinking in a way no resume line can.
Do this now
Run the process inventory on your own life if you don't have client work yet: list 25 recurring things you do (paying bills, backing up files, preparing for class or church or content posting). Score, multiply, pick the winner. Then write a full SOP for it using all six parts — title, trigger, tools, numbered one-action steps, at least two exceptions, owner line. Give it to someone in your household and watch them try to follow it without your help. Every place they stop and ask you something is a hole; patch it. The final doc joins your portfolio. 25 minutes.
Tip: use your ← → arrow keys.