What happens to an employee's electronic records when they leave the company?

When someone leaves an organization, the electronic records they created or received do not leave with them. Those records belong to the organization, not the individual, and they remain subject to the same retention, legal, and access obligations as any other record. The departure simply triggers a transfer of custody — a step that should be planned in advance, not improvised after the person is gone.

Records belong to the organization

A useful starting principle: a record is evidence of business activity, regardless of who created it or where it happens to sit. An employee’s mailbox, shared drive folders, chat history, files stored in collaboration platforms, and content on a work-issued laptop or phone can all contain records. The fact that material lives in a personal account or device does not exempt it — if it documents official business, it is a record the organization must account for.

What should happen at offboarding

A defensible offboarding process treats records as a deliberate handoff, typically covering:

• Identify where the departing employee held records — email, network shares, cloud storage, line-of-business systems, and any sanctioned messaging tools.
• Preserve active records by transferring ownership to a successor, manager, or shared location so business continuity and access are maintained.
• Apply retention so each record is kept for its required period and not destroyed early — or kept indefinitely by default.
• Honor legal holds, which override normal disposition. If the person’s records are subject to litigation, audit, or investigation, nothing may be deleted until the hold is lifted.
• Decommission accounts only after records have been captured, since deleting a mailbox or wiping a device can destroy records irretrievably.

Why this matters

Handled well, offboarding keeps an organization able to find and produce records for electronic records requests, discovery, and operational needs long after a person leaves. Handled poorly, it creates orphaned data, accidental loss of records under hold, and unmanaged accumulations that raise both cost and risk.

The goal

The aim is not simply to lock down a departing employee’s data, but to bring their records under normal lifecycle management: captured in the right place, retained for the right time, and disposed of only when policy allows. Building this into routine HR and IT offboarding — rather than reacting after the fact — is what makes the outcome reliable.