If you run a small nonprofit, you are probably wearing six hats, working unpaid overtime, and holding the entire operation in your head. The idea of stepping back feels impossible.
Here is what nobody tells you: succession planning for a small nonprofit is not about hiring an executive or building a leadership pipeline. It is about answering one question. What happens to the donor list, the logins, the grant deadlines, and the relationships if you cannot do this anymore? Today, all of it lives in one person's head and one person's personal inbox. That is the real risk.
Burnout is the trigger most of us are quietly racing. The Center for Effective Philanthropy's State of Nonprofits 2024 found that 95% of nonprofit leaders are concerned about burnout in their organization. Small orgs feel it hardest because one or two people hold everything.
This guide gives you a 2-page continuity binder you can fill out this weekend, the four cheap moves that matter most, and an inline sample succession plan framework you can copy into your own doc. No download, no gated PDF. Just the framework on the page.
Succession planning, in the textbook sense, means identifying and developing future leaders so the organization keeps running when leadership changes. For a large nonprofit with staff, that is real work: leadership pipelines, ED transition committees, board-led searches.
For a small nonprofit where one or two people are the org, that definition is the wrong size of the problem. What you actually need is continuity planning. Make sure the org can survive 60 days without you.
The sector uses three labels you should know:
Most small nonprofits only need the first one done well. The second matters when you have notice. The third is a years 3–5 project, not a week-1 project, and the rest of this guide is honest about that.
The scale of the gap is wide. BoardSource's Leading with Intent research reports that only about 27% of nonprofits have a written succession plan, which means roughly three out of four do not. (Source: BoardSource, Leading with Intent.)
For a small nonprofit: if you write a 2-page emergency succession plan and centralize donor data, you are already ahead of the majority of the sector. You do not need the 30-page corporate version.
The risk is not abstract. It looks like this.
A 30-hour-a-week solo staffer runs donor management, comms, and reporting. Volunteers say they will help and then do not. As one solo staffer put it: "because we're so small and I'm only thirty hours, you know, and I do everything… this person and that person volunteered to help, but they never did their end of it." Anything beyond the daily grind never gets built or maintained, including the continuity binder.
A cofounder juggling a part-time job, the nonprofit, and family caregiving sees the value of better systems but cannot find the bandwidth to learn them. As she said: "So it's just having time, one, to learn the system and two, it being as user friendly for me as possible." The knowledge stays in her head because writing it down is the task that always loses to today's fire.
A retired teacher who founded an animal rescue described how fundraising had outgrown her: "I'm not sure how to do that. Like I said, it's all just kind of run away from me. I'm a retired fourth grade teacher. I'm not a financial person." There is no obvious second-in-command and no time to recruit one.
We hear two patterns over and over from small-org leaders.
One: a full staff transition leaves no documentation anywhere. The contact list and donor history lived in one person's personal email, and the org's logins followed that person out the door. Rebuilding takes a year.
Two: a founding networker tries to retire while the board is still being stabilized. The relationships, the funder conversations, and the day-to-day decisions are concentrated in that one person. The handoff is fragile because nothing was institutional in the first place.
Neither story needs a corporate succession framework to fix. Both needed a 2-page binder and one shared donor platform, written years earlier.
For a small nonprofit: the danger is not that you forgot to groom a successor. It is that today, if you stopped working tomorrow, nobody else could log into the bank, find the donor list, or know which grant report is due Friday. Fix that first.
Before any framework, do these four. Each is cheap, takes hours not weeks, and removes the biggest single-point-of-failure risks.
List every account the org runs on: bank, donor platform, website CMS, email, social, grant portals, accountant login, insurance broker. Record where the credentials live and who can reach them. Move passwords out of personal Gmail and into a shared password manager. Done looks like: one document, stored in a shared drive, that a board chair could use to keep the lights on for 30 days.
If your donor list is a spreadsheet on a founder's laptop and your donation flow runs through a personal payment account, that data leaves when the person leaves. Get donor records and giving history into a shared platform on the org's account. You can centralize donor records in Zeffy's free CRM at no cost, and donations can run through free donation forms that live on the org account, not a personal one. Done looks like: the next person to log in can see every donor, every gift, and every receipt without asking you a single question.
Write the email you would want your board chair to send to donors if you stepped away. Write the version that goes to the board. Save them as drafts. They do not have to be polished. They have to exist. Done looks like: two templates in the shared drive, dated, with placeholders for the news of the day.
One person who can keep the lights on for 60 days. A board member, a trusted volunteer, a peer ED at a partner org. Tell them. Walk them through the access sheet. Ask them to say yes out loud. Done looks like: their name is on page 1 of your binder, and they know it.
For a small nonprofit: if you do only these four things and nothing else from this article, your org is meaningfully more resilient than it was yesterday.
Three labels show up in every sector report. Here is what they mean in plain terms, and which one fits a small org.
Covers 30 to 90 days of immediate gap. Who signs checks, who emails donors, who answers the phone, where the passwords are. This is the 2-page binder. Right fit when: always. Every nonprofit needs this one.
A planned transition with notice. The ED announces retirement six months out, the board runs a search, the outgoing leader documents and trains. Right fit when: you know the change is coming and you have time to prepare.
Long-term leadership development. Identifying future leaders inside the org, training them over years, building a real pipeline. Right fit when: you already have more than two people on staff and a working board. Revisit this only after the emergency plan is built and tested.
For a small nonprofit: build the emergency plan now. Sketch the departure-defined plan when a transition is on the horizon. Save the strategic pipeline for the year you finally hire your third staff member.
Here is the full checklist, organized by category. Treat it as a living Google Doc. Update it once a year on a calendar reminder.
For a small nonprofit: if every bullet above has one named person and one shared location, you have a real succession plan. If half of them say "ask the founder," you have a memory.
Even a working board (the kind that pitches in on events rather than just governs) has a continuity job. Three things the board owes the org:
For working boards at small orgs, the simplest move is to add succession to the annual board agenda. Review the binder once a year, confirm the named backup human is still available, update logins. That is it. For a deeper look at what a board should actually be doing, see our guide to nonprofit board responsibilities.
For a small nonprofit: you do not need a governance committee. You need one board member who can find the binder when you cannot.
Sit down with one question: what breaks if I disappear for 60 days? Walk the calendar. What grant report is due? What payroll run? What donor stewardship is overdue? Make a list. The items only you can do are your vulnerabilities. Aim for a 1-hour first pass; do not try to be exhaustive.
For each item on the vulnerability list, write a short page. Not a procedure manual, a page. What it is, when it happens, who the contact is, where the file lives, what "done" looks like. The goal is not to teach a stranger your job. It is to give someone who already cares about the org enough to keep going for two months.
One backup human is the minimum (move 4 above). If you can identify two, do that. Spend an hour with each walking through the access sheet and the binder. Have them log in to one system while you watch, so you know it actually works.
This is the binder. Use the sample framework in the next section as your starting structure. Save it in the shared drive in two formats: a working Google Doc and a printed copy in the office. Pre-draft the donor and board comms so they exist as templates, not as a future task. Layer in automated donation receipts so the org keeps issuing tax records even if nobody is at the desk.
If your org has the bandwidth, start looking at who could grow into a leadership role. A senior volunteer, a part-time program manager, a board member edging toward staff. This is years 3–5 work. Do not start it before the binder exists.
Calendar reminder. Same week each year. Open the binder, update logins, confirm the backup human is still available, refresh the comms templates. 90 minutes a year is enough.
For a small nonprofit: Steps 1–4 are the whole game. Step 5 is optional. Step 6 is what makes the binder real instead of theatre.
This is the inline sample. Open a new Google Doc, copy the headings below, fill in your specifics. No download, no template card, no PDF. The framework on the page is the deliverable.
Name the people who step in for each function and what they can decide on their own.
Record each system, where the credentials live (shared password manager, not personal Gmail), and who has access today.
For each, note name, last contact, and the next touchpoint owed.
For a small nonprofit: finish a first pass in one afternoon. Leave blanks where you do not know yet. A binder with gaps you can see is much better than a binder you never started.
This is the section you should read last, not first. For most one-person orgs, this is years 3–5 work. Read it once you have the binder built and tested.
The honest playbook:
For a small nonprofit: the realistic pipeline is one person, identified over time, brought along slowly. Skip 9-box grids and competency frameworks; they were built for orgs with 50 staff.
For a small nonprofit: the most expensive mistake is the one that feels least urgent. Write the binder this weekend.
Zeffy addresses one specific failure mode that wrecks small-org transitions: donor data and giving history living in one person's spreadsheets and personal inbox. With Zeffy, that data lives on the org's account, free and unconditionally. Specifically:
Zeffy is free. No platform fee, no transaction fee, no credit card fee. Ever. Used by 100K+ nonprofits, $2B+ raised. For the password vault and the shared drive parts of your binder, use a dedicated password manager and a shared cloud drive.


Amplify your impact with these tested 7 strategies to run a nonprofit. Learn about financial management, creating a funding funnel, and more!


Discover the responsibilities of an executive director in a nonprofit. Read on to find the three vital skills to develop to be the best executive director.
.webp)