Virtual assistant role knowledge transfer

Key takeaways

• Use a written brief and definition of done.
• Keep approvals and escalation rules visible.
• Review quality before expanding the workflow.

# Virtual assistant role knowledge transfer

Document queue, sources, normal output, review points, exceptions, escalation contacts, and owner decisions. A receiving person should complete a supervised normal task and escalate ambiguity.

Applying virtual assistant role knowledge transfer

Transfer is complete only when the receiving person can perform a normal task and explain where uncertainty goes. Pair the queue map with source examples, review points, exception cases, escalation contacts, and owner decisions. A document dump transfers files but not working judgment.

Role boundary and review

The outgoing assistant can demonstrate the task and identify hidden dependencies. The receiving operator practices under supervision, while the owner confirms readiness and retains decisions involving access, commitments, or exceptions. Record the questions raised during the practice run because they often reveal missing guidance. the [services library](/services) helps identify the role being transferred, while the [[provider vetting guide](/provider-vetting)](/provider-vetting) frames continuity questions. [NIST guidance](https://www.nist.gov/itl/smallbusinesscyber) is useful when access changes hands. ### Transfer record Keep the queue map, examples, practice result, open questions, escalation contacts, owner sign-off, and date.