Onboarding

Create a client offboarding checklist for a virtual assistant

A closeout checklist that fixes the last day, final deliverables, access removal, records transfer, and the confirmation the client receives.

By OnboardingEmployees editorial team | | 7 min read

Create a client offboarding checklist for a virtual assistant
On this page
  1. Fix the last day and the final deliverables
  2. Close the records and payment trail
  3. Remove access on a dated schedule
  4. Transfer the working history
  5. Confirm the client has what they need
  6. Review the closeout after it ends
  7. Key takeaways
  8. Related reading

A client offboarding checklist is not a goodbye email and it is not a final invoice. For a virtual assistant, the checklist is the record that says what was delivered, what access ends, and what the client keeps. A closeout that ends with a verbal thanks leaves loose access and unanswered questions. The checklist makes the ending as deliberate as the start.

Fix the last day and the final deliverables

Write the contracted last day and the date the team will stop taking new work. These dates are often different, and the assistant should not let a request arrive after the cutoff. Record the person who can approve an exception. A clear cutoff protects the team from an open-ended ending.

List every deliverable that must be handed over before the close. Include the final report, the working files, the account credentials owner, and any scheduled item that another person must pick up. The assistant should mark each item as delivered or outstanding. A deliverable without an owner is not closed.

Confirm the format the client expects for the final files. A client may need an editable document, a spreadsheet, or a read-only copy for an archive. The assistant should test that each file opens after export. A file that only opens on the team's system is not a handover.

Record the acceptance step for each deliverable. The client should confirm receipt in writing, even when the work was reviewed in a meeting. The assistant should keep the confirmation with the closeout folder. An unconfirmed deliverable can reopen the engagement weeks later.

Close the records and payment trail

Reconcile the final invoice against the delivered work before the close. Check the period, the line items, and any credit that was promised during the engagement. The assistant should route a discrepancy to the owner rather than adjust the record alone. A clean final invoice prevents a late dispute.

List the records the client will keep and the records the team must retain. A signed agreement and a final report may stay with the team, while working notes may belong to the client. The assistant should record the retention rule for each item. A record that is deleted too early can be impossible to rebuild.

Remove shared links that will stop working and replace them with a durable copy. A client should not depend on a folder that is tied to a departing account. The assistant should test the replacement link from outside the team. A dead link after the close is a common source of frustration.

Confirm the payment status and the remaining balance before the account is closed. The assistant should record the amount, the date, and the person who confirmed it. A verbal assurance is not a closed balance. The closeout folder should show the evidence.

Remove access on a dated schedule

Build an access list that names every system the client or the team touched. Include shared inboxes, project boards, file stores, and any third-party portal. The assistant should mark which access belongs to the client and which belongs to the team. A closeout that removes only the obvious accounts leaves a quiet gap.

Set a removal date for each item rather than removing everything at once. Some access must survive until the final report is accepted. The assistant should record the date and the person who performs the removal. A dated schedule is easier to verify than a general instruction.

Remove the departing team member's access first when the close involves a role change. The client should not lose access before the handover is complete. The assistant should confirm each removal in the system log. A screenshot of the settings page is useful evidence for a later review.

Ask the client to confirm which of their own users should keep access. A client contact may leave at the same time as the engagement. The assistant should record the confirmed list and the date. An unconfirmed list keeps dormant accounts alive.

Transfer the working history

Package the working history that the client will need to continue without the team. Include decisions, open questions, contacts, and the location of the source files. The assistant should write a short index rather than a folder with no guide. A package without an index is a pile of documents.

Explain any custom process that is not obvious from the files. A naming rule or a review step may be invisible to a new owner. The assistant should record the reason for the process, not only the steps. A rule without a reason is likely to be dropped.

Mark the items that are unfinished and the state each one is in. A draft that was never approved should be labelled as a draft. The assistant should name the next action for each open item. A client who inherits an unmarked draft may treat it as final.

Share the package through a channel the client can access after the engagement ends. A temporary link that expires in a week is not a handover. The assistant should confirm that the client opened the package. A delivery that was never opened is not a transfer.

Confirm the client has what they need

Send a short closeout note that lists the deliverables, the access changes, and the contact for a later question. The note should not repeat the whole engagement history. The assistant should use plain language and a clear subject line. A concise note is more likely to be read and kept.

Ask the client to confirm that the package opens and that the access list is correct. The confirmation can be a reply to the note or a signed form. The assistant should record the date and the person who confirmed. A closeout without confirmation is only an assumption.

Offer a short window for questions and name the person who will answer them. A client may discover a missing file a few days after the close. The assistant should record the window and the owner. A bounded window prevents an informal support arrangement from continuing forever.

Close the engagement in the project system and archive the folder. The assistant should remove the client from active reports and distribution lists. A record that stays in the active list distorts the next report. Archive is not the same as delete, and the rule should be written.

Review the closeout after it ends

Hold a short review after the close and compare the checklist to what actually happened. Note any item that was missed, delayed, or added late. The assistant should record the reason rather than only the result. A review that names causes produces a better checklist.

Update the template with one change that would have prevented the largest delay. A second change can wait until the next close. The assistant should record the date the change was adopted. A template that changes every time is hard to compare.

Check that the archived folder can be found by someone who did not work on the engagement. Ask a colleague to locate the final report and the access list. The assistant should record how long the search took. A folder that only its creator can navigate is not an archive.

Keep the closeout note and the client confirmation with the archive. These records explain what was promised and what was received. The assistant should review them before the next similar engagement. The next closeout starts from a tested template rather than a blank page.

Key takeaways

Fix the last day, the new-work cutoff, and the final deliverable list before the close begins. Record who can approve an exception and confirm each deliverable in writing. A verbal thanks does not close a deliverable. A clear cutoff protects the team from an engagement that never really ends.

Reconcile the final invoice against the delivered work and record the retention rule for each record. Replace shared links that will stop working with a durable copy. Remove access on a dated schedule rather than all at once. A closeout that removes only the obvious accounts leaves a quiet gap.

Package the working history with an index, the open items, and the reason behind each custom process. Share it through a channel the client can still open after the engagement. Ask the client to confirm the package and the access list. A delivery that was never opened is not a transfer.

Send a short closeout note with the deliverables, access changes, and the contact for later questions. Bound the question window and name its owner. Review the closeout and adopt one improvement. A folder that only its creator can navigate is not an archive.

Continue building the workflow

Related support: onboarding operations support, contact us. The National Institute of Standards and Technology - Cybersecurity Framework provides a framework for managing access and protecting business records.