Most founders treat their first week with a virtual assistant like the first day of college. They hand over a syllabus of tasks, a folder of logins, a Loom video that's 47 minutes long, and then wonder why the person is quietly drowning by Thursday. Two weeks later, the VA is gone or the founder is doing the work themselves again, muttering that good help is impossible to find.
The problem isn't the VA. The problem is the onboarding. When you compress what should be a 30-day ramp into 72 hours, you get shallow understanding, brittle habits, and a person who's afraid to ask questions because they think they should already know. Good VA onboarding is boring on purpose. It's slow at the start so it can be fast for the next two years.
Here's the day-by-day playbook we use with clients who place their first full-time VA. It works whether you hired through us or somewhere else. And it explains why week two is where the real work actually starts.
Before They Start: The 60-Minute Prep
Onboarding a virtual assistant fails when you improvise on day one. Block 60 minutes the Friday before they start. Do these four things and nothing else.
Create their accounts. Email, project management tool, password manager, shared drive. Add them to Slack or whatever you use for chat. Send the calendar invites for week one before Monday morning. If they show up on day one and spend two hours waiting for logins, you've already lost trust.
Write one document called "How I Work." One page. Your hours, your response expectations, how you like to be interrupted, what you consider urgent, and what you consider a fire drill. This one page prevents more misunderstandings than any training video.
Pick their first small win. Something they can complete by end of day two that shows visible value. Not a project. A task. Something like cleaning up your inbox rules, or building a simple tracker in a spreadsheet. New hires need proof they belong.
Finally, tell your team they're starting. Sounds obvious. Half the founders we work with forget. Then the VA emails a client and gets ignored because nobody knew who they were.
Day One: Context, Not Tasks
Resist the urge to assign work on day one. Your job on Monday is to install context, not output.
Start with a 45-minute video call. Walk through the business. What you sell, who buys it, how money comes in, what a good week looks like versus a bad week. Show them your calendar. Show them the last three deals you closed. Show them the client you're worried about losing. This is not fluff. A VA who understands your business makes better decisions on autopilot six months from now.
Then hand over the "How I Work" doc and read it together. Answer questions. Add anything you forgot.
Give them one task for the afternoon. Something observational. Ask them to spend two hours inside your email, your CRM, or your project tool and come back with five questions. Not fix anything. Just look. This forces them to explore without pressure, and their questions will tell you exactly where your systems are unclear.
End the day with a 15-minute check-in. Ask what surprised them. Ask what confused them. Write it down.
Day Two: One Real Task, End to End
Tuesday, they do one thing all the way through. Not five things halfway.
Pick something with a clear start, middle, and end. For an executive admin, that might be booking a week of meetings from your inbox. For a video editor, cutting one short from a longer recording using your template. For a lead gen VA, sourcing 25 contacts from a defined list and running them through your enrichment tool.
Record a Loom while you do it once. Then have them do the next one while you watch. Then let them do the third one alone and review it before it goes anywhere. This is the show-one, do-one-together, do-one-alone method. It takes longer on Tuesday. It saves you 40 hours over the next month.
Do not correct every small thing. Correct the two or three things that matter. New hires who get 15 pieces of feedback in one sitting remember zero of them.
Day Three: Introduce Systems, Not Software
By Wednesday, they've seen enough to understand why your systems exist. Now walk them through how the pieces connect.
Draw the flow. Literally. Open a whiteboard tool or grab a piece of paper and sketch how a lead becomes a client, how a project becomes an invoice, how a support ticket becomes a resolved issue. Most founders skip this because it's obvious to them. It's not obvious to a new person, no matter how experienced.
Then map their role onto the flow. Where do they touch things? Where do they hand off? Who's downstream of them? This is the difference between a VA who executes tasks and a VA who owns outcomes.
Give them a second task on Wednesday afternoon, ideally something adjacent to Tuesday's task. You want reps, not variety, in week one.
Day Four: Let Them Ask The Uncomfortable Questions
Thursday is when the honeymoon ends. They've been polite. They've been nodding. They've been writing things down. Now they have real questions, and if you don't create space for them, they'll never surface.
Block a 30-minute call and open with, "What's confusing? What contradicts something else I told you? What am I doing that seems weird?" Then shut up. The silence is uncomfortable. Wait through it.
The answers you get on day four are gold. They reveal where your process is broken, where your instructions contradict, and where you assume knowledge that doesn't exist. Fix what you can that day. Add it to the "How I Work" doc so the next hire doesn't hit the same wall.
Then give them a slightly harder task. Something where they have to make one or two small judgment calls. Watch what they choose. Their choices tell you how they think.
Day Five: Their First Solo Deliverable
Friday, they own something start to finish without you looking over their shoulder. It should be something you'd be genuinely annoyed to have to do yourself.
Set the expectation clearly. Here's the input, here's the output, here's when I need it, here's what "done" looks like. Then leave them alone for four hours.
When they submit it, review it once. Not five times. Give them one piece of positive feedback and one piece of constructive feedback. Then end the week with a 20-minute retro.
Ask three questions. What went well this week? What was hardest? What do you want to work on next week? Take notes. These notes become your week two plan.
Why Week Two Matters More
Here's the part nobody talks about. Week one is scripted. You planned it. You prepared. You showed up. That's easy to sustain for five days.
Week two is when your calendar comes back. The client emergencies return. The prospect who's been ghosting you finally responds. You get busy again, and the natural thing to do is assume the VA is fine because they made it through week one.
They're not fine. Week two is when everything they learned starts to fade unless you reinforce it. It's when they start to make small mistakes because they're operating on their own for the first time. It's when the good habits either lock in or the bad habits do.
Do these four things in week two and your retention triples.
Daily 10-minute check-ins. Not meetings. Just a quick sync at the start or end of the day. What are you working on? Anything stuck? This is not micromanagement. This is scaffolding. You'll drop to three per week by week four and one per week by month three.
NDWritten feedback on their first three deliverables. Not verbal. Written. Verbal feedback disappears. Written feedback becomes a reference document they'll pull up in month two when they're doing the same task and can't remember exactly what you said.
One new skill introduced. Just one. Do not pile on. If they nailed calendar management in week one, week two might add inbox triage. Small expansion. Compound growth.
A frank conversation on Friday. Not a review. A conversation. Are they enjoying the work? Do they feel set up for success? What would make their job easier? Founders who ask these questions in week two find out about problems while they're still small. Founders who don't ask find out in month three when the VA quits.
The 30-Day Arc
Zoom out. Here's what good remote employee onboarding looks like across the full first month.
Week one: Context and one deliverable. They should end the week understanding your business and having completed one thing you'd have paid someone else to do.
Week two: Reinforcement and one new skill. They should end the week doing week one's work faster and having started something new.
Week three: Ownership begins. Pick one recurring responsibility and hand it to them fully. They own the outcome, not just the task. Something like "our inbox is at zero by 6pm every day" or "every video we post has a thumbnail by Tuesday."
Week four: Independence check. Give them a project with a Monday brief and a Friday deadline. Don't check in unless they ask. See what they produce. This is your data. If it's good, you have a keeper. If it's rough, you have information about where to invest more training.
By day 30, a good VA should own at least two recurring responsibilities and be capable of one-off projects with light supervision. That's the bar. Anything less means the onboarding was rushed or the hire was wrong.
The Mistake That Kills Most VA Relationships
The most common failure mode isn't hiring the wrong person. It's founder impatience. You hire someone smart, you rush the first week because you're already behind, you skip the check-ins in week two because you're busy, and by week three you're frustrated that they don't just "get it."
They didn't get it because you didn't give it. A VA is not a plug-and-play solution. They're a person you're building a working relationship with, and the ROI on the first 30 days is measured in years.
Slow down for two weeks. Follow the plan. The first week with a VA feels like it's costing you time. It's not. It's buying you back every Tuesday afternoon for the next two years.