The point where work gets scattered
Tools and passwords do not explain authority. The assistant still needs to know which replies can be sent, which files changed and who resolves conflicting requests.
Confirm decision boundaries
Start with accepted scope and first tasks. Permission to act is separate from access: having a tool role does not authorize every action available there.
- Name the priority owner.
- List allowed tasks and approval-dependent actions.
- Clarify spending, deletion, external replies and account changes.
Prepare access without secrets
The client grants access through its existing authorized process. Record status and owners here, never passwords, payment details, recovery codes or tokens.
- Test only required tools and folders.
- Confirm naming, storage and privacy expectations.
- Agree windows, timezone and urgent-request handling.
- Choose a first output and review point before expanding work.
Ready-to-work checklist
Do not mark ready while permissions or instructions are ambiguous. A small approved first task gives better evidence than a large unchecked inventory.
- Scope and priority owner are identified.
- Communication and limits are understood.
- Access is appropriate and tested.
- Approval boundaries cover sensitive changes.
- The first task has an output, reviewer and date.
The working template
Use the complete text below, or download the text file and edit it in your preferred document editor.
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]Download text template
A filled example
Fictional example for illustration. Replace its facts and amounts with the details you actually agree.
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.
Keep the context with the conversation
Prepare the first-task summary in Bankeiz Messages with chosen context. Keep credentials in the approved access process and review external actions or supported payments separately before confirming them.
Understand your Twin · See Business access and metered AI usage