Records That Keep Faith After Staff Leave
This lesson teaches how to write stewardship-continuity records for bequest intenders: records that preserve donor meaning, permissions, boundaries and uncertainty without turning the CRM into a forecast, legal file or surveillance log.
Listen to the lesson
The next fundraiser should inherit judgement, not fragments
Course 1 Lesson 9 owns the Four-Stage Bequest Record. This lesson does not rebuild it. The planned Administration & Pipeline course will handle full CRM architecture, reporting systems, coding, dashboards and pipeline administration.
This lesson is narrower.
It asks: what must be recorded so the next person can steward the donor safely?
Bequest-intender stewardship is unusually exposed to staff turnover. A major-gifts pledge might be completed in months. A campaign commitment may run for five years. A bequest intention may sit inside the organisation’s memory for a decade or more. During that time, the original fundraiser may leave, the donor may move house, the organisation may merge, the CRM may be replaced and the donor’s wishes may change.
The Facts & Evidence Pack notes that bequest income is delayed and lumpy: a gift disclosed today may arrive years or decades later, or not at all. Wishart and James found that bequest intentions can change before death. The record therefore has to preserve two truths at once.
The donor told us something important.
The donor did not give us something we own.
A stewardship-continuity record is not a legal file. It is not a biography. It is not a place to store gossip, family judgement, capacity speculation or every emotional detail a donor shared. It is not a shadow forecast.
It is a disciplined note that allows the charity to keep faith with the donor’s actual words, permissions and preferences after the original relationship-holder is gone.
The standard is simple:
A new staff member should be able to read the record and know how to care for the donor without guessing, overreaching or asking the donor to repeat private information.
Framework
The Stewardship-Continuity Record
Use this record for disclosed intenders and for high-care interest-stage supporters. Keep it short enough to be used, but complete enough to prevent harm.
-
1
Record stage and evidence
What it is: The existing stage from Course 1 Lesson 9, paired with the evidence for that stage. Do not write only “legacy donor” or “bequest prospect.” Name what was actually said or done.
Why it matters: A bare label lets future staff inflate the record. Evidence keeps the stage honest.
Show it in use: “Stage: disclosed intention. Evidence: donor said during 3 September 2026 call, ‘I have added the choir to my will as a percentage gift.’ No amount or percentage volunteered.”
Do not write: “Confirmed legacy donor — high value.” -
2
Exact donor language
What it is: The donor’s own words about meaning, values, people, place or motivation.
Why it matters: The exact phrase helps future stewardship stay personal without forcing the donor to retell the story. It also stops the organisation reducing the donor to “bequest file.”
Show it in use: “Donor phrase to preserve: ‘The choir gave my son a room where his stutter didn’t matter.’”
Do not write: “Likes inclusion work.” -
3
Permission boundary
What it is: What the donor has allowed the charity to record, share internally, send, ask, publish or revisit.
Why it matters: A bequest disclosure is not general consent. Future staff need the boundary more than they need enthusiasm.
Show it in use: “Permission: may record confidential intention and connection to youth choir. Access limited to bequest lead and supporter care manager. Do not share with board, volunteers, event hosts or communications team. Donor does not want questions about value.”
Do not write: “Very private.” -
4
Contact preference and cadence
What it is: The channel, rhythm and limits for stewardship contact.
Why it matters: A future staff member should not have to infer whether to call, write, invite or suppress contact. Lesson 4 established that cadence is remembered presence inside clear limits.
Show it in use: “Contact: handwritten note once each November after youth concert season. Ordinary annual report by post is welcome. No phone calls unless donor initiates. No event invitations because donor finds evening travel difficult.”
Do not write: “Keep warm.” -
5
Recognition and story status
What it is: Whether the donor allows recording, invitation, naming, storytelling or later review of recognition preferences.
Why it matters: Lesson 6 separated recognition permissions. Future staff must not mistake private disclosure for permission to name or profile the donor.
Show it in use: “Recognition: no public naming, no legacy society listing, no story use, no photograph. Donor is comfortable receiving private thanks from program staff if routed through bequest lead. Review only if donor raises it.”
Do not write: “Anonymous for now.” -
6
Legal and information boundary
What it is: A note of what organisational information was provided and what advice boundary was stated.
Why it matters: In Australia, the charity may provide its full legal name, ABN, DGR status and approved wording where relevant. It must not advise on estate structure, family provision, personal tax outcome or whether wording is legally valid.
Show it in use: “Sent approved gifts-in-wills information on 5 September 2026: legal name, ABN, DGR status and suggested wording. Staff stated charity cannot provide legal or financial advice and encouraged donor to speak with solicitor.”
Do not write: “Will wording sorted.” -
7
Sensitive-context flag
What it is: A factual note of any stewardship-relevant sensitivity: family concern, health context, recent bereavement, third-party involvement, vulnerability concern, restriction request or escalation decision.
Why it matters: Future staff need to know what should slow contact. They do not need staff opinions about relatives, capacity or motives.
Show it in use: “Sensitive context: donor mentioned adult daughter is unaware of the intended gift and may disagree. No discussion of family fairness. Staff advised donor to seek independent legal advice. Do not raise family topic unless donor does.”
Do not write: “Daughter may cause trouble.” -
8
Next action and owner
What it is: The next appropriate stewardship action, who owns it, and when it should be reviewed.
Why it matters: A record without an owner becomes passive. A record without a review date becomes stale. The action must be stewardship, not extraction.
Show it in use: “Next action: bequest lead to send youth concert season note by 30 November 2026, focused on inclusive rehearsal practice. Review contact preference in March 2028 unless donor re-engages earlier.”
Do not write: “Follow up later.” -
9
Reporting caveat
What it is: A short internal warning about how the record may and may not be used in reporting.
Why it matters: Lesson 1 established that a bequest intention is private, non-binding and volatile. Lesson 3 established that disclosed intentions are relationship indicators, not income. The record should carry that caution forward.
Show it in use: “Reporting: disclosed intention only. Not confirmed income. No value estimate. Do not include in budget forecast. Count only in stewardship-intention reporting.”
Do not write: “Pipeline: likely $500k.”
Scenario
The file that almost broke the relationship
Ruth Okafor is 76. She has supported an inclusive youth choir for eight years. Her gifts are modest: $25 most months and an extra $200 after the annual concert. Her adult son sang with the choir as a teenager and still attends concerts when he can.
The former bequest officer, Daniel, had a careful relationship with Ruth. After one concert, Ruth told him she had added the choir to her will. She did not want public recognition and did not want phone calls. She liked receiving a handwritten note after the annual youth concert because it reminded her of her son’s time in the choir.
Daniel left the organisation. His CRM note read:
“Ruth O — legacy donor. Son connection. Private. Good prospect. Keep close.”
Eight months later, a new development manager, Priya, reviews the file before the annual appeal. She sees “legacy donor” and “good prospect.” Wanting to be attentive, she sends Ruth an invitation to a legacy-society lunch and adds a handwritten line:
“It would be wonderful to celebrate the future gift you have so generously confirmed.”
Ruth replies by post:
“I am disappointed. I told Daniel I did not want to be in any group. I also did not say anything was ‘confirmed’ for you. Please remove me from whatever list this is.”
The problem is not that Priya ignored the record.
The problem is that the record was too thin to guide her.
A proper stewardship-continuity record would have protected both Ruth and Priya:
“Stage: disclosed intention. Evidence: after 2025 annual concert, donor told Daniel, ‘I have included the choir in my will.’ No amount, percentage or documentation provided.
Donor meaning: son sang with choir as teenager; donor said, ‘It was the first place he sang without trying to hide.’
Permission: confidential record only. Do not add to legacy society, public list or event invitation stream. Do not use phrase ‘confirmed gift.’
Contact: no phone calls. Donor welcomes one handwritten note after annual youth concert, focused on current singers and inclusion practice. Ordinary receipts and annual report by post remain welcome.
Recognition: anonymous. No public naming. No story use. No photograph. No legacy society invitation unless donor asks.
Information boundary: approved legal name, ABN and DGR status sent on 12 May 2025. Donor advised to seek solicitor advice. No will copy requested.
Sensitive context: donor protective of son’s privacy. Do not mention son by name in external materials.
Next action: send post-concert note each November. Owner: bequest lead. Review preference in late 2027 by post only.
Reporting: disclosed intention only. Not income. No value estimate. Not for budget forecast.”
Priya’s correct next step is not another invitation. It is repair:
“Dear Ruth,
I am sorry. We did not respect the preference you had already given Daniel, and our wording overstated what you had told us.
I have removed you from the legacy-society invitation list. We will not refer to your intention as a confirmed gift, and we will keep your information confidential.
If you are still comfortable receiving the quiet post-concert note each year, we will continue that. If you would rather we stop those notes too, please tell me and I will update the record.
Thank you for correcting us.
Priya”
The repair works because it does not defend the CRM, blame the former staff member or ask Ruth to re-explain herself. It corrects the record and restores the boundary.
Next step
Run a continuity-record audit
Choose ten bequest-intender records. For each record, answer these questions.
1. Could a new staff member tell which Course 1 Lesson 9 stage the donor is in and what evidence supports it?
If no, add exact source evidence:
“Donor requested wording only.”
“Donor said she is considering a gift.”
“Donor disclosed existing provision.”
“Estate notification received.”
2. Does the record preserve the donor’s own words?
If no, add one exact phrase where available. If none exists, write:
“No donor meaning language recorded yet. Do not invent.”
3. Does the record state what the donor has permitted?
If no, mark:
“Permission unclear. Before changing stewardship, ask preference; do not assume recognition, phone contact or internal sharing.”
4. Does the record tell future staff what not to do?
If no, add the relevant boundary:
“No public naming.”
“No phone calls.”
“No family discussion.”
“No value questions.”
“No legacy society invitations.”
“No story use.”
5. Does the record separate stewardship from reporting?
If no, add:
“This is a relationship record, not confirmed income. Do not assign value unless donor has volunteered it and internal policy allows restricted recording.”
6. Does the record include a next action and owner?
If no, add a single stewardship action:
“Send annual written update after program milestone.”
“Check contact preference by post in 18 months.”
“Pause bequest-specific contact until ethics review is complete.”
“Return to ordinary donor care only.”
7. Does the record contain material that should not be there?
Remove or restrict:
– staff opinions about family members;
– amateur capacity assessments;
– unsupported value guesses;
– private medical detail not needed for stewardship;
– solicitor details where the donor did not authorise recording;
– copied will documents unless the organisation has a clear policy, authority and secure storage process.
End the audit by creating one standard note template:
“Stage and evidence:
Donor language:
Permission boundary:
Contact preference and cadence:
Recognition and story status:
Legal / information boundary:
Sensitive-context flag:
Next action and owner:
Reporting caveat:”
Do not wait for a CRM rebuild. A plain note written properly is better than a sophisticated system filled with unsafe shorthand.
Key idea
Record enough for the next steward to honour the donor, and not enough to turn private intention into organisational possession.
What you now know
Bequest-intender records are not administrative residue. They are part of stewardship.
A good record protects the donor after the original staff member leaves. It preserves exact words, permissions, boundaries, cadence, recognition choices, sensitive context and reporting caution. It does not store gossip, guesses, legal conclusions or value estimates dressed as strategy.
Course 1 Lesson 9 gives the stage. This lesson gives the continuity note that lets the stage become safe behaviour.
The next fundraiser should not need to rediscover the donor’s boundaries by breaking them.