The Handover Test Before You Leave an Agency

A clean handover does not prove the agency was right. It shows whether the work can survive the relationship.

Leaving a digital partner is often discussed as a procurement event. The more useful view is operational: what must remain true when the old team no longer answers the questions?

Accounts, repositories, hosting, source files, content rules and decisions are usually distributed across people. A project can look complete while its operating knowledge remains private.

If the handover is weak, the new agency spends its first months rediscovering the old system. The client pays twice for the same understanding.

A folder of files is not a handover. Neither is a final meeting. The next team needs relationships, ownership, environments, credentials and acceptance conditions.

Ask the current agency to produce one practical handover: what exists, where it lives, what depends on what, what is unfinished and who can change it safely.

If the record is clear, you can leave with less risk. If it is not, that is evidence about the operating model you are leaving. Make that gap visible before appointing the next partner.

What the work should actually look like

Define the outcome. State what the customer or staff member should be able to do.
Name the affected page or workflow. Make the boundary visible.
Find the blocker. Identify missing copy, approval, access, data or a technical decision.
Assign the owner. Give every open decision one person who can complete it.
Run the acceptance check. Test the result under the agreed conditions.
Release and hand over. Record what changed, what remains limited and who owns it next.