Published: October 5, 2026
A manager's absence can turn a prepared onboarding plan into a week of unanswered questions. The usual fix is to name a backup, but a name alone does not supply context, access, or authority. A useful backup plan identifies the decisions likely to arise, separates support from approval, and gives the new hire a safe route when both people are unavailable.
List the manager's first-week obligations
Work through the schedule and mark where the manager must act. Common obligations include welcoming the employee, explaining role outcomes, approving access, reviewing practice work, resolving conflicting priorities, and confirming what may move into live production. Some can be prepared or delegated. Others may stay with the manager or another authorized leader.
Write obligations as outputs. "Check in with new hire" is vague. "Review the first drafted queue summary and decide whether the next sample may use live records" tells the backup what evidence and decision are involved. Add the latest safe completion time so the team knows which items threaten the plan.
Choose backups by authority and context
The nearest available colleague is not always the right backup. Confirm that the person understands the role, can access the relevant systems, and is authorized to make the named decisions. One person may handle day-to-day questions while an IT owner approves access and a department leader changes work priorities.
Ask each backup to accept the assignment before publishing the plan. Calendar availability is not acceptance. Show them the dates, expected workload, decision boundaries, and escalation route. If nobody has authority for a critical decision, change the first-week plan rather than quietly allowing a coordinator or virtual assistant to decide.
Prepare a concise context packet
Give the backup the current role brief, first-week outcomes, schedule, agreed work arrangement, open prerequisites, practice tasks, review criteria, and known exceptions. Link to governed records instead of copying candidate interviews, medical information, background checks, or unrelated recruiting notes. The backup needs operational context, not the entire hiring file.
Include commitments already made to the new hire, such as an approved schedule or start arrangement, where the backup is authorized to see them. Mark information that remains pending. A packet that presents assumptions as settled facts can lead the backup to contradict the offer, HR process, or manager.
Separate support from formal decisions
A buddy or coordinator can help the new hire locate instructions, understand team conventions, and reach the right owner. That does not automatically allow them to approve system access, change compensation, interpret policy, assess an accommodation, or make an employment decision. Put those exclusions beside the assigned support tasks.
When a question falls outside the backup's boundary, the plan should state the holding action and next owner. The new hire can continue safe training, document the question, or move to another assignment. They should not be pressured to accept an informal answer because the primary manager is away.
Test the contact routes
Before the start date, confirm that the new hire can reach the backup through an approved channel and that the backup can open the onboarding record. Check the calendar invitation from an ordinary account. Include time zones, recurrence rules, and a second route if corporate login fails on day one.
Run a short scenario: the new hire cannot access the practice system thirty minutes before the scheduled exercise. The backup should be able to find the access owner, choose a safe alternate activity, update the plan, and tell the employee when the next decision will arrive. The test often reveals missing permissions or an outdated contact list.
Design the first day for resilience
Do not place every meaningful activity behind one live manager meeting. The new hire can review current instructions, complete low-risk setup, examine examples, and prepare questions while waiting for decisions, provided the material is accessible and appropriate. Put those activities in order and explain which ones must not begin without approval.
Avoid filling the day with generic reading merely to appear busy. Each item should connect to the role and lead to a reviewable output, such as an annotated workflow or practice classification. If the manager's absence removes the only qualified reviewer, delay that task instead of treating completion as evidence of readiness.
Record decisions for the returning manager
The backup should preserve the question, facts available, source used, decision, effect on the schedule, and open follow-up. This prevents the returning manager from reversing a decision without understanding what the new hire was told. One-time exceptions should be labeled so they do not become accidental procedure.
Set a handback time. The manager reviews open items, confirms or corrects temporary arrangements through the authorized route, and tells the new hire who owns the next step. Do not make the employee reconcile two leaders' instructions alone.
Keep an unresolved-decision list beside the handback record. Each entry should show the deadline, temporary holding action, and person expected to close it. The returning manager can then address work that is still blocked before revisiting routine conversations that the backup already completed.
Review the plan after actual use
Check whether the backup received enough notice, had the promised authority, responded within the required window, and preserved decisions in the right place. Ask the new hire whether the route was understandable, without turning the review into a judgment about the manager's reason for absence.
Update the role coverage plan for future leave and unexpected outages. The OPM onboarding guidance offers general orientation material, but each organization must assign its own managerial and employment authority. OnboardingEmployees can help turn that assignment into a practical manager handoff and first-week plan.
Continue building the workflow
Related support: virtual assistant role brief, virtual assistant onboarding checklist. The U.S. Equal Employment Opportunity Commission explains that employment selection procedures should be job related and consistent with business necessity.
Related reading

Run a First-Day Readiness Check for a Virtual Assistant
A practical virtual assistant first day readiness check for making evidence, ownership, decision boundaries, and handoffs visible.

Plan a Virtual Assistant's First Week Around Real Work
A practical virtual assistant first week manager plan for making evidence, ownership, decision boundaries, and handoffs visible.

Use a 30-Day Review to Strengthen Virtual Assistant Retention
A practical virtual assistant 30-day retention review for making evidence, ownership, decision boundaries, and handoffs visible.