An experienced buyer knows why an apparently inefficient campaign remains active, which product is about to run out of stock, and which client dislikes a particular claim. Those facts may never appear in an account dashboard.
When an AI operator receives access without that context, it can produce confident recommendations that are locally sensible and commercially wrong. The handoff should therefore transfer decision context before transferring execution authority.
Begin with an account identity sheet
Record the advertising platform, account ID, business owner, timezone, currency, and the campaigns included in the engagement. Add the people responsible for budgets, creative claims, measurement, and incident response.
Do not rely only on a display name. Agencies often have several accounts with similar names or separate regional accounts for one brand. The identifier needs to appear in the handoff and in the first account readback.
Google's access-model documentation distinguishes direct access from access through a manager account. Review the effective account scope when connecting software. The existence of a working connection does not establish that every accessible account belongs in this handoff.
Explain the business outcome behind the campaign goal
Translate the platform objective into a business result. A purchase campaign might be intended to acquire first-time customers at an acceptable contribution margin. A lead campaign might be intended to fill qualified appointments in a specific service area.
Write down the definitions. Does revenue include tax and shipping? Are refunded orders removed? What counts as a qualified lead? Does the owner care about immediate contribution, payback over time, or a temporary launch objective?
Include missing facts explicitly. If repeat-purchase value is unknown, do not replace it with an optimistic lifetime-value estimate. If the business has not agreed on an allowable acquisition cost, the operator can help organize the calculation without pretending the target already exists.
Transfer the current account story
The handoff should explain how the account reached its present state. Summarize the current campaign roles, recent meaningful changes, active experiments, known problems, and decisions that are waiting on someone else.
Google Ads change history is one source for reconstructing account changes. It can corroborate settings and timing, but the buyer still needs to supply the business reason behind them.
An illustrative note might say: “Campaign B is intentionally capped while the warehouse replenishes Product B. Its historical ROAS is not permission to increase spend before the inventory owner confirms availability.” This is more useful than a generic instruction to prioritize strong performers.
Use a compact handoff packet
| Section | What belongs in it |
|---|---|
| Account identity | Platform, identifiers, owners, timezone, currency |
| Business objective | Outcome, unit economics, time horizon, constraints |
| Measurement | Conversion definitions, attribution basis, known delays |
| Campaign roles | Acquisition, retention, tests, launches, exclusions |
| Creative context | Approved claims, assets, offers, brand requirements |
| Recent changes | What changed, why, and when it should be reviewed |
| Pending work | Unresolved questions, owner, and next check |
| Authority | What may be read, prepared, recommended, or executed |
Keep the active packet concise. Link to supporting materials instead of pasting an entire archive. The operator needs the current truth and a way to inspect evidence, not a mixture of current and superseded instructions with equal weight.
Separate active rules from historical lessons
A failed test can be useful context without becoming a permanent prohibition. “This hook underperformed in a holiday campaign” is not equivalent to “never use this hook again.” Preserve the audience, offer, period, and evidence behind the lesson.
Similarly, expired promotions and former budget limits should be marked as historical. If the operator cannot distinguish active instructions from old examples, it may obey a rule that no longer applies.
Resolve conflicts before the first executable task. Use a conflict-resolution policy when the brand brief, campaign owner, and live destination disagree. Record who settled the conflict and whether the decision is temporary.
Make the first task a readback
Ask the AI operator to summarize the account in its own words: the goal, in-scope campaigns, measurement definition, immediate constraints, and the next decision it believes matters. Require it to identify unknowns.
Review that summary with the outgoing buyer. Look for incorrect account identity, confusion between gross revenue and contribution, overlooked promotions, or recommendations that contradict the campaign roles.
A good readback does not need to find a dramatic optimization opportunity. It needs to demonstrate that the operator understands the operating environment. An accurate statement that no change is justified yet can be more valuable than a speculative list of actions.
Introduce execution one task family at a time
After the readback, use a shadow-mode pilot or another bounded evaluation to observe recommendations. Decide which action family, if any, is ready for execution authority.
The permissions matrix should identify the approver and evidence required for that family. A successful report-writing task should not automatically unlock budget changes, conversion-goal edits, or account-wide launches.
Record the first executed action and verify its resulting platform state. Then compare the result with the approved proposal. This closes the handoff loop: the team can see that context was understood, authority was respected, and the intended action reached the intended account.
Retain a human owner after the handoff
Delegation changes who performs work; it does not remove business responsibility. Name the person who will review changes, answer private business questions, handle exceptions, and decide whether the operating scope should expand.
Schedule a review based on meaningful account events rather than a promise that the system is “set and forget.” New products, tracking changes, promotions, and staffing constraints can all make the original packet incomplete.
The handoff is successful when another teammate can explain why the account is configured as it is, what the operator is allowed to change, and which questions still require a business owner. Access is only the starting point.