Blog

Social media handovers without records gaps

← All posts

A social media account handover is not just a password swap. For a city, county, school district or public agency, the account may hold official posts, public comments, direct messages, metadata and evidence of edits or removals. Some of that material may be a public record, depending on your jurisdiction and the content.

That is where handovers get risky. A communications manager leaves. A department page moves to a new owner. A vendor had admin access and nobody wrote it down. The new person can still post, so everyone assumes the handover worked. Then a request for public records arrives and the team discovers the archive, access trail or message history did not move with the account.

This guide is general information, not legal advice. US local governments answer to state and local public-records rules, and those rules vary. The safe working principle is simple: treat account access, content capture and response ownership as part of the same handover.

Start with the record, not the login

The National Archives and Records Administration says social media use can create records when content is made or received in the course of government business. Its federal guidance asks whether content contains evidence of agency policy, business or mission, whether it exists only on the social site, and whether the agency uses the platform to communicate official information. The same guidance says a record needs content, context and structure, along with useful metadata such as author and date. NARA Bulletin 2014-02 is federal guidance, not a state-local rulebook, but its test is a useful starting point for handovers.

State examples show why local context matters. Washington State Archives says a work-related social media post is a public record for retention purposes if it relates to the conduct of public business, including when it is created or received through a personal device or account. Washington State Archives ties that statement to Washington law. Tennessee’s Office of Open Records Counsel explains that Tennessee public records include material made or received in connection with official business by a governmental entity, and that each entity must have a public records policy and coordinator. That Tennessee guidance is Tennessee-specific. It should not be treated as the rule in Florida, Washington or any other state.

Define who owns each part

A clean handover needs named owners. “Comms will sort it out” is not enough.

  • Communications owns account continuity. They confirm which pages, profiles, ad accounts, scheduling tools and inboxes are active, who needs access, and what publishing calendar or crisis process is in flight.
  • Records owns recordkeeping requirements. They confirm which retention schedule applies, where captured records are held, how requests are searched, and what evidence must be preserved when ownership changes.
  • IT owns secure access. They remove departing users, reset shared credentials where they still exist, check multi-factor authentication, and make sure recovery email and phone numbers belong to the agency.
  • Legal or the public-records coordinator owns release decisions. They decide what is responsive, exempt or redacted. A tool can preserve and find records; it should not make disclosure calls.
  • The outgoing owner owns context. Before access disappears, they should identify unofficial workarounds, pending complaints, sensitive inbox threads, scheduled posts and any personal-account use for public business.

NARA makes a similar point for federal transitions: official social media accounts used for agency business should stay under agency control, and officials should keep personal materials separate from official systems. Its transition guidance is aimed at federal service, but the handover lesson translates well for local government.

Use a practical account handover checklist

Run this checklist before the departing owner’s last day, then repeat it after access changes are complete.

  • Inventory every official account. Include Facebook Pages, Instagram, X, LinkedIn, YouTube, TikTok, Threads, emergency-alert channels, Meta Business assets, ad accounts and department-specific pages.
  • Classify the purpose of each account. Note whether it is used for public notices, emergency updates, community engagement, service requests, recruitment or campaigns.
  • List current access. Record administrators, editors, agencies, vendors, shared inboxes, scheduling tools and archive tools. Remove people who no longer need access.
  • Check recovery controls. Confirm agency-owned email, phone and MFA. A profile tied to a former employee’s personal phone is not under proper agency control.
  • Confirm capture status. Check whether posts, comments, replies, edits, deletions, messages and available metadata are being captured where your policy requires it. Do not assume a platform export is complete enough.
  • Document pending activity. Save scheduled posts, open inbox threads, moderation queues, complaint-related comments, ad campaigns and any holds or preservation notices.
  • Test retrieval. Ask the new owner and records staff to find a known post, a comment thread and a date range from the archive or recordkeeping system.
  • Record the handover decision. Keep a dated note showing what changed, who approved it, what access was removed and where the evidence lives.

Do not ignore messages and comments

Many handovers focus on the visible page and forget private or semi-private communication. The Florida Department of Health says it does not use direct messaging or instant messaging through its social media accounts in order to comply with Florida public records law. That is one agency’s Florida policy choice, not a national rule. It is still a useful reminder: if your agency allows direct messages, someone must own how they are captured, reviewed and handed over.

Comments need the same care. Public conversations can continue after a post is published. A handover should state who monitors comments, who can hide or remove content under the agency’s moderation policy, and how removed material is preserved if it is a record under the applicable law or schedule.

Make the next handover easier

The best handover is the one you can repeat without drama. Keep a living register of official accounts. Review it quarterly with communications, records, IT and counsel. Add a handover step to onboarding and offboarding, not just to the social media policy. Then test it with a sample request: “Find every post and comment about this topic between these dates.”

If the answer depends on screenshots, memory or a former employee’s login, the handover is not ready.

Brolly helps public-sector teams keep supported social media activity from connected official accounts in one searchable archive, so records and communications staff can review posts, comments, edits and available metadata before a request lands. Exemptions, redactions and release decisions stay with your agency. For a grounded next step, compare your handover checklist against Brolly’s social media account handover checklist, then test whether your current process can find last month’s posts and comments without asking the former account owner.

The record is easier before the request.

See how Brolly captures posts, comments, edits and deletions in near-real time.