Most VA relationships that fail don't fail because the VA was bad. They fail because the founder handed someone a login, said "figure it out," and then got annoyed when nothing was done right by week three. Onboarding is the job. If you skip it, you don't get to blame the hire. This is the exact va onboarding checklist that Jarvis uses to get VAs running independently inside a week. Follow it, and you'll have a VA you can trust by day seven.

Why VA Onboarding Almost Always Goes Wrong

The number one onboarding mistake is treating a VA start date like a problem solved. Founder hires VA, VA starts, founder immediately stops paying attention, VA has no process, no example outputs, no clear definition of "done." Three weeks later: a pile of confused messages, tasks half-done, and a founder who's now managing the situation instead of the business.

A McKinsey study on operational delegation found that unclear role definition and insufficient process documentation are the top two causes of delegation failure. This holds for VA placements too. The VA isn't the variable. The onboarding is.

The good news: a structured 7-day onboarding fixes almost all of it. Here's the full va onboarding checklist, starting before your VA's first day.

Before Day 1: The Pre-Onboarding Checklist

Don't wait until day one to build this. Prepare it the week before your VA starts.

Tool access prepared. Every platform your VA will touch needs to be ready with their credentials before they log in. For most Jarvis founders, that list includes: GoHighLevel, Gmail (delegated access or shared inbox), Calendly, Notion, your CRM, and Slack or WhatsApp. Use a password manager (1Password or LastPass) to share credentials — never over chat.

Loom walkthroughs recorded. Record a 10-15 minute screen walkthrough of each tool your VA will use. Keep it simple: here's what we use it for, here's where things live, here's what you'll be doing in it. This is orientation, not training. The training happens with real tasks.

Priority task list written. Pick three tasks to hand off in week one. Only three. Write them down with as much specificity as you can: what the task is, what triggers it, what a completed version looks like. If you can't describe the output, the task isn't ready to delegate.

Communication protocol set. Before they start, your VA needs to know: what channel do you prefer for daily communication, what's the expected response time for messages from you, what does the end-of-day report look like and when should it arrive. Set this in writing before day one.

Test tasks prepared. Prepare simplified versions of real tasks you'll be handing off. Use these in days 3-4 to evaluate whether the VA understands the work. A test task should be real enough to be meaningful but scoped enough to complete in under an hour.

Success metrics defined. What does "good" look like at 30 days? Write it down. Not vague goals like "getting better at email" — specific metrics like "inbox cleared and sorted by 9 AM, 5 flagged items or fewer requiring my attention, zero missed follow-ups." If you can't define success, you can't evaluate it.

Sample outputs shared. Show the VA what a finished task actually looks like. A completed CRM entry. A drafted email reply. A formatted weekly report. The clearer the example, the faster they calibrate.

Escalation path clear. What decisions can your VA make autonomously? What requires your sign-off? Define the boundary before a situation forces it. Most founders want VAs to handle anything under $50, anything that follows a defined script, and anything time-sensitive that doesn't involve client relationships.

NDA and contract signed. If your VA will have access to client data, financial records, or sensitive communications, have documentation in place before access is granted. Jarvis handles this as part of the placement agreement, but verify regardless.

Password manager activated. This deserves its own line because so many founders skip it. Sharing passwords in Slack or WhatsApp is a security risk. Set up 1Password or LastPass, share access to the relevant credentials there, and revoke chat-based credential sharing immediately.

That's your pre-onboarding list. If all ten items are ready, your VA can start day one with clear direction instead of dead air.

Day-by-Day: The 7-Day VA Onboarding Plan

Day 1: Access and Orientation

Your VA's first day is not a working day. It's an orientation day. The goal is simple: they get into all the tools, they understand the context of the business, and they ask every dumb question now so they don't have to ask it mid-task later.

Run a 30-minute kickoff call. Cover: what the business does, who the customers are, what the VA's role covers, what you expect in the first week. Send them to explore the Loom walkthroughs. They take notes. They do not take action yet.

If they try to start doing tasks on day one before they understand the system, you'll be fixing errors instead of reviewing work. Slow is smooth here.

Day 2: Shadow Mode

The VA watches you do the task — or watches a recording of you doing it — before they touch it. This is non-negotiable. Even if the task seems obvious, the VA needs to see how you do it specifically: which fields you fill, what your tone sounds like in an email reply, how you decide what gets flagged.

Record yourself doing each priority task if you can. A 10-minute Loom of you working is worth more than any written SOP for calibrating execution style.

Day 3: First Attempt With Same-Day Review

The VA does the task. Not watched. Not supervised. They do it, submit it, and you review it the same day.

When you give feedback, use this format: "What happened, what should have happened, how to fix it." Not "this is wrong." Not "this isn't what I wanted." Specific, actionable, quick. The goal is pattern correction, not criticism.

This is the most important review session in the entire onboarding. What you catch and correct on day three determines whether the same error shows up on day ten.

Day 4: Independent Attempt Without Watching First

The VA does the same task again, but this time without rewatching the recording first. You want to see what they retained and internalized. Review at end of day again, same feedback format.

If the quality improved from day three, you're on track. If the same errors repeated, the issue is either unclear SOP or a skills gap. Diagnose before moving forward.

Day 5: Speed and Quality Check

Full day of the task. The VA isn't doing one test version — they're doing the actual volume they'd do on a normal operating day. You review the output at the end and check two things: quality held at acceptable level, and pace is reasonable for the workload.

If quality drops under volume, the process isn't solid enough yet. Add more structure before moving to a second task.

Day 6: Add the Second Task

Repeat the shadow-then-attempt cycle on task two. The VA is now running task one independently during part of the day, learning task two during the other part. Adjust time allocation based on complexity.

This is where the onboarding compounds. A VA who has fully internalized one task learns the second task faster because they understand your communication style, your quality standards, and how you give feedback.

Day 7: Full Handoff Review

Review everything. Look at output quality across both tasks. Review the daily reports from the past week. Talk to your VA for 20 minutes: what was confusing, what do they still need from you, what questions came up that they didn't ask?

Set the weekly check-in cadence. For most founders, this is one 15-minute call per week after month one. Confirm the daily report format. Clarify what requires escalation. Then step back.

Day 7 is the last structured onboarding session. After this, the VA runs independently.

Get the full Jarvis VA Onboarding Template — the exact daily report format, escalation matrix, and task handoff checklist we use for every placement. Download at gojarvis.ai/pages/use-cases.

The Daily Report Template

The daily report is the simplest thing that keeps onboarding from falling apart. Five minutes to write. Saves you 30 minutes of check-ins.

Here's the exact format:

Date: [date]
Tasks completed today:
- [task name] — [status: done / in progress / blocked]
- [task name] — [status]

Issues or blockers:
- [anything that stopped or slowed the work]

Questions for tomorrow:
- [anything needed before tomorrow's tasks can start]

Time log:
- [task] — [X hours]

That's it. Require it at the same time every day (5 PM in their timezone is standard). If the report doesn't arrive, follow up. Consistency in the report builds consistency in the work.

Common VA Onboarding Mistakes (and the Fix for Each)

Giving too many tasks at once. You're overwhelmed, so you hand everything off immediately. The VA drowns, quality drops, you lose confidence in the hire. Fix: one task per week until each is mastered. Add the next task only when the previous one is running at 90% without your input.

No written process, just verbal. You explain the task on a call, assume they got it, move on. They didn't get it, or they got a version of it that doesn't match what you meant. Fix: Loom plus a written checklist, minimum. If you can't make a Loom, write the steps out line by line.

Not reviewing output until week three. You're busy, so you assume it's going fine and check in later. By then, the VA has been repeating the same misunderstanding for three weeks. Fix: daily review for the first five working days. Non-negotiable. It takes 10 minutes and saves you weeks.

Disappearing after day one. You hand over the login and go back to work. The VA has no one to ask questions to, makes guesses, does the work wrong, and either doesn't tell you or tells you too late. Fix: be reachable for quick questions during the first week. 15-minute response time on messages during business hours. After week two, the questions stop.

When a Pre-Trained VA Cuts the Ramp in Half

Here's the honest version of the onboarding timeline above: if you're starting with a VA who has never touched your tools, day one through day three is almost entirely tool orientation. They're learning what buttons do before they learn how to do your tasks.

A Jarvis VA arrives pre-trained on GoHighLevel, Gmail, Calendly, Notion, and Apollo. They don't need Loom walkthroughs for the tools. They need walkthroughs for your specific use of those tools, which is a 15-minute conversation, not a three-day ramp.

That shifts your onboarding from seven days to five. The VA starts on real tasks by day two instead of day four. By the end of week one, they're running independently on functions that would take a standard hire a full month to stabilize.

See how the Jarvis matching process works and the roles we source for. If you're ready to skip the recruiting process entirely, start with the hire page or review pricing first.

Frequently Asked Questions

How long should VA onboarding take?

A well-run onboarding takes 7 days for a VA who arrives with tool knowledge already in place. For a VA learning tools from scratch, add 5-7 days of orientation before task-specific training begins. With a pre-trained Jarvis VA, most founders are at full independent operation by the end of week two.

What tools should my VA have access to on day one?

Give access only to the tools the VA will use in their first task set. For most founders, that's inbox access, the CRM, and the scheduling tool. Expand access as you add functions. Limiting scope in week one reduces mistakes and simplifies the onboarding.

Should I write SOPs before my VA starts?

You don't need polished SOPs. You need the task clearly defined, a sample output the VA can reference, and a Loom walkthrough. Full SOPs can be built by the VA over the first two weeks as part of their onboarding tasks. That's often the best way to get SOPs written — have the VA document the process as they learn it.

How do I know if my VA onboarding is working?

By day five, quality on task one should be at 80-90% without your intervention. By day seven, the VA should be able to complete task one from start to finish independently, catch their own errors, and know when to escalate. If neither of those is true, the onboarding has gaps. Review your SOP, your feedback sessions, and whether you've been consistent about reviewing daily output.

What happens if the VA makes a mistake during onboarding?

Mistakes in week one are expected and normal. The issue isn't the mistake — it's whether the correction stuck. Give specific feedback, check that the next attempt improved, and track whether the same error repeats. Repeated identical mistakes after correction are a signal to investigate whether the task instructions are clear enough.

What's a fair workload for a VA in the first week?

One primary task, done well, is a successful first week. Two tasks if the first is simple and mastered by day four. The goal of week one isn't maximum output — it's calibration. You want to know what your VA's default quality looks like, how they handle ambiguity, and whether they ask good questions. That tells you more than a high task count.

Get a VA Running in 7 Days, Not 7 Weeks

Jarvis handles the recruiting, vetting, and pre-training. You handle the onboarding with the checklist above. Most placements are running independently inside two weeks.

Book a Free 15-Minute Call — tell us what you need covered and we'll match you with a VA who's already trained to do it.