You hired for time back, and now you're managing.
Three weeks in, you're spending your mornings explaining tasks, re-explaining them, and quietly redoing what came back wrong. That's usually not a bad hire. It's onboarding that got skipped or crammed into a day. Onboarding a virtual assistant well means getting tool access ready before they log in, handing over real context about how your business runs, documenting the first few tasks with the output you actually want, naming one point of contact, and calibrating over a few weeks rather than expecting full speed on day two. Do that and the assistant takes work off your plate. Skip it and you've just added a second job: managing the person you hired to save you time.
Get this ready before they log in.
Most of the friction in the first week traces back to prep that didn't happen. Handle it in one batch, not as a trickle of access requests over the next two weeks.
- Access, all of it, in advance. Company email, your messaging tool (Slack or Teams), the project board (Asana, ClickUp, Notion, whatever you run on), shared drives, and any specific software the role touches. Nothing kills a first day faster than an assistant sitting idle waiting to be added to a tool.
- A password manager, not a plain-text list. Set up shared logins through something like 1Password, Bitwarden, or LastPass so you can hand over access to accounts without emailing raw credentials, and revoke it cleanly later. This is also the honest answer to the trust question: you control what they can reach and can pull it back in seconds.
- The first two or three tasks, written down. Not a vague "help with admin." Name the task, the expected output, where finished work goes, and roughly how long it should take. Written direction on day one beats a live call you'll both half-remember.
- A short welcome recording. Five minutes on Loom walking through who you are, what the business does, and who the key people are gives more context than a page of text and costs you almost nothing to make.
- One point of contact. Decide who the assistant reports to and asks questions of. When three people hand a new VA work with no coordination, nothing gets prioritized and everything feels urgent.
Day one is orientation, not output.
The first day isn't a working day, and treating it like one is the most common early mistake. It's an orientation day: the assistant gets into every tool, reads the context you prepared, and asks every question now so they're not stuck mid-task on Thursday. Expecting billable output on day one is how you end up with rushed, wrong work you have to unwind.
From there, go slow on purpose. Days two and three, hand over one real task, something low-stakes with a clear right answer, and let them do it end to end. One task done well is a successful first week. The goal isn't maximum throughput, it's calibration: you're learning how they work and they're learning what "done" looks like to you. Add a second recurring task only once the first is clearly handled. Piling on five tasks in week one feels productive and reliably backfires, because you've given yourself five things to correct at once instead of one thing to get right.
Check in daily for those first five working days. It takes ten minutes, usually an end-of-day note covering what got done, what's blocked, and what's next, and it catches drift before it becomes a week of misaligned work. As proficiency grows, that daily rhythm loosens to a couple of times a week, then a weekly recap. The cadence is supposed to shrink. If you're still doing daily hand-holding in month two, something in the documentation or the task fit is off.
What actually makes it stick.
Strip away the day-by-day and onboarding comes down to four things you're really setting up. Get these right and the timeline mostly takes care of itself.
SOPs for anything recurring
A standard operating procedure is just a short doc: what triggers the task, the steps in order, what the finished output looks like, and where it gets saved. Write the first ones together as the assistant does the task, or have them draft it and you correct it. Once a task has an SOP, it stops living only in your head and can move to anyone on the team without you re-explaining it.
Communication norms, written
Which channel for what, how fast you expect a reply, what they should flag versus decide on their own, and what an update should contain. Ambiguity here is where remote work quietly goes wrong. Spell out that blockers get raised within a couple of hours rather than sat on until the end-of-day note, and you've removed most of the guesswork.
A single point of contact
One person owns the relationship, sets priorities, and answers questions. This matters more the more people the assistant supports. Without it, work arrives from every direction with no sense of what comes first, and the assistant burns their hours guessing at your priorities instead of executing them.
Feedback, early and specific
Correct the small things in week one while they're cheap to fix. "Put the summary at the top, not the bottom" on day three saves you from silently redoing that summary for a month. Praise what's right just as plainly. The whole point of the early check-ins is to make correction routine and low-drama, not a performance review that arrives too late to matter.
Most onboarding failures aren't the assistant underperforming. They're the business not being ready to hand work over.
Start narrow, then widen.
The instinct is to offload whatever's annoying you most that week, which is usually the worst first task because it's the one buried in context only you have. Start instead with something recurring, rules-based, and low-stakes: inbox triage against clear criteria, calendar scheduling, data entry, formatting documents, chasing invoices, publishing content you've already written. Tasks where "right" is unambiguous, so calibration is fast and a mistake costs almost nothing.
Higher-judgment work, drafting in your voice, handling a sensitive client, owning a project end to end, comes later, once the assistant has enough context to make the calls you'd make. Trying to delegate judgment before you've delegated the mechanical stuff is how people conclude "this doesn't work for my business" when what actually happened is they handed over the hardest thing first. Widen the scope as trust builds, not before.
The overhead has to live somewhere.
Everything above, the SOPs, the norms, the check-ins, the being-the-point-of-contact, is real work. The honest question isn't whether onboarding takes effort. It's who does that coordinating, and that answer differs a lot depending on how you've hired.
A solo virtual assistant
Lowest cost for one narrow task, and you are the manager.
- ✓ Cheapest option for a single recurring task and a direct one-to-one working relationship
- ✓ One person who learns your preferences deeply over time
- × You write the SOPs, set priorities, run the check-ins, and do the quality control yourself
- × One skill set, and when they're sick or leave, the work and the onboarding start over with you
A managed team with a PM
The coordination layer is part of what you're buying.
- ✓ A project manager coordinates your team and handles delegation, so you hand off the managing, not just the tasks
- ✓ Access to specialists across admin, web, design, and content instead of one fixed skill set
- ✓ Work doesn't stall when one person is out, and hours can shift across functions as your priorities move
- × You still hand over context up front, and it's a recurring commitment, not the cheapest route for one tiny task
This is where a flexible-team model like Lil Assistance is worth a look if the managing is the part draining you. You submit tasks to a project manager who assigns them across a team of specialists and coordinates the handoffs, which absorbs a lot of the delegation and quality-control overhead that makes a solo VA feel like more work rather than less. Every plan includes a project manager who coordinates your team, though that manager handles several clients rather than working with you exclusively, so confirm what coordination comes with the plan you're considering rather than assuming it. Pricing is a flat weekly rate by hours (a one-time setup fee applies per worker), so if cost is your deciding factor, the current figures on the plans and pricing page are the honest place to compare against a fully-loaded hire. It isn't magic: you still have to hand over context and build the first SOPs. It just means you're not also the one routing every task and chasing every handoff.
How to know it worked.
Give it about 30 days before you judge it, and judge it against calibration, not raw volume. A healthy sign at the month mark: a few recurring tasks the assistant runs without you re-checking each one, two or three tasks that now have written SOPs, updates arriving without you having to ask, and noticeably fewer interruptions to your day. You should feel the shift from "I have to explain this" to "this just gets handled."
If none of that has happened, resist blaming the hire first. Look at whether the tasks had clear outputs, whether the SOPs existed, whether one person owned the relationship, and whether you actually ran the early check-ins or let them slide. Fix those and it usually turns around. If the fundamentals were solid and it still isn't working, then it's a fit problem, and the earlier calibration approach means you'll know that in weeks rather than after half a year of frustration.
How do you onboard a virtual assistant?
Prepare tool access and the first tasks before day one, use the first day for orientation rather than output, hand over one clear task at a time, set written communication norms and a single point of contact, document recurring work as SOPs, and check in daily for the first week before easing to weekly. Judge results at around 30 days on calibration, not volume.
What should you do before your virtual assistant starts?
Set up every tool and account they'll need in one batch, share logins through a password manager rather than plain text, write down the first two or three tasks with their expected outputs, record a short welcome and context video, and decide who their single point of contact is. Prep that doesn't happen before day one becomes friction in week one.
How long does it take to onboard a virtual assistant?
Plan for roughly 30 days to reach a steady rhythm, not a single day. The first week is orientation and one or two tasks, the following weeks add recurring work and SOPs, and by around the 30-day mark a well-onboarded assistant is running several tasks without close supervision. Rushing the timeline is the main reason people conclude delegation "doesn't work."
What should I delegate to a virtual assistant first?
Start with recurring, rules-based, low-stakes work where "right" is unambiguous: inbox triage against set criteria, scheduling, data entry, document formatting, invoice chasing, or publishing content you've already written. Save higher-judgment work like drafting in your voice or owning a project until the assistant has enough context. Handing over the hardest, most context-heavy task first is a common and avoidable mistake.
Do I have to manage a virtual assistant myself?
With a solo freelance VA, yes: you set priorities, write the SOPs, and handle quality control. With a managed team model, a project manager coordinates your team and takes on much of that overhead, so you're delegating the management rather than just the tasks. You still have to hand over context either way, but the ongoing routing and follow-up can sit with someone else.
Onboard once, get the time back for good.
If the managing is the part you'd rather not own, see how a project manager and a flexible team handle the delegation for you.