Client Offboarding Checklist for Freelancers: Final Files, Access, and Acceptance

Client offboarding is the process of closing an engagement deliberately: confirming the accepted work, delivering the agreed files, assigning any remaining actions, and deciding what happens to access and records.

The checklist should leave both you and the client with the same understanding of what is finished and what continues. Use the contract, agreed scope, and applicable requirements as inputs. The workflow below helps organize those decisions; it does not supply legal, tax, or retention terms for your business.

Copy this client offboarding checklist

Keep passwords, recovery codes, payment details, and unrelated client data out of the checklist. Use the appropriate secure account and file-sharing processes for material that needs them.

Start with acceptance, not a tidy folder

A folder containing the latest files does not necessarily establish that the client accepted the work. Record the actual acceptance decision or the remaining condition under the agreed process.

For example: “The final guide is accepted; the client will replace two internal screenshots by the agreed date.” That is different from marking the whole project complete while assuming someone will remember the screenshots.

Keep a remaining task visible even if the main engagement is ending. Name its owner, deadline, and the evidence that will close it. If the remaining work changes the agreed scope, resolve that through the appropriate business process before promising it.

Deliver files someone else can navigate

Make a short handoff index rather than sending a pile of attachments with no explanation:

Engagement and final delivery date:
Accepted deliverables:
Final file locations and versions:
What each file is for:
Instructions or dependencies needed to use it:
Open actions and owners:
Support or follow-up arrangement, if agreed:
Person to contact for questions:

Use the delivery format and location the parties agreed. Check links and permissions with an appropriate authorized recipient. “Uploaded” and “received in a usable form” are separate points in the handoff.

A short walkthrough may be useful for a complex deliverable, but agree it as part of the handoff. Do not assume the client needs a new training package after the project is already being closed.

A fictional example: closing a small website-content engagement

A freelancer has delivered approved copy and a content inventory. The client will implement the copy through its own team.

The closing record might say:

• Approved copy is in the final document at the agreed location.
• The inventory identifies each destination page and its corresponding text.
• The client owns implementation and the final live-page checks.
• One unresolved product detail is marked clearly for the client's owner.
• The final billing reference is recorded in the invoicing system.
• Temporary file access will be handled by the relevant account owner according to the agreed plan.

This is a fictional workflow example. It does not imply that delivering copy also authorizes publishing, changing accounts, or issuing an invoice.

Notice how the record distinguishes your accepted output from the client's next phase. That prevents a vague “all done” message from hiding a real handoff.

Handle access as a planned decision

List the systems involved and who owns each account. For each, record whether access must continue for an agreed follow-up period, change to a different role, or end.

The authorized account owner should make and verify the actual changes. Avoid deleting shared files or removing access before the client has the material and the parties have resolved the intended arrangement.

Check linked resources as well as the main workspace: a final document may refer to images, folders, or recordings that still depend on temporary access. Keep the completion confirmation with the offboarding record.

Close billing questions through the right system

Use the actual work and the agreement to resolve the final billing record. Do not infer an hourly rate, tax treatment, or payment obligation from a task timer.

If you need help describing completed work, use the separate client invoice summary guide. Keep invoice creation, sending, and payment status in the system and process you use for them.

Offboarding should also distinguish completed work from follow-up support. If support continues, record what was agreed, how requests arrive, and who responds.

Write a closing message that matches the record

The agreed deliverables are ready at [location].
Accepted work: [brief list or reference].
Open items: [owner, next action, and date, or none].
Handoff instructions: [reference].
Access and follow-up: [agreed arrangement].
Please confirm that you can locate the final material and flag any issue
through [agreed channel].

Check every sentence against the project record before sending it. Avoid promising availability or additional work that has not been agreed.

Keep the closeout visible in SelfManager

Use a dated table in SelfManager Individual, or a shared table under Team, to track the checklist and remaining owners. Put the handoff index in notes, use task comments for clarification, and keep sensitive account information in its proper system. The client-work workflow shows how a client-facing view can fit.

Your project handover covers responsibility moving forward; a postmortem covers what you learned. This checklist closes the engagement itself. Finish when the agreed outputs, open actions, files, access decisions, and closing communication all have a clear recorded outcome.