Client Onboarding Checklist for Virtual Assistants

Client onboarding is the bridge between “yes” and useful work. A good onboarding process does not need branded software or a 20-page questionnaire. It needs written decisions: what you will do, what you may approve, where work lives, when you will communicate, and how payment works.

This checklist is for independent client work. It is general operational information, not a contract or legal advice. Employment, tax, privacy, and invoicing 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 every opportunity against Is Being a VA Legit or a Scam?.

Phase 1: qualify the work before saying yes

Ask enough questions to price and schedule responsibly:

What result does the client need in the first 30 days?
Which recurring tasks and one-time tasks are included?
What volume is typical: messages, posts, meetings, records, or hours?
What deadline, time zone, and response window matter?
Which systems and kinds of data will you access?
Who gives instructions and who approves work?
Is there a budget, paid trial, or proposed contract?

Watch for a role described as “a few admin tasks” that also includes sales calls, bookkeeping, weekend availability, design, and personal errands. Rewrite it as a defined scope before quoting. Your beginner rate calculation only works when the workload is visible.

Do not pay to unlock a job, accept a check and forward money, buy gift cards, install unverified remote-access software, or share banking credentials. A legitimate client may need your payout details; they do not need your password or one-time security code.

Phase 2: put the agreement and payment route in writing

Before work begins, record at least:

legal or business names and reliable contact details;
services, deliverables, exclusions, and expected volume;
hourly rate, fixed fee, or retainer capacity;
start date, milestones, deadlines, and dependencies;
revision or change-request process;
working hours, response expectations, and meeting cadence;
confidentiality, ownership, data handling, and account-access duties;
invoice schedule, due date, currency, fees, and payment method;
pause, termination, and offboarding steps.

A written agreement helps both sides remember the same deal, but its title does not override the real relationship. For example, US worker-classification guidance looks at control and the facts of the relationship, not only the label “contractor.” Other countries use their own tests. Seek local advice if the client controls how, when, and where you work in a way that resembles employment.

For direct work, confirm whether a deposit or funded milestone is required before the start date. On a marketplace, keep scope, messages, time records, delivery, and payment inside the platform when its protection rules require that. Set up the agreed currency and test the payment route using How to Get Paid as a Virtual Assistant.

Phase 3: create a one-page client brief

Turn the discovery conversation into a document you can actually use:

Primary outcome:
First 30-day result:
Included tasks:
Not included:
Priority order:
Client time zone:
Working / response hours:
Approver and backup contact:
Communication channel:
Task tracker and file location:
Escalate immediately when:
Never do without approval:
Weekly report day:

The two authority lines are especially important. An inbox VA might be allowed to send routine scheduling replies but required to draft, not send, messages involving refunds, legal threats, personnel, or confidential financial information.

Phase 4: arrange secure, limited access

Create an access list with the tool, permission level, owner, and removal date. Ask for the minimum permission needed for the task. Someone scheduling posts may not need billing or account-owner access.

Prefer these methods, in order:

A separate user account created for you.
Native delegation or role-based access.
A business password manager’s secure sharing feature when no delegated option exists.

Do not ask a client to send a plaintext password in email or chat. Google, for example, supports Gmail delegation so a delegate 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 where client data may be stored, which devices may be used, whether downloads are allowed, and how incidents are reported. If you handle personal data for an EU or UK business, 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 those obligations.

Phase 5: run a focused kickoff

Use a 30- to 45-minute agenda:

Confirm the first outcome and priority order.
Walk through one real task from start to approval.
Confirm what you can decide without asking.
Test tool access while the client is present.
Agree on urgent and non-urgent communication.
Set the first deliverable and check-in date.

Record decisions in the client brief, not only in a call recording. If recording is useful, get consent and follow applicable privacy law and company policy.

After the call, send a short recap: “Here is what I understood, what I will deliver first, what I need from you, and when we will check in.” Give the client a chance to correct it.

Phase 6: make the first week deliberately small

Do not migrate an entire system on day one. Start with a representative, reversible piece of work and make quality visible.

Worked example: inbox support

Leah’s new client wants help with a busy shared inbox. The vague request is “keep it organized.” During onboarding, they convert that into:

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 two-week trial.
Friday’s report shows volume handled, unresolved items, and proposed filter changes.

On day one, the client delegates Gmail access and reviews ten sample messages with Leah. On day three, they correct two routing rules. At the end of the week, they approve the process before adding automation. This is safer than chasing “inbox zero” immediately.

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

Phase 7: review after the first week and first month

At the first-week review, ask:

Which output was correct, incomplete, or unnecessary?
Where did approval block progress?
Was the estimated volume accurate?
Should any access be added or removed?
What one process should become an SOP?

At 30 days, compare actual work with the agreement. Document added tasks and propose a new scope, capacity, or price before continuing them. Silence is not approval for unpaid scope expansion.

Keep offboarding in the onboarding checklist

An engagement will eventually pause or end. Your process should already say how to:

finish or hand over open tasks;
send the final invoice and confirm payment;
transfer client-owned files and SOPs;
remove delegated access, sessions, API keys, and shared folders;
return or delete client data as the agreement and law require;
confirm completion in writing.

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

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

Sources & further reading

Video references

Watch the workflow

Before you act: platform rules, fees, eligibility, and local requirements can change. Check the official links in this guide and verify the current terms for your country and account.