The transition playbook

When a departure is planned (a retirement, a known move, a promotion from within), the transition can be designed rather than survived. This playbook is the apparatus: what to document, whom to introduce, and in what sequence, so that the person who inherits your program inherits its relationships and knowledge intact, not just its logins. Adapt it to your timeline; even a compressed transition benefits from doing these things in this order.

The master transition document

One organized document (or a well-structured folder), built over your final months, containing:

1. The state of the program. Where things stand: the current plan and its progress, the pipeline's shape, the calendar's next year, open commitments and promises, and the honest paragraph about what is working and what your successor should watch. This is the philanthropy strategy memo, updated as a handoff.

2. The relationship briefs. The heart of it. For every top relationship (start with the top [20–40]), a brief that goes far beyond the CRM: who they are and their history with the institution, what they care about and why (in their words), the state of the relationship and its next steps, the sensitivities and the do-nots, the family and advisor context, and the story only you know. Written so a capable stranger could pick up the relationship without re-discovering what took you years to learn.

3. The knowledge that lives nowhere else. Board dynamics and histories, vendor and consultant relationships, the institutional memory ("why we do it this way"), the landmines ("never seat these two together"), and the practical wisdom that no policy document holds.

4. The systems documentation. How the machine runs: the calendar and its deadlines, the moves and stewardship rhythms, the reporting cadence, the passwords and access (transferred securely), and the vendors and their contacts. Enough that the program keeps running during the gap.

The introduction plan (the irreplaceable part)

Documents transfer knowledge; only you can transfer trust. In your final months, personally introduce your successor (or, if they are not yet hired, prepare the ground) to the relationships that matter:

• The top tier, in person, together. A transition visit where

you introduce your successor, vouch for them in your own voice, and explicitly hand off: "Sarah is taking this on, and I have told her everything about what you have built here. You are in good hands." Donors take their cue from your confidence; give it generously.

• The next tier, by warm letter or call. A personal note

introducing the successor and the continuity, so no important donor learns of your departure from a form letter or, worse, from silence.

• The board and key partners, briefed and reassured, with the

succession framed as designed, not disruptive.

The introduction plan is what most transitions skip and what most determines whether relationships survive. A successor introduced warmly by a trusted predecessor starts with borrowed trust; a successor who inherits only a database starts cold, and the donors feel the drop.

The timeline (for a planned departure)

• 6+ months out: begin the master document; identify the

relationships needing personal handoff; ensure systems are documented and multi-threaded.

• 3 months out: the introduction visits begin with the top

tier; the successor (if hired) shadows key meetings.

• Final month: the next-tier introductions; the document

finalized and walked through with the successor or interim; the board's formal reassurance.

• After you leave: a clean break with a bridge: available for

a defined period for questions ("call me anytime for the first ninety days"), but not hovering, because the successor must be allowed to own the relationships, not borrow them from your shadow.

If the departure is not planned

Not every exit is designed; sometimes you are the one receiving a program from a predecessor who left nothing. The same document, built in reverse, is your first-90-days project: reconstruct the relationship briefs from the records and from asking (donors, colleagues, board), rebuild the knowledge by interviewing everyone who holds a piece, and resolve that your own eventual successor will inherit better than you did. The best response to a bad handoff is to break the cycle.

The playbook's deeper point

A transition done well is a final proof of everything this curriculum teaches: that fundraising is relationships and systems, not personal magic, and that a program built on relationships and systems can be handed forward intact. The leader who can leave a program stronger than they found it, and transfer it cleanly to the next steward, has done the whole job, including its last chapter. The next lessons look past the handoff to what comes after, the consulting and teaching paths that let a seasoned professional keep giving to the field, from a new seat.

Evidence and adaptation note

This is a working tool, not a universal benchmark. Replace every bracketed field and example number with your organization's facts. Composite cases are labeled; their figures illustrate the method and should not be cited as sector results. Check legal, tax, privacy, employment, and accounting language against current guidance and your jurisdiction before adoption.

Primary reference for review

Use this as a professional-practice starting point. The named reviewer still owns the final interpretation and must confirm that the source is current.

• Association of Fundraising Professionals, Code of Ethical Standards: https://afpglobal.org/ethics/code-ethical-standards