Create a Virtual Assistant Handoff That Works During an Unexpected Absence
For an unexpected absence, put the immediate task status, next action, access route and approval limits on a short restart card. Keep the detailed manual alongside it for recurring procedures and exceptions. Together, they tell a substitute both where to start today and how to carry out unfamiliar steps.
A useful handoff identifies an accountable owner, names the current substitute and separates confirmed facts from open questions. It also points to the approved place for working files without copying credentials or unnecessary personal information into the card.
Meeting preparation is a useful example because a substitute may need to check invitations, assemble an agenda and coordinate approvals under a deadline. The Government of Canada’s Job Bank lists scheduling and confirming meetings, preparing documents and recording minutes among administrative assistant duties.
When should you use a manual, a restart card or both?
Use a manual for instructions that remain broadly stable: how to find the approved agenda template, prepare a draft, check a calendar and submit materials for review. Use a restart card for the state of one particular assignment: what has already happened, what remains and who can decide an unresolved issue.
A manual alone can leave the substitute reading several pages before discovering that invitations have already gone out. A card alone can become too thin when the substitute has never used the organization’s process. For recurring or consequential work, pair them: put the next action on the card and identify the relevant manual section by name.
Keep both in an approved location that the designated backup can find. The card should identify its last update time and the person who updated it; otherwise, a confident-looking instruction may describe yesterday’s situation.
Need | Best place | Example
Current state and immediate action | Restart card | Agenda drafted; request chair’s review
Repeatable procedure | Manual | Steps for preparing and routing an agenda
Authority and escalation | Card, with fuller policy in manual | Do not send the final pack without chair approval
An exception or unanswered decision | Restart card | Ask whether the final agenda includes the budget item
What does a usable restart card look like?
Imagine a fictional virtual assistant, Alex, preparing a monthly planning meeting for a fictional team. Alex is unexpectedly absent, and Morgan is the designated backup. All names, dates and task details below are dummy data; adapt the fields to the actual assignment and authorized people.
Task and deadline: Prepare the meeting pack for the planning meeting on 18 June at 10:00 a.m. Eastern Time. The chair wants the draft pack ready for review by 16 June at noon Eastern Time. The time zone matters because a remote substitute may work elsewhere.
Owner and coverage: Alex owns preparation under normal circumstances. Morgan is the temporary operator; the meeting chair, Dana, remains accountable for the agenda and final release. Last updated: 15 June at 3:00 p.m. Eastern Time by Alex.
Current status: The calendar invitation has been sent. The agenda draft contains three proposed items, and the standard meeting-pack template has been copied into the approved team workspace. The draft has not yet been reviewed or sent to participants. Confirm the current workspace and calendar before acting, in case anything changed after the update.
Next action: Open the draft agenda in the approved workspace, check it against the meeting request, and send it to Dana for review by the stated draft deadline. After approval, follow the manual’s meeting-pack procedure. Record the review request and its outcome on the card so another substitute can see what happened.
Access request: Morgan should request access to the planning meeting folder through the organization’s normal access process, naming Dana as the person who can authorize it. If access is delayed, tell Dana before the review deadline and ask for an authorized alternative. Do not borrow Alex’s account or include passwords, recovery codes or authentication prompts in the handoff.
Approval boundary: Morgan may format the draft and correct obvious typos. Morgan must not add or remove agenda topics, change the meeting time, invite additional participants or distribute the final pack without Dana’s approval. If Dana cannot be reached, use the organization’s designated escalation route rather than assuming silence means approval.
Unresolved question: Does Dana want the proposed budget item included? The request is pending; no answer has been recorded. Ask Dana before treating the item as final, and note the answer and time when it arrives.
How much detail belongs in the manual?
Write enough for an authorized substitute to complete the recurring workflow without relying on the absent assistant’s memory. For this example, the manual might identify the approved template, explain how the draft is named and stored, describe the chair’s review route and specify how to confirm that the final pack is ready for distribution.
Include decision points and failure routes, not just a sequence of clicks. For example: if the calendar invitation and meeting request disagree, ask the chair which is authoritative before changing either. If the agenda is still awaiting review at the deadline, notify the chair and follow the agreed escalation process. If the meeting is cancelled, confirm who will notify participants and update the task record.
Avoid filling the manual with one meeting’s changing details. Put the current deadline and pending answer on its restart card. If the procedure changes, update the manual and its review date; if the meeting status changes, update the card. That separation makes stale information easier to spot.
How can the handoff protect access and personal information?
Give the backup a way to request their own authorized access and only the information needed for the task. A card can name the workspace and access approver without reproducing the attendee list, private correspondence or the contents of an attachment. Store the working material in the organization’s approved system, with access set by the person responsible for it.
The Office of the Privacy Commissioner of Canada advises protecting personal information according to its sensitivity and limiting access to sensitive files on a need-to-know basis. Which privacy requirements apply depends on the organization, the information and the relevant federal or provincial law. A tidy handoff supports responsible handling but does not by itself establish legal compliance.
Agree on who will remove temporary access when coverage ends and how long the card should be kept under the organization’s retention practices. If a card contains information that does not need to travel with it, remove that information before sharing it through an approved channel.
How do you test the handoff before an absence?
Ask the designated backup to read the card using their own account and explain the first action, deadline, approver and escalation route. Have them locate the manual and request any missing access through the normal process. The exercise should reveal whether the instructions depend on a private inbox, an unexplained abbreviation or a decision only the absent assistant knows.
Run the check with dummy data when possible. If the backup would send a draft that was never approved or repeat an invitation already sent, clarify the status and approval boundary. Then update the card when work advances: record what was done, when, and what remains. On the owner’s return, agree who resumes the task and close or transfer any pending requests.
For someone building these administrative skills, Workvella virtual assistant resources include a guide to virtual assistant work in Canada and its common tasks. Use the fictional card as a practice exercise, then adapt its fields to the actual client’s tools, instructions and approval process.