Five Moves to Make Before the Resignation Letter Lands

In most American companies, the offboarding checklist covers the predictable basics: revoke system access, collect the badge, run the exit interview, wish them well on LinkedIn. What the checklist almost never covers is the thing that actually matters—the accumulated judgment, relationships, and unwritten know-how leaving the building along with the laptop.

This is not a marginal oversight. In knowledge-intensive functions, departing experts routinely take with them the only complete map of how the work really gets done: which vendor responds fastest, why a process has an undocumented exception, which client needs a particular communication style. The replacement hire inherits the title, not the map.

The good news is that capability loss at departure is largely preventable—if you treat the exit as a managed transfer rather than an administrative event. Here is a five-step framework that works whether you have ninety days of notice or ninety minutes.

Step One: Map Dependencies Before You Map Knowledge

Start with a blunt question: what breaks if this person disappears tomorrow? List the systems only they can access, the decisions only they make, the relationships only they hold. This dependency map—not the job description—defines the actual scope of the handoff. In urgent departures, a two-hour dependency mapping session with the person's manager and one peer is the highest-return investment available.

Step Two: Capture Judgment, Not Just Facts

Documentation of procedures is table stakes, and most of it already exists in some form. The scarce asset is judgment: the reasoning behind decisions, the exceptions, the "here's why we don't do it that way anymore" knowledge. Structured debrief interviews work well here—ask the departing employee to walk through three recent difficult decisions and explain their reasoning. Record and transcribe. An hour of this outperforms a hundred pages of updated SOPs.

Step Three: Transfer Relationships Deliberately

Client and partner relationships rarely transfer through a group introduction email. Identify the five most critical external relationships and schedule direct handover conversations—ideally with the departing employee present, the successor leading. The successor should leave each conversation owning the next committed action, not just the contact information.

Step Four: Assign a Knowledge Steward

Every handoff needs a named owner inside the organization—someone accountable for verifying that the transferred material is complete, findable, and actually usable. Without a steward, captured knowledge migrates to a shared drive folder nobody opens. The steward's job is to test the handoff: can a competent peer solve a realistic problem using only what was transferred?

Step Five: Run the Retro—and Fix the System

After the departure, spend thirty minutes with the manager and steward asking one question: what did this exit reveal about how fragile our capability structure is? If one person's leaving created a crisis, the problem was never the resignation—it was the concentration of expertise that preceded it. Feed those findings into succession planning, cross-training, and documentation priorities.

Turning Exits Into Inputs

Organizations that operationalize this framework notice something counterintuitive: departures become informative rather than merely painful. Each structured handoff exposes where the organization is over-dependent, under-documented, and under-prepared—intelligence that no engagement survey provides. Resignations will keep happening. The capability loss doesn't have to.