Most VAs ramp in 30 days when the first 4 weeks are structured. Here's the exact plan we use with every new client.
Goal: your VA can get into every system and shadow your routines.
Do this in week 1: grant logins via password manager, share your calendar and inbox in read mode, and record 5–7 short Looms walking through your daily and weekly rituals.
Goal: your VA fully owns 3–5 recurring tasks end-to-end, with daily check-ins.
Examples: inbox triage by 9am, calendar audit by Friday EOD, CRM hygiene daily, weekly report drafted by Monday.
Goal: your VA writes the SOPs for what they now own. This is the asset that makes the role replaceable and trainable forever.
You review and approve. Daily check-ins drop to 15 minutes.
Goal: layer in 2–3 tasks that require more judgment, and shift to a single weekly 30-minute sync.
By the end of week 4, you should be saving at least 8 hours a week and your VA should be making low-stakes decisions without you.
Most onboarding plans start at week 1 — VA day one. The plans that actually work start a week earlier, with what we call week zero: the prep you do before the VA logs in. Without it, week 1 turns into a scramble of access requests, missing logins, and ad-hoc explanations. With it, week 1 starts with the VA shadowing real workflows on day one.
Week zero is short — usually 2–3 hours of prep over a few days. It includes: setting up shared folders and access in your password manager, recording 5–7 short Looms walking through your daily and weekly routines, drafting a 1-page 'how I work' document (tone of voice, communication preferences, decision-making style), and scoping the first 3 recurring tasks the VA will own. None of this is exotic. All of it pays back 5x in week 1.
Each week of the ramp has a different signal. Week 1 is about access and observation — by Friday, the VA should be able to navigate every tool without your help. Week 2 is about owned recurring tasks — by Friday, the VA should be running 3–5 workflows end-to-end with daily check-ins. Week 3 is about SOP creation — by Friday, the VA should have written first-draft SOPs for everything they own. Week 4 is about expansion and judgment — by Friday, you should be saving 8+ hours a week and the VA should be making low-stakes decisions without you.
If a week's signal isn't met, don't push forward — work the gap. Most ramp problems compound when you skip past a missed milestone. The whole 30-day plan is built on the assumption that each week's foundation supports the next.
The single most important meeting in the first 30 days is the Friday review. 30 minutes, same time every week, non-negotiable. The agenda is fixed: what did the VA own this week (and how did it go), what's coming next week, what's blocked, and one specific piece of feedback in each direction. That cadence does three things — it surfaces problems while they're still small, it builds the trust that lets you expand decision rights faster, and it gives the VA a predictable rhythm to plan against. Skip it and the ramp slows; protect it and the role compounds week over week.
Talk to us about staffing a VA matched to your industry, tools, and tone.
A great SOP is a 3-minute Loom plus a 1-page checklist. Here's how to produce them in under an hour each.
12 things to set up before your VA touches anything sensitive — from password managers to access reviews.
Put what you learned into practice — see the roles we staff and the industries we serve.