Resources · automationagenciesoperations
Agency client offboarding automation - close access without loose ends
Agency client offboarding automation should make the last week clear, not cold. Use one handover ledger to list access to revoke, assets to transfer, recurring work to stop, data to retain, and the client receipt. A human confirms every row before credentials disappear.
The goal is a clean close. Former clients should not be left wondering who owns a domain, a report, or a file after the final invoice.
What should an agency offboarding ledger include?#
The ledger is the operational artifact. It gives the account manager, delivery lead, and client one shared view.
| Area | Record | Human check |
|---|---|---|
| Access | Tool, account, permission, and revocation date | Is the client able to take over first? |
| Assets | Folder, campaign, creative, documentation, and new owner | Has the transfer link been tested? |
| Recurring work | Report, scheduled task, subscription, or automation | Should it stop, transfer, or continue briefly? |
| Retained data | What the agency keeps and why | Does the contract allow that retention? |
| Open work | Remaining decision, owner, and due date | Does the client know what is still open? |
| Final receipt | A plain summary sent to the client | Did a person approve the wording? |
This is the reverse of client onboarding. Onboarding proves the team has what it needs to start. Offboarding proves the client has what it needs to continue without you.
When should access actually be removed?#
Remove access after the handover has been checked, not when someone sends a cancellation email. A client may need a final export, an owner change, or a replacement login. A rushed revocation can create a security problem and a trust problem at the same time.
Set a final review with an account owner. The reviewer confirms the transfer link works, the last recurring jobs have a decision, and no open work is hidden in a private task list. The final receipt tells the client what happened in plain words.
How does the offboarding build actually go?#
We begin by listing the accounts and assets the agency touches for one client. We group them into the ledger above and name a human owner for each group. The client keeps the completed ledger and the final receipt.
The build can collect the usual records from the project tool, shared drive, and recurring-job list into a draft ledger. It can also prepare reminders for rows that still have no owner. It does not delete accounts, transfer ownership, or cancel a subscription on its own.
Before it runs for a live departure, we shadow it against a closed client account. The team compares the draft ledger with what really happened. Missing shared folders and forgotten scheduled reports are the checks that matter. Then the account owner approves the final client-facing receipt and the access changes happen in the agreed sequence.
A strong project handover makes the final close easier because it records the original owners and source links from day one. For recurring reports and tasks, use the same inventory from agency recurring work so nothing continues without a decision.
What should you check before the next client leaves?#
Pick one former client and try to answer three questions: which access was removed, which assets moved, and which recurring jobs stopped. If the answers live in five tools or one person's memory, make a handover ledger before the next notice arrives.
Where does this fit with the rest of the operation?#
The same handoff discipline appears in automating your best thinking: write the decision rule down before a system acts on it. If the close is still small and unusual, building it yourself or hiring helps sort whether a checklist is enough.