The most dangerous things in your organization are the ones that exist only in one person's head.
The funder who only deals with you and whose history is nowhere written. The quirk in how payroll actually runs. The password to the account that matters most. The promise you made to a partner that nobody else knows about. If that person is suddenly gone, a successor inherits an empty desk and a hundred landmines. This guide gets what lives in one head into a pack the organization controls, so whoever steps in can actually keep the mission running. It is not documenting every process in the organization, which is a bigger, slower job that lives in your operations and systems work; this is focused on what only one person holds and what would matter most, fastest, in an emergency. It is a rescue pack, built so a frightened successor on day two can find the thread and pull it. Use this if what keeps the organization running lives in one or two heads and nowhere findable.
You cannot capture everything, and trying to would mean capturing nothing useful in time. Decide which functions the organization must keep running through any loss: paying and keeping staff, serving the people you serve, meeting funder obligations, keeping the doors legally open. These come ahead of everything that could pause for a month without harm. Then, for each essential function, name the knowledge, relationships, and access it depends on that live in a single head: the contacts, the history, the logins, the undocumented steps, the gotchas.
Open the Mission-Essential Function and Relationship Map →A map of what to capture is not the capture. For each item on the map, write it plainly enough for a successor: the steps, the logins and where they are kept, the key contacts and the real history of each relationship, and the things that would take months to learn the hard way. Store it where the organization, not the person, controls it. Then pull it into one clearly organized pack, pointed at a real reader: a successor on day two who is scared and needs the thread.
Treat it as both a serious risk and a warning sign, of insecurity, of something being hidden, or of a culture where knowledge is hoarded for job security. Where it concerns control of money or records, secure the organization's access regardless, because that is not optional. Where it is about trust and a culture of hoarding, that routes to culture and team health. This is a route, not a stop.
If capturing what only you hold makes plain that the organization has been built entirely around you, and that no pack can really substitute for the relationships and judgment you carry, notice that honestly, because it is the real risk under the paperwork, and it points to the longer conversation with your board about building an organization rather than extending one person. And where captured records include sensitive personal, donor, or client data, protect them accordingly and get a professional's read on your obligations if you are unsure.
For every function that must keep running, the knowledge, relationships, and access it depends on exist somewhere other than one person's head. A successor could open the pack and find who to call, how to run the essentials, and where everything is. And nothing critical to the mission would vanish if a single person did.
With the knowledge captured, most leaders move to Write, Adopt, and Maintain the Emergency Plan, to pull every piece into one plan the board adopts and keeps current. The everyday version of documenting and cross-training is the operations and systems work, and if knowledge hoarding is the block, that is culture and team health. If you came in through a crisis and have steadied, the whole-organization check-up is the honest next look once your plan is complete.