Client offboarding checklist for freelancers and small studios

Offboarding closes the engagement, not just the project folder

Client offboarding is the administrative process of ending an engagement clearly. Confirm the service end date, record completed and outstanding obligations, reconcile financial records, check transferred responsibilities, remove unnecessary access and document what information will be retained or disposed of. Give every unfinished action an owner rather than marking the whole relationship “closed”.

Aero Workflow’s offboarding guidance for bookkeeping practices highlights notifying the relevant parties, sending the final invoice, addressing account access and reviewing the engagement terms. Those administrative principles are useful beyond bookkeeping, but professional obligations and contractual notice requirements depend on the actual service and jurisdiction.

Record the reason for closure and the obligations that survive it

A successfully completed fixed project, an expired recurring agreement and an early termination need different closure records. Name which situation applies. For early termination, review notice, unfinished work, fees, confidentiality and transfer obligations before promising a date or a final financial outcome. Seek appropriate advice if the agreement is disputed.

Keep three fields separate: delivery status, acceptance status and payment status. A completed delivery can still await client review. Accepted work can still have an unpaid invoice. A settled invoice does not prove that the work was accepted. Administrative closure should preserve those differences, not erase them.

Technical handover establishes whether the client can use and administer the deliverables. Offboarding references that handover evidence and closes the remaining administrative actions. It is not another opportunity to redefine the deliverable or assume that silence means approval.

Use an administrative closure checklist with evidence

A checklist needs more than a tick. For each action, record its owner, due date, evidence and any exception. A cancellation request awaiting provider confirmation is still open; an email saying that you intend to revoke access is not evidence that access has been revoked.

1. Confirm the engagement end date, the reason for closure and who receives the closing notice.
2. Link the delivery inventory and acceptance decisions; assign unresolved reviews or corrections separately.
3. Reconcile invoices, approved credits, payments, expenses and any deposit treatment under the agreement.
4. Confirm client ownership of accounts, files, subscriptions and renewals before withdrawing your access.
5. Remove or reduce access that is no longer needed, including contractor invitations and integrations you control.
6. Document retention purposes, applicable requirements, disposal or review dates and the responsible person.
7. Send a dated closure summary with open actions, support boundaries and the contact for financial questions.

Reconcile money without confusing the balance with acceptance

In this fictional example, illustrator Priya is closing a festival artwork engagement. Issued invoices total $4,800 USD. An agreed reduction is documented by a $200 credit, and payments received total $4,000. The remaining balance is $4,800 minus $200 minus $4,000 = $600. Taxes are excluded only to make the example arithmetic clear; that is not a tax treatment recommendation.

The closing record links each invoice, the credit and the allocated payment entries. It does not issue a second $600 charge for an amount already invoiced. The billing contact receives a balance summary and the applicable due date, while the creative contact receives the separate acceptance request.

Priya supplied artwork version 5 and the client confirmed receipt, but the authorized approver has not yet decided. Her record therefore says “delivery supplied; acceptance pending; $600 outstanding”. It names a review follow-up owner and a collections follow-up owner. No part of the balance calculation changes the delivery decision.

Where a deposit, refund or disputed expense exists, reconcile its actual contractual and accounting treatment rather than subtracting it twice. Preserve original records and use the appropriate correction process. Complex tax or accounting questions belong with a qualified adviser.

Remove access without breaking the client’s operation

Use the handover inventory to confirm that the client has a working owner account and its own recovery details. Then arrange removal of your named access and that of any subcontractors. If the client controls removal, request confirmation and keep the action open until it arrives.

Check shared folders, project portals, hosting, licensed tools and integration credentials as applicable. A password change alone may not remove separate user invitations or service credentials. Conversely, deleting a service credential without checking its dependencies can stop a live workflow. Coordinate any replacement and rotation with the authorized owner.

Cancel only services you are authorized to cancel and that are no longer required. Record who will pay for and administer any continuing subscription. If limited access is necessary for agreed support, record the purpose, permissions and review date instead of leaving full access available indefinitely.

Make a retention decision by record type, not by habit

Separate financial records, agreements, acceptance evidence, working files, personal data and access secrets. They do not necessarily share a purpose or retention period. Review applicable law, contractual duties, your role in handling personal data and any dispute or preservation requirements before setting the schedule. Client preference alone does not override those obligations.

The UK Information Commissioner’s Office explains that the UK GDPR does not specify one retention limit for every type of personal data. Retention must be justified by purpose, with review and deletion or anonymisation when information is no longer needed. This is UK-specific guidance, not a worldwide deadline; the cited page also notes that its guidance is under review.

Copyable retention entry: “Record category; purpose for holding it; applicable requirement or policy; storage location; authorized access; review or disposal date; owner; completed action and evidence.” Apply it to the records you actually hold. An archive is still retained information, not deletion.

Do not promise immediate deletion from every system unless you can deliver it. Account for local copies, collaborators, service providers and backups, explaining the actual disposal process and any justified exceptions. Keep retained information restricted and protected, and arrange expert review where the requirements are unclear.

Send a closure note that remains useful later

Copyable wording: “Our service period ends on [date]. The supplied deliverables and transfer evidence are linked here: [record]. Acceptance is [status and reference]. The financial position is [balance and records]. Remaining actions are [action, owner, date]. Support after closure follows [agreed terms]. Our record-retention arrangements are [summary and contact].”

Ask the client to flag factual errors, but do not make a reply a hidden condition that creates acceptance or changes payment terms. A polite feedback request can be separate and optional. Do not withhold a proper closure record until the client gives a testimonial or agrees to more work.

Finally, carry open balances and unresolved obligations into the appropriate follow-up process. An archived project should not make them disappear. The goal is a clear ending with accountable exceptions, not an artificially perfect dashboard.