Client offboarding agency work is one of the least-glamorous parts of running a retainer business — and one of the most consequential. At Choco Media, we learned the hard way that a poorly handled handover doesn’t just create friction at the end of an engagement; it damages the memory of everything that came before it. Clients who leave well tend to refer. Clients who leave confused tend to write Google reviews.
This post is for agency owners, account managers, and anyone who has ever watched a client’s eyes glaze over during a final call because nobody could find the assets, the logins, or the explanation of why the campaign was set up the way it was. We’ll walk through the exact handover document we use, why each section exists, and the mistakes we made before we built this process.
If you’re currently running retainer engagements without a formal offboarding structure, this is the template to start with. It takes about three hours to complete properly and saves everyone — including you — from weeks of follow-up emails.
Why most agency offboarding fails
The most common reason client handovers go badly is timing. Most agencies start thinking about handover documentation on the last day of the engagement, which is also the day when everyone is already mentally elsewhere. The client is excited (or anxious) about what comes next. Your team is moving on to the next project. Nobody wants to spend four hours writing documentation when the relationship is functionally over.
The second reason is scope creep in reverse. Handover documents grow to include everything that was ever discussed, every asset ever created, every decision ever made. By the time it lands in the client’s inbox it’s 47 pages of information architecture they’ll never read and can’t search.
We’ve found a different approach works better:
- Start the handover document in week one of the engagement, not the last week
- Write for the person who will inherit the work, not the person you’ve been working with
- Keep it under 12 sections with one page per section maximum
- Distinguish between what’s essential to operate and what’s nice-to-have context
The goal isn’t completeness. The goal is operability — can someone competent pick this up and run it without a 90-minute briefing call?
The structure of our handover document
Our template lives in Notion, though it transfers cleanly to Google Docs or a PDF. We share it with the client as a live link so they can comment and flag gaps before the final call. Here’s the full structure:
Section 1: Engagement summary
One page. What did we actually do together? What were the original objectives, and how did they shift over the engagement? What were the main wins and the main constraints?
This section exists not for documentation but for memory. In six months, when someone at the client company wonders why the website looks the way it does or why the ad account is structured around three campaigns instead of one, the engagement summary gives them the context to understand decisions rather than just reverse them.
Section 2: Assets and access
This is the most critical section and the one most agencies handle worst. We list every account, platform, and file location with the following structure:
- Platform name — the specific tool (Google Ads, Meta Business Suite, Hotjar, etc.)
- Access method — direct login, shared access, agency seat being transferred
- Current account holder — whose email owns the account
- Action required — what the client needs to do before or after handover (transfer ownership, add billing, revoke our access)
- Status at handover — active, paused, archived
We also include a checklist the client signs off on: every item confirmed as transferred before the engagement officially closes. This protects both sides — we’ve had situations where a client assumed we still had access two months later and were actively managing campaigns that had been handed over.
Section 3: Current performance baseline
What were the numbers when we handed over? Not the peak numbers from the best month. The current numbers. Traffic, conversion rate, cost per acquisition, average position in search, email open rate — whatever was relevant to the work we did together.
This section gives the client (and their next agency or in-house team) a baseline to measure from. Without it, every new partner arrives with no benchmark and has to spend weeks figuring out whether the current state is good, bad, or about to fall off a cliff.
Section 4: What’s working and why
The most underestimated section. Most handover documents list what was done. Fewer explain why it’s working. We try to write one paragraph per major active strategy or asset that answers: what is this, why does it work, and what would break it?
For example: “The awareness campaign on Meta is running to a lookalike audience built from purchase data. It’s working because the creative matches the visual language of the landing page — if you change the landing page significantly, expect performance to drop until you refresh the creative to match.”
Section 5: What’s fragile
This is the section most agencies skip because it feels like admitting failure. We include it because it’s honest and because clients who understand the fragile parts of their setup are less likely to accidentally break something and more likely to prioritize the right fixes.
“The landing page conversion rate depends heavily on the current checkout flow. If payment processing changes or a new step is added, run an A/B test before rolling out to 100% of traffic. We’ve seen a single extra field drop conversion by 18% in a similar client work.”
Fragile areas we commonly document include: ad accounts that rely on audience sizes close to the minimum threshold, SEO positions held by a single well-linked page, email automations with complex branching logic that hasn’t been QA’d in six months, and any tracking setup that depends on a specific URL structure.
Section 6: The content and campaign calendar
If we were producing content or managing campaigns, we hand over a 90-day forward calendar with everything we had planned. Even if the client decides to go a different direction, seeing what was coming helps them understand the strategic logic — and sometimes they continue with it.
We also include the briefing templates we were using. If there’s a prompt library, a creative brief format, or a reporting template we built during the engagement, it goes here. These are often the most practically useful assets a client walks away with, and they’re easy to miss in a handover because they live in our internal systems rather than in deliverable files.
The access transfer checklist
Separate from the document, we run a 12-item checklist in the final two weeks of every engagement. These are the items that require action rather than documentation:
- Client has admin access to all ad accounts (not just view access)
- Billing for all tools has been transferred to client payment method
- Agency team members have been removed from client Google Analytics, Search Console, and Tag Manager
- Domain access and DNS records have been confirmed (not just assumed)
- Any API integrations are using client-owned keys, not agency keys
- Email sending domain authentication (SPF, DKIM) is set up on client domain
- Social media accounts have no lingering agency admin roles
- All creative assets are in a client-owned storage location (not a shared drive only we can access)
- Any automated workflows (Zapier, Make, n8n) are running on client accounts or have been transferred
- Passwords for any shared accounts have been rotated since our team had access
- Client has been introduced to any third-party vendors we brought in during the engagement
- Contracts with third parties have been reviewed for transferability
We go through this list on a call with the client, not in an email thread. Doing it synchronously means gaps get caught in real time rather than surfacing three months later when something breaks.
What to include in the final call
The handover call is not a presentation of the document. The document is already with the client. The call is for questions, gaps, and transition planning. We keep it to 60 minutes with a fixed agenda:
- 15 minutes: walk through what’s working and why (Section 4)
- 15 minutes: walk through what’s fragile and what to watch (Section 5)
- 15 minutes: open questions from the client on any section
- 15 minutes: next steps, who to contact if something breaks, and the access checklist confirmation
We send a summary email within 24 hours confirming what was discussed and noting any outstanding items. This becomes the final record of the engagement and the starting point for any future re-engagement.
How this connects to referrals
We track where new clients come from, and referrals from past clients account for a significant share of new work — around 60% in recent years, which we covered in more detail in our post on building a referral engine. The pattern we’ve noticed: clients who go through a formal offboarding process refer more, and they refer faster.
Our theory is that a well-handled handover signals something to the client even after the commercial relationship ends. It says: we were professional throughout, we respected your time, and we cared about the outcome more than the invoice. That’s a harder signal to fake over a two-year retainer than over a single project, but the handover is the last impression — and it tends to stick.
There’s also a practical element. A client who has a clean handover document can actually explain what we did when talking to a peer who needs similar help. A client who is drowning in a disorganized file dump cannot.
Common mistakes we’ve made and fixed
We’ve improved this process through failure. The main ones:
- Starting too late. We now open the handover document at the start of every engagement and update it monthly. The final version takes 90 minutes to complete, not 8 hours.
- Writing for ourselves, not the next team. Early versions of our handover documents assumed the reader knew what we knew. We now read every section and ask: “Would this make sense to a capable marketer who has never seen this account?”
- Skipping the fragile section. We used to only document what was working. The fragile section was added after a client changed their URL structure post-handover and lost a significant share of organic traffic overnight. We hadn’t flagged that the SEO was dependent on those URLs.
- Not confirming access in writing. We had a situation where a client’s billing for a tool was still on our company card six months after handover. The access checklist with client sign-off stopped that from happening again.
Adapting the template to different engagement types
Not every engagement produces the same kind of handover. We adjust the weight of each section depending on what we actually delivered:
- SEO-focused engagements — more emphasis on content architecture, internal linking structure, and which pages hold the most authority. Useful to include a list of pages not to delete or significantly restructure.
- Paid media engagements — the access transfer checklist becomes more complex. Ad accounts, pixel ownership, custom audiences, and conversion tracking all require explicit action items. Our paid media service covers how we structure campaigns, which gives context for what needs to transfer.
- Brand and identity engagements — a separate brand kit delivery document goes alongside the handover. Font licenses, color system documentation, logo usage guidelines, and the rationale behind key decisions all go in the brand kit rather than the handover document itself.
- Full-stack retainers — the handover is longer but follows the same structure. We split it into parallel tracks (content, paid, SEO, brand) with a master summary at the top.
If you’re thinking about how this fits into a broader client relationship model, our post on managing client expectations in a retainer covers the communication rhythm that sets up a clean handover from the start.
The one-page version
For shorter engagements — a brand sprint, a single campaign build, an audit — the full 12-section document is overkill. We use a one-page format instead:
- What we did (3 bullet points)
- What to do next (3 bullet points)
- Assets and access (table: platform, login method, current status, action required, by when)
- One number to watch (the single metric that tells them whether the work is holding)
This takes 30 minutes to write and covers 80% of what a client actually needs for a contained engagement. The goal is the same: leave them able to operate without us, and leave them with a clear memory of what the work was for.
If you’re building this process from scratch and want to talk through how it fits your engagement model, our contact page is the fastest way to start a conversation — we’re happy to share the full Notion template with agencies who are figuring out their own client offboarding agency workflow.