Which accounts and source files should stay with the client?

Make the next handover possible before the first campaign begins.

Inventory ownership and permission

For each domain, ad account, analytics property, CRM and repository, record the owner, administrator and delivery access. An invitation to view a report is not the same as ownership. Retain an administrative recovery path controlled by the client.

Name reusable work products

Request editable designs, copy, event definitions, integration mappings and build instructions where they are part of the scope. Check third-party licenses separately. Some tools or assets may be licensed for limited use; document the limit instead of assuming every file can be freely reused.

Test the handover

Have the receiving team open the files, reproduce one key operation and locate the latest approved version. After acceptance, revoke permissions that are no longer needed and rotate shared secrets where appropriate. A folder link without a usable process is incomplete handover.

Take this checklist

Client-controlled ownership and recovery.
Minimum necessary delivery access.
Editable files with license notes.
A demonstrated receiving-team workflow.

Background sources

The working method above is editorial guidance. These primary sources provide context and examples; they are not proof of a universal procurement rule.

Primary source: croud.com / mpb-in-housing ↗Reviewed 11 September 2026. Publication reviewed; performance not independently audited.