The month after you hire a virtual assistant is where the placement is won or lost, in our view. Problems that look like a question of ability often turn out to be a handover that never quite happened: context that stayed in someone’s head, access that was never granted, a task explained once and taken back the moment it came back imperfect.
This guide sets out a first month, week by week, and the failures we would plan against. It is our recommended approach, not research, and it is written to suit any business.
What does onboarding a virtual assistant involve?
Onboarding is the transfer of context, access and ownership, in that order. The assistant brings the skills. What they lack is your inbox conventions, your client history and your reasons for doing things your way.
With a managed service, the provider handles recruitment, onboarding and payroll, you direct the daily work, and the provider owns the employment relationship, according to our FAQ. That leaves the part only you can do: explaining the work and then letting go of it. You are briefing a professional who needs your specifics, not training someone from scratch.
Four failures to plan against
- Access arrives late. The assistant starts on Monday and spends days waiting for an email address, a CRM login and drive permissions, so the work starts slowly.
- Context is never transferred. The task is explained but the reasoning is not, so the assistant follows the instruction literally, meets a case it did not cover, and guesses.
- The handover is never completed. You delegate, review the output, find it mostly right, fix the rest yourself, and quietly keep doing that.
- Feedback is saved up. Small corrections go unmentioned, then arrive together in week three as a verdict instead of coaching.
All four are process problems, so you can fix them in week one.
Week 1: set up, shadow, and write nothing down twice
The goal of week one is not output. It is that by Friday the assistant can describe your business to someone else without you in the room.
Before day one, have ready:
- An email address, calendar access, and whatever your team uses to talk to each other.
- Logins for every system the role touches, with the permission level already decided.
- A password manager entry instead of credentials sent over chat.
- A named point of contact: one person who answers questions.
Our FAQ recommends granting the minimum each task needs, using the permission levels your tools already have, and agreeing confidentiality terms in writing during scoping.
During the week, walk through the actual work, not a job description. If the role is inbox and calendar management, sit with the inbox and talk through how you triage it: which senders matter, which meetings you protect, what you never want booked before 10am and why.
Record those sessions. A short screen recording of you working through a real morning means the explanation exists once instead of being repeated in week three.
Ask the assistant to write the documentation as they learn. Someone meeting the process for the first time tends to notice which steps are not obvious, and you review what they write instead of authoring it.
If you are still deciding what to hand over, work through the task list before the assistant starts.
Week 2: shadowing becomes owning
By week two the assistant should own something small and complete, with you reviewing instead of doing.
Pick a task with a clear boundary and a low cost of error: inbox triage without sending, calendar coordination for internal meetings, updating records after a call. You should be able to check the work in five minutes, and a mistake should be recoverable.
Review daily this week, briefly. A ten-minute call at the same time each day lets corrections land while the work is fresh. This is also the week to say the small things. A correction about the tone of a reply reads as training in week two and as a complaint in week four.
Weeks 3 and 4: hand over a full process
By the end of the month, aim to have one complete process running without you in the loop. Not every process. One.
Choose something that recurs: a weekly report, booking confirmations, follow-ups after enquiries. Pick something you can judge by whether it happened and whether anyone complained, so you do not need to inspect each instance.
Then move from checking the work to reviewing exceptions: what came up that the process did not cover, and what the rule should be next time. That conversation is how the process improves.
Agree the working window at scoping instead of discovering it now. According to our FAQ, you specify the window and the assistant is staffed to it.
The 30-day checkpoint
At the end of the month, ask whether the handover worked, not whether the assistant is good.
| By day 30 | Healthy | Needs attention |
|---|---|---|
| Access | Everything granted, nothing pending | Still waiting on a system login |
| Questions | Fewer than in week one, and more specific | The same questions recurring, or none at all |
| Ownership | One process runs without you | You are still reviewing every item |
| Documentation | Written by the assistant, reviewed by you | Still in your head |
| Your time | Measurably less spent on the delegated work | Unchanged, or worse |
| Corrections | Given the same day and decreasing | Saved up, or avoided |
An assistant who has stopped asking questions may have started guessing, so treat “none at all” as a prompt to check in. If your own time has not moved by day 30, look first at whether the work was handed over but the responsibility was not.
What if it is not working?
Say so early, and raise it with your provider. In a managed arrangement, our managed vs marketplace guide explains that if the VA is not a fit, the provider handles the replacement.
Before you raise it, separate two problems, because they have different fixes. A skills mismatch means the assistant cannot do the work, and a replacement is the answer. A handover failure means the work never properly reached them, and a replacement will reproduce the same result with a different person.
What you still own with a managed service
According to our managed vs marketplace guide, a managed provider stays responsible for HR, payroll and performance. Three things stay with you.
- Context: why the work matters, which clients are sensitive, and what a good outcome looks like.
- Decisions: what gets priority when two things conflict. An assistant can follow a rule you set. Setting it is your job.
- Feedback: nobody else can tell your assistant that a reply was not quite right for your client.
Where DesertVA fits
We recruit, screen and evaluate candidates, you interview and choose, and the assistant starts supporting your business within days while we handle management, payroll and ongoing support, as described on our home page. Our FAQ says placement is usually measured in days rather than the weeks or months a local hire takes, because candidates are pre-screened before you are introduced.
The context transfer is still a conversation between you and the person doing your work. If you have not hired yet, start with how to hire a virtual assistant in Dubai. If you have, and you are not sure what to hand over first, work through the tasks worth delegating.
Frequently asked questions
How long does onboarding a virtual assistant take?
Plan for a month to reach one process running independently. Useful output often starts in week two, and full ownership of a recurring process by the end of week four is a reasonable target for a generalist admin support role. Roles with more business-specific context may take longer.
Should I write procedures before the assistant starts?
We suggest not. Have the assistant write them during week one while they are learning, and review what they produce.
How much of my own time should onboarding take?
Expect to spend real time in week one, concentrated in walkthroughs. Week two is mostly short daily reviews. By week four the time should be less than the work used to take you. If it is not falling, something in the handover has stalled.
What access should I give a virtual assistant?
Only what the role requires, granted through a password manager and not shared credentials. Our FAQ says an assistant works inside the accounts and tools you grant and nothing beyond them, so you can narrow or revoke the boundary at any point. Have it ready before day one.
What if the assistant is not the right fit after a month?
Raise it immediately with your provider, and first check whether the problem is a skills mismatch or a handover that never completed. See the section above for how the two differ.
Sources and methodology
Researched and written: October 2026. Next review due: April 2027.
| Claim | Source |
|---|---|
| The provider handles recruitment, onboarding and payroll; you direct the daily work; the provider owns the employment relationship. Placement usually measured in days because candidates are pre-screened. Assistants work inside the accounts and tools you grant; minimum access and written confidentiality terms agreed at scoping. You specify the working window and the assistant is staffed to it. | DesertVA FAQ |
| A managed provider stays responsible for HR, payroll and performance; the provider handles the replacement if the VA is not a fit. | DesertVA managed vs marketplace guide |
| The four-step process: we recruit and screen, you interview and choose, the assistant starts within days, we handle management, payroll and ongoing support. | DesertVA home page |
The week-by-week plan, the four failures, the checkpoint table and the time estimates are our recommendations, not published research, and no performance figures or client outcomes are cited.