Onboarding Checklist for a New VA: Your Complete Guide 2026

Did you know that 73% of employees in hybrid onboarding feel more confident in their roles? I’m not going to pretend I can verify that number from the text alone—so I removed it as a hard claim and kept the real point: onboarding quality really does impact confidence, speed, and retention.

When I onboard a new VA (or when I’ve inherited one midstream), the difference is almost always the same: clear access, clear SOPs, and a plan for the first 30 days. Want a checklist you can actually use? Here you go.

1. Prepare Before Your VA’s First Day

If you want a smooth onboarding, don’t start on Day 1. Start the day you hire them.

Here’s what I set up before the first login:

• Create accounts and confirm access for the exact tools they’ll use (email, CRM, project management, docs, Slack/Teams, etc.).
• Prepare password manager sharing (or SSO) so you’re not manually sending credentials.
• Draft SOPs (even if they’re “v1”). A VA can’t follow instructions that don’t exist.
• Send a welcome email with an onboarding questionnaire so you can tailor expectations early.

For tools, I recommend setting up a “starter stack” like this (adjust to your business):

• Email: shared inbox or role-based mailbox (plus alias rules if needed)
• CRM: lead stage definitions + where notes should go
• Project management: Trello or Asana board with pre-made columns
• Docs: Notion or Google Drive folder structure
• Async updates: Loom for screen recordings + short check-in form

Practical “artifact” you should create: a simple onboarding checklist PDF/Notion page (yes, a real one). Your VA shouldn’t have to guess what “done” means.

Welcome Email Template (copy/paste)

Subject: Welcome aboard, [VA Name] — your first-week plan inside

Hi [Name],

Welcome to [Company]. I’m excited to have you on the team.

First, here’s what to do before our kickoff:

• Check your access to: [Slack], [CRM], [Trello/Asana], [Docs folder]
• Reply to this email with the onboarding questionnaire (5 minutes)
• Watch: “How we work” (Loom link: [insert])

Next steps: We’ll meet on [date/time] for a 30-minute kickoff. After that, I’ll assign your first 2–3 tasks for Day 2–Day 4.

Quick question: What’s your preferred communication style—Slack updates, Loom recordings, or email summaries?

Thanks again,

[Your Name]

Onboarding Questionnaire Fields (what I actually ask)

• Time zone + working hours you want to stick to
• Tools you’re already comfortable with (and what you’re not)
• How you prefer to receive feedback (short notes vs Loom vs live call)
• Communication preferences: response time expectations you can meet
• Any constraints: internet reliability, calendar availability, device limits
• Your “definition of done” for common tasks (so you don’t guess later)

In my experience, clear expectations around roles, KPIs, and deadlines from day one prevent misunderstandings later. What I’ve seen go wrong? A VA does “busy work” for 10 days because no one clarified priorities. Then you’re not onboarding—you’re re-onboarding.

2. Introduce Your Company and Team

Early connection matters. Not because it’s “nice,” but because it reduces friction. Your VA should feel like they’re joining a real operation—not a pile of tasks.

I usually run a 30-minute welcome + onboarding meeting on video. Here’s the agenda I use:

• Company snapshot: what we do, who we serve, how we make money
• Team map: who does what (and who they escalate to)
• How work moves: how requests arrive, how tasks get assigned, how “done” is verified
• Communication norms: Slack vs Loom vs email + response-time targets
• 30-day overview: what they’ll learn first, what they’ll own later

Share your platforms (shared drive folder structure, Notion pages, Slack channels). If you don’t, your VA will create their own structure—and it’ll be wrong. I’ve been there.

For more on this, see our guide on quik news.

Also, assign a “buddy” if you can. A peer connection can be the difference between “I’m stuck” and “I’m progressing.”

One more thing: include a launch calendar review. Even if they only look at it for 20 minutes, it helps them understand priorities. And no, it shouldn’t be a mystery later.

3. Provide Training and Resources

Training is where most onboarding posts get vague. So let’s be practical.

I recommend building role-specific SOPs as Loom videos plus a written checklist. The Loom video is for speed; the written version is for consistency.

SOP Structure (simple and effective)

• Purpose: what this SOP accomplishes
• When to use: triggers/conditions (examples)
• Tools: which platforms and where to click
• Step-by-step: numbered instructions
• Quality checks: what “good” looks like
• Common mistakes: the top 3 issues you see
• Escalation: who to ask + what to include in the message
• Change log: date updated + what changed

In my setup, I start with 2–3 manageable tasks. For example:

• Task A: data cleanup or lead list formatting (with a clear template)
• Task B: email filtering + tagging (with defined categories)
• Task C: updating a CRM field or creating a draft response (with an approval step)

Then I schedule check-ins. Not “whenever.” Actual times. If you don’t, the VA will either wait too long or ask too often.

This initial training phase usually reveals gaps fast—like missing context, unclear definitions, or a tool workflow that doesn’t match your assumption. Fix it early, or it turns into week-long rework.

4. Set Goals and Expectations

KPIs are only useful if they’re tied to what you actually do. Otherwise, you get “numbers” that mean nothing.

For a new VA, I like to set 5–8 KPIs for the first 30 days, then tighten later. Here’s an example set you can adapt:

Example KPI Set (VA onboarding)

• Response time (Slack/email): target within 2 business hours for quick questions
• Task throughput: number of tasks completed per week (with the same task type)
• QA pass rate: % of tasks that pass review on the first submission (target 80%+ in week 2)
• Rework rate: % of tasks requiring changes (lower is better; target 20% by day 30)
• SOP adherence: checklist score during QA (e.g., 10-point rubric)
• Update quality: clarity score for Loom updates or status check-ins (simple 1–5 rating)

Then I tie goals to milestones:

• Week 1: complete training tasks with 1–2 revisions max
• Week 2: begin owning a recurring workflow (drafts or partial responsibilities)
• Week 3: increase complexity and reduce oversight
• Week 4: full ownership of one workflow + propose one improvement

For more on this, see our guide on global climate summit.

And yes—I do talk about an “autonomy ladder,” but I make it concrete. It’s not a buzzword. It’s a progression like:

• Level 1: follow SOP exactly
• Level 2: follow SOP + ask when unsure
• Level 3: propose options; decision comes from me
• Level 4: recommend + execute within defined boundaries

In my experience, aligning goals with your client expectations and workflow ensures your VA’s efforts directly support the business—not just activity.

5. Task Management and Planning

This is where your onboarding either stays organized… or becomes chaos.

Create a Trello/Asana board with columns that match your workflow. Don’t leave it blank and “figure it out later.”

Sample Trello/Asana Columns (works for most VAs)

• Ready for Start (assigned + has links/templates)
• In Progress (VA working)
• Needs Review (submitted with QA notes)
• Approved (done)
• Blocked (waiting on info; includes what’s needed)

Also, use labels/tags to help filtering. I typically use tags like:

• Priority: High / Medium / Low
• Client: Client A / Client B
• Type: Admin / Research / Outreach / QA

Cadence matters. Here’s a simple first-week rhythm I’ve used:

• Days 1–3: daily 10–15 minute standup (or async check-in form)
• Days 4–7: 2 check-ins + one longer QA review
• Weeks 2–4: 2–3 check-ins per week, plus Loom updates

For asynchronous updates, Loom is your friend. The rule I use: if it takes more than 60 seconds to explain, record a Loom video. It saves time for both of you.

Finally, track progress in a dashboard—not just in your head. A simple “onboarding dashboard” can be a table with:

• Task name
• Due date
• Owner
• Status (Ready/In Progress/Needs Review/Approved)
• QA score (0–10 or Pass/Fail)
• Notes (what was missing or improved)

That dashboard becomes your evidence. When you review performance, you’re not arguing vibes—you’re reviewing data.

6. Project Kick-off and Role Clarification

Kick-off shouldn’t be a “nice meeting.” It should create clarity.

Give your VA visibility into upcoming launches or campaigns. Even a quick launch calendar review helps them anticipate tasks instead of reacting to surprises.

Then document role clarity. This part is underrated. I clarify:

• What they own vs what they support
• Where requests come from (forms, Slack channel, CRM tasks)
• Response time expectations
• Escalation workflow: what triggers escalation and who they contact
• Client communication boundaries (what they can say/do without approval)

For more on this, see our guide on fiction writing checklists.

And I’ll say it plainly: if client expectations aren’t documented, your VA will “assume.” Assumptions create rework. Rework kills onboarding speed.

7. Access to Tools and Platforms

Technical access is the difference between “productive” and “stuck.” Confirm logins on Day 1, not Day 5.

Here’s what I do:

• Test logins myself (yes, actually log in)
• Verify permissions (view vs edit vs admin)
• Provide quick-start guides for each tool (links + 3–5 screenshots or a Loom video)
• Create a shared troubleshooting FAQ or support channel

For example, your FAQ might include:

• “I can’t access the CRM pipeline—what should I check?”
• “How do I create a task in Trello/Asana?”
• “Where do I find the latest SOP version?”
• “What’s the correct naming convention for files?”

Also, review permissions after week 2. Roles expand, and so do access needs. Just don’t leave everything on “admin” forever. Security matters.

8. Communication Process

Clear communication protocols reduce misunderstandings. Simple as that.

I set a channel map like:

• Slack: quick questions, short updates, blockers
• Loom: walkthroughs, detailed “here’s what I did” updates
• Email: formal client-facing messages or approved summaries
• Notion/Docs: policies, SOPs, and ongoing documentation

Then I define response targets. For example:

• Quick question response: within 2 business hours
• Daily async update: by end of day
• Weekly progress review: scheduled time block

Async communication is great—especially if time zones are involved. It also makes onboarding more scalable because your VA can reference Loom recordings later.

For more on this, see our guide on openais new device.

What I don’t do: I don’t rely on “we’ll talk when needed.” That’s how tasks get lost in the cracks.

9. Ongoing Feedback and Check-ins

Onboarding doesn’t end at day 30 unless you want churn. I schedule a recurring feedback loop so your VA keeps leveling up.

30-Day Review Agenda (use this as-is)

• Wins (5 min): what went well and why
• Challenges (10 min): what was confusing or slow
• Metrics review (10 min): KPIs + QA pass rate + rework rate
• Process improvements (10 min): update one SOP or template
• Next 30 days plan (5 min): new ownership scope + target KPIs

Scoring Rubric (simple and fair)

• Accuracy: 0–3
• Speed: 0–2
• Communication: 0–2
• Ownership: 0–3 (did they unblock themselves or escalate early?)

Then adjust KPIs if needed. If QA pass rate is low, you don’t just “push harder.” You improve the SOP, tighten definitions, and reduce ambiguity.

And yes—celebrate wins. If your VA hits an 85%+ QA pass rate by week 3, say it. That motivation matters.

This ongoing feedback loop creates trust and continuous learning. Long term, that’s what improves retention.

10. Conclusion and Final Tips

If there’s one theme across all of this, it’s simple: your VA needs a system, not a pile of tasks.

When you provide role clarity, access, training resources, and a real 30-day plan with KPIs, you turn onboarding from “hope they figure it out” into predictable ramp-up.

For more tips on managing remote teams, check out our Quik News Review for the latest updates and strategies.

Quick final reminder: update your SOPs as you go. The best onboarding checklists aren’t the ones you wrote once—they’re the ones you improve every month.