VA Pre-Start Checklist: Everything to Prepare Before Your Virtual Assistant's First Day

Day 1 arrives. Your VA logs on. You realize they don’t have access to the shared drive. The project management tool invite is sitting in their spam folder. You haven’t written down a single process. The first two hours are improvised scramble, and neither of you is doing the work you were supposed to start.

None of it needed to happen.

The most common VA onboarding failures don’t happen because of the VA. They happen because the founder wasn’t ready. Pre-start preparation is the single highest-leverage thing you can do before your VA’s first day, and it takes less than three hours to complete correctly.

Why Pre-Start Preparation Is the Founder’s Job, Not the VA’s

When a VA shows up for Day 1 without access to tools, without documented processes, and without a clear task list, they don’t fail. They wait. They ask questions you’re too busy to answer. They make guesses. Some of those guesses are wrong. Some of those mistakes take time to unwind.

Every gap in your pre-start preparation converts into dead time for the VA and frustration for you. A VA at $15 per hour working 20 hours per week costs $1,200 per month. A poorly prepared first week costs you more than money, it damages the working relationship before trust is established.

The Four Access Categories structure everything you need to prepare:

1. Systems Access, the accounts and platforms they need to do the work
2. Communication Access, how you’ll talk and what to do in urgent situations
3. Knowledge Access, the context, processes, and reference materials they’ll draw on
4. Role Access, clarity on what they can act on independently and what requires your sign-off

Work through all four before Day 1. The 20-item checklist above covers every item across all four categories.

Systems Access: The Accounts They Need to Do the Work

Do not issue every account at once. Prepare a staged access plan: communication and documentation first, read-only operational access after training, then role-scoped write access after supervised practice. Record the approver, provisioner, date granted, and review date for each system.

Before access to patient information, confirm that applicable agreements and privacy training are complete, the device and secure connection are ready, multi-factor authentication is enabled, and the workspace meets the practice’s requirements.

Systems access is the most commonly incomplete area on Day 1. The fix is to complete every item in this category before the VA’s start date, not on the morning of, not during the first call. Before.

Build a Systems Access Map, a simple document listing every platform the VA will use, with their login status confirmed. Include: platform name, URL, username, whether login has been tested by the VA, and permission level. This document takes 20 minutes to build and prevents 80% of Day 1 access problems.

Check each system for permission level. Calendar access is frequently set up as view-only when edit access is needed. File storage folders are shared at the wrong permission level. Project management tools require the right workspace permissions, not just a generic invitation that lands in an unread inbox.

Password management is worth doing correctly once. A shared vault in 1Password or LastPass gives the VA access to the credentials they need without you emailing passwords in plain text. Add only what’s necessary for their role, not blanket access to everything.

Communication Access: How You’ll Talk and What Happens When Something Goes Wrong

VA work is asynchronous by default, but every working relationship needs a clear protocol for urgent situations. Establish your communication access setup before Day 1 and document it so neither party has to figure it out under pressure.

Decide on a primary channel (Slack, Teams, or another messaging platform), a secondary channel for urgent items (WhatsApp or Signal), and what “urgent” actually means in practice. In most VA relationships, a same-day message is the norm. A phone call is reserved for genuine time-sensitive situations, not for questions that can wait two hours.

Confirm the VA’s timezone and availability window in writing before Day 1. This is not a courtesy, it is foundational. A VA in a timezone eight hours ahead is not available for a 4pm call your time. Build your task handoffs and response expectations around the reality of their schedule, not an assumption.

Knowledge Access: The Context and Processes They’ll Draw On

Most founders don’t write SOPs until they have to. That moment arrives when a VA asks how to do something and there’s no documentation to point them to. Writing SOPs before Day 1 means the VA has something to reference independently, rather than waiting for you to explain the same process three times in the first week.

You don’t need to document everything before Day 1. Document the first three tasks you’re handing off. For each one, write a step-by-step process document or record a screen-share walkthrough. Five to ten minutes per task. Loom makes screen recording fast and shareable. Google Docs, Notion, or even a simple Word document handles the written version.

The business overview is equally important. Your VA needs to understand who you serve, what problem you solve, and the vocabulary of your business before they communicate on your behalf. A one-to-two page document covering your core offer, key clients or audience, and relevant terminology gives them the context they need to represent you well from their first interaction.

A FAQ document covering your ten most common operational questions eliminates an entire category of interruptions. Include answers to questions like: “Who approves outgoing client emails?” “What’s the process for rescheduling a client call?” “What’s the spending threshold I can act on without approval?” Writing these answers once means you’re not explaining them individually throughout Week 1.

Role Access: Clarity on What They Own and What They Escalate

The most common source of over-dependence in VA relationships is failing to define role access upfront. Without clear boundaries, VAs default to asking for approval on everything, which means you’re doing the decision-making twice, for every task, indefinitely.

Your role clarity document answers three questions explicitly:

What do you own? The task categories that are entirely theirs, no check-in, no approval required. They complete and move on.

What do you decide? Situations where they use judgment and act without asking, within defined parameters. For example: “You can approve meeting requests that don’t conflict with blocked time, without checking with me.”

What do you escalate? Situations where they must come to you before acting, because of cost, client relationship risk, or your specific preference. For example: “Any email to a current client that involves a complaint or a refund must come to me before it goes out.”

Writing this document once, clearly, means you don’t answer the same question five different ways in the first week.

The Day 0 Setup Call: 30 Minutes the Day Before the Official Start

The offboarding checklist should already exist by this point. It should list every account, equipment action, data-return step, and person responsible for same-day access removal if the relationship ends.

The Day 0 Setup Call is a 30-minute video call the day before your VA officially starts. The agenda:

Minutes 0–10: Confirm all access is working. Have the VA log into each platform on the call while you watch. Fix any issues in real-time. This is the moment to catch problems when you have time to resolve them, not at 9am on Day 1 when neither of you has bandwidth.

Minutes 10–20: Walk through the role clarity document. Read through what they own, what they decide, and what they escalate. Ask: “Do you have any questions about where the line is?” Gaps surface here rather than in a tense Week 2 conversation.

Minutes 20–30: Preview the first week. Open the project management tool and show them their task list. Explain what’s due when and what the quality expectation is for each item. Confirm the time for the Day 1 Kickoff Meeting.

Close with a single question: “Is there anything you need from me before tomorrow?” Address whatever they name before the call ends.

Your Next Step

Open a new document right now and start your Systems Access Map, before you set your VA’s official start date. List every platform you need them to access, then work through each item in this checklist in the four days before they begin. The founders who prepare well have better VA relationships from Day 1. The ones who don’t spend their first two weeks paying for it.