
Guides
Five workflow phases turn a new virtual assistant agency client into a documented account
A virtual assistant agency onboarding workflow in five phases, each ending in an artifact, so the first month produces a documented account rather than a rescue.
What to take away
- Onboarding is not a welcome sequence. It is the process of turning one person's understanding of a client into something the agency owns.
- Five phases, each ending in an artifact. If a phase produces no document, it did not happen.
- Access is the phase that stalls, always. Start it before the start date and make the client's part of it explicit.
- The measure of onboarding is not how the client feels in week one. It is whether a second trained person could take the account in week six.
Plan around dependencies rather than fixed day ranges: confirm scope and request access before the start; begin observation once access is ready; and complete documentation and handover after a full cycle of the recurring work.
Why the first month is expensive
A new account consumes supervision, clarification and rework at a rate the tenth month never will. That cost is real and it is usually invisible, because nobody records the hours spent working out what the client meant.
Track the labor onboarding consumes, then decide whether to show that cost as a setup line or include it in the recurring price. Do not let it disappear into unrecorded delivery time. Also shorten onboarding deliberately, because every day saved is margin recovered on every client you ever take.
The way to shorten it is not to work faster. It is to stop rediscovering the same things.
Five phases and their artifacts
Name an agency account lead accountable for the process from confirmation through closeout. The client contact supplies scope corrections and arranges access; the assigned assistant logs observed work and drafts the standard; the account lead reviews it; and a second trained assistant performs the handover test.
| Phase | What happens | The artifact it must produce |
|---|---|---|
| Confirm | Restate what was sold, in writing, before anything starts | A scope note the client has agreed |
| Access | Credentials granted, tested and recorded | An access register naming system, holder and removal route |
| Observe | Work is done alongside the client, not for them | A task log in the client's own words |
| Document | The recurring work is written up | A working standard a second person could follow |
| Hand over | A different trained person performs a real task | A confirmation that the account is not single-person |
The last phase is the one agencies skip, and skipping it is what turns every assistant's resignation into a client loss.
Five phases, five artifacts
- Confirm: scope note agreed
- Access: access register with removal route
- Observe: task log in client's words
- Document: working standard a second person follows
- Hand over: confirmation not single-person
Phase one: confirm before you begin
Whatever was agreed verbally in the sale has to be restated in writing before work starts. Scope, exclusions, the unit, the overage rule, the intake channel, coverage hours.
A scope note can use this fill-in format: Client/account: __. Included work: __. Exclusions: __. Unit and overage rule: __. Intake channel and coverage hours: __. Day-to-day approver: __.
Send it as a short note, not as a contract restatement, and ask them to correct anything. The corrections you receive are the gaps between what you sold and what they think they bought, and they are cheaper to find now than in month two.
Anything agreed verbally by the seller and never written down becomes a dispute. That handover is part of the sale, and the process for it belongs in the sales and proposal guide.
Phase two: access, the phase that stalls
Nearly every delayed onboarding is delayed here, and usually because the client's part of it was never made explicit.
Do four things.
- List each system the work requires and the task it supports; leave out access that is not needed.
- Identify the client-side system holder and the agency user for each system, and ask the client contact to arrange access.
- Request an individual account with only the permissions needed, then test that it works for the assigned task.
- Record the system, holder, user, permissions, test status, and removal route in the access register.
Access phase: four required actions
- List every system with permission level and reason
- Name who holds each credential
- Test each grant the day it arrives
- Record the removal route for each
Keep the controls proportionate to what you actually hold. NIST’s Cybersecurity Framework 2.0: Small Business Quick-Start Guide describes practices a small operator can maintain, which is the right standard here: a control nobody follows is worse than a simpler one everybody does.
Phase three: observe before you optimize
The instinct is to improve the client's process immediately. Resist it for the first cycle.
Do the work as they currently do it, with them, and log every task in their language. What you learn is where the exceptions live, and exceptions are what make a documented process fail later.
The task log should record each task in the client's language, along with what triggered it, the input received, the result, and any exception or clarification. This gives the next phase a record of the actual work rather than a remembered summary.
At the end of this phase you should be able to answer three questions: what arrives, how often, and what makes an instance unusual.
Phase four: document so somebody else could do it
The working standard is the point of the whole exercise. It has four parts.
Use these four parts in the working standard:
- Inputs and trigger:
- what arrives and what starts the task.
- Steps and tools:
- the order of work and the systems used.
- Decisions and exceptions:
- how to handle variations and when to escalate.
- Output and completion check:
- what finished work looks like and how to verify it.
Four parts of the working standard
- Recurring tasks and what triggers each
- Decisions the assistant may make alone
- Client preferences written as rules
- Exceptions seen in phase three and responses
Write it while the work is unfamiliar. Once it is habit, you will document only the parts you remember being hard.
Which of these tasks belong to which service line, and how they were priced, follows the menu in the virtual assistant agency services guide for owners and the reasoning in the virtual assistant agency pricing and profit guide.
Phase five: prove it is not one person
Have a second trained person perform a real task on the account, with the first person available but silent.
Everything they have to ask is a gap in the working standard. Fix the document rather than answering the question, and repeat until the questions stop.
The hand-over confirmation should record the second person's name, the task tested, any remaining gaps, the final working-standard location, and the date the account lead accepts the transfer.
This is the phase that converts a relationship into an asset. Until it happens, the client belongs to an individual, and the agency is exposed to that individual's resignation, illness and vacation.
Where the work touches the client's customers
Some retainers include customer communications, scheduling for the public, or edits to a client's website. That work carries obligations that belong to the client's business rather than to yours, and they should be named at onboarding rather than discovered.
Accessibility is the common one. The Department of Justice’s ADA Update: A Primer for Small Business is a reasonable starting point for understanding a small business's obligations. Raise it with the client and let them take advice; do not decide on their behalf.
The same applies to anything touching reviews or public testimonials. The FTC’s Soliciting and Paying for Online Reviews: A Guide for Marketers sets out what is not acceptable, including incentives conditioned on a favorable review and undisclosed material connections. If an onboarding task list includes asking the client's customers for reviews, that guidance governs how it may be done.
Who is directing the work
One question deserves an explicit answer at onboarding: who gives the assistant day-to-day instructions.
It matters operationally, because an account taking direction from four people has no scope. It also matters for worker status, since the Labor Department's page on misclassification myths explains that the economic reality of the working relationship decides the question rather than the label in an agreement.
Settle it in phase one and write it into the scope note.
What the client should feel
Not gratitude. Confidence that this has been done before.
Three signals produce that: you asked for the right access without being prompted, you asked about exceptions instead of assuming none, and you told them what you would need from them and when. Those three matter more than any welcome package.
They are what the virtual assistant agency marketing and growth guide means when it treats delivery as the strongest channel you have.
When to stop onboarding
Onboarding ends when the working standard is complete, a second person has used it, and the client has stopped needing to explain things twice.
Three tests to end onboarding
- Working standard is complete
- A second person has used it
- Client no longer explains things twice
Put a date on it and review against these three tests rather than letting it fade out. Accounts that never formally finish onboarding are the ones that stay dependent on one person, and the capacity arithmetic that this all feeds into is in the virtual assistant agency startup and market guide.
Common questions
How long should onboarding take?
Use milestones rather than a fixed calendar estimate: access must be ready before work starts, and onboarding stays open until one full recurring-work cycle has been observed, documented, and tested by a second trained person. If access or the work cycle is delayed, the end date moves with it.
Should the owner run it personally?
For the first several clients, yes. After that, the working standard should be good enough that the owner reviews rather than performs.
What if the client will not grant proper access?
Then define what you can do without it and say plainly what you cannot. Working around missing access with shared credentials is the arrangement everyone regrets.
Can onboarding be billed?
It can, and pricing it as its own line makes the cost visible to both sides. What matters more is that it is priced somewhere, rather than absorbed and forgotten.







