Social media client offboarding checklist
A social media client offboarding checklist should leave the client able to operate their accounts and give every remaining publishing job an owner. Inspect pending posts before disconnecting anything. Delivering a folder and removing a teammate does not settle a queue that can still publish.
Agency operations: a handover you can verify.
In short:
- Record a decision and evidence for every pending post before changing connections.
- Verify native account control separately from scheduler membership and automation credentials.
- Close the engagement with receiver acceptance and named owners for unresolved exceptions.
The illustrative ledger is an operating template, not a legal standard or client record. Adapt it to your scope.
The publishing cutoff must be explicit before access changes
Agree on the final agency-managed publishing time, including its timezone. The last billable day and the last scheduled post need not be the same date.
Write down the client account lead, receiving administrator and notice-period publishing scope. Define exceptions individually: a launch can remain scheduled after the engagement ends only if someone accepts responsibility for it. Do not treat silence as approval.
The illustrative cutoff below is October 23, 2026, at 17:00 UTC. Replace it with the client’s agreement. An unavailable receiving administrator remains an unresolved dependency.
Existing account boundaries matter, but this is an exit task. The separate guide to structure one workspace per client covers organization; use this checklist to prove what remains when work ends.
Every pending post needs a disposition and an owner
Build a ledger from the actual publishing inventory, then record the result of each agreed change. A planned move to draft is not evidence that the post is now a draft.
Start with the calendar, drafts and failed or approval-pending jobs. Include platform-native scheduled posts as well as scheduler records. Check recurring or evergreen publishing and any external workflow that can create new posts. A calendar snapshot will miss content that an active trigger adds afterward.
Copy this illustrative ledger into a shared sheet. Replace example identifiers and evidence labels with actual records. The scheduled rows show starting states and verified outcomes.
| Post ID or native URL | Account | Publish time + zone | Current state | Disposition | Owner after cutoff | Evidence |
|---|---|---|---|---|---|---|
| Example P-101 | Client LinkedIn Page | Oct 22, 2026, 14:00 UTC | Scheduled | Keep agreed pre-cutoff post | Client lead owns later questions | Recorded approval; schedule readback |
| Example P-102 | Client Instagram | Oct 26, 2026, 09:00 UTC | Draft, previously scheduled | Hold for client decision | Receiving editor | Draft readback after change |
| Example D-103 | Client LinkedIn Page | Unscheduled | Draft | Deliver caption and media files | Receiving editor | Revision folder opened by receiver |
| Native URL for example P-104 | Client LinkedIn Page | Oct 19, 2026, 14:00 UTC | Published | Retain URL as reference | Client lead | Native URL checked |
These are handover labels, not invented product buttons. A post being delivered as files remains a separate record in the old system until its agreed disposition is verified.
PostSider’s posts API reference documents date-range listing, exact-post retrieval and draft/schedule status changes. If using the API for inventory, set the range deliberately and inspect unresolved records separately. A narrow final-week query is not a complete exit audit. After each change, read back the exact post and update the evidence cell.
Files are delivered only when the receiver can use them
Prepare the agreed captions and media in a location the client can access independently. Ask the receiver to open the files from their own account before closing the agency’s access route.
Include revision labels and identify original media or source locations. A thumbnail is not necessarily the original asset. A shared link that works for the agency may fail for the client, or depend on an agency-owned account that will soon be removed.
Describe the delivery method honestly. A manually assembled folder or retrieved API record is not a one-click workspace export. API JSON alone does not prove delivery of media binaries, usage rights or the full approval history. Check those items against the agreement rather than assuming they travel with a caption.
For the final report, state coverage and unavailable metrics. Use the structure to prepare the final client reporting handoff, but check this account’s available data. Retention and asset-license terms come from your agreement and policy.
Native account control and scheduler access need separate acceptance
Have the client verify native platform control before removing agency permissions. Being able to review content in a scheduler does not establish the ability to manage platform administrators or recover the account.
LinkedIn’s Page role documentation makes the distinction concrete: a super admin can add or remove admins, while a content admin manages Page content. Confirm the receiver has the required native role; do not infer it from their ability to post. Other platforms need their own role checks, not copied LinkedIn menu instructions.
Use this illustrative access acceptance matrix. Add account identifiers and completion timestamps.
| Access path | Accountable owner | Planned action | Acceptance evidence |
|---|---|---|---|
| Native platform admin and recovery | Client administrator | Confirm client control, then remove obsolete agency roles | Receiver checks role and recovery route |
| Scheduler membership | Authorized scheduler administrator | Remove eligible agency members after delivery | Membership list checked afterward |
| Scheduler channel connection | Account lead | Disconnect only after post reconciliation | Exact channel state checked afterward |
| Organization API key or approved OAuth app | Credential owner | Revoke obsolete access; replace shared credentials where needed | Revocation record and authorized access check |
| n8n, Make or CMS intake trigger | Automation owner | Disable client-specific intake and inspect active runs | Workflow state and remaining runs reviewed |
| Shared asset link | File owner | Confirm client possession, then remove obsolete sharing | Receiver opens retained files; sharing checked |
Never use password sharing as the handover method. Name the person authorized to make each access change; do not assume any scheduler member can remove an owner or administrator.
Inspect before disconnecting, then verify the remaining access paths
Stop new intake and reconcile existing jobs before disconnecting the channel. Disconnect is a connection change, not a substitute for the post ledger or proof that every external credential is revoked.
The public PostSider channel reference identifies channel-listing and disconnect endpoints. Inspect the exact account and pending records first, and check the resulting state afterward instead of relying on disconnect as your content-handling strategy.
If a publishing request has already reached a social platform, do not promise that disconnect cancels it. Inspect the destination for its actual outcome and keep any unresolved action in the ledger with an owner. Likewise, deleting a scheduler record is not the same as deleting published platform content.
Remove obsolete API keys and approved apps separately from team membership. Google’s linked-app guidance distinguishes sign-in links from app data access: removing a sign-in link does not delete data held by the app. That is Google-specific guidance, not a universal menu path or data-deletion guarantee.
In a mixed-client workspace, do not use an organization-wide publishing pause as a client-specific switch. Scope changes to the departing client, check shared dependencies, and verify the unaffected clients still have their intended setup. Record billing or data-retention questions separately; channel disconnect does not settle them.
Written acceptance closes the handover, not a goodbye email
Send the receiver a short acceptance record that points to evidence and exposes exceptions. An unresolved item stays open until its named owner handles it.
Adapt this copyable operational message to your agreement; it is not legal advice:
Subject: Social media handover acceptance for [client]
Agency-managed publishing ends at [date, time, timezone].
Post disposition ledger: [link]. Each remaining job has its final state and owner recorded.
Delivered files: [link and revisions]. Please confirm you can open them from your account.
Native account control: [receiver, account, confirmed role].
Completed agency access changes: [roles, membership, connections and credentials, with evidence link].
Remaining exception: [item, owner, next action and agreed date].
Final reporting coverage: [start/end dates and unavailable data]. Retention/contact terms: [agreed terms and contact].
Please acknowledge receipt and identify any item that remains inaccessible or unresolved.
When choosing a scheduler for agency work, ask whether you can inspect pending job states and account for external credentials during an exit. I built PostSider, so my recommendation is affiliated: See PostSider for agency publishing.
About the author: Lukasz Blania is the solo founder of PostSider. He runs PostSider’s own social media with the product.
Frequently asked questions
What belongs in a social media client offboarding checklist?
Include a content disposition ledger, client-controlled platform access, delivered files, reporting coverage, automation shutdown, revoked agency access and a written acceptance record.
Should scheduled posts keep running during the notice period?
Only according to the agreed publishing plan. Assign each pending post a disposition and owner, and define the final publishing cutoff with an explicit timezone.
Does disconnecting a scheduler transfer account ownership?
No. A scheduler connection and a social platform admin role are separate access paths. The client must confirm native account control before agency access is removed.
Can I promise a one-click export of the whole workspace?
Not without verifying that capability. Prepare the agreed captions, media and reporting files explicitly, and verify that the client can open them before removing access.
Does removing an agency team member stop its automations?
Do not assume so. Check organization API keys, approved app connections, webhook triggers and external workflows separately, then verify that the intended access paths are closed.
