The first week with a new VA sets the tone for the entire engagement. Get it right and the relationship stabilizes more smoothly. Get it wrong and you spend weeks correcting misaligned expectations.
This checklist covers the five things that matter most in week one: access, context, tasks, communication, and feedback. Work through it in order and you will not miss the steps that cause most early failures.
Virtual assistant onboarding checklist: what to cover in week one
The first-week checklist has five categories. Each one resolves a different type of early engagement failure. Skipping any of them does not save time; it moves the problem to week two or three when it is harder to fix.
The five categories are: tool access and permissions, business context, initial task assignment, communication norms, and a structured end-of-week review. The sections below cover each one.
Structured first-week onboarding reduces confusion and prevents avoidable rework. For VA engagements, that matters even more because the VA cannot simply walk over and ask a question in real time.
Day one: access and tools
On day one, set up every tool the VA needs before their shift starts. Email access, calendar permissions, CRM login, project management tool, and any communication channel you use (Slack, Teams, or similar) should all be live before the first session.
Send a written welcome document that includes: your business in two sentences, your communication preferences, your response time expectations, and who to contact if they are blocked on something. This document answers 80 percent of first-day questions before they are asked.
Do not skip the two-factor authentication setup. A VA with incomplete tool access on day one loses momentum and starts the engagement with a frustration rather than a win.
Days two to three: context and first tasks
Share three to five recordings or written walkthroughs of the tasks you are handing off. Show your process, not just the outcome. A VA who understands why a task is done a certain way makes fewer errors and better judgment calls than one who is just following a checklist blindly.
Assign two or three well-documented tasks to run independently by end of day three. These should be your most repeatable, lowest-risk tasks. The goal is an early successful output that builds confidence on both sides.
Check the output on day three. Give specific feedback: what was correct, what needs adjusting, and exactly how to adjust it. The tone of this feedback sets the communication pattern for the whole engagement.
Days four to five: norms and end-of-week review
By day four, confirm your communication rhythm: how the VA should flag blockers, how they should ask clarifying questions, how often you will check in, and what the response time expectation is in each direction.
On day five, hold a brief end-of-week review. Ask: what went well, what was unclear, and what would make week two more effective. This 20-minute conversation surfaces the adjustments that prevent the most common second-week breakdowns.
For how to structure the ongoing task handoff after onboarding, see our VA management guide. For the foundation of a good delegation system, see our guide on how to delegate tasks to VA and keep quality consistent over time.
Frequently asked questions
What should I cover in a virtual assistant's first week?
Cover tool access, business context, first task assignments, communication norms, and an end-of-week review. Missing any of these five areas is the cause of most early VA engagement failures.
How long does it take to onboard a virtual assistant?
The timeline depends on the complexity of the work and the quality of the onboarding. The first week is usually setup and calibration. After that, scope can expand as the VA demonstrates consistent output.
What should I include in a VA welcome document?
Include your business context in two to three sentences, your communication preferences, your expected response times, and who to contact when blocked. One to two pages is sufficient; a longer document will not be read as carefully.
How many tasks should I assign in week one?
Start with two or three well-documented tasks. Enough to keep the VA productive and generate feedback data, but not so many that errors in multiple tasks are hard to diagnose. Expand scope in week two based on what you observe.
