Virtual Assistant Training Guide: Onboard Your VA in 2 Weeks

Hiring a virtual assistant is the easy part. Training one so you can actually stop thinking about the tasks you handed over - that is where most business owners get stuck. The onboarding period is short but high-leverage. Done right, it produces a VA who operates with minimal oversight within a month. Done wrong, it produces a VA who is always asking for clarification and a business owner who is always correcting.

Here is a training guide that works.

Week One: Access, Orientation, and First Tasks

Day 1 - Access and Context

Before the VA touches any task, get them set up:

• Access provisioning: Add them to the tools they need - email (as a delegate, not a forwarded alias), calendar, project management tool, password manager (create a shared vault, never send raw credentials), cloud storage folder.
• Company context: Send a short written brief (one page is enough) covering: what the business does, who the clients are, the communication norms you expect (response time, tone, escalation path), and who they report to.
• Role context: Clarify the specific tasks they are being hired for and what success looks like at the 30-day and 90-day marks.

Resist the urge to front-load every piece of information on Day 1. People absorb less than they think when starting a new role. Keep Day 1 to access + context and one simple first task.

Days 2-3 - First Task Walkthrough

Pick one recurring task the VA will own and walk through it step by step. Use a Loom video if you are in different time zones - record yourself doing the task narrating each step as you go. This video becomes a permanent training resource.

After the walkthrough, have the VA complete the task once while you are available for questions. Review the output together. Document what they got right and what needs adjustment as a note you will add to the SOP.

Days 4-5 - Expand to Two or Three Core Tasks

Once the first task is running smoothly (even at 80% quality), add two more recurring tasks using the same walkthrough process. By end of Week 1, the VA should have three to five tasks they are executing on their own.

Do not try to train everything in Week 1. Depth on a small number of tasks outperforms surface coverage of many.

Week Two: Repetition and Calibration

The Repetition Loop

Week 2 is where habits form. The VA is executing the Week 1 tasks without hand-holding. Your job is to review outputs daily, provide specific feedback, and update the SOPs where your feedback reveals documentation gaps.

A common mistake is to review output once a week and give a batch of corrections. This slows learning. Daily lightweight review - even just 5-10 minutes - gives the VA calibration signals while the tasks are fresh.

Introducing New Tasks

If the core tasks are running well by midweek, introduce one new task using the same walkthrough process. Keep the same structure: record or narrate, observe the first attempt, document feedback.

The Week 2 Sync

At the end of Week 2, schedule a 30-minute live conversation to cover:

• What tasks are now running reliably
• What still has quality gaps and why
• What the VA needs from you to keep improving (more examples, updated SOPs, faster feedback)
• What to prioritize in Week 3 and beyond

This conversation is important because it surfaces things that do not appear in task output - the VA's sense of where they are stuck, what they are uncertain about, and where the communication is working or not.

Building Your SOP Library

Standard operating procedures are the backbone of VA training. A VA with good SOPs can handle tasks without asking you questions. A VA without SOPs will ask the same questions repeatedly.

A good SOP for a VA task includes:

1. Purpose - one sentence explaining what this task achieves
2. When it runs - daily, weekly, triggered by X event
3. Tools required - with links to the relevant tools and any login notes
4. Step-by-step instructions - numbered, specific, with screenshots where useful
5. Common errors - what goes wrong and how to fix it
6. Output standard - what a correctly completed task looks like
7. Escalation path - who to contact and how if something falls outside the documented steps

Write SOPs for every recurring task within the first month. The act of writing them will reveal gaps in your own process documentation.

Format tip: Numbered steps are better than paragraphs. "1. Open the CRM. 2. Filter contacts by last contacted more than 30 days ago. 3. Export to CSV." is better than "Go into the CRM and find the contacts who haven't been contacted recently, then export them."

Month One: Moving Toward Autonomy

The goal for Month 1 is a VA who can handle their core task list with minimal daily direction. Signals that you are on track:

• The VA completes tasks without asking clarifying questions you have already answered
• Output quality is consistent across the recurring task set
• The VA flags blockers proactively rather than going silent
• You are reviewing output, not correcting the process

If you are still answering the same questions in Week 4 that you answered in Week 1, the answers need to be documented in SOPs, not repeated verbally.

Common Training Mistakes

Training too much at once: Flooding a new VA with 20 tasks in Week 1 produces superficial coverage. Start narrow and expand.

Inconsistent feedback timing: Feedback given two weeks after a task is too late to calibrate effectively. Keep it within 24 hours where possible.

No written SOPs: Verbal training alone means every new task relies on memory. Written SOPs are the asset that survives staff turnover and makes replacement training faster.

Expecting full autonomy in Week 1: Even the most experienced VA needs a calibration period for your specific preferences, tools, and communication style. Two weeks of active investment usually produces 12+ months of smooth operation.

FAQ

Q: How long does it take for a VA to be fully trained?

A: For a focused set of recurring tasks, most VAs reach solid independence within four to six weeks. More complex roles or wider task sets take eight to twelve weeks. The timeline depends heavily on how well the first two weeks go - poor onboarding doubles the calibration period.

Q: Should I use video walkthroughs or written SOPs?

A: Both. Video walkthroughs (Loom) are better for the initial introduction because they show context, not just steps. Written SOPs are better for ongoing reference because they are searchable and editable. Record the Loom, then transcribe the steps into a written SOP.

Q: What if the VA keeps making the same mistake?

A: Check the SOP first. If the mistake is not addressed in the written documentation, add it. If it is documented and still recurring, that is a performance conversation - be direct about the specific expectation and ask the VA what is getting in the way.

Q: Is it worth training a VA for tasks that only take me 10 minutes?

A: If the task recurs daily or weekly, yes. Ten minutes per day is 40 hours per year. Training a VA to own it takes two to three hours of SOP writing and oversight. The math works within a month.

A structured two-week onboarding investment is what separates a VA who runs on their own from one who constantly requires direction. Stealth Agents dedicated full-time VAs start at $10/hr and come with professional foundations - but your SOPs, task context, and first-week feedback are still what make the relationship productive long-term.