First virtual assistant checklist before you hire
Use this first virtual assistant checklist to define tasks, SOPs, access, success measures, and a 30-day review plan before you interview or hire.
Operator sections with practical steps.
Decision points before handoff.
Visible citations and source notes.
Key takeaways
- Give your first VA one repeatable task group, not a catch-all.
- Build the role around one task group, 3 SOPs, 3 to 5 success metrics, and a 30-day ramp.
- Protect access from day one with a password manager, named accounts, MFA, and a written rule for what the assistant may never do alone.
- Use short templates for daily updates and quality review so you manage finished work, not activity.
- Use the checklist for the job post, onboarding, and weekly review.
Hiring your first virtual assistant gets expensive when you treat it like buying extra hands. Work leaves your desk only after you name it, package it, and check it.
Use this before posting the role to define admin, follow-up, scheduling, reporting, or CRM-cleanup work.
First-VA readiness scorecard
Use this quick scorecard before recruiting so the role has boundaries, proof, and review rules.
Two scripts to copy into the handoff
- Daily update: "Completed: [tasks]. Blocked: [issue + what I tried]. Questions: [items needing your call]. Next: [tomorrow's first 3 priorities]."
- Pause-and-ask note: "I paused this because [risk/exception]. My suggested next step is [option]. Please approve, change, or redirect me."
Choose the work before you choose the person
Start with a 7-day task capture. List repeat work in four columns: task, frequency, minutes, and risk. By Friday, you should know which 10 to 20 tasks steal attention from sales or delivery.
Inbox and coordination work show up first for a reason. McKinsey Global Institute estimated that knowledge workers spent 28% of the workweek managing email and almost 20% searching for internal information. Those are good places to look for repeatable work.
The best first VA tasks are frequent, visible, and reversible: calendar coordination, inbox labeling, meeting notes cleanup, CRM hygiene, invoice follow-up, vendor research, report formatting, and first-draft customer replies. Avoid unexplained judgment work like key-client negotiation or refund approval.
Turn the task pile into one clear role
Do not hire a "general VA" if the real job is founder operations support. A simple mission works better: "Keep the founder's calendar, inbox, CRM reminders, and weekly admin follow-up organized so no important client or sales item gets missed."
Build the scorecard on one page: 1 mission, 3 to 5 ownership areas, tools, hours, response window, ask-for-help rules, and the 30-day outcome. By day 30, the assistant might sort inbox twice daily, schedule within 1 business day, update CRM tasks, and send a Friday admin summary by 3 p.m.
The U.S. Bureau of Labor Statistics describes administrative assistant work around scheduling, correspondence, files, and office operations. Give your first VA observable work and the context to do it.
Document only the first three work processes
You do not need a 40-page manual before hiring. You do need 3 usable SOPs: usually one inbox work process, one calendar or CRM work process, and one reporting or research work process. Each SOP should show the purpose, trigger, inputs, finished result, and ask-for-help rule.
Use examples, not lectures. For inbox sorting, include 8 to 12 sample emails with the label, priority, and action you expect. For CRM cleanup, include before-and-after screenshots of 5 records. Ten real examples beat 1,000 abstract words.
Add the update and pause-and-ask templates near the top of the SOP. They show the assistant when to ask and keep decisions out of scattered chat messages.
Plan access like a security process, not an afterthought
Before the assistant starts, list every tool they need: email, calendar, CRM, project management, cloud drive, password manager, chat, invoicing, scheduling, and any industry software. Decide the access level for each one. Use named accounts, least-privilege permissions, and a password manager. Do not send passwords in chat because it feels faster on day one.
NIST's Digital Identity Guidelines treat authentication, authenticators, and account recovery as formal security controls, not office admin details. For a small business, the practical translation is simple: turn on MFA, remove access when the role ends, and avoid shared logins where you cannot tell who changed what.
Write one sentence for red-line decisions. For example: "The VA may draft refunds, vendor payments, payroll changes, contract edits, or customer credits, but the owner must approve before anything is sent or processed." That line prevents nervous guessing and protects the assistant from decisions they should never own.
Use a 30-day ramp instead of a sink-or-swim handoff
A capable VA can contribute in week one, but stable ownership takes a month. Week 1 is access, shadowing, and 2 or 3 safe tasks a day. Week 2 adds reviewed work. Week 3 moves one task group to spot checks. In week 4, decide what is independent, needs review, or requires a better SOP.
A realistic version: a solo consultant hires a VA for 15 hours per week. On Monday, the VA watches a 20-minute inbox walkthrough and labels 25 old emails as practice. By Wednesday, they draft 5 follow-ups from approved templates. On Friday, they report 14 replies drafted, 3 scheduling conflicts flagged, 2 invoices needing approval, and 6 CRM records updated. By week four, routine scheduling replies move to spot checks.
Microsoft's 2023 Work Trend Index reported that 68% of surveyed workers lacked enough uninterrupted focus time. Your first VA should protect focus time without adding a heavy review routine. Keep the rhythm light: one daily update, one 15-minute check-in two or three times a week during the first month, and one weekly scorecard.
Review finished work with a simple scorecard
Decide how quality will be checked before the first assignment. For the first 2 weeks, review risky work before it goes out. For safe work, use the quality sampling schedule planner to sample 20% to 30% and look for patterns. After the assistant is consistent, move to spot checks, exception review, and a Friday scorecard.
The first scorecard should fit in 10 minutes. Track tasks completed, on-time rate, errors found, response time, blockers, and SOP updates. Use plain notes: "Calendar invites were accurate all week. CRM notes missed source links on 4 of 18 records. Add source-link step to SOP before next Friday." That gives you a specific SOP change to make before the next review.
End every week with one decision: keep, tighten, or expand. Keep the same work process, tighten the SOP or permissions, or add the next adjacent task. This avoids throwing 12 unrelated tasks at a new VA because the first 2 went well.
How to use this playbook
Read this article like a work guide. Pick one task, one role, or one quality rule and turn it into a short checklist before you give it to an assistant. Small changes are easier to train and easier to check.
The next step is simple: connect the idea to a role scorecard, SOP, onboarding plan, or weekly scorecard. That turns the article into a tool you can use.
Where this fits
First virtual assistant checklist before you hire fits the same basic path used across OutsourcedU: choose the work, write the rule, train the person, check the result, and add more only when the work is steady. Skipping steps usually creates cleanup work.
If this topic is active in your business, the next supporting page is Outsourcing foundations. Use that page to connect the article to a broader setup plan, including outcomes, rhythm, quality checks, and management expectations.
FAQ
What should my first virtual assistant do?
Start with one related task group of repeatable, safe work: inbox sorting, calendar coordination, CRM cleanup, simple reporting, document organization, research, or routine customer follow-up.
How many SOPs do I need before hiring a VA?
Prepare 3 usable SOPs for the first week. Each should include purpose, timing, inputs, steps, examples, quality checks, and ask-for-help rules.
How long does it take a VA to become useful?
With a clear scorecard and access ready, a VA can do useful work in week one. Stable ownership usually takes a 30-day ramp.
Sources
- McKinsey Global Institute, The social economy — Email and internal-search time.
- U.S. Bureau of Labor Statistics, Secretaries and Administrative Assistants — Common administrative responsibilities.
- NIST SP 800-63B Digital Identity Guidelines — Authentication and access controls.
- Microsoft 2023 Work Trend Index — 68% focus-time finding.