When the Team Changes: Handing Over Account Responsibilities Cleanly

Editorial team Spend Ledger

Map what the account is for

• Describe the account’s business purpose. State which products, services, regions or campaigns it supports so the incoming owner can judge whether proposed changes fit its role.
• Record the account’s place in the wider structure. Explain how it relates to the business’s other advertising accounts, shared assets, payment arrangements and internal teams, without implying that accounts can be used to bypass platform rules.
• Identify the accountable business owner. Name the role responsible for the account’s overall use and decisions, so operational work does not become confused with approval authority.
• Clarify who can approve changes. Specify which role authorises spending, campaign launches, changes to access or billing, and responses to significant account notices.
• Separate account ownership from daily operation. Make clear who sets direction and who carries out routine work, because a person who manages campaigns may not have authority to make every business decision.
• Explain any agency or supplier involvement. Describe the agreed scope of outside support and the business contact responsible for overseeing it, so the incoming team knows where internal responsibility begins and ends.

Keep the description factual and current. If the account’s intended use has changed, record the change and check that the activity remains consistent with the platform’s policies and the business’s own commitments. Do not treat a handover as a reason to alter an account’s identity, ownership information or use in ways that conflict with platform requirements. A clear account map helps the team understand what it is responsible for before anyone changes campaigns, permissions or payment settings.

Write down the operating routine

• Document the regular review tasks. Describe what the team checks during routine account reviews, such as campaign status, spend, delivery and account notices, so important work does not depend on memory.
• Explain how campaign decisions are made. Record the business considerations behind starting, pausing or changing activity, rather than leaving instructions that invite unexplained edits.
• State how changes are recorded. Set out where the team notes significant adjustments and the reason for them, so later reviews can distinguish planned decisions from accidental changes.
• Describe the internal approval path. Identify how the person handling a campaign obtains the business approval needed for material changes, especially when those changes affect spend or customer-facing claims.
• Record routine checks that have a policy purpose. Note how the team reviews ads and destinations for accuracy and compliance, since a technically active campaign may still need attention.
• Mark tasks that should not be automated or assumed. Explain where human review is required, so recurring processes do not continue unchecked when business conditions change.

A useful procedure says what to check, who is responsible, where to record the outcome and when to escalate a concern. It should not depend on a departing colleague’s private habits or undocumented judgment. Avoid copying old instructions without review: a workflow that once suited the business may no longer reflect the current account structure, campaign goals or platform requirements. Where platform processes or available settings can change, direct the team to the platform’s current help and policy pages rather than preserving uncertain steps as permanent facts.

List open work and upcoming commitments

• Create a handover list of unfinished tasks. Include the current state, the next action and the responsible role, so work is neither abandoned nor duplicated.
• Mark decisions that are waiting for approval. Explain what has been requested and who must decide, because an unresolved choice can affect campaigns, spending or supplier work.
• Record planned campaign changes. Note what is proposed, what remains unapproved and what business reason supports the proposal, so an incoming colleague does not mistake an idea for an instruction.
• Identify renewals and recurring commitments. Document applicable service renewals, billing arrangements, creative permissions and supplier obligations, because missed administrative work can disrupt otherwise sound operations.
• Flag unresolved account or policy issues. Summarise the issue, the steps already taken and the official channel being used, so the new owner can continue the matter without starting from an incomplete account of events.
• Distinguish confirmed facts from estimates. Label assumptions clearly and direct the reader to current platform help or policy pages for values that may change.

Do not record a renewal as settled merely because it was discussed, or mark a platform concern as resolved before the platform confirms its status. If a deadline or current amount matters, verify it through the relevant official source and record where the current information can be checked. Keep the list focused on actionable work, not speculation about why a platform made a decision. If the incoming owner needs to make a judgment, provide the relevant context and evidence rather than presenting an uncertain interpretation as fact.

Transfer supplier and agency context

• List the suppliers involved and their agreed roles. Explain what each is responsible for and what remains with the business, so no one assumes that an outside party owns internal decisions.
• Keep current contact routes in the approved business record. The incoming owner needs a dependable way to raise operational questions without relying on a departing colleague’s personal correspondence.
• Summarise the written agreement. Point to the record covering scope, fees, access responsibilities, deliverables and termination or transition terms, rather than relying on informal recollection.
• Record active requests and promised work. Note what has been requested, what has been delivered and what remains outstanding, so the team can check performance against the agreed scope.
• Explain who reviews supplier work. Assign a business role to check campaign changes, invoices and relevant documentation, because delegation does not remove the need for oversight.
• Confirm that records remain accessible to the business. Store approved copies of relevant agreements and work records where authorised staff can find them, subject to applicable privacy and confidentiality requirements.

When an agency or supplier manages advertising activity, the handover should make the division of responsibility explicit. Clarify who communicates with the platform, who handles business approvals and who maintains records. Do not assume that a supplier can transfer an account or make changes that the platform does not permit. Where ownership, access or service terms are unclear, consult the written agreement and the platform’s official guidance before acting. A clean transition depends on accurate expectations, not on treating an account as a commodity that can be reassigned without regard to the applicable rules.

Assign billing oversight and financial records

• Name the role that monitors billing. State who reviews charges, payment status and billing notices, so financial attention does not disappear during a staff change.
• Explain the reconciliation routine. Describe how account activity is compared with internal finance records, because campaign performance and business spending need a shared record.
• Identify the approved source for current billing details. Direct the incoming owner to the platform’s official billing and help pages for current values, requirements and available options.
• Record the approval path for financial changes. Clarify who can authorise changes to budgets, payment arrangements or billing details, so operational access is not mistaken for financial authority.
• Document questions that finance still needs to resolve. Include the issue and its owner, rather than leaving an unexplained discrepancy for the next person to investigate.
• Keep relevant records in an authorised location. Preserve invoices, internal approvals and reconciliation notes according to the business’s recordkeeping and privacy practices.

Do not place sensitive payment details in a general handover document. Point to the approved, access-controlled record instead, and ensure the person responsible knows how to find it through authorised business processes. If the platform requires a particular billing action or verification, follow its official instructions; do not try to avoid a restriction by changing account arrangements in a misleading way. Where a charge or payment status is uncertain, record the facts available and route the question to the appropriate finance or platform support channel rather than guessing.

Show where records live and what they mean

• Identify the official storage location for account records. Use the business’s approved repository so the team can find current documentation without depending on personal devices or inboxes.
• Organise records by purpose. Separate operating procedures, campaign decisions, supplier documents, billing records and platform correspondence, making it easier to locate the evidence relevant to a task.
• Explain the naming and filing conventions. Give a brief guide to how records are labelled, so the incoming owner can distinguish current material from drafts or superseded notes.
• Link decisions to supporting context. Preserve the business rationale, approval and relevant source for significant changes, because a bare change log may not explain why an action was taken.
• Mark obsolete material clearly. Retain records when required, but indicate when instructions no longer apply so outdated guidance is not mistaken for current policy.
• Limit access to people with a legitimate role. Follow the organisation’s security and privacy practices, since a handover should improve continuity without exposing information unnecessarily.

The record set should help someone understand the account without collecting more sensitive information than the role requires. Do not copy credentials, private payment data or identity documents into working notes. Instead, document the approved process for requesting access or completing a required check. Keep records factual: distinguish what the platform has stated from the team’s interpretation, and retain the original notice or official correspondence when appropriate. When platform details may have changed, use the platform’s own help and policy pages as the current reference.

Set up responsibility for platform notices

• Assign a role to monitor official account communications. State who checks the relevant business channels and who covers that duty when the primary contact is unavailable.
• Explain how notices are triaged. Describe how the team identifies the subject, urgency and required action, so important messages are not treated as ordinary campaign updates.
• Record the response path for policy or access concerns. Direct the responsible person to the platform’s official support and appeal channels when those are appropriate.
• Preserve the notice and the response. Keep the original communication, submitted information and follow-up in the approved record location, because a clear history supports accurate continuity.
• Escalate uncertain or consequential messages. Route them to the designated business owner, legal or compliance contact, or other appropriate role rather than improvising a response.
• Keep responses accurate and consistent. Use verifiable information and correct the underlying issue where possible, because unsupported explanations can make a difficult matter harder to assess.

A handover should not encourage a colleague to work around an account restriction, verification request or platform decision. Do not conceal a connection between accounts, misstate who operates the account or submit inaccurate material. If a platform requests information, follow its stated process and provide truthful, relevant information through the official channel. If the team does not understand a notice, preserve it and seek guidance through the platform’s official support resources. The new owner should know both who is responsible and what boundaries apply before responding.

Confirm the transition and review it

• Walk through the handover with the incoming owner. Discuss the account map, open tasks and escalation routes so the written record is understood rather than merely filed.
• Check that responsibilities have been accepted. Confirm who now owns each operational, financial and communication duty, because an unassigned task can be missed even when it appears in a document.
• Test access through authorised processes. Ensure the incoming role can reach the necessary business records and platform functions without sharing credentials or bypassing access controls.
• Record unresolved gaps. List missing information, unclear authority or outstanding platform matters, and assign each to a responsible role for follow-up.
• Review the handover after the role change. Check that routines and contact details remain accurate once the new owner has taken over, since a transition can reveal omissions that were not obvious beforehand.
• Keep the departing person’s knowledge in the record, not as a hidden dependency. Capture relevant context in approved documentation so ongoing work does not rely on informal access to someone who has left the role.

A clean handover is complete when the business can explain the account’s purpose, find its records, identify the next actions and know who is accountable for each responsibility. It does not require every uncertainty to be resolved immediately, but it does require uncertainties to be visible and assigned. Keep the process within the platform’s rules and the organisation’s security practices. Treat the advertising account as a work tool governed by its applicable terms, not as a transferable shortcut around review, verification or access requirements.