Back to all articlesAgency customer operations

Onboard a Client Moving From Another Agency Without Inheriting Assumptions

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

All scenarios and examples in this article are fictional and hypothetical.

The previous agency’s report says a campaign is ready. A task board says it is awaiting approval. The client remembers being promised a launch, but nobody can locate the approved version. Receiving all three records does not tell your team which one to follow.

Start by classifying consequential inherited assets and commitments as confirmed, disputed, obsolete, or awaiting a named client decision. Then agree on a provisional operating baseline: what continues, what stays paused, and what decision would change that position.

The objective is not to prove the previous agency wrong. It is to stop historical habits and unfinished work from becoming current instructions by default. This checklist covers incoming-agency responsibility and acceptance of inherited work, not technical account transfers or data migration.

1. Separate receipt, authority, acceptance, and release

A handover folder establishes that something exists. It does not establish that the client still wants it or that your agency has agreed to deliver it. Keep four questions separate:

  • Receipt: What arrived, and which version is it?
  • Authority: Who can establish the current client instruction?
  • Acceptance: What work has your agency agreed to undertake, with what boundaries?
  • Release: Who can authorise publication or another external action once its conditions are met?

Assessment is one possible accepted action, not a promise to finish the item. In a hypothetical case, your team might agree to inspect a landing-page draft and propose revisions without accepting its launch date.

Record the item’s status separately from the agency’s next action. Otherwise, a task labelled “review inherited campaign” can quietly become “finish and launch inherited campaign.” If accounts conflict about past commitments, preserve that disagreement rather than attempting to settle it through the production schedule. Establish the current instruction separately.

2. Define the four statuses before reviewing the backlog

Shared definitions prevent “confirmed” from meaning “we found a file” to one person and “approved for publication” to another.

  • Confirmed: A named client authority has established the current instruction, and your team has recorded the work it accepts. Specify the version and boundaries.
  • Disputed: Material accounts conflict. Record the competing positions and identify what decision is needed now.
  • Obsolete: A named client authority has confirmed that the item no longer governs current work. Retain useful historical context without keeping it in active instructions.
  • Awaiting a named client decision: Direction is insufficient, but there is no established conflict. Name the decision-maker, question, and response checkpoint.

Apply status to the stated item, not everything surrounding it. A report layout can be confirmed while its metric definitions remain disputed. A creative concept can be approved while its production budget remains undecided.

Avoid “pending” without explanation. It hides whether the blocker is evidence, authority, or capacity. Silence should leave the recorded interim action in place, not turn an unresolved item into an accepted commitment.

3. Build a register around decisions, not file counts

Start with items that could change external activity, spending, deadlines, client expectations, or the interpretation of results. An exhaustive file inventory can wait if it would delay those decisions.

Use these reusable fields for each material item:

  • Item and exact version or reference.
  • Evidence received, including gaps and conflicting accounts.
  • Status.
  • Named client decision-maker and incoming-agency owner.
  • Decision requested or action accepted.
  • Interim action and boundaries.
  • Review checkpoint, including a fallback when another decision is a dependency.

A checkpoint needs a consequence. “Review after creative approval” is incomplete if creative approval never arrives. Add a dated fallback and state whether the item stays paused, moves out of the active schedule, or goes to another named authority.

Confirm who can decide each question. A client contact may approve a report layout but lack authority for additional spending. If authority is unclear, resolving that ownership is the next task—not guessing the answer to the underlying request.

4. Worked example: a filled takeover checklist

Fictional worked example: Harbor Studio is taking over marketing work for Cedar & Field. All names, assets, commitments, and timings below are hypothetical. Maya Chen is the client marketing lead; Daniel Ortiz owns the client budget; Priya Shah leads the incoming agency. “Day” means a working day after the takeover meeting. The checkpoints are illustrative, not service standards.

This filled register can be reused by replacing the item, evidence, owners, decision, interim action, and checkpoint in each entry.

  1. Monthly report layout — CONFIRMED.
    Evidence: the previous report and Maya’s written request to retain its layout for the next reporting cycle.
    Client decision-maker: Maya.
    Agency owner: Priya.
    Accepted action: produce the next report in that layout, marking unresolved metric definitions.
    Boundary: layout confirmation does not validate historical calculations.
    Checkpoint: review at the first report meeting, or day ten if that meeting slips. If the report is not ready, Priya presents its structure and outstanding questions on day ten.

  2. “Qualified enquiry” definition — DISPUTED.
    Evidence: report notes describe submitted enquiries; Maya says sales-accepted enquiries were intended.
    Client decision-maker: Maya, after consulting the client sales lead.
    Agency owner: Priya.
    Decision requested: choose the future reporting definition; Priya will show which comparisons it affects.
    Interim action: keep the measures separate rather than present a continuous trend.
    Checkpoint: day three. If unresolved, retain separate labels and ask Maya to set a new decision date at that checkpoint.

  3. Campaign creative, version C — AWAITING CLIENT DECISION.
    Evidence: the folder labels C as final, but the approval message identifies B.
    Client decision-maker: Maya.
    Agency owner: Priya.
    Decision requested: approve C, request specified changes, or retire it; Priya will summarise differences from B.
    Interim action: no production or release using C.
    Checkpoint: day two. If unresolved, keep C paused and move dependent production out of the active schedule.

  4. Inherited launch commitment — DISPUTED.
    Evidence: Maya recalls a promised launch; the outgoing board shows approval outstanding.
    Client decision-maker: Maya.
    Agency owner: Priya.
    Decision requested: Maya may issue a new instruction stating current priority, preferred timing, and creative choice without resolving the historical disagreement. Record the conflicting historical accounts separately.
    Accepted action: Priya assesses feasibility, dependencies, and capacity after that instruction. The revised launch becomes confirmed only when Harbor accepts the defined delivery instruction; release conditions remain explicit.
    Interim action: do not treat the inherited date as accepted.
    Checkpoint: immediately after the creative decision, with a fallback on day three. If creative remains unresolved, keep launch unconfirmed and ask Maya to choose between continued pause and a smaller, separately assessed brief.

  5. Additional video production — AWAITING CLIENT DECISION.
    Evidence: an unfinished storyboard and estimate, but no current spending instruction.
    Client decision-maker: Daniel.
    Agency owner: Priya.
    Decision requested: authorise a defined production scope or remove it from the active plan; Priya supplies a bounded proposal.
    Interim action: preserve the storyboard; commission nothing.
    Checkpoint: day four. Without a decision, remove production from the active schedule and notify Daniel that a later start requires reassessment.

  6. Retired seasonal offer sheet — OBSOLETE.
    Evidence: Maya confirms the offer has ended.
    Client decision-maker: Maya.
    Agency owner: Priya.
    Accepted action: mark it historical and remove it from active creative references.
    Boundary: retain it only to interpret earlier activity.
    Checkpoint: inspect the next production brief, or review the active reference list on day five if no brief exists. Remove any active reference found and flag any affected draft to Maya before further work.

  7. Weekly client status meeting — CONFIRMED.
    Evidence: Maya requests continuation and Priya accepts it within the operating plan.
    Client decision-maker: Maya.
    Agency owner: Priya.
    Accepted action: circulate decisions, blockers, and next actions after each meeting.
    Boundary: attendance does not confer authority to approve every type of work.
    Checkpoint: review usefulness after the first reporting cycle, or day twenty if that review slips. If postponed, Maya and Priya retain the current cadence and set a replacement review date on day twenty.

  8. Unfinished landing-page copy — AWAITING CLIENT DECISION.
    Evidence: two drafts contain different offers, with no preferred version identified.
    Client decision-maker: Maya.
    Agency owner: Priya.
    Decision requested: choose the current offer; Priya then identifies reusable passages and proposes revision work.
    Interim action: assessment only; no revision or publication commitment.
    Checkpoint: day three. If unresolved, keep copy revision unscheduled and tell Maya which downstream work remains blocked.

5. Convert the register into a provisional operating baseline

The register holds detail; the baseline gives the delivery team a short working instruction. For the hypothetical takeover, Priya could propose:

  • Continue the status meeting and retain the report layout.
  • Show unresolved reporting definitions separately.
  • Keep campaign release, video production, and copy revision out of the active schedule until their recorded conditions are met.
  • Remove the retired offer from active references.
  • Review unresolved decisions at the listed checkpoints and resequence dependent work when necessary.

Ask Maya to confirm the baseline explicitly. Record its version, confirmation date, and next review date. Identify which earlier working assumptions it replaces and which questions remain unresolved.

This allows low-ambiguity work to proceed without hiding uncertainty. If the client disagrees with a pause, discuss the particular dependency and available alternative rather than asking for blanket approval of the backlog.

6. Use staged acceptance where uncertainty matters

Staged acceptance means assessing material, identifying reusable parts, proposing the remaining work, and accepting a bounded delivery instruction. Use it where incomplete approvals or uncertain quality could materially change effort or timing.

The trade-off is real: assessment takes time, and the client may believe the work is nearly finished. Make the decision concrete. In the hypothetical example, Priya can offer to reuse the landing-page structure once Maya chooses the offer, rather than either discarding the draft or accepting an unsupported completion date.

Do not apply the same review burden to everything. A confirmed meeting cadence needs less scrutiny than a disputed launch. If speed matters, propose a smaller deliverable with fewer dependencies, identify exclusions, and assess that brief. A reduced scope still needs an achievable instruction; urgency is not evidence that the inherited schedule works.

7. Handle newly discovered commitments without rewriting history

A late email or newly surfaced promise should trigger a targeted review:

  1. Capture the evidence: preserve the relevant version and describe what it changes.
  2. Identify affected work: check production, spending, reporting, and client expectations.
  3. Contain the impact: pause the affected action where appropriate, not unrelated work.
  4. Request direction: give the named client authority the conflict, options, and practical consequences.
  5. Update the baseline: record any new instruction, agency acceptance, and revised sequence.

If your team already acted on an unsupported assumption, state what happened, what remains reversible, and the proposed correction. Preserve the earlier record rather than changing its status retroactively.

Repeated surprises suggest a missing class of evidence. Ask specifically for approval messages or current work requests instead of requesting another undifferentiated folder dump.

8. Check whether the takeover is becoming clearer

At each review, count material items missing a decision-maker, agency owner, interim action, or checkpoint. List overdue decisions separately from decisions whose dependencies are still unresolved. That distinction tells you whether to request an answer, clarify ownership, or change the work sequence.

Also inspect accepted work for inherited dates that entered the schedule without feasibility review. Check whether obsolete references have disappeared from new briefs and whether disputed reporting measures remain visibly separate.

The practical test is whether someone outside the handover meeting can identify what the agency will do next, what remains blocked, and who can change that position. If they cannot, improve the instruction—not merely the amount of documentation.

Agency operationsClient onboardingClient handoversScope management

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications