What leaves the building with your development director
Gratefully is an AI donor intelligence and stewardship platform built exclusively for nonprofits.
Best fit: nonprofit leadership, HR and executive publications, board governance
When a development director resigns, the organisation runs a well-practised process. Notice period, exit interview, files handed over, laptop returned, a leaving card. Somewhere in there, a successor is recruited and briefed.
What almost never happens is any serious attempt to capture what that person knew, as distinct from what they filed. And the gap between those two things is where the actual cost of the departure sits.
The knowledge that was never a document
Consider what an experienced development director carries about a single major donor.
Why they give, which is rarely the reason on the pledge form. Which family member is the actual decision maker. That they will not take a meeting in the last week of their fiscal year. That the previous executive director handled a grant badly in 2021 and it is still remembered. That their interest moved from the capital campaign to the scholarship fund after a specific conversation nobody minuted.
None of that is in a CRM field. Some of it is in free text notes, unevenly. Most of it exists only as the reason that person makes the choices they make, and it is invisible precisely because it works.
Multiply by a portfolio of eighty relationships. That is what walks out.
Why the handover does not catch it
The standard handover fails for a structural reason, not a motivational one.
You cannot hand over what you do not know you know. Ask a departing officer to document their portfolio and you will get the things they can consciously retrieve, which is the top few relationships and whatever they happen to think of on the day. The rest is tacit. It surfaces only when a situation calls for it, and by then the person is gone.
Notice periods make it worse. The last four weeks are typically the busiest and least reflective of a person's tenure, competing with wrapping up live work, and documentation is the item that slips.
We wrote about the wider pattern in institutional memory loss in nonprofits, including why the effect compounds in organisations with normal sector turnover rather than unusually high turnover.
What the successor inherits
The new director opens the database and finds names, giving history, contact details and a variable quantity of notes. What they cannot see is the shape of each relationship: how warm it is, what stage it is at, what was promised, and what would be a misstep.
So they do the only rational thing. They start again. They introduce themselves, ask discovery questions the donor has answered three times before, and rebuild an understanding that already existed six weeks ago.
Donors notice. Being asked to re-explain yourself to a new person at an organisation you have supported for eleven years is a small indignity, and small indignities accumulate. The giving does not usually stop dramatically. It softens.
A handover that works
The exercise that produces the most for the least effort is narrow and specific. Rather than asking for portfolio documentation, ask for twelve answers per relationship, in the departing officer's own words, recorded rather than typed if that is faster.
The twelve are things like: why does this person give, who is the real decision maker, what did we last promise them, what has gone wrong before, what should the next conversation be about, and who else here knows them.
Twelve questions across the top thirty relationships is a manageable amount of work in a notice period, and it captures the majority of what matters. We turned it into a free donor handoff checklist that teams can run without any particular system.
The harder truth is that a handover is the worst possible time to do this. The information should already exist, captured as it was created, rather than reconstructed under time pressure by someone who has already mentally left.
The board framing
If you sit on a board, this is worth one question a year: if our development director left next month, what would we lose that is not written down anywhere?
The answer will be uncomfortable, which is the point. Turnover in this role is normal and will happen to you eventually. The organisations that handle it well are not the ones with better exit processes. They are the ones where the knowledge was never held in one person's head to begin with.