Build a client offboarding handback packet

Start the packet when notice arrives

Open the handback packet on the day notice arrives, even if the last working day is weeks away. List the notice date, the final service date, the client contact, and the internal owner for the transition. Put the packet in a shared location that both parties can reach without asking the departing assistant. Starting early gives the client time to name a receiver and challenge the inventory.

Confirm which services end and which continue under a new scope. A client may end one lane while keeping another, and a blended exit is harder than a full stop. Write the boundary in the packet so nobody assumes the whole relationship is closing. Send the client a short summary of the plan within two business days.

Assign a transition owner who is not the departing assistant. That person should be able to answer questions, approve file access, and sign off on the final packet. If the client has a different contact for the exit, record both names and their responsibilities. A transition with no internal owner tends to stall when the assistant leaves.

Inventory files, accounts, and open commitments

Build three lists: files the client owns, accounts the provider controls, and commitments still open. For each file, record the location, format, owner, and last update. For each account, record the system, the account name, the permission level, and who can disable it. For each commitment, record the request, the due date, and the next action.

Include the unglamorous assets that are easy to forget, such as calendar sharing, mailbox rules, templates, saved searches, and password manager entries. Check for documents stored in personal drives or local downloads. A handback that returns the main folder but leaves working copies scattered across devices is not complete. Add the browser bookmarks and saved form entries that contain client information, because they are easy to overlook and hard to reconstruct.

Give each item a status that a reviewer can read at a glance: delivered, pending, blocked, or not applicable. Add the evidence link for anything marked delivered. A list without status invites a second round of questions after the final meeting. The status column also makes the client's remaining actions visible.

Decide who owns the client relationship after the handback. A client may need a new contact for billing, a new contact for service questions, and a different contact for data requests. Put those names in the packet before the last week. A handback that leaves the client with no route for follow-up feels like an abandonment, even when the work was delivered.

Return the client's data in usable formats

Ask the client which formats they can open and which systems they will keep. Export spreadsheets as spreadsheets, not as pdf prints, and keep the original files where the client wants them. Include a manifest that maps each delivered file to its source and version. Test one export before producing the full set.

Remove provider-internal notes, drafts, and unrelated client records before delivery. If a file contains both client data and internal commentary, separate the two rather than sending the whole document. Record any file that cannot be delivered and explain why. A clean handback protects the client and reduces the provider's own risk.

Confirm the delivery channel before the final week. A large export may need a secure transfer link, an encrypted drive, or a direct upload to the client's system. Test the recipient's access while the team is still available to fix it. A packet that arrives after the last working day is much harder to repair.

Close access with dated evidence

Disable the assistant's accounts in a planned order, starting with the broadest access and ending with the tools needed to finish the handback. Record the time, the system, the person who performed the change, and the confirmation the tool returned. Ask the client to confirm that their own user list no longer shows the provider account. Keep the evidence with the handback packet.

Check for shared credentials, API tokens, forwarding rules, and device enrollments that a normal user list may not show. Revoke sessions as well as passwords, because an active session can outlive a password change. If a system cannot be audited, document the limitation and the compensating control. An access close that relies on a verbal assurance is not evidence.

Record the order in which access will be removed and the work that depends on each system. Removing the document drive before the final export will stop the handback, while leaving the inbox open after the last day extends exposure. Sequence the removal around the work, not around the tool list. Share the sequence with the client so nobody is surprised by a lost login.

Hand over the open work list

Give the receiver a dated list of every open request, including the requester, the current state, the next action, and the deadline. Mark the items that need a decision rather than more work. Add the source of each instruction so the receiver can verify it. A list that only names the task will force the receiver to rebuild the context.

Walk through the list in a live session and let the receiver ask questions. Record the answers beside the relevant item instead of leaving them in a meeting note. Confirm which items the provider will finish and which move to the client. Close the session with a named owner for every remaining item.

Confirm receipt and remaining obligations

Send a final handback summary that lists what was delivered, what was removed, and what remains open. Ask the client to confirm receipt in writing and to name any missing item within an agreed window. Keep the confirmation with the contract record. The confirmation is the difference between a closed transition and a dispute waiting to happen.

Review the packet after thirty days for any late request, retained file, or access issue. Update the record if the client reports a gap, and keep the correction with the original evidence. Use the review to improve the template for the next client. A handback process earns trust only when it survives the quiet month after the work stops.