How to Onboard a Virtual Assistant in Week One (SOP + Checklist)
A day-by-day week-one plan, a copy-paste SOP template and a 25-point checklist for onboarding a virtual assistant.
Joshua is an SEO and digital marketing specialist at Nomad VAs, where he manages local and national SEO, on-page optimization and content, and writes on delegation and remote hiring.
Most VA relationships do not fail in month three. They stall in week one, when logins are missing, instructions live in one person's head and nobody has defined what a good first task looks like. This guide gives you a day-by-day plan, a copy-paste SOP template and a 25-point checklist. It draws on published onboarding research and on what we see at Nomad VAs, including first-party data you can cite.
Key takeaways
- Week one is a five-day sequence: access, SOPs, first task, feedback, retrospective.
- At Nomad VAs, the most common cause of a rough week one is missing tool access, not skill.
- Record first and document second. Three SOPs on day 2 are enough to start.
- Share logins through a password manager with multifactor authentication, never by chat or email.
- Judge week one by outcomes: zero open access blockers and one client-accepted task.
Why does week one decide whether a virtual assistant works out?
Because the first days set expectations, tools and trust, and those are hard to reset later. Gallup reports that only 12% of U.S. employees say their company does a good job of onboarding, and that only 29% of new hires feel fully prepared and supported after onboarding. SHRM notes that new hires get roughly 90 days to prove themselves, and that structured onboarding is linked to better retention. Read the Gallup report.
These studies measure employees, not contractors. The mechanism still applies. A remote VA in another time zone has fewer chances to ask a quick question, so unclear instructions and missing access cost more days than they would in an office.
Table 1: What onboarding research says and what it means for a VA
| Finding | Source | What it means for your VA |
|---|---|---|
| Only 12% of U.S. employees say their company does a good job of onboarding | Gallup | Most onboarding is weak by default, so a written week one is a real advantage. |
| Only 29% of new hires feel fully prepared and supported after onboarding | Gallup | Preparation, not talent, is the usual gap. Give context, not only tasks. |
| Employees are 3.4 times as likely to call onboarding successful when their manager takes an active role | Gallup | You set the quality of week one. Block time for the kickoff and check-ins. |
| New employees take around 12 months to reach peak performance | Gallup | Week one is a start, not a finish. Plan weeks two to four too. |
| Structured onboarding is linked to 58% higher odds of staying three years | SHRM | Written structure pays off in retention, even for a contractor. |
What should you prepare before day 1?
Do four things before your VA starts. Write a one-page scope with three outcomes for the first 30 days. List every tool and permission. Pick the first task. Block your calendar for the kickoff call and the day 5 retrospective. If you want a head start on the scope, the free SOP and job description generator builds a role outline in minutes, and our guide on how to vet a virtual assistant explains how to confirm the person is ready before they start. Not sure you need one yet? Start with seven signs it is time to hire your first VA.
How should you set up access?
Give the lowest level of access that lets the VA do the job, and share it through a manager rather than by message. CISA explains that multifactor authentication stops an attacker who has stolen one factor, such as a password, from meeting the second requirement. Credentials also remain a live risk: Verizon's 2026 breach report, as covered by Help Net Security, found that stolen credentials still feed ransomware and are packaged and sold by access brokers.
You own the accounts. Your VA works inside them.
Tap a level for who should hold it.
Use role-based seats and a shared vault with multifactor authentication so you can change or remove access at any time
Figure 1: Who holds which access in week one.
Table 2: Week-one access setup by tool
| Tool | Access to grant | Safest way to share | Done when |
|---|---|---|---|
| Google Workspace (Drive, Docs, Sheets) | Edit on named folders only | Share folders to the VA's own account | VA edits a test file |
| Slack | Member of one shared channel | Invite to a dedicated channel | VA posts the day 1 recap |
| Password manager (1Password or Bitwarden) | One shared vault for needed logins | Vault sharing with MFA switched on | VA signs in with MFA |
| Asana or Trello | Member of one project or board | Invite to the specific board | VA moves a card |
| Loom | Shared folder for SOP videos | Share the folder, not your account | VA records a 2-minute clip |
| Role tool (CRM, ad account, CMS, helpdesk) | Lowest role that does the job | Role-based seat or delegate access | VA completes a harmless test action |
For deeper guidance, see password and access management for delegation and social media account security . Read the official CISA guidance on multifactor authentication before you set policies.
What does the day-by-day week-one plan look like?
The plan below moves from access to a real, accepted task in five working days. Each day has one goal and one clear finish line, so you always know whether week one is on track.
Five days from access to an accepted task
Tap a day for what you do and what done looks like.
Access and kickoff
Logins shared, kickoff held.
Record three SOPs
Three one-page SOPs approved.
First real task
One small task, delivered.
Review and feedback
Reviewed within 24 hours.
Retrospective
Week two planned.
Tap a card for detail.
Figure 2: The week-one plan, day by day.
Table 3: The week-one plan at a glance
| Day | Goal | You do | Your VA does | Done when |
|---|---|---|---|---|
| 1 | Access and context | Share logins, run the kickoff, post a recap | Confirms every login, asks questions | Zero open access blockers |
| 2 | SOPs and standards | Record three recurring tasks | Drafts three one-page SOPs | Three SOPs approved |
| 3 | First real task | Write a short brief | Repeats it back, then delivers | Task submitted |
| 4 | Feedback | Review within 24 hours | Revises work and updates the SOP | Task accepted |
| 5 | Retrospective | Run a 30 minute review | Reports blockers and ideas | Week-two plan agreed |
Day 1: Access and kickoff
Send access through your password manager before the call and ask the VA to confirm each login by the end of the day. Hold a 30 to 45 minute kickoff. Cover the business in five minutes, the three 30-day outcomes, where to ask questions, expected response times and working hours. Post a written recap in Slack so the decisions are searchable later.
Day 2: Record and write three SOPs
Screen-record yourself doing three recurring tasks, then have the VA turn each recording into a one-page SOP. This record-then-document method is faster than writing from memory and captures the small decisions you make without noticing. Our guide to creating SOPs for your virtual assistant goes deeper.
Day 3: Assign one small, real task
Choose a task that takes 60 to 90 minutes, carries low risk and has an obvious finish line. Write a brief with the goal, inputs, output format and deadline. Ask the VA to repeat the task back in their own words before they start. If the brief needs structure, borrow the format from how to brief a content writer.
Day 4: Review and give structured feedback
Review within 24 hours and give feedback in three parts: what to keep, what to change and why. Gallup links active manager involvement to much better onboarding ratings, and fast feedback is the simplest form of involvement. Ask the VA to update the SOP wherever the task exposed a gap.
Day 5: Retrospective and week-two plan
Spend 30 minutes on three questions: what worked, what blocked progress and what should change. Close any remaining access gaps, agree the week-two tasks and set a check-in rhythm. Then decide how to split the next 25 days using the delegation matrix and the filter in the founder's guide to delegation.
What should an SOP for a virtual assistant include?
A good SOP answers one question: could a capable stranger complete this task correctly using only this page? Keep each SOP to one page, written by the VA from your recording and approved by you. The free SOP and JD Generator gives you a starting structure. In its first three months, the tool produced around 25 or more SOPs, mainly for SEO, social media and content writer tasks.
SOP TEMPLATE (copy and paste) Title: Purpose (one sentence): Owner (who approves changes): Trigger (when is this done?): Tools and access needed: Steps (numbered, one action each): 1. 2. 3. Quality check (how do we know it is right?): Example of a good result (link): Common mistakes: Escalate to (name) when: Last updated and by whom:
What is the week-one checklist?
Use this 25-point checklist as your tracking sheet. Five items per day keeps the workload realistic for both of you.
WEEK-ONE CHECKLIST (copy and paste) DAY 1: ACCESS AND KICKOFF [ ] Scope page with three 30-day outcomes shared [ ] Password manager vault shared, MFA on [ ] Slack channel, Drive folders and board access granted [ ] Kickoff call held (30 to 45 minutes) [ ] Written recap posted in Slack DAY 2: SOPS [ ] Three recurring tasks screen-recorded [ ] Three SOP drafts written by the VA [ ] SOPs reviewed and approved [ ] SOPs stored in one shared folder [ ] Escalation rules written down DAY 3: FIRST TASK [ ] Task chosen (60 to 90 minutes, low risk) [ ] Brief written with goal, inputs, output, deadline [ ] VA repeats the task back [ ] Task delivered [ ] Questions logged for the SOPs DAY 4: FEEDBACK [ ] Review done within 24 hours [ ] Feedback given as keep, change, why [ ] Revisions delivered [ ] Task accepted [ ] SOP updated with what was learned DAY 5: RETROSPECTIVE [ ] Retrospective held (30 minutes) [ ] All access blockers closed [ ] Week-two tasks agreed [ ] Check-in rhythm set [ ] Decision made to continue, adjust or stop
What does Nomad VAs data show about week one?
The table below summarizes first-party observations from Nomad VAs. They are practical benchmarks from a small sample, not a formal study, and are labeled with their basis so you can cite them accurately.
Table 4: Nomad VAs first-party week-one data (October 2026)
| Metric | Finding | Basis |
|---|---|---|
| First client-accepted task | Typically within 1 to 2 days of starting | Observation across fewer than 10 recent Nomad VAs onboardings |
| Most common week-one problem | Missing tool access | Nomad VAs onboarding experience |
| What week one includes | Kickoff call, shared Slack channel, scheduled check-ins and paid trial hours | Nomad VAs process, which follows our four-stage vetting |
| SOPs generated | Around 25 or more in the first three months, mainly SEO, social media and content writer tasks | Nomad VAs SOP and JD Generator |
What goes wrong in week one, and how do you fix it?
Most week-one problems fall into six patterns. Fixing them early costs minutes. Fixing them in week three costs weeks. Our article on the most common first-VA mistakes covers the longer-term ones.
The same week with and without a plan
Tap a row to compare. The right column is the fix.
Tap a row to compare.
Figure 3: Week one with and without a plan.
Table 5: Common week-one problems and fixes
| Problem | What you see | Fix |
|---|---|---|
| Missing access | VA waits for logins, idle days | Use the access table and confirm every login on day 1 |
| Vague instructions | Work that misses the point | Use a brief with goal, inputs, output and deadline |
| No SOPs | Repeated questions | Record first, write three SOPs on day 2 |
| Overload | Many tasks, none finished | One real task in week one |
| No feedback loop | Same mistakes repeat | Review within 24 hours using keep, change, why |
| Time zone gaps | Slow answers | Overlap on days 1 and 5, written handoffs between |
How does week one change by VA role?
The five-day sequence stays the same, but the first task and the access list change. Use the table to pick a sensible first task, then adapt the plan for your role. Dedicated 30-day plans for each role are on the way .
Table 6: First task and access by VA role
| Role | Good first task | Access to prepare |
|---|---|---|
| SEO VA | Keyword gap pull for one section | Search Console, analytics, CMS editor, rank tracker |
| Social Media VA | One week of captions from existing pillars | Page roles, scheduler, brand kit |
| Customer Service VA | Ten tickets in shadow mode with macros | Helpdesk seat, macro library, knowledge base |
| Executive VA | One day of inbox triage with a daily brief | Delegate access to mail and calendar |
| Content Writer | Outline from a written brief | CMS draft access, style guide |
How do time zones change week one?
Plan live time for days 1 and 5, and rely on written handoffs in between. For a Philippines-based VA, the gap depends on the client region and shifts when clocks change. The Philippines does not observe daylight saving time.
Table 7: Overlap planning by client region (relative to Manila time)
| Client region | Typical gap | Kickoff approach |
|---|---|---|
| US East Coast | Manila is 12 to 13 hours ahead | Kickoff at the end of your day, such as 8:00 pm in New York, which is 8:00 am next day in Manila during US daylight time |
| US West Coast | Manila is 15 to 16 hours ahead | Kickoff at 5:00 pm Pacific during US daylight time, which is 8:00 am in Manila |
| UK and Europe | UK is 7 to 8 hours behind; central Europe 6 to 7 | Morning kickoff, such as 8:00 am in London during British Summer Time, which is 3:00 pm in Manila |
| Australia and New Zealand | Sydney is 2 to 3 hours ahead; Auckland 4 to 5 | Near-full overlap, so hold live check-ins daily |
How do you know week one worked?
Judge week one by outcomes, not by hours logged. The targets below are editorial rules of thumb from our own practice, not industry benchmarks.
What good looks like by Friday
Editorial rules of thumb from Nomad VAs practice, not industry benchmarks.
Figure 4: The week-one scorecard.
Table 8: Week-one success measures
| Measure | Target by Friday | How to check |
|---|---|---|
| Open access blockers | 0 | Ask the VA to list any tool they cannot open |
| Client-accepted tasks | At least 1 | Your review on day 4 |
| SOPs approved | 3 | Shared SOP folder |
| Revision rounds on the first task | 2 or fewer | Task thread |
| VA can state the three 30-day outcomes | Yes | Ask on day 5 |
What happens after week one?
Treat week one as the start of a 30-day plan. Use week two to add one new task type, week three to run a task end to end without your input and week four to review results and hours. To decide what to hand over next, read how much time a VA can save you and run your own numbers in the Founder Time Calculator. When you are ready to add roles, browse the roles.
Book a Discovery Call Generate SOPs and JDs free
Frequently asked questions
How do I onboard a virtual assistant in week one?
Share access through a password manager on day 1 and hold a kickoff call. Record and write three SOPs on day 2. Assign one small real task on day 3, review it on day 4 and run a retrospective on day 5. The goal is one client-accepted task by the end of the week.
What access does a virtual assistant need on day 1?
Give the lowest level of access that lets the VA do the job: specific shared folders, a dedicated Slack channel, a shared password-manager vault, one project board and a role-based seat in each work tool. Turn on multifactor authentication and avoid sharing owner or admin logins.
How long does it take a VA to become productive?
A VA can deliver a first accepted task within days when access, SOPs and a clear brief are ready. At Nomad VAs, the first client-accepted task typically lands within 1 to 2 days in a small sample of fewer than 10 recent onboardings. Gallup notes that employees take around 12 months to reach full performance, so week one is a start, not a finish.
Do I need SOPs before I hire a VA?
No. Record first and document second. Screen-record three recurring tasks while you do them, then turn each recording into a one-page SOP with the VA on day 2. Starting with three SOPs is enough, and the VA can improve them as they work.
Should week one be a paid trial?
Yes. Paying for trial hours keeps the test fair and gives you a real working sample of the VA's output and communication. At Nomad VAs, paid trial hours are part of how week one runs, alongside a kickoff call, a shared Slack channel and scheduled check-ins.
What should I avoid sharing with a new VA?
Avoid sharing owner or admin logins, banking details, card numbers and personal accounts. Use role-based seats, delegate access and a shared password-manager vault with multifactor authentication so you can change or remove access at any time.
Sources
- Gallup: Onboarding new employees in the remote work era (12%, 29%, 3.4 times, 12 months)
- SHRM: Don't underestimate the importance of good onboarding (58% more likely to stay three years, 90 days)
- CISA: Multifactor authentication
- Help Net Security: Verizon 2026 DBIR findings
- First-party data: onboarding observations and SOP and JD Generator usage, October 2026. These are practical benchmarks from a small sample, not a formal study.