Client Offboarding Checklist for Agencies That Deliver Video
A nine month video retainer can leave seventy odd live review links and a pile of stale members behind. Here is the offboarding pass I run at my own agency, in order, with a worked two week example.
Seventy two review links is roughly what one nine month video retainer leaves behind in a workspace, right. Nine months is about thirty six weeks, and at two videos a week every deliverable got its own share link. That one number is basically why I take a client offboarding checklist for agencies as seriously as the intake call, because seventy two links means seventy two open doors into work the brand already paid for.
Stack three or four versions on each of those cards and you are sitting on something close to two hundred and fifty files that nobody will open again. Then add the people, right, the freelance colourist from one campaign, the account lead who moved on, the client side manager who got promoted out of the brief, and so on, until your workspace is full of members you no longer work with.
To be very honest, I did not lift this from a template on somebody's blog. Former clients do come back, sometimes most of a year later, asking for the approved cut of one spot, and the first time it happened to me I had no clean answer, which felt really really bad. So here is the client offboarding process I run at my own agency, in order, with the PlayPause settings I touch and a worked two week example near the end.
Why offboarding matters as much as onboarding
Everybody in this industry obsesses over the start, right, the kickoff call, the brief, the folder structure, and I have covered that side in the onboarding checklist that stops scope creep. The difference is that at the start a client is patient with you, and by the end they are already comparing you to whoever comes next, so the exit is where your reputation quietly leaks.
The leak I worry about most is the forgotten share link, a file sitting on the open internet with a brand's unreleased campaign inside it long after anybody remembers it exists. The expensive one, though, is the referral, right, because a client who leaves confused tells the next agency owner you were disorganised, and a client who leaves with a tidy handover tells them you were the professional in the room.
So I treat the wind down as a defined phase with an owner and a date, the same way a project management plan treats closure as its own stage. In my agency the account lead owns it, it gets a calendar slot the week after final delivery, and it is not done until somebody ticks the last item.
Deliver the final and confirm approval on record
The first item is the boring one, and it is the one people get wrong most often, right. Before you ship anything, pull up the original scope and check every deliverable against it, for instance the hero film, the cutdowns, the vertical versions and the caption files, because a missing 9:16 cutdown found after you close down means reopening a project the client thinks is finished.
Then ship the final into the same project card the whole job lived on, not a fresh folder and definitely not an email attachment, because the moment the deliverable leaves the review trail you lose the reason it looks the way it does. In PlayPause the versions stack as MV1, MV2, MV3, MV4 on one card, so the approved cut sits on top with every earlier round underneath, and the frame-accurate comments that produced each change stay on the exact frames they were written on. On Agency, side-by-side version compare lets the client check MV3 against MV4 before signing, and if you owe caption files, AI transcription exports an SRT from the approved version.
Set a custom status on that final card so anybody opening the workspace in a year reads the word approved rather than guessing from a file name. If the sign off arrived as a comment, which is how it usually goes, it is already in the thread with a name and a time against it, and that thread works a lot like version control does for code, where the history becomes the documentation. I also raise the final invoice the same day and put the version number on the invoice line, so the commercial close and the creative close point at the same file.
The final lives in an email thread and the approval is a thumbs up emoji nobody can find eight months later.
The final is MV4 on the same card, marked approved, with the full comment history sitting right underneath it.
The catch here is that you have to do this before the relationship cools, because chasing a written approval from a client who has mentally moved on is genuinely painful. I go further into it in the piece on keeping the approval trail intact, and the short version is that the trail is worth more than the file.
Revoke client access to links, members and shared tools
The part that made me write this whole thing is revoking every share link attached to that client, right, one by one, on the day you planned to, because putting it off to next week is exactly how a workspace ends up with seventy odd live links.
PlayPause revokes a link instantly, so the URL stops working the second you kill it, and every plan lets you password protect links, which is worth doing for anything unreleased while the job is live. How long a link lives on its own depends on your plan, and that matters at offboarding more than most people expect.
On Creator the files expire with the link after 30 days, while Enterprise links never expire, which is lovely during the work and is exactly why the manual revoke matters after it.
Then walk the member list, right, because pricing is flat per workspace rather than per person, so nobody ever feels the cost of leaving one extra freelancer invited. Remove whoever rolled off, and step down anybody internal who no longer manages that client, since the roles run Owner, Admin, Manager and Editor and your workspace does not need four Admins left over from the busy months. If that client's comments were posting into a Slack channel, archive the channel too.
Revoking access also runs the other way, which most templates skip. Over a long retainer your team collects access to the client's world, for instance their brand folder on Drive, the ad account where the cutdowns went live, a login to their asset library, and all of it should be handed back in the same sitting, with the client resetting any shared passwords. The access model is covered in the guide to secure video sharing across many clients, and the controls themselves sit on the sharing and security page.
Hand over the client Playbook as a no login page
This is the item almost nobody has on their list, and it is the one that turns a decent exit into a referral, right. Every client you keep for more than a month builds up rules, say the brand never uses a hard cut on the logo sting, the founder hates being framed centre, captions always sit above the lower third, and so on. Those rules live in your editors' heads and in scattered chat messages, and when the client leaves they evaporate unless somebody wrote them down.
Playbooks on Agency and above are a per client document of creative style and direction, with brand playbooks for the permanent rules, folder playbooks for a single campaign, and checklists that are not done until somebody ticks them. At offboarding the useful bit is that a Playbook can be shared as a page with no login, so the client opens it in a browser and their next agency or in house team inherits the accumulated taste instead of rediscovering it over four painful rounds.
Think of it as the closing counterpart to a creative brief, right, because the brief says what we are about to make and the Playbook says what we learned while making it. I'm pretty sure this one habit has brought my agency more repeat work than anything else on this list, since handing over the rules reads as confidence. The page on how PlayPause works for creative agencies shows how that per client structure holds up across a whole roster.
Frame-accurate note, everyone sees the exact same thing.
Back up the project before you archive it
Before anything gets archived, get the deliverables somewhere the client controls, right. On Agency and above the Google Drive integration lets viewers save straight to their own Drive and gives you a backup path for the folder, so the finals land in the client's world without you zipping up 60 GB and praying a transfer service holds the download open. I explained why those tools keep failing agencies in the piece on a better way to deliver final videos.
Decide the raw footage question here too, in writing, because the awkward version of that conversation happens eleven months later when the contract turns out to be vague. My own policy sits in the post on whether clients should get raw footage, and whatever you land on, settle it before the relationship ends.
If the retainer ends and you move to a smaller plan, the projects, the versions and every comment stay in the workspace, so you can archive calmly instead of worrying about what disappears.
Does that make sense, right, because plenty of agency owners keep paying for a bigger plan out of fear that scaling down will wipe a client history they might need one day, and that is simply not how it works here.
Close the loop with a final handoff email
The last item on my project handoff checklist is one short email. It confirms the final by its version number, restates what was delivered and where it now lives, links the Playbook page, gives the date the project gets archived on your side, and thanks them like a human being rather than like a closed ticket. I also ask one question, what should we have done differently, because a single honest answer from a departing client teaches me more than a long survey.
The last email a client gets from you is the one they quote when somebody asks them who to hire next.
One small trick comes from the who-watched analytics on Creator and above, which show who opened the final link, when and from which city. Before the closing email goes out I check whether the brand director ever watched the final, and if they did not, I mention the link once more instead of assuming silence means satisfaction. The post on the agency to brand video handoff covers what causes last minute chaos, and when several wind downs overlap, managing every project in one place is how I see which ones are genuinely closed.
The client offboarding checklist for agencies, worked over two weeks
Here is how this end of project checklist for video plays out on that nine month retainer, using the days I actually block in the calendar, and you see what I mean here, the hands-on work is small, it just has to happen in the right order.
- Day 0: the client approves MV4 in a comment, the card moves to approved, and the final invoice goes out with the version number on it.
- Day 1: the Playbook gets its last update and the raw footage decision goes over in writing.
- Day 2: the deliverables land in the client's Drive and the handoff email goes out with the archive date.
- Day 14: every review link is revoked in one pass, stale members come off, and shared logins are handed back.
- Day 30: a last look at who watched the final, then the project is archived.
- Ship the final version and mark it approved
- Revoke every live review link for that client
- Remove members and freelancers who no longer belong
- Share the client Playbook as a page with no login
- Back the folder up so the client holds a copy
- Send the handoff email with the archive date in it
Trust me on any level, the first run feels slow, and by the third departing client it becomes a routine your account lead runs without you, which at the end of the day is the whole point. Aditya Kumar wrote on Trustpilot, "Must have tool for professionals in 2026. Reviews, feedback and file sharing super streamlined for our clients at my agency." File sharing only stays that streamlined, right, if somebody also closes it down cleanly when the work is over.
Frequently asked questions
How long after final delivery should I revoke the review links?
I give it two weeks, right, because clients often circle back with one small internal request in the first few days, and killing every link on day one makes you look rigid. On day fourteen I revoke everything in one pass, and if the client genuinely needs ongoing access to the final file, I send a fresh single link for that one deliverable rather than leaving the whole review history open.
What if the client asks for a file a year after we finished?
This is exactly why the archive step exists. Downgrading never deletes content, so the project, its versions and its comments are still sitting in your workspace, and you just open the card, find the approved version and send one new share link. It takes a few minutes instead of an afternoon of digging through old hard drives, and the client remembers you as the organised one.
Should I hand over the Playbook to a client leaving for a competitor?
I do, every time, even though it stings a little, because the creative rules belong to their brand and withholding them buys you nothing except a bad story told at dinners. What you actually keep is the judgement behind those rules, which never travels in a document anyway, so handing it over cleanly is the cheapest reputation insurance an agency owner can buy.
Which plan do I need to run this whole checklist?
Link revoking, password protection, member roles and custom statuses work on every plan, and the who-watched check starts on Creator. Playbooks, the Google Drive backup, SRT export and side-by-side compare start on Agency, which at $19 a month is where most agencies running several clients end up. White-label pages or a custom share domain for the handover are Enterprise territory.
If you want to see which plan fits the number of clients you offboard in a year, read the plan breakdown on our pricing page, start the 7-day free trial on whichever one matches your member count, and run your next departing client through this list before you commit to anything.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free