First virtual assistant checklist before you hire

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.

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, use the list to choose one repeatable task group with a clear finished result and a review point.

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 instead of lectures. Include a handful of labeled inbox emails and before-and-after CRM screenshots; concrete examples beat a long abstract manual. Then write the finished result, evidence check, reviewer, and pause rule before the first sample.

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 live work, give the assistant only the named tools the first task needs. Have them label three old emails or schedule a test meeting; if that requires a password in chat, a shared login, or broader permissions, stop and fix the setup.

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

Use four weeks as a practical ramp, then adjust it for the task and its risk. Week 1 covers access, shadowing, and 2 or 3 safe tasks a day; week 2 adds reviewed work, and week 3 moves one task group to spot checks. In week 4, decide what is independent, needs review, or requires a better SOP.

A solo consultant might hire a VA for 15 hours per week. On Monday, the VA watches a 20-minute inbox walkthrough and labels 25 old emails; 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. The report does not set a universal meeting schedule, so keep the rhythm light enough to sustain: use a written daily update and set check-ins around the task, volume, and reviewer capacity. Review risky or customer-facing work before it goes out; for safe, consistent work, inspect a small completed sample before moving to spot checks, then revisit the rhythm when scope, sources, or approval rules change.

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 check a small safe sample for patterns, then move to spot checks and a Friday scorecard when the work is consistent.

The first scorecard should fit in 10 minutes. Track completed tasks, on-time rate, errors, response time, blockers, and SOP updates. Use a plain note that names the missed step and the SOP change to make before next Friday.

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

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.