Transferring a posting operation when a VA leaves means moving operational knowledge, authorized access, pending work, and accountability to a replacement owner. A password handover alone leaves unresolved publications and client commitments behind. Start with continuity: establish who owns the queue before changing access or assigning new work.
What should be inventoried first?
List the managed accounts, platforms, business owners, recovery contacts, storage locations, publishing tools, and active campaigns. Identify which assets and services belong to the client, the agency, or the departing contractor. Do not assume that an account created during a campaign is automatically transferable under the existing agreement.
Verizon 2025 DBIR found: Third parties were involved in 30% of breaches; credential abuse was an initial vector in 22%.
These breach findings are not specific to social media VAs. They support treating access changes as a controlled part of the handover. Shared credentials and undocumented recovery ownership make it harder to know who can still act on an account after the operator changes.
How do you preserve the active queue?
Export or record scheduled jobs and their current states before anyone starts recreating them. Capture the approved media version, caption, destination, requested window, and submission identifier. Separate pending requests from jobs that have already been sent to a publishing system.
Use a handover table that the outgoing and incoming operators can both review:
| Work item | State | Evidence | New owner |
|---|---|---|---|
| Approved clip | Ready | Approval reference | Incoming operator |
| Scheduled publication | Queued | Job reference | Incoming operator |
| Uncertain submission | Investigating | Original request | Named incident owner |
| Client amendment | Awaiting decision | Amendment record | Account manager |
Do not retry uncertain submissions merely because the new operator cannot immediately find a result. Reconcile the destination first to prevent accidental duplicate posts.
How should knowledge be transferred?
Ask the departing operator to demonstrate a normal publishing cycle and a common exception. Record the steps in the agency’s approved documentation system. Capture client-specific approval rules, escalation contacts, recurring deadlines, and known access dependencies.
Then reverse the demonstration: the incoming operator performs the task while the outgoing operator observes. This exposes gaps that a written checklist can miss, such as a file stored in a personal folder or an approval routinely arriving through a private message thread.
When should access change?
Coordinate access changes with the authorized account owner and the agreed departure timeline. Confirm that the replacement can use the intended access path before ending the old arrangement, unless an immediate security issue requires a faster response. Keep recovery methods under appropriate organizational control.
Revoke obsolete invitations, sessions, tokens, and shared-folder permissions as applicable. Record completion rather than treating an account password change as proof that every connected tool or device has been disconnected. The posting handover guide expands the operational checklist.
How do you verify the transfer worked?
Run a supervised publishing cycle and compare the planned queue with the actual results. Confirm that the replacement can locate approved content, resolve routine blockers, and produce the expected report. The account manager should know whom to contact for an urgent correction without involving the departed VA.
Review the first exceptions for missing knowledge rather than immediately attributing them to operator performance. A transfer is complete when ownership and execution are functioning, not when a document has been sent. Retain the final handover record alongside the agency distribution workflow.
How Conbersa Fits an Operations Transition
If the agency is moving to managed distribution, agree on account eligibility, ownership, access, and queue migration before ending the previous arrangement. Existing accounts may require a different transition from newly provisioned ones; confirm the specific route rather than assuming every account can move unchanged.