What a proper handover looks like when an engagement ends

Engagements end for good reasons as well as bad ones. Projects complete, strategies change, businesses move work in-house.

What happens at that point determines whether two years of work remains an asset or becomes something the next partner has to reconstruct.

What has to be handed over

Account access and ownership, transferred not shared. Ad accounts, analytics, search console, tag management, social accounts, the email platform, the CMS, the domain registrar, the hosting.

The distinction between access and ownership matters. A client granted a login to an account owned by someone else can lose it at any point.

Source files. Working design files, video project files, photography in its original resolution, document originals. Exports are not source files, and a logo supplied only as a small image file is a problem the client discovers at the worst moment.

Content, in an editable form, including anything drafted and not published.

Documentation. What was built and why. The tracking setup and what each event means. The campaign structure and the naming conventions. The keyword and content plan. Audience definitions. Anything a successor would otherwise have to reverse engineer.

The current numbers, with a baseline and a history. Reporting to date, so performance is comparable across the transition.

Work in progress, with its current state stated honestly.

Passwords and credentials, transferred securely and then removed from the outgoing party's systems.

The documentation is the part that gets skipped

Accounts and files get handed over because they are obvious. The knowledge does not, because it lives in people.

Which is why a successor frequently rebuilds tracking that was already correct, restructures campaigns that were performing, and repeats research that was already done. All of that is paid for twice.

A short written record, even a few pages, prevents most of it. What was tried, what worked, what did not, what was deliberately decided against and why. That last category is the most valuable and the least often recorded, because it stops the next partner spending a quarter on something already ruled out.

Agreeing it before you need it

A handover negotiated at the end of a relationship is negotiated at the worst possible moment.

Which means it belongs in the agreement at the start: what is handed over, in what format, within what period, and that ownership of accounts and assets sits with the client throughout.

Set up that way, a handover is a task rather than a dispute, and it takes days rather than months.

Doing it well when you are the one leaving

Worth doing properly for reasons that are not sentimental.

Reputation. The industry is small and how a business exits is discussed more than how it performed.

Referrals. Clients who leave well refer. Clients who leave badly warn people.

Returning clients. A meaningful proportion of departed clients come back, usually after discovering the alternative. That door stays open only if the exit was clean.

It is the work. Leaving a client worse off than they would have been is a poor outcome regardless of who decided to end it.

Practically: hand over everything without being chased, write the documentation, offer a transition call with the incoming party, and answer questions for a reasonable period afterwards without invoicing for it.

Doing it well when you are the client

Ask for the list before the final payment. Not as leverage, as sequencing.

Verify the transfers rather than assume them. Log in to every account yourself and confirm you are the owner, not a user.

Get the files while people are still employed there. Personnel move and institutional memory goes with them.

Record the baseline on the day of the change, every number, dated. Without it neither the outgoing nor the incoming party can demonstrate anything.

Do not let the new partner rebuild what works without an explicit reason. Inheriting a performing setup is faster and cheaper than starting again, and the cost of starting again falls on you.

The underlying principle

The client owns the outcomes of the work, and the infrastructure that produced them.

A relationship set up on that basis is straightforward to end and, not coincidentally, is usually a better relationship while it runs, because neither side is relying on lock-in to keep it going.