What should a GEO supplier exit and handover plan include?

Plan the exit before notice is given

A supplier exit is a normal contract-lifecycle event, not necessarily a sign of failure. A GEO engagement may end at expiry, move in-house, change supplier, reduce scope or stop after a pilot. The buyer should therefore agree the exit method while the service is stable, when ownership, access and knowledge are still easy to verify.

The UK Government Sourcing Playbook says contracts should require an exit plan that joins the outgoing supplier's exit strategy to mobilisation by an incoming supplier or in-house team. It also says preparing for exit takes time and that the plan should be revisited as the relationship and processes change. Treat the plan as a controlled working record, not a paragraph that remains untouched in the original proposal.

Create one eight-part exit and handover record

Name a buyer owner and supplier owner for every line. Add the required format, due date, acceptance evidence, dependency and status. A link or folder location is useful only if the buyer can open it, understand it and retain it after supplier access is removed.

Keep the buyer's asset boundary visible

Do not use the word 'content' as a catch-all. List each deliverable and its working format: audit tables, approved fact records, prompt or question sets, measurement definitions, raw permitted exports, bilingual source copy, design files, code or configuration, test results and approval history. Record whether the buyer owns it, licenses it, may modify it, or must replace it after exit.

Separate buyer accounts from supplier tools. A dashboard screenshot is not a transferable monitoring setup, and a published page is not a substitute for its approved source, evidence and change history. If a third-party licence cannot transfer, record the replacement dependency, export route and final access date before the licence ends.

Test continuity instead of accepting a folder

Ask the incoming or in-house team to perform one representative workflow using only the handover material: update an approved fact, adapt it for English and Simplified Chinese, release it through the agreed route and record the test. The exercise can expose missing permissions, unclear ownership, hidden spreadsheet logic and undocumented review steps while the outgoing team is still available.

Use a short defect log for the rehearsal. Classify each issue as missing asset, inaccessible asset, incomplete instruction, unresolved decision, unsupported dependency or failed control. Agree who corrects it and what retest closes it. Receipt of files is delivery evidence; successful re-performance is stronger continuity evidence.

• Choose a workflow important enough to test but safe enough to run without disrupting production.
• Include the real buyer approver and language reviewer rather than testing only supplier-to-supplier transfer.
• Keep original dates and source history when assets move; do not reset provenance during migration.
• Record exceptions that the buyer accepts, including their consequence, owner and review date.

Close access and data with evidence

Build an access list from the identity source and the service itself, including external users, shared accounts, privileged roles, API keys and service accounts. The NCSC recommends managing joiners, movers and leavers and removing access when it is no longer needed. Transfer buyer administration first, then revoke or rotate supplier access according to the transition plan, and retain a dated confirmation.

Where the supplier processes personal data for the buyer, the ICO says the contract must provide for deletion or return of personal data at the buyer's choice at the end of services, and deletion of existing copies unless law requires storage. Record the chosen action, export, backups, subprocessors, legal exceptions and secure deletion evidence. This operational checklist does not replace data-protection or contract advice.

Support planned and emergency exits

The planned route can use normal notice, orderly transition and a final acceptance window. The emergency route may need buyer-held credentials, current exports, alternative owners and a minimum service runbook immediately. Keep both routes in the same plan, but make the trigger, authority and acceptable loss of service explicit.

Review the plan after a major scope, team, platform, language, data or dependency change, and before renewal or recompetition. Do not wait for the final week to discover that the buyer lacks an administrator, the latest working files or permission to reuse a critical asset.

Ask SALIENS for a buyer-controlled handover

SALIENS provides GEO audits, AI visibility monitoring, content and technical improvements, and ongoing GEO delivery. A scoped engagement can define buyer-owned assets, evidence records, access and data controls, multilingual workflows, acceptance checks, transition support and a closing handover pack from the start.

Email info@oxfordintelligence.co.uk with your website, markets and languages, current supplier or in-house model, material accounts and data, required transition date and procurement constraints. SALIENS is operated by Oxford Intelligence Limited. A controlled handover supports continuity but does not guarantee crawling, indexation, AI mentions, citations, rankings, traffic or enquiries. This guide is a procurement framework, not legal, data-protection or commercial advice.