How to onboard a virtual assistant: a 30-day plan that works
Onboard against outcomes, not a task list. Week one: access, context and one narrow task run under observation. Week two: the same task owned with daily reporting. Week three: a second task plus exception-only reporting. Week four: review against three metrics — quality, speed and consistency — and decide whether to expand scope. Start with a paid test assignment before the full engagement; it predicts fit better than any interview.
Before day one
- One-page company context: what you sell, to whom, what matters
- Access checklist with tool, role and who grants it
- The first SOP, written or recorded
- A written definition of the first outcome they own
- Communication rules: channel, response windows, weekly report format
The four-week arc
Week one is observed execution and correction. Week two is ownership with daily reporting. Week three adds a second task and moves to exceptions-only reporting. Week four is the review: quality (errors per output), speed (cycle time), consistency (percentage delivered on rhythm).
The paid test assignment
A three to five hour paid task representative of the real work, with a real deadline and a written brief. You are testing comprehension, questions asked, adherence to format and communication under a deadline — not raw speed.
The escalation rule
Write down what must always come to you: anything above a money threshold, anything client-facing that deviates from template, anything irreversible. Everything else is theirs. Without this, either everything escalates or nothing does.
Common follow-up questions
How long until a VA is productive?
Two to four weeks for a documented first task. Longer if documentation is created during onboarding rather than before.
Should I pay for the test assignment?
Yes. Unpaid tests attract the wrong candidates and give you a worse signal.
Which of the four systems is missing in your case?
Four questions, no email. You get the constraint, how sure we are, and the one thing to do next.