Module 4: Onboarding & SOPs
Most VA relationships die in week one — not from bad hiring, from bad onboarding. You found a good person, handed them chaos, and wondered why nothing worked. This module gives you the first-week plan that builds trust fast and the documentation habit that makes delegation stick.
The first-week plan
Day one has two jobs: get your VA into the tools, and get them a win. Grant access through a password manager (shared vault, never your actual passwords typed into a message), then hand them one tiny task they can finish in under an hour — flagging five emails, booking one appointment, cleaning one list. The task is not the point. The point is they finish something on day one and think: I can do this job.
Day two, they shadow you on one real task. Share your screen, talk through what you are doing and why, and let them ask questions. Day three, they do that same task while you watch — and you review the result together, correcting course in real time. Day four, introduce a second task using the same pattern: you show it once, they do it, you review. Day five is the week review: what went well, what was confusing, and a clear task list for next week.
Why small wins first? Confidence compounds. A VA who nails three small tasks trusts you, trusts themselves, and takes bigger tasks seriously. A VA handed your entire backlog on day one learns one lesson: this job is overwhelming. You hired carefully — do not throw away the hire with a chaotic start. On day one, share only what they need: the password vault, the task board, and the messaging channel. Full email or admin access comes later, once trust is earned, never before.
Week 1 confidence builds task by task
Build brief
What does your VA's day-one win look like — the smallest task that proves the relationship works?
Saved
The SOP Rule
Here is the rule that changes everything: The SOP Rule — if you explain it twice, write it down. The first time you show someone a task, that is teaching. The second time, that is a signal: this task will be done again and again, and it needs a written record. The third time you explain it from memory, you have wasted time you will never get back.
An SOP that actually gets followed has exactly four parts. First, the goal: what "done" looks like, so the VA knows when to stop. Second, the steps: numbered, in order, with no step skipped — including the steps that feel obvious to you. Third, one screenshot or short video per tricky step, because words fail where images succeed. Fourth, the "when stuck" line: who to ask, what to do, and what never to do without checking first. Keep every SOP in one shared folder, not scattered across messages.
Take inbox triage. A bad SOP says: "Check my email and handle the important stuff." The VA guesses, deletes something important, and you stop delegating. A good SOP says: "Goal: every morning my inbox holds only emails needing my reply. Steps: 1) flag client emails, 2) archive newsletters, 3) forward invoices to the bookkeeper. Screenshot: the flag button is here. When stuck: anything from a stranger asking for money goes to me before you act." Same task, two outcomes. The difference is not your VA. It is the document.
Same task, two outcomes
Vague SOP vs. working SOP
| SOP part | Vague version | Working version |
|---|---|---|
| Goal | “Check my email” | “Inbox holds only emails needing my reply” |
| Steps | Handle the important stuff | 1) Flag clients 2) Archive newsletters 3) Forward invoices |
| Visual | None | Screenshot of the flag button |
| When stuck | Figure it out | Stranger asking for money goes to me first |
Build brief
Which task have you already explained twice (to anyone)? That's your first SOP — name it.
Saved
Loom walkthroughs
The fastest way to write an SOP is to never write it at all — record it. Open a screen recorder, do the task once, and talk through what you are doing and why. "I flag client emails first because those are the only ones I answer personally. Newsletters get archived — see this button here." One recording, done in real time, becomes the training. Your VA watches it, follows along, and asks questions in the document comments.
Keep each recording to fifteen minutes maximum. If the task takes longer than that, it is not one task — it is two or three tasks bundled together, and you should split them. A thirty-minute video gets skimmed; a ten-minute video gets watched twice. Long recordings also hide the structure: when you split by task, each recording maps to one SOP, and your library stays searchable. Ask the VA to watch each video and reply with one question — questions surface the gaps your recording missed, and you add the answer to the SOP.
Your library of walkthroughs becomes more valuable than you expect. When you hire VA number two and three, they watch the same videos instead of pulling hours from you or from your first VA. Adopt a naming convention from the start: TASK-NAME plus the date, like "inbox-triage" with the month recorded. Six months from now, when a process changes, you will know exactly which recording is stale. Record one good walkthrough and you train every future hire for free.
Keep it short
How much of a walkthrough gets watched
Example for illustration — not real results.
Build brief
List every tool and account your VA needs on day 1, and how you'll grant access securely.
Saved
Week one: your VA finished the inbox triage differently than you would have, but nothing broke and clients are happy. Do you rewrite the SOP?
Your turn: Write your first SOP using the 4-part format — goal, numbered steps, a visual note per tricky step, and the "when stuck" line. Pick your simplest handoff task.
Saved.
Your next 24 hours
Record one screen walkthrough of your simplest task — under fifteen minutes. Name it TASK-NAME plus the date, and save it in your shared SOP folder. That's the first entry in your training library.
Steal this template
Module 4 cheat sheet
- Week one runs five days: tools plus a tiny win, shadow, do-with-review, second task, week review.
- Small wins first — confidence compounds and early trust pays for months.
- The SOP Rule: explain it twice, write it down.
- Every SOP has a goal, numbered steps, a visual per tricky step, and a "when stuck" line.
- Record screen walkthroughs under fifteen minutes; name them TASK-NAME plus date.
- Grant access through a password manager — never send real passwords in messages.