A useful handover gives a virtual assistant enough context to move a task forward and enough boundaries to know when to ask. You do not need to document your entire business before you begin. Start with one recurring administrative workflow and make its next steps clear.
This guide walks through a practical first handover: choosing the task, describing the outcome, sharing the process and agreeing how you will review the work. Adapt it to your team, systems and responsibilities.
1. Choose one task with a clear finish
Pick something you can explain, demonstrate and check. Examples include preparing a meeting agenda, organizing incoming appointment requests or updating a follow-up tracker. “Help with administration” is a starting conversation; it is too broad to use as a working instruction.
Write down the trigger, the expected output and the deadline. For example: “When a meeting is confirmed, collect the agenda items, prepare the agenda in our shared folder and send it to me for approval one working day before the meeting.” Keep the first assignment small enough to review together.
2. Explain what a good result looks like
Describe how the finished task will be used. An accurate spreadsheet, a draft email and a confirmed appointment each have different acceptance criteria. Include the details that matter: required fields, naming conventions, tone, date format or the person who must approve the result.
An anonymized example can make your expectations easier to understand. Mark any outdated details and explain which parts should be followed. If there is no example, create a simple checklist with the assistant rather than expecting them to infer every preference.
3. Capture the steps, including exceptions
A short written process is often enough. List the steps in the order they happen and link to the current templates or reference material. A screen recording can help explain a complicated system, but keep the written summary easy to scan when someone is doing the work.
Include the points where routine processing stops. What happens if information is missing, two appointments conflict or a request is outside the agreed scope? Name the person to contact and the channel to use. Do not turn an unresolved decision into a hidden assumption inside the process.
4. Agree access and decision boundaries
List the tools needed for this task and arrange access through your organization’s approved method. Use individual accounts and the level of access appropriate to the agreed work where your systems support it. Keep passwords out of handover documents and ordinary email threads.
Separate actions the assistant may complete from actions requiring your approval. For example, drafting a reply may be delegated while sending it remains with you. Set clear boundaries around spending, changes to records and external commitments. Any industry-specific responsibilities should follow the team’s established procedures and qualified supervision.
5. Decide how updates and questions will work
Agree where tasks live so instructions do not become scattered across inboxes and chat messages. A shared task list can show the owner, due date, current status and next action. Choose a communication rhythm that fits the work rather than assuming constant availability.
Define what should be raised immediately and what can wait for the next check-in. A concise question is easier to answer when it includes the task, the issue, what has already been checked and the decision needed. Confirm working hours and time zones when agreeing deadlines.
6. Review the first run together
Treat the first completed task as a chance to improve the handover. Compare the result with the checklist and explain any changes. Be specific: “Use the client’s local time zone in the confirmation” is more helpful than “make this clearer.”
Ask which step was uncertain or took longer than expected. Update the instructions in the shared source so the next run benefits from the review. As the task becomes familiar, revisit how much approval is needed and keep responsibilities explicit when the workflow changes.
A simple handover checklist
Before you send the first task, check that the handover covers these eight points: the purpose, the trigger, the finished output, the deadline and time zone, the process, the required access, the approval boundaries and the escalation contact. Add links to the current templates and agree where progress will be recorded.
A handover does not need to be perfect to be useful. It needs to be understandable, safe to act on and easy to improve. Start with one well-defined workflow, review it together and build the next layer of support from what you learn.