Your club president resigned last Tuesday. She’d been running things for four years. The board meets in ten days, and here’s what you’ve discovered so far: nobody knows the login for the organization’s bank account. The membership list lives on her personal laptop. The caterer who gives you the annual gala discount? She had that number in her phone. The insurance renewal is due next month, and the policy documents are in a Gmail account with a password nobody else has.
Four years of knowledge, gone in one resignation email.
This isn’t rare. It’s the default. Most volunteer organizations run on institutional knowledge stored in exactly one person’s head, and when that person leaves, the next leader starts from almost zero. Research on knowledge management finds that 42% of institutional knowledge is unique to the person in the role and isn’t shared with anyone else. When that person walks, so does nearly half of what they knew about how things actually worked.
BoardSource’s Leading with Intent survey found that only 29% of nonprofits have a written succession plan, and just 12.5% have a board leadership succession policy. For small volunteer-run groups (PTAs, cultural clubs, sports leagues, HOAs), those numbers are almost certainly lower. And a succession plan is the easy part. The harder question is: even if you’ve identified who takes over, have you figured out what they need to know?
What “Institutional Knowledge” Actually Means
People hear “institutional knowledge” and think it means the bylaws and the budget. Those matter. But they’re the obvious stuff. The knowledge that actually disappears during a leadership transition is far more mundane and far more critical.
It’s the name of the guy at the parks department who approves your field permits. It’s knowing that the bank requires two signatures on checks over $500. It’s the fact that your venue gives you a 20% discount because someone negotiated it three years ago, but only if you book before March. It’s the password to the Mailchimp account, the Venmo business profile, the domain registrar, and the Zoom subscription.
It’s the reason you don’t schedule events on the third Saturday in October (it conflicts with the homecoming parade, and you learned that the hard way in 2022).
None of this is written down. It lives in text threads, in someone’s memory, in a folder on a desktop that nobody else can access.
Transition researchers sometimes call this the “undocumented operating system” of an organization. CompassPoint Nonprofit Services, which has studied executive transitions for over two decades, consistently finds that the most damaging losses during transitions aren’t strategic. They’re operational. The new leader can figure out the mission. What they can’t figure out, without help, is how the printer at the community center works on Tuesdays or why the newsletter goes out on the 15th instead of the 1st.
The Cost of Starting Over
Every time a volunteer leader turns over without a proper handoff, the organization pays a tax in lost time and lost trust.
The new president spends weeks (sometimes months) just figuring out what systems exist and how to access them. Members who had a relationship with the outgoing leader feel disconnected. Vendors and partners who dealt with one point of contact have to rebuild trust with someone new. Recurring tasks get missed because nobody told the successor they existed.
If your organization manages its member records in a spreadsheet on someone’s personal computer, the risk is even higher. One laptop crash, one departed leader, and you’re rebuilding your entire membership list from bank statements and memory.
CompassPoint’s “Daring to Lead” studies found that roughly two-thirds to three-quarters of nonprofit executives plan to leave their position within five years. The nonprofit sector’s turnover rate runs around 19%, which is 58% higher than the rate in other sectors. For volunteer organizations with one- or two-year terms, the clock is always ticking. The question isn’t whether you’ll have a leadership transition. It’s whether you’ll be ready for it.
The Handoff Checklist Your Organization Needs
Below is a practical list of everything an outgoing leader should transfer to their successor. Print it out. Tape it to the wall of wherever your board meets. Make it part of your bylaws if you have to.
Access and Accounts
- All login credentials for shared accounts (email, social media, website, payment tools, video conferencing, cloud storage)
- Bank account access and signatory information
- Domain registrar and web hosting credentials
- Any subscription services the organization pays for (and when they renew)
- Physical keys, storage unit access, mailbox keys
- Two-factor authentication recovery codes and backup phone numbers for critical accounts
- Contact info for the IT person, web developer, or anyone who maintains your digital tools
Financial Records
- Current budget and last two years of financial statements
- Bank statements for the past 12 months
- List of recurring expenses and when they’re due
- Tax filings (for 501(c)(3) and similar organizations, your Form 990s)
- Insurance policies and renewal dates
- Any outstanding contracts with vendors or venues
People and Relationships
- Vendor contact list with notes on the relationship (who to call, what rates you’ve negotiated, any quirks)
- Key partner contacts at schools, city offices, other community organizations
- List of active members with roles, committee assignments, and any notes on engagement
- Donor or sponsor contacts (if applicable)
- Any members with special circumstances the new leader should know about (accessibility needs, ongoing disputes, outstanding commitments)
Operations and Processes
- Annual calendar of recurring events and deadlines (filings, renewals, elections, events)
- How-to documentation for regular tasks (sending the newsletter, running the annual meeting, processing new members)
- History of what worked and what didn’t at past events
- Pending projects and their status
- Any verbal agreements or informal commitments the organization has made
Governance
- Current bylaws
- Meeting minutes from the past two years
- Board member contact list with term end dates
- Any pending votes, unresolved motions, or ongoing governance issues
That’s a long list. Most outgoing leaders won’t hand over all of it unless you ask. And most organizations don’t ask until it’s too late.
Stop Storing Knowledge in One Person’s Head
The checklist above solves the handoff problem once. But you’ll have another transition in a year or two, and you’ll be right back to scrambling if you don’t fix the underlying issue: too much knowledge living in too few heads.
Here’s how to distribute it.
Create a shared “operations manual” (and keep it simple)
This doesn’t need to be a 50-page binder. A shared Google Doc or folder with sections for each officer role is enough. Each section answers: What does this role do? What accounts and tools does it use? What recurring tasks happen on what schedule? Who are the key contacts?
Update it once a quarter. Put it on the agenda for one board meeting a year. Assign someone to check that it’s current.
Use a password manager
Shared credentials are one of the most dangerous points of failure in volunteer organizations. When the president changes the Gmail password and forgets to tell the secretary, things break quietly. When the outgoing treasurer is the only person who can log in to the PayPal account, you’re stuck.
A free or low-cost password manager (Bitwarden and 1Password both offer free or discounted tiers for nonprofits) lets you store every credential in one encrypted vault. When someone rotates off the board, you revoke their access with one click and the credentials stay safe. No more sticky notes, no more texting passwords, no more “does anyone remember the login for…?” Real organizations have lost access to their own websites because domain hosting expired and no one had the registrar login. That’s not a hypothetical. It happens constantly.
Make sure two people know everything
For every critical function, at least two people should understand how it works. Not in theory. In practice. Your treasurer should have a backup who can run a financial report. Your events chair should have someone who knows where the supplies are stored and how to book the venue. Burnout and sudden departures are real. If any single person leaving would create a crisis, you’ve got a fragility problem.
Move records into systems that survive leadership changes
If your member list, payment records, and communications history live in a tool like Somiti rather than on someone’s personal laptop, the handoff becomes simple: give the new leader admin access. Everything is already there. No files to transfer, no spreadsheets to untangle, no “where did the old treasurer keep that?”
The guide to choosing membership management software covers what to look for if your organization hasn’t made this switch yet.
Document Processes, Not Just Data
Handing over files is only half the job. The new leader also needs to understand how things get done. And “how things get done” is almost never written down.
Take something as simple as your annual fundraiser. The outgoing events chair knows that you need to book the venue by February, that the sound system comes from a member who loans it for free, that the printing company on 5th Street gives you a nonprofit discount if you mention the PTA, and that you should never schedule it the same weekend as the high school play.
None of that’s in a file. It’s tribal knowledge. And it vanishes the moment that events chair steps down.
The fix is dead simple, if tedious. For every recurring task or event, write a short process document. Not a novel. A page at most. Cover the steps, the contacts, the timing, and the “watch out for” notes that only experience teaches.
If you’re a new president trying to get your arms around all of this, the first 90 days guide walks through exactly how to collect this information during your early weeks.
The Emotional Side of Transitions
Not every transition is smooth, and the difficulty isn’t always logistical. Sometimes it’s personal.
Some outgoing leaders don’t want to let go. They built the organization, or they’ve been running it so long they can’t separate their identity from the role. They hold on to access, second-guess their successor’s decisions, or hover at meetings in a way that undermines the new leadership. This is understandable. It’s also damaging.
If your organization’s bylaws include clear term limits and transition procedures, this becomes a structural issue instead of a personal confrontation. The rules say the transition happens. Nobody has to be the bad guy.
Other times, the outgoing leader is so burned out that they just want to disappear. They hand over the minimum, stop returning messages, and check out entirely. You can’t force someone who’s done to stick around, but you can reduce the damage by having documentation systems in place before they hit the wall. Burnout-driven departures are the most abrupt and the least planned. They’re also the most common.
And sometimes there’s a political dimension. A new president who won a contested election may not get much cooperation from the outgoing group. Factions form. Information becomes a bargaining chip rather than a shared resource. The best defense against this is making institutional knowledge organizational property from day one, stored in shared systems, not personal accounts.
Building a Leadership Pipeline
The best transition planning starts long before anyone announces they’re leaving. In 2025, the government and nonprofit sector led all industries in CEO departures, according to Challenger, Gray & Christmas tracking data. The trend isn’t slowing down.
If nobody in your organization wants to step up, you don’t have a transition problem. You have a pipeline problem. And a pipeline problem becomes a knowledge crisis the moment your current leader walks away.
Start grooming successors a year before you need them. Invite promising members to shadow board roles. Give committee chairs a vice-chair who learns the job alongside them. Make it normal for two people to attend vendor meetings, handle finances, or manage event logistics.
BoardSource recommends that boards treat succession as a continuous process, not a crisis response. When you always have someone ready to step in, transitions stop being emergencies and start being routine.
The complete guide to running a volunteer organization covers governance structures that make this kind of bench-building part of how your group operates, not an afterthought.
A Transition Timeline That Works
Here’s a realistic timeline for a planned leadership transition in a volunteer organization.
Three months before the transition: The outgoing leader starts updating the operations manual. They verify that shared accounts and passwords are current in the password manager. They write “state of the union” notes for each area of responsibility: what’s working, what’s broken, what’s pending.
Two months before: The incoming leader shadows the outgoing one. They attend vendor calls. They get added to the bank account. They sit in on the budget review. This overlap period is the single most valuable part of the transition.
One month before: The incoming leader takes the lead on day-to-day tasks while the outgoing leader stays available for questions. This is the rehearsal. Better to discover what’s missing now than after the handoff is complete.
Transition day: All account access is formally transferred. The outgoing leader hands over physical materials (keys, files, devices). The board formally acknowledges the transition.
One month after: The outgoing leader makes themselves available for questions (within reason). A single check-in call can save the new leader hours of guesswork.
Planned transitions are a luxury. Many volunteer organizations deal with sudden departures, health issues, or leaders who simply stop showing up. You can’t plan for every scenario, but you can build systems that make any transition survivable.
The One Thing You Can Do This Week
You don’t need to overhaul your entire organization to start protecting institutional knowledge. You need to do one thing: make a list of every account, login, contact, and recurring obligation your organization depends on. Write it down. Put it somewhere at least two board members can access.
That’s it. That one list, maintained and updated, would have saved thousands of volunteer organizations from the chaos of an unplanned departure.
Your current leaders won’t be around forever. The knowledge they carry doesn’t have to leave with them.