Knowledge loss after layoffs: how to keep what people knew

What knowledge actually leaves when people are laid off?#

The knowledge that leaves in a layoff is partly in people's heads and partly in records only they could reach. The first kind, judgment and relationships, can only be partly captured through handover. The second kind, mailboxes, files, chats and work queues, stays recoverable as long as nobody deletes it first.

Operations leaders tend to focus on the first and lose the second by accident. A departing estimator's quotes and the email threads explaining each price, a support lead's private notes on difficult accounts, or a dispatcher's spreadsheet of which technician handles which building often sit in personal locations. IT removes the account to free a license seat, and the record goes with it.

The rule that prevents most loss is simple: preserve first, then remove access. Cutting access protects security on the day; deleting content is a separate decision that can wait until someone has looked at what is there.

Where departing employees' knowledge sits in your systems#

Departing employees' knowledge sits in a predictable set of places, and each needs a different action. The table is a starting map for a mid-sized company running common business systems; add any industry tools your teams use daily.

Admin accounts deserve their own line in the plan. When the only person with super admin rights to the helpdesk, the WMS or the field service platform is in the reduction, the company can lose the ability to run exports at all, which turns a routine archive task into a vendor support case.

Before the announcement: a preservation checklist#

A preservation checklist completed before the announcement keeps the reduction from deciding your retention policy for you. Most steps are quiet configuration work that IT and HR can finish with a short, confidential list of affected names.

Preservation work does not require telling anyone why an account is being reviewed. HR and counsel should decide how and when the company communicates with affected staff, and whether any pending dispute or investigation calls for a formal hold.

• 1List every system each affected person can access, including vendor portals and shared admin logins.
• 2Confirm that mailbox, drive and chat retention settings cover the affected users, and ask counsel whether a legal hold applies.
• 3Identify files stored only in personal drives or on laptops, and pick a shared destination for each team's material.
• 4Find admin, integration and service accounts tied to affected people and assign a new owner.
• 5Pull the open tickets, jobs, opportunities and projects assigned to each person.
• 6Prepare a short handover template and put handover time on each person's calendar.
• 7Decide in writing which accounts will be suspended, converted or kept, and who must approve any later deletion.

What deletion does in common business tools#

Deletion in common business tools is often faster and less reversible than leaders assume, so vendor documentation is the place to check before closing accounts. The behaviors below, taken from vendor help pages, show why the order of steps matters.

Plans and settings differ by edition, and vendors revise their documentation, so confirm each behavior against your own tenant before relying on it. The pattern holds across most tools: suspending access can be undone, deleting content often cannot.

After the reduction: handover notes that capture judgment#

Handover notes capture judgment when they explain why things are the way they are, not just what is open. A status line says a job is waiting on a part; a useful note says the customer has rejected two substitutes and the original specification matters because of a past failure.

Attach every note to a record the next person will actually open: a customer account, a job number, a project code or a ticket. Notes kept in a separate document drift out of sight, while a note on the account record is found the next time someone works it.

Recorded handover conversations can help, but ask HR and counsel about notice and consent first, and store recordings with the same care as other personnel material. Written or recorded, the prompts below draw out what status lists miss.

• 1Which customers or sites need special handling, and why?
• 2Which decisions are pending, and what has already been tried?
• 3Which workarounds exist that are not written down anywhere?
• 4Where are the files, spreadsheets or scripts this work depends on?
• 5Who outside the company should hear about the change, and who should call them?

Illustrative: an engineering firm after a project slowdown#

Illustrative: a fictional civil engineering firm reduced its staff after several large municipal projects were delayed. Its project history lived in Deltek Vantagepoint for time and billing, Procore for RFIs and submittals, Bluebeam markups on a shared server, and Outlook mailboxes where project managers negotiated scope changes with clients.

IT's first plan was to remove the departing users' Microsoft 365 licenses at the end of the week. The COO paused that step for a short review and found that several project managers kept design calculations and client correspondence in personal OneDrive folders rather than on the project sites.

The firm confirmed retention on the affected mailboxes, moved OneDrive project folders into each project's SharePoint site, reassigned open Procore RFIs with a note on each, and held handover sessions organized by project number. When a client later asked why a drainage detail had changed, the answer was in a preserved email thread and an RFI response, not in the memory of someone who had left.

How preserved records keep their value, and where SourceX fits#

Preserved records keep their value well after a reduction, because the mailboxes, tickets and project files that support continuity also document how the company does its work. Companies reuse them for onboarding the next hire, refreshing a knowledge base, answering warranty claims and supporting due diligence.

Some companies also assess whether those records could be licensed to AI developers. SourceX approaches that through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The first assessment uses metadata only, personal and confidential details are removed during preparation, and the company approves each step and keeps ownership of its records. Records deleted during offboarding cannot be assessed for any purpose, which is why preservation comes first.