First virtual assistant checklist: what to prepare before you hire

Key takeaways

• Your first VA role should remove 5 to 10 hours of repeatable work each week, not become a vague catch-all for everything you dislike doing.
• Build the role from 1 workflow cluster, 3 documented SOPs, 3 to 5 success metrics, and a 30-day ramp plan before recruiting starts.
• 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 are managing output, not hovering over activity.
• The best first VA checklist becomes the job post, onboarding plan, first-month scorecard, and operating rhythm after the hire starts.

Choose the work before you choose the person

Start with a 7-day task capture. For one week, keep a running list of work you repeat, postpone, or redo because it is easier to handle it yourself. A spreadsheet with four columns is enough: task, frequency, minutes, and risk. By Friday, you should know which 10 to 20 tasks are stealing attention from sales, delivery, or leadership.

There is a reason inbox and coordination work show up first on most delegation lists. McKinsey Global Institute estimated that knowledge workers spent 28% of the workweek managing email and almost 20% searching for internal information. Even if your numbers are half that, reclaiming a few hours from inbox triage and information hunting is worth real money.

The best first VA tasks are frequent, visible, and reversible: calendar coordination, inbox labeling, meeting notes cleanup, CRM hygiene, invoice follow-up, vendor research, weekly report formatting, document organization, and first-draft customer replies. Avoid first tasks that require judgment you have not explained yet, such as negotiating with a key client or approving refunds.

Turn the task pile into one clear role

Do not hire a "general VA" if the actual job is founder operations support. Name the lane. A simple mission statement works better than a bloated job description: "Keep the founder's calendar, inbox, CRM reminders, and weekly admin follow-up organized so no important client or sales item gets missed." That sentence tells the assistant what the role protects.

Build the scorecard on one page. Include 1 mission, 3 to 5 recurring ownership areas, the tools they will use, expected working hours, response window, escalation rules, and the first 30-day outcome. For example: by day 30, the assistant owns inbox triage twice per day, schedules meetings within 1 business day, updates CRM tasks every afternoon, and sends a Friday admin summary by 3 p.m.

The U.S. Bureau of Labor Statistics describes administrative assistant work around scheduling appointments, handling correspondence, maintaining files, and supporting office operations. That matters because your first VA role should be built around observable operations, not a wish that someone will "be proactive" without context. Proactive comes later, after the assistant has seen enough examples to make good calls.

Document only the first three workflows

You do not need a 40-page operations manual before hiring. You do need 3 usable SOPs. Pick the workflows the assistant will touch in week one, usually one inbox workflow, one calendar or CRM workflow, and one reporting or research workflow. Each SOP should explain why the task exists, when it happens, what inputs are required, what finished work looks like, and when to escalate.

Use examples, not lectures. If the SOP is for inbox triage, include 8 to 12 sample emails with the label, priority, and action you expect. If the SOP is for CRM cleanup, include before-and-after screenshots of 5 records. A smart assistant can learn faster from 10 real examples than from 1,000 words of abstract instructions.

Add two small templates directly into the SOP. Daily update: "Completed: [tasks]. Blocked: [issue + what I tried]. Questions: [items needing your call]. Next: [tomorrow's first 3 priorities]." Escalation note: "I paused this because [risk/exception]. My suggested next step is [option]. Please approve, change, or tell me to handle it another way." These templates save you from the two worst patterns: silence when something is stuck and random chat pings for every tiny decision.

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. Then decide the access level for each one. Use named accounts, least-privilege permissions, and a password manager. Do not send passwords in Slack, email, or text 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 one line prevents a lot of nervous guessing. It also protects the assistant from being blamed for decisions they should never have owned.

Use a 30-day ramp instead of a sink-or-swim handoff

A capable VA can contribute in week one, but ownership takes a month. Week 1 is access, shadowing, and 2 or 3 low-risk tasks per day. Week 2 adds reviewed execution on the first workflow cluster. Week 3 gives the assistant one recurring lane to run with spot checks. Week 4 is the scorecard review: what is independent, what still needs review, and what workflow gets documented next.

Here is a realistic version. A solo consultant hires a VA for 15 hours per week. The first workflow cluster is client follow-up. 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 client replies drafted, 3 scheduling conflicts flagged, 2 invoices needing approval, and 6 CRM records updated. By week four, the VA sends routine scheduling replies independently and escalates only pricing, complaints, and contract questions.

Microsoft's 2023 Work Trend Index reported that 68% of surveyed workers said they did not have enough uninterrupted focus time during the workday. Your first VA should buy back focus, not create another meeting-heavy management loop. Keep the cadence light: one daily written update, one 15-minute check-in two or three times a week during the first month, and one weekly scorecard.

Review output with a simple scorecard

Decide how quality will be checked before the first assignment. For the first 2 weeks, review high-risk outputs before they go out. For low-risk work, sample 20% to 30% of completed items 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 needed. 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 is useful management.

End every week with one decision: keep, tighten, or expand. Keep means the assistant continues the same workflow. Tighten means the SOP, examples, or permissions need work before more responsibility is added. Expand means you add the next adjacent task. This stops the common founder mistake of throwing 12 unrelated tasks at a new VA because the first 2 went well.

How to use this playbook

Read this article as an operating document, not just an overview. Pick one workflow, one role, or one quality standard from the guide and turn it into a written checklist before assigning it to an assistant. Outsourcing improves fastest when each article becomes a small change in the way work is delegated, reviewed, and improved.

For OutsourcedU, the practical next step is to connect the idea back to a role scorecard, SOP, onboarding plan, or weekly scorecard. That keeps the content aligned with the broader offshore team system instead of leaving it as general advice.

Where this fits in the outsourcing system

First virtual assistant checklist: what to prepare before you hire supports the same sequence used across the OutsourcedU playbooks: clarify the work, document the standard, train the remote team member, review output, and expand ownership only after quality is consistent. Skipping any part of that sequence usually creates avoidable rework.

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 implementation plan, including outcomes, cadence, quality checks, and management expectations.

FAQ

Sources

• McKinsey Global Institute, The social economy — Cited for time spent on email and searching for internal information.
• U.S. Bureau of Labor Statistics, Secretaries and Administrative Assistants — Used to anchor common administrative responsibilities such as scheduling, correspondence, and file management.
• NIST SP 800-63B Digital Identity Guidelines — Referenced for authentication and account access controls.
• Microsoft 2023 Work Trend Index — Cited for the 68% uninterrupted focus-time finding.

Related articles

• What tasks should I outsource first? A founder's prioritization framework
• Remote Assistant Onboarding Checklist: The First 30 Days