Build a handover for a shared social account

The next person managing an account inherits conversations as well as content. They need to know what has been promised, which questions remain open and why upcoming posts were planned. A handover that contains only passwords and a calendar leaves them to reconstruct the account's purpose while responding in public.

Explain what is active now

Summarise current campaigns, scheduled posts, recurring series and any temporary notices. Mark content that is approved separately from material still being drafted. Include the destination links and relevant factual sources so the new person can check a post without searching old messages. Identify anything that should be paused if circumstances change.

Provide a concise account of unresolved conversations. State the issue, the response already given and the internal contact handling it, while sharing only the personal information needed for the work. A new moderator should not send a contradictory reply or promise a different remedy because the earlier exchange was invisible.

Transfer access through the proper route

Use the platform's current account-management options and your organisation's approved access process. Do not put passwords, recovery codes or other credentials in an ordinary editorial handover document. Confirm that the incoming person can perform the required work before the outgoing person's access is changed. Have the appropriate administrator handle permissions and recovery arrangements.

Check connected scheduling or reporting tools too. Access to the main profile does not necessarily provide access to the queue, saved replies or underlying assets. Conversely, an old integration may retain capabilities after a person leaves. The account administrator should review the actual setup rather than relying on the handover writer's assumptions.

Pass on judgement, not only files

Include examples of the tone, moderation boundaries and escalation situations. Explain why a previous series was stopped or why a particular topic needs careful checking. Distinguish an established rule from one person's preference so the new manager can adapt sensibly.

A handover rehearsal

Give the incoming manager a fictional but realistic situation: a scheduled post refers to an event whose time has changed. Ask them to find the approved facts, identify the queued material and locate the person who can confirm the revised wording. They should not have to use an outgoing colleague's personal memory as the only source.

Then test an unresolved reply. The incoming manager should be able to see that the support team already contacted the person, without exposing more account information than needed. If the same conversation appears in several tools, establish which record is maintained. Otherwise, the handover can introduce duplicate replies that look automated or careless.

Finally, check an absence scenario. Who can pause the queue or publish a factual service notice if the main manager is unavailable? Confirm the actual access with the administrator rather than assuming a colleague's job title provides it. Record the operational route, not credentials. This small rehearsal reveals whether the account can continue safely when the normal pattern changes.

Run one ordinary task together: inspect a draft, confirm its approval, check its link and review a response. This reveals gaps that a document-only transfer can miss. Finish by confirming who is responsible for the account from the agreed date and where future questions belong. A handover is complete when the next person can operate the account coherently, not merely when the files have been sent.