Offboard a Content Vendor Without Losing Source Material

TL;DR

• Keep offboarding focused on maintaining usable content: ensure the team can access accepted versions, evidence and assets so editors can continue work without the vendor's private folders or memory.
• Follow a concrete handover method: create an inventory of active assignments and reconcile briefs, drafts and CMS records using stable identifiers so files map reliably to production status.
• Validate the transfer with a meaningful success check: don’t accept a file list as proof—rehearse maintenance by asking the new owner to make a harmless update and record any missing context.

Begin with the work that must remain usable

Editorial vendor offboarding should leave the team able to maintain its content without depending on a departing supplier's private folders or memory.

Create an inventory of active assignments, accepted articles, source material and assets. Distinguish work that is complete from drafts that still require review.

The handover should reflect the actual agreement and the organization's access rules. If ownership or permitted reuse is unclear, route that question to the responsible business or legal owner rather than assuming every file can be used in every way.

Reconcile the article inventory

Use stable identifiers to map briefs, drafts, accepted revisions and CMS records. Titles alone may be unreliable when they changed during production.

Ask the receiving editor to open a sample from each category. A file list is not evidence that the files are complete, accessible or understandable.

Preserve the source context

Collect the material needed to support future factual updates: source references, accepted expert claims and important limitations. Avoid requesting unnecessary private working material when a concise evidence record is sufficient.

For a fictional comparison article, the maintainer should know which product conditions informed the recommendation. A polished final document without that context may be difficult to update responsibly.

Our guide to updating old posts can help identify the maintenance information worth preserving.

Resolve incomplete work explicitly

For each unfinished assignment, record its current state and the next decision. Do not mark it complete merely to close the vendor relationship administratively.

Decide whether the remaining work belongs to the outgoing vendor under the agreement, an internal owner or a replacement supplier. Keep that business decision separate from editorial acceptance.

Use the content approval workflow to confirm which revisions were accepted and which still require changes. A delivered file is not automatically an approved article.

Transfer access through the proper owners

Identify publishing accounts, shared folders and integrations associated with the vendor's work. Have the authorized administrators transfer ownership or adjust access according to the organization's process.

Avoid placing credentials in the handover document. The receiving team needs controlled access, not a widely shared list of secrets.

Sequence access changes so the required files can be transferred and verified, while avoiding unnecessary continued access after the work is complete. Record who is responsible for each action.

Close with a maintenance rehearsal

Choose one published article and ask the new owner to make a harmless proposed update using the delivered source, evidence and assets. The exercise can stop before publication; its purpose is to test whether the handover is usable.

Record missing context and resolve it while the outgoing team is still available through the agreed process. Then confirm the final inventory, unresolved exceptions and future owners.

A successful offboarding leaves more than a collection of exports. It leaves a team that can locate the accepted version, understand its evidence, revise its assets and make the next publishing decision with confidence.