Virtual Assistant Onboarding Checklist: The First 30 Days

What should be done before day one?

Before your VA logs in for the first time, three things need to exist on paper: a role brief that names the outcomes for the first 30 days, a documented set of the two or three workflows they'll pick up first, and every account, tool and login they'll need to do the work. Most onboarding fails because the person arrives and the work doesn't. Fixing that means treating day one as a delivery date, not a start date.

This is where we do the heaviest lifting for clients. The foundations get built with the client before the VA is even matched, so day one is genuinely a day of working, not a day of waiting for someone to be told what to do.

What's in the client onboarding questionnaire?

The client onboarding questionnaire captures the context a new VA can't guess from the outside. Fill it in with the person who'll be managing the VA, not just the founder. Keep it short enough that it gets done and specific enough that it's useful.

• Business context. What the business does, who it serves, the top three offers, average deal size and how leads currently come in.
• Role outcomes. The two or three things this role needs to be true in 30, 60 and 90 days. Not tasks. Outcomes.
• First workflows. The specific processes the VA will pick up first, in the order you want them picked up.
• Tools and stack. Every platform they'll touch, the account owner and the level of access required.
• Communication rhythm. Daily BOD and EOD format, weekly review time, escalation path, hours of overlap.
• Voice, brand and standards. Tone guide, examples of good and bad output, non-negotiables that would get work rejected.
• Sensitive areas. Anything the VA should not touch, publish or send without approval.
• Success measures. How you'll know at the end of month one whether this is working.

What's in the VA setup checklist?

The VA setup checklist is the practical side: what has to be provisioned, sent and signed so the person can actually work on day one. Run through it the week before the start date.

• Contract, NDA and confidentiality. Signed and stored before access is granted.
• Managed device or approved BYOD. With endpoint security, drive encryption and a locked screensaver policy.
• VPN and secure browsing. Standard on our roles through NordLayer, so client systems only get accessed from a trusted network.
• Password manager. Shared vault set up with access to only the credentials the role needs.
• Email, calendar and chat. Company-domain email if possible, calendar shared, Slack or Teams provisioned.
• Time tracking and reporting. Login and logout monitoring plus a standard BOD/EOD template.
• Access to first workflows. CRM, project management, files, folders and any platform-specific access already granted at the right level.
• Documented processes. The two or three workflows they'll start on, written up in the shared knowledge base.
• Escalation contacts. Names, roles and preferred contact channels for the manager, the second-in-command and the technical lead.
• Emergency playbook. What to do if a system is down, a client asks something they can't answer, or a piece of work is rejected.

What happens in week one?

Week one is about safe wins, not volume. The goal is to have the VA producing real output by day three and to catch any friction while it's small. Run a 30-minute kickoff on day one with the client, the VA and a senior operator from our side, then daily 10-minute stand-ups for the rest of the week.

• Day 1: kickoff, access check, first workflow walkthrough, one small task completed end-to-end.
• Day 2-3: pick up the first documented workflow with the manager reviewing every piece of output.
• Day 4-5: begin the second workflow, catch questions in the daily stand-up rather than DMs.
• End of week: written retro from the VA on what was clear, what wasn't, and what's missing.

What happens in weeks two and three?

Weeks two and three are where the workload widens and the review cycles start to space out. The manager reviews samples of output rather than every piece, and the VA starts flagging their own quality issues before they get flagged for them.

• Move from full review to sample review on any workflow the VA has run cleanly for a week.
• Add the third and fourth workflows from the onboarding plan.
• Introduce the weekly one-on-one: 30 minutes, agenda run by the VA.
• Document any process the VA has learned on the job so the next hire doesn't have to relearn it.

What happens in week four?

Week four is the honest assessment. Are the 30-day outcomes from the questionnaire actually true? If yes, agree the next 30-day plan and move to a lighter cadence. If not, name the specific gap, decide whether it's a coaching issue, a brief issue or a fit issue, and act on it now rather than at 90 days.

• Review the 30-day outcomes against the questionnaire, in writing.
• Get feedback from the VA on the client, the tools and the workflows. It matters.
• Set the next 30-day outcomes and any change to hours, scope or focus.
• If something isn't working, use the 60-day replacement window rather than waiting.

What are the most common onboarding mistakes?

• No work on day one. The person arrives to a blank calendar and finds their own tasks. They get set up to fail.
• Access granted late. Every day spent chasing logins is a day of paid time producing nothing.
• No documented workflows. Verbal walkthroughs vanish the moment the call ends.
• Manager unavailable. First-week questions need answers inside the hour, not the day.
• No standards examples. Without examples of accepted and rejected work, quality is a guessing game.
• Waiting for the 90-day mark. If something's off at day 20, address it at day 20.

This is the sequence we install on every new placement. It's the difference between a hire that works out and one that doesn't, and it's most of the reason our placements stay.