Home  →  Guides

How to Onboard a Virtual Assistant: A Day-by-Day Plan for Week One

Most founders spend weeks choosing a virtual assistant and about forty minutes onboarding one. They send a few logins, a message that says "start with the inbox," and then go back to their own work, hoping the problem has been solved. By Friday they are still doing everything themselves, and by week three they are wondering whether they hired the wrong person.

I run Virtual Assistant Capital, and we sit in the middle of a lot of first weeks. The pattern is consistent enough that I would put it plainly: the first five working days decide most of what happens in the first three months. A good VA with a bad first week often struggles. An average VA with a well-run first week often turns into a very good one.

This guide is the week-one plan we use, written so you can run it yourself whether you hire through an agency, a marketplace or a referral. It covers what to prepare before day one, what to do each day, how to hand over access safely, how to set the communication rhythm, and how to know at the end of the week whether things are on track. If you have not hired yet, start with how to hire a virtual assistant and the interview questions and trial task, then come back here.

Why week one matters more than the hire

When a placement fails, the founder usually blames the person. When we look closely, the cause is more often that nobody onboarded them. I wrote a whole post-mortem on this in why virtual assistants don't work out, and "no onboarding" shows up in nearly every story.

The reason is simple. A remote VA cannot absorb your business by sitting near you. They cannot overhear how you talk to clients, see which emails you ignore, or notice that you always check the bank balance before approving a supplier invoice. Everything an in-office hire picks up by osmosis has to be made explicit for a remote one. Week one is where you make it explicit.

Before day one: the preparation that saves the week

You can run a good first week with very little preparation, but not with none. Set aside two or three hours in the days before the VA starts and do four things.

1. Pick the first three tasks

Not ten. Three. Choose tasks that are frequent, reasonably well defined, and low risk if something goes slightly wrong. Common good starters are inbox triage, calendar management, CRM updates after calls, invoice chasing and preparing a weekly report.

Avoid starting with anything that touches money movement, anything client-facing and sensitive, or anything that only you fully understand. Those come later, once trust and context exist. If you are unsure what to hand over at all, the 20-minute delegation test in our guide on what a virtual assistant does will give you a list in one sitting.

2. Record yourself doing each task once

You do not need to write perfect SOPs before day one. In fact, you should not. Instead, the next time you do each of the three tasks, record your screen and talk through what you are doing and why. "I archive anything from this newsletter. Anything from this client gets starred and I reply same day. If an invoice is over a certain amount, I check it against the purchase order first."

The "why" is the valuable part. It is the judgment that turns a task-doer into someone who can handle the exceptions. A rough ten-minute recording with the reasoning spoken out loud beats a polished document that only lists the steps.

3. Prepare access, but do not hand it all over

Make a list of every tool the VA will need for the first three tasks, and only those tools. Typical first-week access is email (or delegated access to it), calendar, a task manager, a shared drive folder, a password manager and perhaps the CRM. Banking, payroll, admin consoles and anything with "delete all" buttons can wait.

We will come back to how to share access safely below.

4. Write a one-page "how I work" note

This is the most underrated onboarding document there is. One page, in plain language:

• Your working hours and time zone, and when you are reachable.
• How you like to receive updates (one daily message, a shared doc, a channel).
• How fast you expect replies, and how fast they can expect yours.
• What you never want them to do without asking.
• Your pet peeves. Everyone has them. Tell the VA now rather than discovering them through your irritation in week four.

Day one: context before tasks

The temptation on day one is to get the VA working immediately. Resist it a little. The first day is mostly about context, and an hour of your time here pays back for months.

Morning: a 60 to 90 minute kickoff call. Cover the business in plain terms: what you sell, who your customers are, who the important people are (key clients, partners, team members), and what a good month looks like. Then walk through your tools on screen share, and show where things live.

Agree the escalation rules. This is the single most important conversation of the week. Split decisions into three buckets:

1. Handle alone. Things the VA does without asking, such as accepting meeting invites from the team, archiving newsletters, or updating CRM fields after a call.
2. Draft for approval. Things the VA prepares and you approve, such as client replies, supplier emails or social posts.
3. Always comes to me first. Anything involving money, commitments on price or dates, complaints, legal matters, or anything that feels unusual.

Write the buckets down in a shared doc. They will change over time, and almost everything starts in bucket two and moves to bucket one as trust builds. That movement is the whole point of the relationship.

Afternoon: watch the recordings and ask questions. The VA watches your task recordings and comes back with questions. Good VAs ask a lot of questions on day one. If yours asks none, gently ask them to restate one task back to you in their own words.

End of day: the first end-of-day update. Ask for a short written note: what they did, what is unclear, what they need. This starts the habit on the first day, before there is much to report, so it is normal by the time there is.

Day two: first real task, done together

Pick the first of your three tasks and do it with the VA watching, then have the VA do the next instance while you watch. Screen share works well for this. It feels slow. It is the fastest way to transfer the small decisions that never make it into documents.

Then let them do a batch alone and review the output the same day. When you give feedback, be specific and neutral: "This reply is good, but for this client I always use their first name and skip the sign-off." Not "this isn't quite right."

Ask the VA to start drafting the SOP for task one from your recording and the morning's session. This is important. The VA writing the SOP, not you, means the document reflects what they actually understood, and the gaps become visible quickly. It also means your business ends up owning the process, not just the person. That matters if anything ever changes.

Day three: second and third tasks

Repeat the day-two pattern for the other two tasks. By now the VA has context and has seen how you give feedback, so this usually goes faster.

Keep the reviews tight. In week one, review everything, and review it the same day. A mistake caught on Wednesday is a two-minute conversation. The same mistake discovered three weeks later, repeated forty times, is a frustrating afternoon and a dent in trust on both sides.

This is also a good day for a short check on tools. If your VA is AI-fluent, ask which parts of the three tasks they would use AI for and how they would check the output. You want someone who uses the tools and verifies the result, not someone who pastes whatever comes back. Agree now which AI tools are approved and what must never be pasted into them, such as client personal data or passwords.

Day four: let go a little

On day four, the VA runs all three tasks on their own and you review afterwards instead of alongside. You are now checking outputs, not watching the work happen.

Two things to look for:

• Are the questions getting better? On day one, questions are about where things are. By day four, good questions are about judgment: "This client asked for a discount. I put it in bucket three, but should it always be?" That shift is the clearest sign the VA is learning your business rather than just the steps.
• Are the SOPs taking shape? The task-one SOP should be fairly complete by now, with tasks two and three in progress. Read them. Correct them. They are the real asset of week one.

If you have spare capacity for the VA, this is also the day to name task four, but do not add it yet. Adding work before the first three are stable is the most common way founders overload a new VA and then misread the result as poor performance.

Day five: the week-one review

End the week with a 30-minute call. Keep it structured:

1. What went well? Be specific. Tell the VA what they did that you want more of.
2. What needs to change? Again, specific. One or two things, not a list of twelve.
3. What is still unclear? Ask the VA. Their answer tells you where the documentation is thin.
4. What moves buckets? Is there anything that can move from "draft for approval" to "handle alone"?
5. What is next? Agree task four and five for week two, and when they start.

Sharing access safely

Access is where week one most often goes wrong in a way that is hard to undo, so it deserves its own section.

Use a password manager with sharing. Do not send passwords over email or chat. Most business password managers let you share individual logins, and some let you share access without revealing the password itself. Share only what week one needs.

Prefer delegated access to shared passwords. Many tools let you add someone as a user or delegate with their own login, rather than handing over yours. Google Workspace and Microsoft 365 both support mailbox and calendar delegation, and most CRMs and task managers support separate user accounts with limited roles. Separate logins mean separate permissions and a clean record of who did what.

Turn on two-factor authentication for any account the VA uses, and agree how codes are handled. A shared authenticator through your password manager is cleaner than texting codes back and forth at odd hours.

Keep money and destructive actions separate. Even with a VA you trust completely, it is good practice that payments and bulk deletions need your approval. That is not a statement about the person. It protects you both.

Put the confidentiality agreement in place before access. If you are hiring directly, sign an NDA and agree on how client data is handled before the first login is shared. If you hire through an agency, ask what agreements are already in place and what they cover. Our virtual assistant security and NDA guide covers what to put in that agreement and how to offboard cleanly.

The communication rhythm that works

The right rhythm depends on you, but a structure that works for most founders looks like this:

• A daily written update at the end of the VA's day: done, blocked, needed from you. Three to five lines. Short is a feature.
• A weekly 30-minute call for priorities, feedback and bucket changes. In week one this is the day-five review. After that it can be any fixed day.
• One channel for urgent things and an agreed definition of urgent. If everything goes in one stream, the urgent items get lost.
• A shared running doc with the escalation buckets, the SOP list, open questions and decisions. It becomes the memory of the relationship.

What a good end of week one looks like

You do not need perfection after five days. You are looking for direction. By the end of a good first week:

• The VA is running three tasks with light review.
• There is a draft SOP for each of them, written by the VA.
• The escalation buckets are written down and at least one item has moved.
• You have a daily update habit and a weekly call booked.
• You have spent noticeably less time on those three tasks on Thursday and Friday than on Monday and Tuesday.

If most of those are true, you are on track. Week two widens the load, week three tightens the SOPs, and by week four you should be reviewing summaries rather than raw work. After that, the job shifts from onboarding to managing, and our guide on how to manage a virtual assistant covers the weekly rhythm that keeps the role growing.

How we handle week one at Virtual Assistant Capital

If you hire through us, we run a structured first week with you: tools and access, your processes documented, the communication rhythm and escalation rules agreed. You still work directly with your VA, day to day. Our team handles vetting, cover during leave, quality support and replacements. You can see the four-step process on how it works.

Because your processes are documented from week one, a replacement, if one is ever needed, inherits that knowledge instead of starting from zero. That is our 30-day replacement promise in practice: if the fit is not right within 30 days, we replace your VA at no cost.

On pricing: Essentials is $899 a month for 20 hours a week, Executive is $1,599 a month full time, and AI Manager is $2,599 a month for a full-time, AI-fluent VA. There is no recruitment fee, you get a free shortlist of 2 to 3 VAs within 72 hours, you pay only once your VA starts, and plans are month to month.

FAQ

How long does it take to onboard a virtual assistant? Expect the first week to be mostly setup and supervised work, and the VA to run their first few tasks with light review by the end of it. Most placements reach a steady rhythm somewhere in weeks three to four, depending on how complex the work is and how quickly feedback flows.

What should I give a virtual assistant on the first day? Context first: a short call on how the business works, a tour of the tools, your "how I work" note, and the escalation rules. Then access to only the tools needed for the first three tasks, and recordings of you doing those tasks with your reasoning spoken out loud.

Should I write SOPs before my virtual assistant starts? Not complete ones. Record yourself doing each task once and let the VA draft the SOP from the recording and your walkthrough. That way the document reflects what they actually understood, and you spend your time correcting rather than writing.

How do I safely give a virtual assistant access to my accounts? Use a password manager with sharing, prefer delegated or separate user logins over handing out your own passwords, turn on two-factor authentication, and keep payments and bulk deletions behind your approval. Sign a confidentiality agreement before access is shared, and keep a list of what was granted.

How do I know if onboarding is going well? Watch the questions. Early questions are about where things are; good later questions are about judgment. By the end of week one you should see three tasks running with light review, draft SOPs written by the VA, and noticeably less of your own time going into those tasks.

What if it is still not working after a few weeks? First check the basics: clear tasks, written escalation rules, regular specific feedback. If those are in place and it is still not working, it may be a fit problem. With Virtual Assistant Capital, if the fit is not right within 30 days, we replace your VA at no cost, and the documented processes carry over.

The short version

Choose three tasks, record yourself doing them, and prepare only the access those tasks need. Spend day one on context and escalation rules, days two and three doing the tasks together and reviewing the same day, day four letting go a little, and day five reviewing the week. Let the VA write the SOPs. Grow access with the work. Give specific feedback early and often. Do that, and the first week stops being a gamble and becomes the foundation the rest of the relationship is built on.