The virtual assistant client onboarding process is where most client relationships are quietly won or lost, and almost nobody treats it that way. A new client signs, everyone is excited, and then the first week turns into a scramble of “can you send me access to this” and “wait, which tool do you use” until the client starts wondering whether hiring you was a mistake. None of that is a skill problem. It is a sequence problem.
I have spent time on the operations side of BPO and virtual assistant work, and the pattern is dependable: the VAs whose first weeks feel calm are not more talented. They run the same onboarding every time, from a checklist, so nothing depends on remembering. The ones who improvise leak time, trust, and sometimes the client. Here is the sequence that holds, what to confirm before you touch a single task, and a checklist you can copy at the end.
Table of contents
Open Table of contents
Why week one decides everything
Onboarding is not paperwork. It is the client’s first evidence of whether working with you will feel organized or chaotic, and people generalize hard from first impressions. A smooth first week tells the client “this person has a system, I can hand things off and stop worrying.” A messy first week plants the opposite thought, and that thought is expensive to undo.
The other reason it matters is scope. The problems that blow up a client relationship later, scope creep, missed expectations, the client adding “small” tasks that were never agreed, almost all trace back to fuzzy onboarding. The clearer you are in week one about what you do, how you communicate, and what success looks like, the fewer of those fights you have in month three.
The onboarding sequence, in order
Run these in sequence. Each step exists because skipping it causes a specific, predictable problem.
Start with the agreement and the deposit, before anything else. Work does not begin until the service agreement is signed and, for a new client, the first-period deposit is paid. This is not you being difficult. It is you being a business. Starting work on a handshake is how VAs end up doing three weeks of unpaid work for a client who vanishes.
Next, send a short welcome and a single intake form. One form, not a scavenger hunt across five emails. Ask for exactly what you need to start: the accounts you will need access to, brand or process notes, priorities for the first two weeks, and the client’s preferred way to communicate. Collecting it in one place means you are not chasing details for a week.
Then set up access deliberately. Get login information or, better, delegated access to the specific accounts you need, and confirm each one actually works before you rely on it. Nothing stalls a first week like discovering on day three that the password you were given is wrong.
Hold a short kickoff call. This is the one live conversation that sets the tone. Walk through how you work, confirm the first-two-weeks priorities, agree on where you will communicate and how fast you respond, and let the client ask anything. Fifteen to thirty minutes is plenty. The goal is a shared picture, not a meeting.
Confirm before you execute. Before you touch the first real task, send a short message that plays back what you understood: here is what I am starting on, here is how I will report, here is when you will hear from me. This single message prevents most week-one misunderstandings, because it surfaces a wrong assumption while it is still cheap to fix.
Then do the first task and report on it clearly. The first delivered task is your proof of concept. Do it well, and report it in outcome language, not “done.” That first report teaches the client what your updates will look like and starts building the trust the whole relationship runs on.
What to confirm before the first task
This is the step VAs skip under pressure, and it is the most protective one. Before you start real work, you should be able to answer four things without guessing: what exactly am I responsible for in the first two weeks, where does the client want to communicate and how quickly do they expect replies, do I have working access to everything I need, and how and when will I report. If any of those is unclear, resolve it before you begin. A five-minute confirmation beats a week of working on the wrong thing.
A copy-ready onboarding checklist
Here is the skeleton. Adapt the wording, keep the order.
- Service agreement signed and saved
- First-period deposit received (new clients)
- Welcome message sent with the single intake form
- Intake form returned: accounts, brand or process notes, first priorities, communication preference
- Access set up and tested for each required account
- Kickoff call held: how you work, first priorities, communication norms, questions
- Confirmation message sent: what you are starting, how you will report, when they will hear from you
- First task delivered and reported in outcome language
- End-of-week-one check-in: anything unclear, anything to adjust
If assembling all of that from scratch is exactly the work you started a business to avoid, that is the point of the VA Business Operations Pack. The client onboarding SOP inside is this sequence, already written with the intake questions, the confirmation wording, and the checks in place, alongside the service agreement it depends on. You change the names, not build the process.
The mistake almost everyone makes
The most common onboarding mistake is starting the work to seem eager. A new client asks “can you just jump on this today,” and the instinct is to say yes to make a good impression. But jumping in before the agreement is signed, the deposit is paid, and access is confirmed does not read as eager to the part of the client that matters later. It reads as someone without a system, and it sets a precedent that the process is optional.
The stronger move is calm structure. “I have a quick onboarding I run so nothing slips, it takes a day, and then I am fully set up to move fast.” That sentence makes you look more professional than any amount of scrambling, and it protects you from the exact situations that turn a promising client into a painful one.
Run the sequence the same way every time. Once it is a checklist instead of a memory, week one stops being a scramble and starts being the thing that makes clients trust you.
Onboarding is one stage of the wider client lifecycle. For how it connects to agreements, invoicing, reporting, and the rest, see the guide on how to run a virtual assistant business.
Frequently asked questions
What should a virtual assistant do first when onboarding a new client? Get the service agreement signed and, for a new client, the first-period deposit paid, before any work starts. Then collect what you need through a single intake form.
How long should VA onboarding take? Usually a day or two to set up, with a check-in at the end of the first week. The setup is quick when it runs from a checklist instead of being improvised.
What should I ask a new client during onboarding? The accounts you need access to, brand or process notes, priorities for the first two weeks, and how and where they prefer to communicate. Collect it in one form, not across many messages.
Should I take a deposit before onboarding? Yes, for new clients. A first-period deposit protects you from doing unpaid work for a client who does not follow through, and it signals that you run a real business.