Inventory
List every account, integration, audience, feed, domain, file, contract, and billing dependency.
Home / Learn / Agency Management
Agency accountability · transition
The safest switch begins before notice is sent. Inventory ownership, preserve the live system, and transfer decisions in a controlled sequence.

Direct answer
Secure administrator access and exports before the switch begins.
01 · Establish control
The client should have direct administrator access to every durable marketing asset. That includes advertising, analytics, tag management, commerce, domain, website, CRM, email, call tracking, creative, and reporting accounts. Google’s own documentation says a client account retains its data when manager ownership changes; the practical risk is access configuration, not a legitimate transfer of the client’s history.
Make a manifest with the asset, account ID, client administrator, agency access level, billing owner, recovery method, and current export. A screenshot of a dashboard is not an export, and an agency login is not client ownership. Test each login before the outgoing team loses access permanently.
02 · Protect the live system
List every account, integration, audience, feed, domain, file, contract, and billing dependency.
Preserve campaign settings, change history, creative source files, dashboards, tag versions, and current channel performance baselines.
Pause nonessential experiments. Do not combine a vendor switch with a site migration, attribution-model change, and total campaign rebuild.
For every active test, record the hypothesis, start date, spend, evidence, and stop condition.
Add the incoming team using individual or manager access. Never share one master password.
Require the incoming agency to explain what it will preserve, change, and measure before changing it.
Confirm client access, exports, billing, and live tracking before removing the outgoing team.
03 · Make the right decision
Missed targets alone do not prove that an agency should be fired. Marketing can miss because the offer is weak, follow-up is slow, measurement is wrong, or the channel is a poor fit.
Access and evidence remain intact. The team can name the cause, owner, correction, decision date, and stop condition.
Access is hidden, explanations change, preventable errors repeat, or agreed stop conditions are ignored.
Use an RFP only after the failure is defined. A broad request for “more leads” will generate broad promises. A useful request names the operating context, evidence, constraints, ownership, reporting logic, and what the first 90 days must establish.
The packet should let a competent operator understand the live system without relying on the outgoing agency’s memory. Include ownership, access, billing, campaigns, budgets, audiences, exclusions, creative, landing pages, conversion definitions, dependencies, open experiments, known defects, and renewal dates. Preserve naming conventions, reporting definitions, and current channel performance baselines.
For each campaign, record what must not be changed during the handoff. A stable campaign with good qualified outcomes is an asset, not a blank canvas. The incoming team should explain why a rebuild is necessary and how it will separate the two effects.
Questions this owner resolves
Q015
The client should own the domain, ad accounts, analytics properties, tag manager, merchant and business profiles, CRM, billing relationship, audiences, and final creative source files. The agency should receive the minimum access needed to work. Ownership protects continuity, but access control still matters: use named users, role-based permissions, recovery contacts, and an offboarding checklist instead of shared passwords.
Use this rule: If an asset contains history, audiences, identity, billing, or recovery access, place it under client ownership before work begins.
Example: Maintain two client administrators, one agency manager link, and zero shared credentials. Review users quarterly and remove agency access on the final service day.
Field note: Creating a new ad account after a breakup does not merely lose convenience. It can sever history, audiences, verification, billing, and troubleshooting context.
Q018
Fire the agency immediately for data withholding, unauthorized spend, deceptive reporting, material compliance violations, or loss of trust that cannot be repaired. For ordinary performance problems, use a written cure plan first: name the miss, evidence, action, owner, and deadline. Leave when the agency fails that plan, repeats the same unexplained mistake, or makes transition risk larger by blocking access.
Use this rule: Terminate for material breach now; otherwise terminate after a fair, documented cure period fails and the transition package is secured.
Example: Use a 30-day cure plan with weekly evidence checks for an execution problem. Do not wait 30 days for unauthorized spend or withheld account access.
Field note: Secure administrators, billing, exports, and creative files before giving notice when access risk exists.
Q019
Start the switch before the old agency leaves. Confirm client ownership and administrator access, export campaign history and reports, collect creative source files, document naming and tracking, preserve active tests, and record current budgets, audiences, exclusions, conversions, and known problems. Give the incoming team a dated operating snapshot. Change access only after the handoff is verified and recovery contacts are tested.
Use this rule: Do not end the old engagement until every critical asset has a client administrator, a verified export, an assigned recipient, and a rollback or recovery path.
Example: Run a 30-day transition: inventory in week 1, exports and documentation in week 2, joint review in week 3, access change and monitoring in week 4.
Field note: Screenshots are not a handoff. Preserve raw exports, change history, source files, conversion definitions, and the reason behind active settings.
Q020
Write the RFP around the business decision, not a long wish list. State the problem, measurable outcome, audience, current marketing, constraints, budget range, required scope, client responsibilities, timeline, decision rights, data access, and weighted evaluation criteria. Ask finalists to solve one small paid working problem. Do not demand speculative finished creative from every agency or hide the budget needed for a serious response.
Use this rule: Use an RFI to screen capabilities; issue an RFP only when the outcome, budget envelope, decision process, and required work are defined well enough for comparable proposals.
Example: Weight evaluation before release: business understanding 25%, proposed method 25%, assigned team 20%, measurement 15%, commercial terms 10%, transition and risk 5%.
Field note: A shorter RFP with a real working session reveals more than 100 boilerplate questions that agencies delegate to proposal writers.
Primary and observed sources
Official documentation supports platform and search requirements. Third-party pricing and practice pages are cited as observed market examples, not universal facts or proof of ranking causation.
Continue the decision