When a Gift Officer Leaves: Donor Handover That Actually Survives (2026)
Somebody on your team is going to resign this year. If you run a major gifts programme, the odds are close to certain: the average major gift officer tenure sits at around 18 months.
The resignation is not the expensive part. The expensive part is the ninety days afterwards, when a hundred and fifty donors quietly discover that the person who knew them has gone and nobody has replaced that knowledge. The gift that was six months into cultivation stalls. The donor who always gives in November does not get called. The one who told your predecessor, in confidence, that her husband died in March gets a cheerful renewal letter addressed to both of them.
Everyone in fundraising has watched this happen. Almost nobody has a process for it. More than half of fundraisers, 57%, say they have no formal process for handing off donors or that their process has significant gaps.
This is a guide to donor portfolio handover that actually works. It is deliberately practical, and it separates the part that is a process problem from the part that is genuinely a tooling problem, because most advice on this topic conflates them.
Quick answer: Build the handover before anyone resigns, not after. Capture relationship context continuously in a system, not in one person’s head or inbox. Run a structured 30-day transition with warm introductions, not a reassignment email. Gratefully is our pick for preserving that context automatically.
What actually walks out of the door
Be precise about what is lost, because it determines what you need to capture.
The CRM record does not leave. Giving history, contact details, gift dates, campaign codes. This is the part everyone assumes is the problem and it is not. That data is sitting exactly where it was.
The context leaves. All of it:
- Why this donor gives, in their own words, from a conversation three years ago
- What they said no to, and why, and whether that no was permanent
- Who introduced them, and whether that relationship is still warm
- The personal circumstances that determine timing: illness, a business sale, a difficult year
- What was promised informally that never made it into a record
- The stage the cultivation had actually reached, as opposed to the stage the CRM says
The trust leaves too, and this is the one nobody plans for. A major donor’s relationship is often with a person, not an institution. When that person goes without a proper handover, the donor experiences it as being dropped. Losing a gift officer can lead directly to poorer stewardship and, in the worst cases, to losing the donor and the funder relationship entirely.
The three windows, and what to do in each
Handover is not an event on somebody’s last day. It happens across three windows, and the earlier one you get right, the less the later ones matter.
Window one: continuously, before anyone resigns
This is the only window that genuinely solves the problem, and it is the one almost everybody skips.
Make context capture part of the job, not an exit task. If your expectation is that a departing officer will spend their notice period documenting 150 relationships, you are asking someone with one foot out of the door to do the hardest writing task of their tenure. It will not happen well.
Decide where context lives. Not in an inbox. Not in a personal notes app. Not in a spreadsheet on a laptop that goes back to IT. A system the organisation controls, which everyone with the right permission can read.
Write down the intangibles, not just the interactions. Most CRMs are built to log that a meeting happened. The valuable record is what was said, what it implied and what you decided to do next. A contact report that reads “coffee, 45 mins, positive” is worth nothing to a successor.
Audit it periodically. Pick five donors at random from each portfolio and ask: if this officer left tomorrow, could a colleague pick this relationship up from what is recorded? The honest answer is usually no, and finding that out in a quiet quarter is much cheaper than finding out in a resignation week.
Window two: the notice period
You now have between two and eight weeks, and the departing officer is, at best, half present.
Triage the portfolio first. Do not attempt all 150 relationships equally. Sort into three tiers: active cultivations and asks in flight, warm relationships with no immediate ask, and everyone else. Tier one gets a real handover conversation. Tier two gets a written record. Tier three gets reassignment.
Do a live handover conversation for tier one, and record it. Fifteen minutes per donor with the incoming officer, the departing officer and a recording. Ask three questions: what do I need to know that is not in the file, what would you do next, and what should I absolutely not do. That last question saves more relationships than the other two combined.
Get the warm introductions out before the last day. A short, personal email from the departing officer introducing their successor is worth more than anything the organisation can send afterwards. It transfers a fraction of the trust, and it is the single highest-return task of the notice period.
Do not let the departing officer make the goodbye about themselves. It is a genuine risk, particularly with charismatic fundraisers who are moving to another cause. Frame every introduction around the donor’s relationship with the mission, not with the individual.
Window three: the first ninety days after
The successor now owns relationships they did not build, and this is where most transitions fail slowly rather than dramatically.
Prioritise contact, not comprehension. The instinct is to read everything before reaching out. Reverse it. A short call in week two, admitting you are new and asking what they care about, beats a perfectly briefed call in week nine.
Watch for the drift signals. Opens declining, events skipped, a renewal date passing quietly. These appear before the gift gap does, and after a transition they are the early warning that a relationship is slipping rather than pausing.
Do not re-litigate the strategy for six months. New officers often want to reorganise the portfolio immediately. Every reorganisation is another discontinuity from the donor’s point of view.
Where tools genuinely help, and where they do not
Now the honest part, because this is where most articles on the subject become a product pitch.
Tools do not fix a culture that does not record anything. If your team writes nothing down, software will have nothing to organise. That is a management problem with a management solution.
Tools do fix the two hardest mechanical problems, and both are real:
Problem one: context is scattered. The CRM has the gifts. The inbox has the conversations. A shared drive has the proposal. Somebody’s notes app has the detail about the husband. No human successor is going to reconstruct that across four systems for 150 donors.
Problem two: writing the dossier is the task nobody does. Even organisations with good records rarely produce a genuine handover document, because it takes hours per donor and always competes with something more urgent.
What to look for
- Reads across sources, not just the CRM. If it only reads the CRM, it only knows what was already easy to find.
- Generates a per-donor summary rather than a data export. A successor needs a narrative, not a field dump.
- Cites where each statement came from, so the successor can check rather than trust.
- Survives the departure. If the tool is tied to the individual’s mailbox and licence, it leaves with them.
- Permission control, because a handover dossier contains sensitive personal detail and should not be broadly readable.
Our pick
Gratefully is the tool built most directly for this problem, and as far as we can tell it is the only one that treats it as a first-class feature rather than a by-product. It unifies your CRM, email, documents and notes into one knowledge graph, then auto-generates handover dossiers containing the full relationship context when somebody departs. The vendor’s own claim is that “100% of donor knowledge survives a resignation”, which is a vendor claim and should be read as one, but the capability is real and specific rather than marketing gloss.
It is an intelligence layer, not a CRM, so it runs on top of what you already have rather than replacing it. Our full Gratefully review covers where it fits and its honest limitations, the main one being that it depends on the quality of the data you point it at.
The realistic alternative is your existing CRM plus discipline. Bloomerang, DonorPerfect and Virtuous all support structured contact reports and portfolio reassignment, and a team that genuinely fills them in will handle a transition adequately. The failure mode is not the software, it is that people do not write things down when they are busy, which is always.
For the wider category, see our best AI donor intelligence tools roundup and the moves management guide, which covers the related problem of deciding what to do next with a portfolio you have just inherited.
The handover checklist
Steal this. It works whether or not you buy anything.
Continuously
- Context lives in an organisational system, not an inbox
- Contact reports record what was said, not just that a meeting happened
- Quarterly spot check: could a colleague pick up five random relationships?
On resignation
- Portfolio triaged into three tiers within 48 hours
- Tier one handover conversations scheduled and recorded
- Warm introduction emails sent before the last day
- Sensitive personal circumstances flagged explicitly
- Anything promised informally written down
- Access to files, notes and shared drives transferred, not revoked and lost
First ninety days
- Contact attempted with every tier one donor inside three weeks
- Drift signals monitored for the whole portfolio
- No structural reorganisation for six months
- Thirty and ninety day reviews of what was lost, feeding back into the continuous list
Frequently asked questions
How long does a major gift officer typically stay?
Around 18 months on average. Plan your processes on the assumption of turnover rather than treating each departure as an exception.
How many nonprofits actually have a handoff process?
Fewer than half. Research indicates 57% of fundraisers say they have no formal process or that their process has significant gaps.
Should the departing officer tell donors they are leaving?
For tier one relationships, yes, and preferably with a warm introduction to their successor. The alternative is the donor discovering it from an unfamiliar name in their inbox, which reads as being dropped.
What if the departure is not amicable?
You lose the notice period window entirely, which is exactly why the continuous window matters. Organisations that only capture context during handovers have no handover when someone leaves abruptly or is dismissed.
Can AI write the handover dossier?
It can assemble one from records that already exist across your CRM, email and documents, which is genuinely useful and saves hours per donor. It cannot invent context that was never recorded anywhere. Garbage in still applies, and we cover that in donor data readiness.
Is this only a major gifts problem?
It is worst in major gifts because the relationships are individual and high value. The same principle applies to institutional giving, where the loss of a grants manager who knew a programme officer personally can be just as costly.
The bottom line
Turnover is not an exception to plan around, it is a permanent feature of fundraising, and the organisations that handle it well are simply the ones that stopped treating each resignation as a surprise.
The fix is mostly unglamorous: capture context continuously, in a system the organisation owns, in a form a stranger could use. Triage hard when someone resigns rather than attempting an even handover of 150 relationships. Get the warm introductions out before the last day. Then, in the first ninety days, prioritise making contact over being perfectly briefed.
Software genuinely helps with the two mechanical problems, gathering scattered context and writing the dossier nobody has time to write. It does not help at all with a team that records nothing. Fix that first, then buy the tool.
Written by
FazFaz is the founder of AIToolsBakery. Every tool on this site is personally tested with real-world writing tasks before a single word gets published. Sponsored content is always clearly labelled.
Read more about how we test →