Onboarding a Virtual Assistant in the First Week
By CodexierPublished 4 min read
Hiring a virtual assistant is the easy part. The first week decides whether the arrangement saves you hours or creates a new source of questions and corrections. Most problems come from the same three causes: the assistant cannot get into the systems, the tasks are described in the owner's head rather than on paper, and nobody checks in until something has gone wrong. This guide gives you a first-week plan with safe access, trial tasks, written routines, short daily check-ins and a simple measure of whether it works.
Access and tools on day one
Prepare access before the first day, so the assistant is not waiting. Use a password manager to share credentials where a shared account is unavoidable, and create personal user accounts wherever the system allows it. That way you can see who did what, and remove access in one step if the arrangement ends.
| System | How to give access | Watch out for |
|---|---|---|
| Email and calendar | Delegated access in Google Workspace or Microsoft 365 | Decide whether they may send in your name |
| Fortnox or other accounting | Own user with limited rights, for example registering but not approving | Payments and approvals stay with you |
| CRM and booking tools | Own user with the role they need | Export and delete rights |
| Shared passwords | Password manager with a shared vault | Never send passwords by email or chat |
| BankID and bank | Not shared. Payments are approved by you | Anyone asking for your BankID is a red flag |
Starting with trial tasks
Pick two or three tasks that recur, have a clear finished state and are low-risk if done imperfectly. They show how the assistant works, where your instructions are unclear and how communication flows, without risking a customer relationship.
- Sorting and labelling the inbox according to rules you write down.
- Entering supplier invoices in the accounting system for your approval.
- Updating a customer list or cleaning up duplicates in the CRM.
- Scheduling meetings using your calendar rules.
- Compiling a weekly summary of bookings or orders.
Written routines and examples
Instructions in your head do not transfer. For each task, write a short routine: what triggers it, the steps, where things are saved, what 'done' looks like and when to ask rather than guess. Add one example of a finished result. A screen recording of you doing the task once is often faster than writing and just as useful. Our guide to documenting routines before delegating has a template.
Make it clear which decisions the assistant may take alone, and which need your approval. 'Reply to booking requests using these templates, but forward complaints to me' is a rule that saves many misunderstandings.
Daily check-ins in week one
Day 1
Access check, walk-through of the trial tasks and the routines. The assistant does the first task while you are available.
Days 2–3
Ten-minute check-in: what went well, what was unclear, questions. Update the routines with each answer.
Days 4–5
The assistant works more independently. You review results rather than steps.
End of week
Short review: keep, adjust or add tasks. Agree on the rhythm for the coming weeks.
Every question the assistant asks in week one is a gap in your documentation. Answer it, then add the answer to the routine so it never has to be asked again.
Measuring whether it works
- Hours you no longer spend on the delegated tasks each week.
- Error rate: how often you need to correct something, which should fall after week two.
- Turnaround: whether tasks are done within the agreed time.
- Your own feeling: are you thinking less about the tasks, or more?
Our virtual assistant and admin support follows this onboarding plan, with hourly prices on our pricing page. When a virtual assistant is not the answer: if your tasks change every day, rely on judgement only you have, or are too rare to document, delegating costs more than it saves. Read admin tasks you should keep in-house, and book a call to check which tasks are worth handing over.
Frequently asked questions
Should I give a virtual assistant my BankID?
Never. BankID is a personal legal identity. Give the assistant their own accounts with limited rights and approve payments and signatures yourself.
How much time does onboarding take from me?
Expect a few hours in the first week: preparing access, writing routines and short daily check-ins. It shrinks quickly from week two.
Does a virtual assistant need a data processing agreement?
If they handle personal data on your behalf, such as customer details or emails, yes. It is a GDPR requirement for processors.
What if the first week goes badly?
Look at the causes: unclear routines, missing access or a poor fit. The first two are fixable; the third is a reason to change assistant early.
Ready to hand over the admin?
Book 15 minutes. Tell us which tasks eat your time, and we will tell you which to delegate first and how the first week would look.
Book a free 15-minute call