Client Onboarding Checklist for Virtual Assistants

Client onboarding is the short stretch between “yes” and the first useful piece of work. It is where a vague promise becomes a working arrangement: what you will do, what you may decide, where work lives, how you will communicate, and when you will be paid.

You do not need branded onboarding software or a 20-page questionnaire. You need clear written decisions and a way to find them later.

This checklist is general operational information for independent client work, not a contract or legal advice. Employment, tax, privacy, invoicing, and contract rules depend on the countries and facts involved.

Still looking for a suitable first project? Read Get Your First Client With No Experience and check unfamiliar offers against Is Being a VA Legit or a Scam?.

The onboarding process at a glance

Phase	Question to settle	Written output
1. Qualify	Can I do and price this responsibly?	Defined scope and assumptions
2. Agree	Are we describing the same deal?	Signed terms and payment route
3. Brief	What do I need during daily work?	One-page client brief
4. Access	What is the safest permission level?	Access register
5. Kickoff	What happens first, and who approves it?	Call recap and first task
6. First delivery	Does the process work on a small scale?	Reviewable deliverable
7. Review	What should change after real use?	Updated scope or procedure
8. Offboard	How will work and data be handed back?	Access removal and handoff record

You may combine phases for a very small project, but do not skip the decisions.

Phase 1: qualify the work before saying yes

Ask enough questions to understand the actual workload:

What result does the client want first?
Which recurring and one-time tasks are included?
What volume is typical: messages, posts, meetings, records, or hours?
What deadlines, time zones, and response windows matter?
Which systems and kinds of data will you access?
Who gives instructions, and who approves the work?
Is there a budget, paid trial, proposed contract, or purchase process?

A role described as “a few admin tasks” may quietly include sales calls, bookkeeping, weekend availability, design, and personal errands. List the work before quoting it. Your beginner rate calculation only works when the scope and likely volume are visible.

Stop when the opportunity requires you to pay to unlock a job, deposit a check and forward money, buy gift cards, install suspicious remote-access software, or reveal banking passwords or one-time codes. A real client may need payment details to pay an invoice. They do not need control of your account.

Phase 2: put the agreement and payment route in writing

Before work begins, record:

the correct names and reliable contact details for both sides;
services, deliverables, exclusions, and expected volume;
hourly rate, fixed price, or retainer capacity;
currency, invoice schedule, due date, fees, and payment method;
start date, milestones, deadlines, and client dependencies;
revision and change-request process;
working hours, response expectations, and meeting cadence;
confidentiality, ownership, data handling, and access duties;
pause, termination, cancellation, and offboarding terms.

A written agreement helps both sides remember the same deal, but the title on a document does not override the real relationship. For example, US worker-classification guidance considers control and the facts of the arrangement, not only whether the document says “independent contractor.” Other countries use their own tests. Get local advice when the working arrangement resembles employment or the contract carries substantial risk.

For direct work, confirm any deposit or milestone before the start date. On a marketplace, keep scope, messages, time records, delivery, and payment within the platform when its protection rules require it. Test the agreed payment route using How to Get Paid as a Virtual Assistant.

Phase 3: create a one-page client brief

Turn discovery notes into a reference you can use while working:

Client and main contact:
Primary outcome:
First deliverable:
Included tasks:
Not included:
Expected volume:
Priority order:
Client time zone:
Working and response hours:
Approver and backup contact:
Communication channel:
Task tracker and file location:
Escalate immediately when:
Never do without approval:
Weekly report day and format:
Invoice schedule and due date:
Review date:

The authority lines matter. An inbox VA may be allowed to send routine scheduling replies but required to draft, not send, messages involving refunds, legal threats, personnel, complaints, or confidential financial information.

Send the brief to the client and ask them to correct anything you misunderstood. That simple step catches many problems before they become rework.

Phase 4: arrange secure, limited access

Create an access register with the tool, account owner, permission level, reason for access, date granted, and date removed. Ask for the minimum permission needed. Someone scheduling posts may not need billing access or permission to change account ownership.

Prefer:

a separate user account created for you;
native delegation or role-based access;
a business password manager’s secure sharing feature when delegated access is unavailable.

Do not ask the client to send a plain-text password by email or chat. Google, for example, supports Gmail delegation so another person can manage email without changing the account password. Enable multifactor authentication on your own work accounts; CISA recommends MFA for email, file storage, remote access, and privileged accounts.

Agree on:

which devices may access the account;
whether files may be downloaded;
where client data may be stored or backed up;
which tools may process the information;
how a suspected incident should be reported;
when access will be reviewed and removed.

If you handle personal data for an EU or UK organisation, data-protection rules may require specific controller-processor contract terms, including documented instructions, confidentiality, security, and end-of-contract data handling. Do not assume a generic nondisclosure agreement covers every obligation.

Phase 5: run a focused kickoff

For many small engagements, 30 to 45 minutes is enough if you arrive prepared. A simpler project may need less; a complex one may need more.

Use this agenda:

Confirm the first outcome and priority order.
Walk through one real task from request to approval.
Confirm what you may decide without asking.
Test only the access needed for the first task.
Agree on urgent and routine communication.
Set the first deliverable, owner, and check-in date.
Confirm invoice timing and any client dependency.

Write down decisions instead of relying on a recording. If recording would be useful, get consent and follow the applicable law and company policy.

Send this kind of recap afterward:

Subject: Kickoff recap and first deliverable

Hi [Name],

Here is my understanding from our kickoff.

First deliverable: [deliverable and date]
I may: [approved actions]
I will ask before: [restricted actions]
You will provide: [access, file, or decision and date]
Check-in: [date, time, and time zone]

Please correct anything I have misunderstood.

Phase 6: make the first deliverable small

Do not migrate an entire system or switch on broad automation on day one. Start with a representative piece that the client can review and, where possible, reverse.

Worked example: inbox support

Leah’s new client asks her to “keep the shared inbox organised.” During onboarding, they turn that into a clear first trial:

Leah triages twice each weekday during agreed hours.
She labels messages as Client, Leah, Waiting, or Archive.
She may send scheduling replies from approved templates.
Refunds, complaints, contracts, and personnel messages stay in Client.
Nothing is permanently deleted during the trial.
Friday’s report shows volume handled, unresolved items, and proposed filter changes.

On day one, the client delegates Gmail access and reviews ten example messages with Leah. A few days later, they correct two routing rules. Only after the first review do they approve the process and consider filters. This is safer than chasing “inbox zero” immediately.

For the underlying workflow, see Email and Calendar Management for VAs.

Phase 7: review the work after real use

Review early enough to correct the process before habits set in. After the first deliverable or week, ask:

Which output was correct, incomplete, or unnecessary?
Which instruction or example was missing?
Where did approval block progress?
Was the estimated volume accurate?
Should any access be added or removed?
What one process should become a written procedure?

At the agreed review point, compare actual work with the original scope. Document added tasks and propose a new scope, capacity, or price before continuing them. Silence is not agreement to indefinite unpaid extra work.

Phase 8: plan offboarding from the beginning

An engagement will eventually pause or end. Agree on how to:

finish, cancel, or hand over open tasks;
send the final invoice and address any dispute;
transfer client-owned files, procedures, and status notes;
remove delegated access, active sessions, API keys, and shared folders;
return or delete client data as the agreement and law require;
confirm the completed handoff and access removal in writing.

Do not retain a client’s contact list or private materials as portfolio samples. Ask for specific written permission before using even anonymised work.

Once the onboarding decisions are clear, issue invoices with the VA Invoice Template and Payment Terms.

Complete onboarding checklist

Before agreement

Verify the client and opportunity.
Define the outcome, tasks, volume, schedule, and required access.
Identify regulated, sensitive, or high-risk work.
Confirm the budget and legal working arrangement.

Before work

Sign or confirm the written terms.
Agree on price, currency, invoice timing, due date, and payment method.
Approve the one-page client brief.
Create minimum necessary access with MFA on your accounts.
Test the first workflow and file location.
Set the first deliverable and review date.

During the first review

Compare actual volume and work with the scope.
Correct authority, approval, or communication gaps.
Remove access that is no longer needed.
Turn one repeated task into a written procedure.
Quote scope changes before continuing them.

At offboarding

Hand over open work, files, and procedures.
Send the final invoice and retain required records.
Remove every account, session, key, and shared folder.
Return or delete client data as agreed and legally required.
Confirm completion in writing.

FAQ

What must be clear before client work starts?

At minimum: scope, authority, communication, payment, and access. You should know what you are delivering, what you may decide, where updates go, when and how you are paid, and which systems you may use.

Should I accept a client’s password?

Use a separate account, native delegation, role-based access, or secure password-manager sharing when possible. Never request a one-time code. Shared passwords make security and offboarding harder for everyone.

How long should a kickoff call be?

Long enough to settle the first workflow and test the required access. Thirty to 45 minutes is often enough for a small engagement, but complexity matters more than the clock. Always send a written recap.

How much work should I do in the first week?

Choose a representative, reviewable piece. Keep irreversible actions and broad automation out of the first pass. Expand only after the client has reviewed the process and corrected any assumptions.

When should I revisit scope and price?

Set a review point in the agreement, and review sooner when the actual volume or duties differ materially from the brief. Document the change and agree on a new price before continuing it.

Sources & further reading

Video references

Watch the workflow

One last check: if your next step involves a fee, an ID, or a platform account, open the official link first. Rules and availability can differ by country and can change after a guide is published.