← All guides

Virtual assistants & online business managers

VA Client Onboarding Process: Steps + Questionnaire

A VA onboarding process from signed agreement to first productive week: welcome email, copyable questionnaire, safe access handling, and a first-week plan.

September 28, 202611 min read

The agreement is signed and the client is excited. Now comes the part that shapes the whole relationship: the first couple of weeks. If onboarding is vague, you spend a month chasing logins, guessing at preferences, and redoing work. If it’s clear, the client sees in week one that they made a good hire.

A good onboarding process isn’t long. It’s the same handful of steps in the same order, every time, with a welcome email and a questionnaire you can copy.

The process at a glance

  1. Confirm the paperwork is complete and recorded.
  2. Send a welcome email that tells the client what happens next.
  3. Send the onboarding questionnaire so you learn the business before the kickoff call.
  4. Hold a kickoff call to fill the gaps and agree on priorities.
  5. Set up access safely, with the client granting it and you logging where it lives.
  6. Plan the first week so you deliver something useful early.
  7. Agree on a communication rhythm so nobody wonders what’s happening.

Step 1: Confirm the paperwork is done

Before any work starts, make sure the business side is settled and written down somewhere you can find it later. You should have:

  • A signed agreement and a clear scope of work
  • The package or retainer: hours per month, billing day, and what happens to unused hours
  • Confidentiality terms, whether an NDA or a clause in your contract (a lawyer can advise on the wording)
  • The client’s time zone and the name of your day-to-day contact

Record these on day one, so a question in month three takes seconds to answer.

Step 2: Send a welcome email

The welcome email does two jobs: it reassures the client that they’re in good hands, and it tells them exactly what happens next. Send it within a day of the signed agreement.

Subject: Welcome aboard, and what happens next

Hi Jordan,

I’m so glad we’re working together. Here’s how the next week or so will go:

  1. Today: I’ve linked a short onboarding questionnaire below. It takes about 20 minutes and helps me learn how your business runs before we talk.
  2. Kickoff call: Once you’ve sent it back, let’s meet for 45 minutes. Here’s my booking link: [link].
  3. Access: After the call, I’ll send a short list of the tools I’ll need. Please don’t send any passwords by email or chat. I’ll explain the safer way to share access when we get there.
  4. First week: I’ll start with [first priority] and send you a short update at the end of the week.

My working hours are [days and hours, time zone]. The best way to reach me is [channel], and I reply within [response time]. For anything urgent, [how urgent requests reach you].

Looking forward to it, [Your name]

Step 3: Send the onboarding questionnaire

A questionnaire keeps your kickoff call from becoming an hour of basic facts. Keep it focused on what you need to start working. A form, a shared document, or questions in an email all work.

Twenty questions can feel like homework to a busy client. The eight marked (essential) are enough to get started. Send those on their own if you’d rather, and cover the rest on the kickoff call.

Copyable onboarding questionnaire

About the business

  1. In a sentence or two, what does your business do, and who are your customers? (essential)
  2. What are your main goals for the next three months?
  3. Who else is on your team, and who should I go to with questions? (essential)
  4. Are there any busy seasons, launches, or deadlines coming up that I should know about?

The work

  1. Which tasks do you most want off your plate first? (essential)
  2. Which tasks come up every week or every month?
  3. Is there anything you’d rather keep doing yourself?
  4. What does “done well” look like for your most important task?

Tools

  1. Which tools do you use day to day (email, calendar, project management, social media, bookkeeping, file storage)? (essential)
  2. Do you already use a password manager, and would you be able to share logins through it? (essential)
  3. Are any tools set up so you can invite team members as users?

Communication

  1. How do you prefer to hear from me: email, Slack, text, or something else? (essential)
  2. How often would you like updates: daily, weekly, or only when something needs your input?
  3. What counts as urgent for you, and how should urgent things reach you? (essential)
  4. Are there hours when you’d rather not be contacted?

Preferences and voice

  1. When I write on your behalf, how should it sound? Please share an email or post that sounds like you.
  2. Is there a standard sign-off, signature, or phrase you use?
  3. Are there any clients, topics, or situations I should always check with you about first? (essential)

Anything else

  1. What’s frustrated you about working with assistants or contractors in the past?
  2. Is there anything else you’d like me to know?

One rule for the questionnaire: never ask for passwords in it. Question 10 asks how the client can share access, not for the access itself. Forms and documents get forwarded, stored, and exported, and credentials don’t belong in any of them.

Step 4: Hold a kickoff call

With the questionnaire back, the kickoff call can focus on what matters. A simple agenda for 45 minutes:

  • 10 minutes: Walk through the questionnaire and ask about anything unclear.
  • 15 minutes: Agree on the top three priorities for the first two weeks.
  • 10 minutes: Go through the tools list and agree how access will be granted (next step).
  • 10 minutes: Confirm the communication rhythm and when the first update will arrive.

Afterward, send a short recap of the agreed priorities.

Step 5: Set up access safely

VAs often need access to email, calendars, social accounts, and business software. That trust is a big part of what the client is paying for.

Let the client grant access

The safest approach is for the client to grant access themselves, in one of two ways:

  • Their own admin invites. Many tools let the account owner add you as a user, team member, or delegate with your own login. This is usually best: the client can remove your access at any time, and nobody shares a password.
  • Sharing through a password manager. When a tool only has one login, the client shares that login with you through their password manager’s sharing feature. They stay in control and can revoke the share later. When the work ends, they should also change that password, since anyone who could see it may still know it.

Passwords should never travel by email, text, chat, or a shared document. If a client sends one that way anyway, thank them, suggest the safer route for next time, and suggest they change that password.

Decide how two-factor codes will reach you

Many tools send a login code to the account owner’s phone, which can stall you while the client is in a meeting. Settle this for each tool before you need it:

  • You have your own user account (recommended). When the client invites you as a user, your two-factor codes come to you, and nothing is passed along. Use this whenever the tool allows it.
  • The password manager holds the code. Some password managers can store a login’s authenticator code with the shared login, so the code arrives with the login. The client sets this up.
  • The client forwards codes during agreed hours. For a tool that only texts codes to the client’s phone, agree on hours when they can pass one on, and plan logins for those hours.

Note the option you agree for each tool in your access log.

A copyable access request

Hi Jordan,

Here are the tools I’ll need to get started:

  • Google Calendar
  • Your project management tool
  • Instagram (scheduling only)

Where a tool lets you invite team members, please add me as a user with my email, [your email]. Where it doesn’t, please share the login through your password manager rather than email or chat. That way you stay in control and can remove my access any time.

If a tool sends login codes to your phone, adding me as a user usually solves it, since I’d get my own codes. Where that isn’t possible, let’s agree on a way to handle codes on the kickoff call.

Thanks, [Your name]

Keep an access log, never the passwords

As access comes in, record each one in an access log. The log notes where the access lives and what was granted, never the password itself. For each tool, write down:

  • Tool: Google Calendar
  • How access was granted: Invited as a user by the client
  • What you can do: Edit events on the main calendar
  • Where two-factor codes go: Your own authenticator, since it’s your own login
  • Date granted: The day it was set up

Don’t store passwords in your notes, task list, SOPs, or any workspace, Notion included. If one of those files were ever shared by mistake, it should contain nothing sensitive. The password manager holds the secrets; your log only says where they are.

Offboarding revokes everything on the list

The access log earns its keep when a client leaves. Go through it line by line: remove yourself, or ask the client to remove you, from every tool, and mark each one as revoked. For any login that was shared rather than invited, suggest the client change the password. Because the log was kept from day one, nothing gets missed.

For more on handling access across several clients, including browser profiles and two-factor codes, see how to manage multiple clients as a virtual assistant.

Step 6: Plan the first week

Aim for one visible win early while you learn the rest. A simple shape for five working days:

  • Day 1: Confirm access works for every tool on the list. Read through recent emails, files, or projects to get context. Set up the client’s recurring tasks with due dates.
  • Day 2: Start the top priority from the kickoff call. Note any questions and send them as one batch rather than one at a time.
  • Day 3: Keep going on the priority. Write down the steps of any recurring task as you do it; that’s your first process draft.
  • Day 4: Finish the first priority, or a clear first piece of it. Check in on anything waiting on the client.
  • Day 5: Send the first weekly update (template below) and plan week two.

Step 7: Agree on a communication rhythm

Agree on these early and write them down:

  • Channel: one main place for requests, so nothing hides in a side conversation
  • Response time: how quickly you’ll reply during working hours
  • Urgent requests: what counts as urgent and how it reaches you
  • Updates: how often, and in what format

A weekly update is a good default. It keeps the client informed without adding meetings.

Copyable weekly update

Subject: Weekly update, week of [date]

Hi Jordan,

Done this week:

  • Set up your recurring tasks and calendar reminders
  • Drafted the three launch emails (in the shared folder for your review)

In progress:

  • Cleaning up the inbox labels, finishing Tuesday

Need from you:

  • Approval on the launch emails by Thursday

Next week:

  • Schedule the launch emails and start on the podcast show notes

Have a good weekend, [Your name]

Your onboarding checklist

Copy this into your own system and use it for every new client:

  • Signed agreement and scope of work saved
  • Retainer hours, billing day, and rollover rule recorded
  • Confidentiality terms agreed
  • Welcome email sent
  • Onboarding questionnaire sent and returned
  • Kickoff call held and recap sent
  • Access requested through admin invites or password manager sharing
  • Each access logged: tool, how it was granted, what it allows, where 2FA goes
  • Recurring tasks set up with due dates
  • First-week plan written
  • Communication rhythm agreed and written down
  • First weekly update sent

Keeping onboarding in one place

If you’d rather not build the checklist and access log yourself, The Virtual Assistant Business System ($39, works on the free Notion plan) has them ready: onboarding and offboarding checklists, a client hub with each client’s retainer, billing day, rollover rules, time zone, and preferred channel, and an SOP library for the processes you write down in week one. Its access log records where each login lives, never the login itself, and keeps a revoke list for offboarding. There are no password fields by design; credentials stay in the client’s password manager.

FAQ

What should a virtual assistant onboarding questionnaire include?

Cover the business, the work, the tools, communication, and the client’s voice. If the full list feels long, start with the essentials: what the business does, who to ask, the first tasks, the tools, how access can be shared, the preferred channel, what counts as urgent, and what to always check first.

How long should VA client onboarding take?

Many VAs aim to go from signed agreement to real work within about a week. The exact timing depends on how quickly the client responds and how many tools are involved.

How should a client share passwords with a virtual assistant?

Ideally they don’t share passwords at all. Where a tool allows it, the client invites you as your own user. Where it doesn’t, they share the login through a password manager and change the password when the work ends. Passwords shouldn’t be sent by email, text, or chat, or stored in documents.

What should a VA access log include?

The tool, how access was granted, what it allows, where two-factor codes go, and the date. Never the password itself, which belongs in a dedicated password manager. Add a revoked date when access is removed, so at offboarding you can show the client that every line is closed.