Virtual Assistant First Week Plan: What to Do on Days 1-5
Your new virtual assistant starts on Monday.
One temptation is to spend the first day explaining everything you know about the business. The other is to drop a long task list into chat and hope the important parts become obvious as they work through it.
Neither approach gives you much visibility into what the VA actually understands.
This virtual assistant first week plan uses a narrower target. By the end of the week, your VA should understand one useful responsibility, know where to ask questions, follow your communication rhythm, and have taken at least one controlled task through a complete cycle of instruction, execution, feedback, and review.
That is very different from expecting someone to be fully trained or fully productive after five days.
If you need the complete setup from pre-start preparation through later reviews, use the full virtual assistant onboarding process. There is also a broader printable onboarding checklist covering preparation, access, kickoff, the first assignment, and first-month review.
This page focuses on one thing: what to do each day during the first working week.
Before Day 1, prepare five things: one clear starting responsibility, the access needed for that responsibility, the relevant instructions or examples, a communication channel and check-in rhythm, and one person who will answer questions and review the work.
BELAY’s VA onboarding checklist takes a similar approach to pre-start preparation, including defining responsibilities, recurring work, success measures, tool access, and communication before the assistant begins.
Day 1: Give the VA Context, Access, and a Clear Starting Point
The goal of Day 1 is not to fill the VA’s calendar. It is to remove the uncertainty that would otherwise slow down the rest of the week.
Start with a kickoff call. About 30 minutes may be enough for a straightforward role, while a more complex position may need longer.
Cover the context your VA needs to understand the work:
what the business does;
where their role fits;
the first responsibility you want them to learn;
the people they may need to work with;
where tasks and source files live;
where questions should be raised;
what requires your approval;
when you expect updates.
If you and your VA work different hours, agree on useful overlap time and response expectations rather than assuming both of you will be available at the same time. The guide to working with a virtual assistant in a different time zone can help you define that rhythm.
Next, verify access.
Do not assume an invitation email means the setup is complete. Ask the VA to open the project board, shared files, email account, CRM, calendar, or other systems they genuinely need for the first responsibility.
Keep permissions proportionate to the work. Someone preparing a WordPress draft, for example, does not automatically need permission to publish it.
Finish Day 1 with something small and reviewable.
That might mean reading an SOP and listing questions, updating a sample spreadsheet row, organizing an approved folder, preparing a draft, or completing another low-risk version of the type of work they will eventually handle.
The point is to create something concrete you can discuss.
Day 1 is complete when your VA can explain:
what their first responsibility is;
where the relevant information lives;
who to ask when something is unclear;
how you expect them to communicate;
which decisions still require approval.
Day 2: Train One Core Process and Assign the First Real Task
Day 2 should move from orientation into actual work.
Choose one process that is representative of the VA’s normal responsibilities. Do not try to train five unrelated systems simply because they are all available.
A useful pattern is:
Demonstrate → Do → Review
First, show how you complete the task.
Explain the purpose, not only the clicks. Your VA should understand what starts the task, which source is authoritative, what the finished output should look like, and what should happen when something does not fit the normal process.
Then let the VA repeat part of the workflow while you are available.
Finally, give them one real assignment to complete for review.
The first task should ideally be recurring, have a visible finished result, and be low enough in risk that you can check it before it affects customers, money, publishing, or another important decision. If you are still choosing suitable work, use the guide to tasks to delegate to a virtual assistant.
Wishup’s 2026 onboarding guide similarly recommends beginning Week 1 with a clearly defined, low-stakes first task rather than handing over an uncontrolled backlog.
Give the task in writing even if you explained it during a call.
A useful first-task brief should answer:
What result do I need?
What information or file is the source of truth?
When is it due?
What does “done” mean?
What may the VA decide without asking me?
What requires approval?
What should be escalated?
The task-brief method for giving clear VA instructions goes deeper into those fields.
Set the review for Day 3 before you finish.
Day 2 is complete when your VA has one genuine task with a defined result and knows exactly how that work will be reviewed.
Day 3: Let the VA Do the Work, Then Give Specific Feedback
Day 3 is where you learn whether your instructions actually work.
Let your VA complete the first real task with less step-by-step guidance. Stay available for genuine questions, but avoid directing every action.
Then review the output itself.
“Looks good” is not enough feedback.
“Do it again” is not enough either.
Useful feedback separates three things:
Keep: what was done correctly and should become the normal approach.
Change: what needs to be different next time.
Clarify: what was unclear because the instruction, example, or process was incomplete.
That final category matters.
If the VA made a reasonable decision because your instructions left two possible interpretations, fixing only the output does not fix the process. Update the instruction so the same uncertainty is less likely to appear again.
Give important corrections in writing so both of you have something to refer back to.
If the first task went well, you can add a second closely related responsibility.
If it did not, repeat the task or retrain the unclear part. Do not expand the workload merely because the calendar says Wednesday.
Day 3 is complete when the VA has received specific feedback on real work and both of you know what should stay the same or change next time.
Day 4: Reduce the Hand-Holding and Establish the Update Rhythm
By Day 4, the VA should have enough context to handle familiar work with more independence.
That does not mean disappearing for the day.
It means moving from constant direction to predictable checkpoints.
Give the VA a normal block of work based on the process already introduced. Let them use the documentation, task board, source files, and feedback from earlier in the week before coming back to you.
You should still be available for exceptions.
This is also a good point to establish a short end-of-day update.
Keep it simple:
Completed: What was finished today?
Blocked: What could not move forward, and why?
Next: What is expected to continue tomorrow?
An update like this gives you visibility without requiring another meeting simply to ask for status.
Check whether the VA is also updating the systems that are meant to hold the work. A message saying “finished” does not help much if the project board still shows the task as in progress or the final file is stored somewhere nobody can find.
If everything is moving smoothly, you may introduce another routine process. If the first responsibility is still unstable, keep working on that instead.
Day 4 is complete when familiar work can move forward without constant prompting and the VA can report progress and blockers clearly.
Day 5: Review the Week and Decide What Is Ready for Week 2
Day 5 is not a final exam.
It is your first useful review point.
Where possible, let the VA take the week’s core task from its normal trigger through to the agreed finished result. You can still keep approval over publishing, sending, payment, or another important final action.
Then hold a short end-of-week review.
Fifteen to 30 minutes may be enough for a simple role.
Discuss five questions:
Which work can the VA now repeat using the current instructions?
Which part still requires close review?
Which questions came up more than once?
Is any missing access, context, or documentation slowing the work?
What should the VA focus on next week?
Do not add responsibilities only because five days have passed.
If one process still needs practice, the sensible Week 2 plan may be to repeat it with better instructions rather than introducing something new.
If the first process is stable, add the next responsibility in a controlled way.
A five-day onboarding framework from Outsourced Scale follows a similar progression from business and tool orientation through role training, observation, supervised execution, and an end-of-week debrief.
The useful idea is the progression, not the calendar deadline.
Day 5 is complete when you and your VA agree on what can continue, what still needs review, and what comes next.
Your Virtual Assistant First Week Plan at a Glance
| Day | Main focus | A useful exit check |
|---|---|---|
| Day 1 | Context, access, communication | The VA understands the first responsibility, tools, contacts, and approval boundaries |
| Day 2 | Process training and first real task | The VA has one clearly briefed task to complete |
| Day 3 | Supervised execution and feedback | Real work has been reviewed and the instructions have been corrected where needed |
| Day 4 | More independent execution | Familiar work can move with less prompting and the VA sends a useful status update |
| Day 5 | End-of-week review | You know what can continue into Week 2 and what still requires training |
A one-page printable 5-Day VA Onboarding Checklist accompanies this article. It contains the same daily sequence in a format you can keep beside your task board or share with whoever is managing the VA’s first week.
What If Your VA Is Not Ready for the Next Step?
Slow the sequence down.
Five days is a useful planning structure. It is not evidence that someone is ready for more responsibility.
If access is still broken on Day 2, fix access before adding more work.
If the first task exposes missing instructions on Day 3, improve the instructions and repeat the task.
If the role involves several clients, complex systems, sensitive communication, or specialist work, your VA may need more observation and review before working independently.
The calendar should help you organize onboarding. It should not override what the work is showing you.
A better question at the end of each day is:
“What can this person now do reliably within the process we have actually trained?”
That gives you a much better basis for deciding what comes next.
Turn the First Week Into a Repeatable Working Relationship
A useful first week does not end with your VA knowing everything.
It ends with less uncertainty.
One responsibility has been explained. Access works. The VA knows where the source information lives. A real task has been completed and reviewed. Feedback has improved the process. Communication has a predictable rhythm. Both of you know what should happen next.
That is enough progress to build on.
At Boost VA, I support founders, agencies, and online businesses with recurring execution across research, data handling, WordPress, outreach, reporting, content operations, and administrative work. If you already know what you want to take off your plate and need reliable support to keep it moving, explore the virtual assistant support available through Boost VA and tell me what you need help with.
