Client Offboarding Checklist: Scope, Delivery, Access, and Records

Client offboarding closes the service workflow. It connects the last piece of work to final delivery, ownership transfer, access changes, communication, and record retention.

A useful offboarding checklist answers six questions: What is finished? What is still owed? What transfers? Who keeps access? What remains available? Who confirms closure?

Copy this client offboarding checklist

• Name the offboarding owner and effective end date.
• Separate completed, open, and out-of-scope work.
• Prepare and verify the final client handoff.
• Transfer ownership of external systems through approved methods.
• Confirm billing and commercial close in the system that owns those records.
• Tell the client when portal access will change.
• Move durable decisions out of temporary conversations.
• Complete the internal retention, access, and risk review.
• Obtain final confirmation from the responsible owner.

The sections below explain the evidence each item needs. Adapt the commercial, legal, billing, and retention steps to the agreements and policies that govern the relationship.

Name one offboarding owner

Offboarding crosses delivery, account management, finance, access, and internal operations. Give one person responsibility for the complete checklist even when several people perform the steps.

The owner should confirm:

• The effective end date
• The final scope and unresolved work
• The client decision-maker
• The people responsible for delivery, billing, and access changes
• The date the client portal or account will become unavailable, if applicable
• The location of the final record

Use your contract and internal policies as the authority for notice, payment, intellectual property, retention, and transition duties. A software checklist cannot decide those terms.

Reconcile the final scope

Start with the work the parties already agreed to.

Create three lists:

1. Complete: outcomes the team has finished and reviewed.
2. Open: agreed work that still needs an owner and date.
3. Outside scope: new requests that require a separate decision.

Record how the team will handle each new request during offboarding: complete it, quote it separately, transfer it, or leave it with the client.

A current Task board can show the remaining owned actions. Board Overview can record the final project status and next steps. The status still requires human review; it is not calculated from task totals.

Prepare the final handoff

The client should receive one recognizable package, not a list of old links.

Before delivery:

• Confirm the final file formats included in scope.
• Remove drafts and internal notes from the delivery folder.
• Check that source files or editable formats are included only when agreed.
• Add a short index or handoff note when the folder structure is not self-explanatory.
• Confirm which client contacts should receive access.
• Record any separate systems or credentials that must transfer outside the file package.

In Sydnee, a Deliverable is a client-facing, view-only presentation created from an existing Files folder. Publishing makes that folder and its nested folders view only for clients. The client can browse, preview supported files, and download the package.

The team can see which portal contacts opened the Deliverable. That open event does not prove approval, acceptance, or complete download.

Use the client file delivery guide before publishing the final folder.

Transfer external ownership separately

Client work often touches systems Sydnee does not own: domains, analytics, advertising accounts, source repositories, hosting, design tools, or social profiles.

For each external system, record:

Never place passwords, access codes, private keys, or other secrets in ordinary task comments, chat messages, or an unrestricted handoff file. Use the approved access-transfer method for the system involved.

Decide what happens to portal access

Access changes should follow the end date and your retention policy. Keep access available through the agreed period for the client to retrieve final work.

In Sydnee you can:

• Remove one portal user's access from a client account while leaving the account and its work available to other authorized people.
• Remove an internal teammate from that account without removing them from the company team.
• Archive the client account when the relationship is no longer active.

An archived account leaves the active account list, and clients cannot sign in to that account or open its work. Archiving does not delete the account; owners and admins can restore it later when the plan has an available active-account slot.

Tell the client the access date before archiving. If they need a final package outside the portal, name the approved transfer method in the offboarding plan and use it before access ends.

Close communication deliberately

Send one final message that states:

• The engagement end date
• What the final package contains and where to find it
• The date portal access changes, if it will
• Any remaining client actions
• The contact for a correction or agreed transition question
• What a future request would start

Set a specific access period that follows your agreement and current product policy.

If Live Chat held active conversation, move durable decisions into the file, task, or offboarding record that owns them. Archiving a channel or removing a direct message from a team member's active sidebar is separate from closing the commercial relationship.

Complete the internal close

After the client-facing handoff, finish the team work:

• Confirm the final scope and delivery record.
• Close or archive active tasks and boards as appropriate.
• Revoke the team's external-system access after transfer is confirmed.
• End agency-funded tools or services according to the agreement.
• Store retention and deletion dates in the system your policy uses. In Sydnee, review the permanent file and folder deletion behavior before removing retained work.
• Record open risks and the person responsible for them.
• Decide whether reusable templates need a correction based on this engagement.

Avoid deleting files merely to make the account look clean. Sydnee's visible Files deletion is permanent and has no in-product Trash or Restore view. Follow the business's retention and deletion policy before removing material.

Use this final confirmation

The offboarding owner should be able to make one complete statement:

The agreed work is reconciled, the final package is available to the named client contacts, external ownership changes are confirmed, access changes are scheduled or complete, and the remaining records follow our documented policy.

If any part is untrue, the offboarding is still open.

Use the client engagement lifecycle to connect this close to the broader relationship, and review the current account access and archiving guidance before changing portal availability. Explore Sydnee File Sharing when you need a controlled path from active files to a client-facing final Deliverable.