How to Train a Virtual Assistant
A structured 30-day training plan that actually gets a virtual assistant to autonomy - without burning your evenings on hand-holding.
What you will learn
- How to sequence training tasks from simple to complex
- The Loom-first documentation habit
- Weekly review structure for the first 30 days
- How to give feedback that builds skill, not anxiety
- Signs the VA is ready for autonomy
Before you start
- You have completed the VA hiring process with a clear scope
- You have identified 10-15 recurring tasks to hand off
- You have allocated 6-10 hours in week 1 for training
- You have basic documentation or are willing to create it
The step-by-step process
Step 1: Week 1: Tools, accounts, and two simple recurring tasks
On Day 1, provision Google Workspace, Notion, Slack, your CRM, and any scheduling tools. Run a 60-minute kickoff on your business and working style. Assign two simple recurring tasks (for example, daily inbox triage and weekly CRM hygiene). Record Loom videos as you walk through each. Do a 15-minute daily check-in all week. Small wins early build confidence for harder tasks later.
Step 2: Week 2: Add two task categories and introduce async communication
Add two more task categories: calendar management and basic research. Switch from daily video check-ins to async written updates in Slack or a shared doc. Your VA should end each day with: tasks done, tasks blocked, and tasks planned for tomorrow. You respond in the morning. This small shift saves 3-4 hours of meeting time per week while keeping visibility.
Step 3: Week 3: Raise the bar on judgment tasks
Week 3 is where you trade speed for quality. Ask the VA to draft emails on your behalf, research vendors with a decision memo, or plan a complex trip. Expect imperfect output. Feedback should focus on the specific judgment call (why this vendor over that one, why this tone over that one), not the output quality alone. This is where real skill is built.
Step 4: Week 4: Delegate a project end-to-end
Pick a project with 5-10 steps and a clear definition of done: a new-hire onboarding packet, a competitive audit, a contact-list cleanup, or an event coordination. Set a deadline, share relevant context, and step back. Review at end-of-project. Projects build autonomy faster than tasks because they force the VA to think in full workflows.
Step 5: Run a weekly 30-minute 1:1
A standing 30-minute Friday 1:1 with three sections (wins, blockers, questions) is the single highest-leverage ritual in VA training. The VA drafts the agenda in advance; you come prepared. Use the time to coach on judgment, unblock decisions, and set priorities for next week. Skipping these is the single strongest early indicator of a relationship that will end badly.
Step 6: Build a living SOP library
Set the rule: any task you do twice becomes an SOP. Use a shared Notion or Google Drive folder. Each SOP should include: purpose, inputs, step-by-step, edge cases, and contacts. By day 30 you should have 10-20 SOPs. This library is the real asset of the training period - it outlasts any one VA and cuts onboarding for the next one in half.
Step 7: Day 30 review: autonomy signals and next phase
At day 30, look for three signals of autonomy: the VA flags issues before you notice them, proposes improvements to SOPs, and closes the loop on tasks without reminders. If those signals are present, move to weekly 1:1s with less frequent check-ins. If they are not, diagnose: is it capacity, clarity, or confidence, and address the specific gap rather than redoing the whole onboarding.
Common mistakes to avoid
- Training once and expecting retention - repetition and documentation matter
- Feedback only when something goes wrong - positive reinforcement is as important
- No written SOPs - you become the single point of failure
- Skipping weekly 1:1s after week 2 - autonomy without reviews becomes drift
- Expecting perfection in week 3 judgment tasks - coach, do not correct silently
Tools and templates
- Loom for screen recordings
- Notion or Google Docs for SOPs
- Slack for async daily updates
- Calendly for meeting scheduling
- 1Password or LastPass for shared credentials
Skip the trial-and-error.
We have hired, onboarded, and managed remote teams for hundreds of businesses. Get matched with pre-vetted candidates in 5-7 business days.
Book a Free Discovery Call →Frequently asked questions
How much of my time should VA training take in week 1?
Realistically 6-10 hours. Much less and the VA will not ramp; much more suggests unclear scope or missing SOPs that need to be written.
What if the VA is not improving after 30 days?
Diagnose precisely: capacity, clarity, or confidence. If the gap is capacity, reset scope. If it is clarity, write better SOPs. If it is confidence, lean into coaching. If none of those move the needle, initiate a fit conversation.
Should I record every task on Loom?
The first time you teach a recurring task, yes. After that, the VA should update or create the SOP and only re-record for major process changes.
How do I measure VA output quality objectively?
Define a small set of output-based KPIs: task turnaround time, inbox zero by EOD, scheduling accuracy. Review weekly in the 1:1.
Can I train a VA while I am traveling?
Yes, but only with pre-recorded SOPs and async communication discipline. Training a new VA while bouncing across time zones without written materials almost always fails.