The VA Onboarding Brief: 28 Questions to Fill Out Before Your Assistant Starts

Why Most VA Relationships Stumble in Week One

A VA's first two weeks often go worse than they should. The kickoff call goes well. You send login credentials. You assume they'll figure out the rest. Then come the questions: Which tasks are most urgent? Who do I contact for approvals? What does a good draft look like? Where do I find the SOPs?

By Day 5, you're spending more time answering questions than you would have spent doing the work yourself.

The root cause is almost always the same: the VA started without enough context. Not because they weren't capable, but because no one gave them a structured brief before they began.

A virtual assistant client onboarding questionnaire solves this. It's a document you fill out, covering your business, tasks, tools, communication preferences, and success criteria, and share with your VA before Day 1. Brief once, then the VA runs it.

This guide walks through all six sections of an effective onboarding brief, with the exact questions to answer in each. The whole thing takes 30-40 minutes to complete, once, before your VA starts.

What a Good VA Onboarding Brief Covers

A complete brief has six sections covering business context, task priorities, tools and access, communication preferences, AI workflows, and 30-day success metrics. Together, they give a VA everything they need to operate independently from the start, without waiting on you for context they should have had on Day 1.

One document, filled out once, referenced throughout the first 90 days. For remote-first teams especially, a written brief like this is not optional: it is what replaces the hallway conversation the VA will never have because they are not in your office.

Section 1: Business Context

Before a VA can do anything useful, they need to understand where they've landed.

Answer these five questions in plain language. Bullet points are fine. The goal is context, not a company overview.

Questions to answer:

1. What does your company do and who is your main customer? (One or two sentences.)
2. How big is the team? Who will the VA interact with directly?
3. What's the primary problem you're hiring a VA to solve? What's currently not getting done?
4. Are there any areas of the business that are off-limits for the VA to touch without explicit approval?
5. Is there any background the VA should read before Day 1? (A product page, a process doc, a past project?)

This section takes five minutes and eliminates the most basic "just checking" questions that otherwise fill Week 1. A VA who understands your company, your customers, and what they're being hired to fix can make better judgment calls from the start, without asking you every time something falls outside a checklist.

Section 2: Tasks and Priorities

The single most common onboarding mistake is starting a VA without a clear task list for the first 30 days. "We'll figure it out as we go" is not a brief.

Questions to answer:

6. What are the three to five tasks you want handled in the first 30 days? List them in priority order.
7. Which tasks does the VA own completely, with no sign-off needed from you?
8. Which tasks require your review or approval before they go out?
9. Are there any active projects they are stepping into mid-stream? If so, what's the current status?
10. Are there recurring tasks (weekly, monthly) they'll take over from someone else?

Use a simple table to capture priorities clearly:

If you have more than ten tasks in the first 30 days, pick the top five. A VA who knows the three most important things to do will outperform one buried in a 20-item backlog without priorities. The table also creates a shared reference, so you both know what counts as success at the end of Week 1.

Section 3: Tools and System Access

Nothing stalls a VA faster than waiting on software access. This section should be filled out and actioned before Day 1, not after.

Questions to answer:

11. What tools does the VA need access to on Day 1?
12. What permission level for each? (View only / Edit / Admin)
13. Is there documentation or a training video for any of these tools?
14. Who manages tool access on your team? (So the VA knows who to contact if access breaks.)

For AI-trained virtual assistants, add any AI tools to this list. They're likely already familiar with the major platforms, but knowing which ones you use, and which data they can access, matters for how they apply those tools to your work.

Section 4: Communication Preferences

Setting communication expectations in the brief prevents most of the awkward "just wanted to check in" messages that slow down remote working relationships.

Questions to answer:

15. Where should the VA send daily or weekly updates? (Slack, email, a project tool?)
16. How often do you want to hear from them unprompted? (Daily async update? Weekly summary? Only when something's blocked?)
17. What's the right channel for urgent questions?
18. What's the right channel for non-urgent questions?
19. Do you want proactive suggestions, or do you prefer they stick to assigned tasks?

One underrated question: do you want your VA to flag potential problems before they become problems, or do you prefer they only surface things they can't resolve themselves? Both are valid. Knowing the answer shapes how the VA operates day-to-day and prevents a common dynamic where the VA either over-communicates or stays too quiet because they couldn't read your preference.

Section 5: AI Tools and Workflows

This is the section most onboarding guides skip entirely, and it's the one that matters most if you've hired an AI-trained VA.

A VA who has graduated from the Delegated AI Academy arrives trained on practical AI workflows: using tools like Claude, ChatGPT, Perplexity, and others in their day-to-day work. They are not a chatbot. They are a skilled human who applies AI where it adds speed and accuracy to their output.

To use that capability well, they need to know your context.

Questions to answer:

20. Which AI tools do you already use in your business, if any?
21. What does "AI-assisted" output look like for you? (A first draft you edit? Publish-ready? Always reviewed before it goes anywhere?)
22. What is your approval process for AI-generated content, outreach, or data? Who signs off?
23. Are there any clients, topics, or formats where you do not want AI tools involved?
24. Are there brand voice guidelines, example outputs, or tone references the VA should use when prompting AI tools on your behalf?

Different businesses have very different answers to these questions. Some want AI-drafted outreach reviewed before sending. Some want blog drafts published as-is once approved. Some have legal or client sensitivity constraints that make AI involvement inappropriate for certain tasks. Being explicit about this in the brief is what allows an AI-trained VA to apply their training precisely, rather than guessing where it's welcome.

This brief section does something the rest of the guide cannot: it aligns an AI-trained VA's capabilities with your actual preferences. Without it, even a highly skilled VA defaults to guessing. With it, they know exactly where to apply AI tools and where to keep a human hand on everything.

Section 6: Success Metrics for the First 30 Days

Define success before the VA starts, not after Week 4 when you're trying to explain why something feels off.

Questions to answer:

25. What would need to be true in 30 days for you to feel confident this working relationship is working?
26. Is there a specific deliverable (a clean CRM, an inbox at zero, a working content calendar) that would signal the VA is set up to own their role?
27. When is the first formal check-in? (Day 7 is reasonable for most roles. Day 14 for lower-touch engagements.)
28. What's the best way to share feedback during the first month?

Be concrete here. "Inbox stays under 10 unread by EOD" is more useful than "the inbox should be under control." A VA who knows the exact target can work toward it without asking what you mean. Writing this down also protects both sides: if the VA hits the agreed milestone, you know the relationship is working. If they don't, you have a shared reference point for the conversation.

Common Onboarding Mistakes the Brief Prevents

Even with the best intentions, most businesses make the same set of onboarding mistakes. A structured brief addresses each one before it becomes a problem.

Starting work before the brief is shared. The VA takes an early task and makes reasonable assumptions. Those assumptions don't match your preferences. You correct them. The VA adjusts. This loop runs for two weeks before you have a shared working style. A brief front-loads that calibration.

Sending access credentials without context. Getting into the tools is not the same as knowing what to do with them. Access without a task list leaves the VA stalled at the login screen, waiting to know what you actually need.

Skipping the AI context section. If you've hired an AI-trained VA, this is particularly costly. An AI-trained VA who doesn't know your AI preferences will either underuse their training (defaulting to slower, manual work) or apply AI tools in places you'd prefer a human approach. Five questions upfront prevents both.

No defined success metric. Without a 30-day goal, there's no way for the VA to know they're on track and no way for you to evaluate whether the relationship is working. The brief makes that evaluation obvious.

The best onboarding systems for remote-first teams are not complex. They're written down, shared early, and reviewed together before work begins.

How to Deliver the Brief

Fill it out three to five days before your VA starts. Share it at least 24-48 hours before the kickoff call, so they have time to read it, highlight questions, and arrive prepared.

Do not send it as a one-way document. Use the kickoff call to walk through it together. Ask if anything is unclear. Let the VA ask the questions they'd have held back on. That 30-minute structured conversation does more work than three weeks of trial-and-error.

Some clients send the brief via a shared Google Doc and ask the VA to add comments or questions inline before the call. This approach makes the kickoff call faster: you arrive knowing exactly what needs clarification, rather than starting from scratch.

After 60 days, revisit the brief. Tasks shift. Tools change. Some priorities disappear; new ones emerge. A brief that reflects the actual role (not the role it was when the VA started) keeps the working relationship running on what matters most.

If you want a VA who can hit the ground running from Day 1, look at our AI-trained virtual assistants. We match businesses with pre-vetted, AI-trained VAs in 48 hours, and helping clients build a solid onboarding brief is part of how we set up new placements to succeed.

For broader context on structuring the first 90 days, see our guide on onboarding a virtual executive assistant with a 30-60-90 day plan.

Frequently Asked Questions

What is a virtual assistant client onboarding questionnaire?

A virtual assistant client onboarding questionnaire is a structured document you fill out before your VA's first day. It covers your business context, task priorities, tools and access, communication preferences, AI workflows, and 30-day success metrics. Sharing it before the kickoff call gives your VA the context to work independently from the start, without back-and-forth.

How long should a VA onboarding questionnaire be?

Six sections and 25-30 questions is the right range. Long enough to cover tools, tasks, communication, and success metrics. Short enough to complete in 30-40 minutes. The goal is one document your VA can reference during the first month, not a manual they will never read.

Should the VA fill out the questionnaire, or should I?

You fill it out and share it with your VA. It captures your preferences, your priorities, your tools, and your definition of success. Some teams also ask the VA to complete a parallel form covering their working style and preferred tools, which is a useful addition to review together on the kickoff call.

What is the difference between a VA onboarding questionnaire and a checklist?

A checklist tracks what actions you have taken: sent access credentials, held the kickoff call, shared SOPs. A questionnaire captures what your VA needs to know: your preferences, priorities, and context. Use both. The questionnaire goes to the VA before Day 1. The checklist keeps you on track as you set things up on your end.

How is onboarding an AI-trained VA different from a standard VA?

An AI-trained VA needs context about your AI tools and workflows: which tools you use, what AI-assisted output looks like, and your approval process for AI-generated work. Without it, they default to guessing. Our questions-to-ask guide for affiliate management VAs shows how that specificity changes outcomes in practice.

How quickly can a VA become fully productive?

With a well-prepared brief, most VAs handle routine tasks independently within the first week. The questionnaire is what compresses the ramp-up: context gathered upfront means fewer delays and fewer "just checking" messages. VAs placed through Delegated AI are typically at full operating speed within two weeks, and often faster when clients arrive with clear priorities.