.jpg){kind=link}
Inventory what must continue
List active profiles, reference pages, campaigns, pending messages and scheduled posts. Identify the organisation and authorised decision-makers. Also find abandoned accounts still carrying its name. Handover may reveal that an old personal account became the group’s main tool without clear agreement.
Transfer editorial context
Prepare a note about audience, tone, recurring replies, sensitive topics and follow-up commitments. Add sources for recurring content and media permissions. Do not transfer an archive of private conversations merely because it is available; determine what is useful and authorised for continuity.
Arrange a controlled transition
Use invitation or administration features documented by the service. Verify the new responsible person’s capabilities before removing the previous person’s. YouTube channel permissions illustrate delegation; other networks may differ. Do not promise a universal ownership transfer without checking the specific case.
Close and record the handover
Check public contact, automatic replies, links, schedule and former contributors’ permissions. Record date, transferred items and remaining tasks without passwords or codes. Plan a short period for operational questions, then clearly assign responsibility to avoid indefinite parallel administration.
Choose the right check for the situation
These editorial pointers help prepare and review your work. Choose the situation matching your content; check current features and conditions in the cited sources before applying it to a service.
| Situation | Useful action | Mistake to avoid |
|---|---|---|
| Planned departure | List accounts, roles, documents, licences and upcoming commitments with an owner. | Handing over only a password in a message. |
| Takeover by a new team | Have the successor verify access and a draft before departure. | Treating handover as complete because a document was sent. |
| Moderation history | Retain useful decisions with restricted access and a defined retention period. | Copying all private conversations into a shared folder without need. |
| End of transition | Remove unnecessary access and check the agreed recovery contact. | Keeping former managers as administrators indefinitely. |
Hypothetical example: apply the method
A club’s coordinator leaves the role. They provide a calendar, link list and publishing procedure. The successor tests a non-sensitive announcement; former roles are reviewed after confirming the transition.
Template to adapt
Copy this outline into your working document. It collects no information on this site; complete it for your situation.
Transferred scope: Incoming responsible person: Public contacts: Scheduled content: Permissions and sources: Access checked: Remaining tasks: Closure date:
Your pre-use check
0 / 4 checks completed
Frequently asked questions
Must all conversations be handed over?
Define needs and permissions. A complete archive may contain information unrelated to continuity.
When should the old role be removed?
After checking intended operation and following service procedure, without unnecessarily extending access.
Continue with related content
Sources and scope
Primary references consulted for factual points. Methods and templates are editorial suggestions; service conditions should still be checked in current documentation.