Remote assistant joining a video onboarding meeting with documents ready
    Back to Blog

    Business Playbook

    Virtual Assistant Onboarding Checklist

    Good onboarding gives a virtual assistant enough context to take ownership without handing over every password and every process on day one.

    Valentina, founder of Rellatech

    Valentina Akpan: Founder of Rellatech, providing administrative and operations support to executives, founders, business owners and teams. Her background combines technical support, customer success, administration and operations.

    ·

    A virtual assistant onboarding checklist should do three things: give the person the right access, explain how work moves through the business, and make the first 30 days measurable. It should not be a folder full of old instructions or a two-hour call followed by silence.

    The strongest onboarding starts with one or two recurring responsibilities, clear approval boundaries, and safe tool access. The virtual assistant watches the process, runs it with review, documents what is missing, and then takes ownership. This guide covers preparation, access, the first week, and the handoff to a reliable monthly rhythm. The timeline in it is an example to adapt, not a fixed schedule. It assumes the hiring decision is already made.

    Good onboarding starts before the first task arrives

    Prepare a short working brief before access is granted. Name the responsibilities being handed over, who can approve changes, where requests should be sent, and what must stay with the owner. If the starting scope is recurring administration, the Administrative Support service shows the kind of work that can move first: inbox triage, scheduling, documents, client follow-up, trackers, and meeting preparation.

    • Choose one primary contact who can answer questions and approve work.
    • List the first two recurring responsibilities and what a completed result looks like.
    • Set expected communication channels, response windows, and update days.
    • Write down decisions the virtual assistant can make alone and decisions that need approval.
    • Collect current instructions, examples, templates, and known exceptions in one folder.

    Secure access uses individual accounts and minimum permissions

    Do not begin by emailing a spreadsheet of master passwords. Invite the virtual assistant as a named user in Google Workspace, Microsoft 365, the CRM, project tool, scheduling system, and website. Grant only the permissions needed for the starting scope. Use a business password manager for the few tools that require shared credentials, turn on multi-factor authentication, and record who controls recovery. This protects the business and makes offboarding much easier.

    • Create a business email address or approved external-user account.
    • Invite the person to shared drives and folders instead of sharing files one at a time.
    • Use delegated inbox or calendar access instead of sharing the owner's login.
    • Start CRM and website permissions below full administrator unless the work requires more.
    • Confirm multi-factor authentication and recovery contacts before the first live task.

    The first week is for context, observation, and one complete cycle

    The first week should include a business overview, a tool tour, and one recurring process from start to finish. The virtual assistant needs to see where a request begins, what information is required, who approves it, where completion is recorded, and what happens when something goes wrong. For inbox or scheduling work, start with the current rules and examples from Inbox and Calendar Management, then adjust those rules after a few real decisions. The day-by-day plan below is one example. A business with more tools, a wider scope, or a part-time schedule will spread the same steps over more time, and that is fine.

    • Day 1: confirm access, scope, contacts, communication, and confidentiality expectations.
    • Day 2: walk through the tools and show where current work is tracked.
    • Day 3: observe one live recurring process and record questions or missing steps.
    • Day 4: run the same process with the owner reviewing before completion.
    • Day 5: review the result, correct the instructions, and agree on next week's ownership.

    The first 30 days should move from review to ownership

    The point of onboarding is not permanent supervision. During week two, the virtual assistant should run the first responsibility with a defined review point. During weeks three and four, review should shift to exceptions and outcomes rather than every click. Add another responsibility only after the first one is stable. Treat the weekly milestones as an example rhythm, not a promise about when the assistant becomes independent. Ownership arrives when the work is stable, whether that is week three or month two. A useful handoff often starts with the work identified in tasks to outsource first, then grows as the assistant learns the business.

    • Week 2: run the first process, send a written update, and note every exception.
    • Week 3: take full ownership of routine cases while escalating unusual ones.
    • Week 4: review quality, turnaround, access, instructions, and the next responsibility.
    • Remove unused access and raise permissions only where completed work proves it is needed.

    A useful checklist records the handoff, not just the setup

    Onboarding is complete when both people can describe the same responsibilities, decision limits, communication rhythm, and definition of done. Keep the checklist in the project system or shared operations folder and mark each item with an owner and date. The virtual assistant should update the process notes while the work is fresh. The business owner should review those notes for accuracy, not rewrite every sentence. The accounting onboarding case study shows what that record can look like: working instructions for a finance role turned into 15 SOPs, a task inventory, and an open-questions register.

    • Scope and first responsibilities confirmed in writing.
    • Primary contact, escalation contact, and approval rules confirmed.
    • Individual accounts, multi-factor authentication, and password manager access tested.
    • Shared files, templates, past examples, and current trackers located.
    • First recurring process observed, completed with review, and documented.
    • Weekly update format and first 30-day review booked.
    • Access register and offboarding steps stored with the operating documents.

    FAQ

    Basic access and context can usually be covered in the first week. Reliable ownership develops as the assistant runs real work, meets exceptions, and improves the written instructions. The 30-day plan in this guide is an example to adapt; a wider scope or a part-time schedule takes longer, and that is normal.

    Start with the communication channel, project tracker, shared files, and the tools required for the first one or two responsibilities. Add access when the scope requires it rather than opening every account on day one.

    No, not when the platform supports individual users or delegation. Named accounts create a clear activity record, allow narrower permissions, and can be removed without changing the owner's credentials.

    The owner or current process holder explains the work and supplies examples. The virtual assistant should draft or update the instructions after running the process. The owner then confirms that the result is accurate.

    Choose a recurring task with a clear finish, enough real examples, and low risk if the first attempt needs correction. Meeting preparation, tracker updates, routine scheduling, and document formatting often work well.

    Need reliable administrative support?

    I onboard inside the tools and communication rhythm your business already uses, then take responsibility for the agreed recurring work. See Administrative Support.

    Request a free consultation

    Tell me what needs attention and which tools you use. I review enquiries personally and normally reply within one business day with the next step. Any detailed audit or implementation is scoped separately.

    Share This Article

    Comments

    Join the conversation.

    Loading comments…

    Leave a comment