Virtual assistant onboarding checklist for approved work Bankeiz client work resources https://bankeiz.com/learn/templates/virtual-assistant-onboarding/ BLANK WORKING TEMPLATE VIRTUAL ASSISTANT ONBOARDING Client / assistant / date / owner: [details] Scope and capacity: [version; period; limits] Priority owner/substitute: [names/roles] Service window/timezone: [details] Intake/communication: [channel; expectations] Allowed tasks: [task; output; limit] Approval before: [action; decision maker; record] Not authorized: [specific actions] [ ] Access authorized — [tool; role; client owner; status] [ ] Scoped access tested — [result; date; no secrets] [ ] Naming/storage confirmed — [reference] [ ] Sensitive-information handling confirmed — [approved process] [ ] Capacity reporting agreed — [method; frequency] First task: [instruction; output; date; reviewer] Blockers: [item; owner; action] Readiness: [ready for named tasks / pending; reason] First-task review: [date; process corrections] FILLED EXAMPLE — FICTIONAL FICTIONAL FILLED EXAMPLE Maple Studio onboarding uses support scope MS-06, ten hours in June. Maya sets priorities; Alex substitutes. Evan works Tuesday and Thursday mornings Eastern time, receiving requests in the agreed conversation. Evan may format drafts and organize copies in the working folder. External replies, deletion of originals, spending and account changes need separate authorization. Maya grants a limited document role through the studio’s process; Evan tests the first file. No credential is recorded here. The first task is formatting a four-page overview without changing claims, due Thursday for Maya’s review. A missing logo is a blocker assigned to Maya. Readiness covers formatting and the task summary only; other work remains pending. The checklist does not convert a general “help with admin” request into permission to act externally or alter account settings. Review and adapt the facts, scope, amounts, dates and responsibilities before using this working document.