donor_stewardship v1.0.0

name: donor_stewardship description: "Keep donors after the first gift: thank donors within 48 hours with a personal, specific thank you, run giving tiers with different treatment, send impact reporting that shows the money at work before the next ask, work a full cadence calendar, and recover lapsed donors in LYBUNT, SYBUNT, and long lapsed order. Covers retention math with a working calculator, monthly donor care and failed payment rescue, and the US acknowledgment wording for gifts of 250 dollars or more. Use when someone asks about donor retention, stewardship plans, thank you letters or calls, donor tiers, impact reports, second gift strategy, monthly donor churn, or winning back lapsed donors."

Donor Stewardship

Purpose

Stewardship is the work between gifts: thanking, reporting, and staying in contact in a way that gives a donor real reason to give again. It is a revenue discipline, not a courtesy task.

The baseline is rough. Fundraising Effectiveness Project reporting, run by the Association of Fundraising Professionals with GivingTuesday, puts overall donor retention in the low 40 percent range in recent years, with a further decline reported for 2024. First time donor retention is far lower, around 18 to 19 percent. Most first time donors never give a second gift, and small donors leave at the highest rates while major donors retain above 50 percent. A program that acquires donors without fixing the first 90 days is filling a bucket with a hole in it.

Research by Penelope Burk, published in Donor-Centered Fundraising and based on long running donor surveys, points to three things donors consistently want: a prompt and personal acknowledgment, confirmation that the gift was set to work on the specific thing intended, and a report on results before the next ask arrives. Secondary summaries of that research report that a prompt thank you call from a board member to a new donor was associated with a larger second gift and stronger retention. Treat that as a reported association worth copying in practice, not as a guaranteed lift.

This skill ships the full system: the tier matrix, the cadence calendar in references/cadence-calendar.md, copy ready message examples in references/message-examples.md, and the retention math plus a calculator in references/retention-math.md and bin/retention.py.

Workflow

1. Measure before writing anything

Pull the last two full years of gifts and run the report:

bash
python3 bin/retention.py report gifts.csv --current-year 2026

The export needs one row per gift: donor_id, date, amount. Read four numbers first: overall retention, first time retention, dollar retention, and the size of the LYBUNT list. Definitions and warning signs live in references/retention-math.md. If first time retention is the weak number, and it usually is, the fix is step 2 and step 4, not a bigger acquisition budget.

2. Thank fast, thank personally, thank specifically

• Send the formal acknowledgment within 48 hours of the gift. Seventy two hours is the outer limit, not the target. In the year end rush, protect this standard first and cut other work before it slips.
• Match the channel to the gift where practical: email for an online gift, letter or call for a mailed check or a large gift. The automated receipt is the floor, never the whole thank you.
• Every thank you carries five things: the donor name (never a generic greeting), the amount and date, the designation in the donor words or yours if they gave unrestricted, one plain sentence on the specific use, and the date or window when they will hear results.
• Put no ask in a thank you. No donation button in the body, no reply envelope doing quiet soliciting, no event ticket pitch. One job per message.
• Add a human layer by size and history: a short call within days for larger first gifts and for any gift above your personal touch threshold, a handwritten note for mid and major gifts, a board member call for new donors where a board member is willing and briefed. Scripts are in references/message-examples.md.
• Close the legal side in the same document where it applies. For a US contribution of 250 dollars or more, the written acknowledgment must include the organization name, the cash amount, a description rather than a value for any noncash gift, and a statement on whether goods or services were provided, with a description and good faith estimate if they were. Check the IRS wording at the link in Operating Rules, and have local counsel confirm your template. Do not improvise tax language.

3. Assign every donor a tier, and treat tiers differently

Segment on three axes: amount, frequency or recency, and relationship depth. First year donors and monthly donors get their own tracks at any amount, because their behavior and their risks differ from everyone else.

A workable starting matrix, adapted from common published practice. Set your own dollar bands from your file so the top tier holds roughly the top 5 to 10 percent of donors:

| Tier | Acknowledgment | Reporting | Personal contact | |---|---|---|---| | First time, any amount | Receipt plus personal thank you within 48 hours | Impact note at day 30 to 45, report before any second ask | Welcome touch, one invitation in the first 90 days | | Small, example under 250 dollars | Receipt plus personal thank you | Newsletter with real impact content, annual short report | Handwritten holiday or anniversary card | | Mid, example 250 to 999 dollars | Personal email or note from a named staff member | Semiannual impact piece plus annual report | Handwritten card, event invitation | | Leadership, example 1,000 to 4,999 dollars | Handwritten note from the development lead | Mailed annual impact report, program updates tied to their interest | Phone call after gifts, VIP invitation, one agenda free check in a year | | Major, example 5,000 dollars and up | Personal call from the executive or a board member | Custom report on their specific gift before any new ask | One to one meeting offered, early word on news affecting their program | | Monthly, any amount | Clean receipt every month, personal welcome on day 1 | Quarterly impact note, annual summary with total and what it covered | Named human contact, failed payment rescue within 3 days |

Two tier rules matter more than the bands. First, recognition follows the donor preference, not your habit: ask before any public naming, and honor anonymity without argument. Second, stewardship follows the gift designation: a donor who funded one program gets reporting on that program, not a general newsletter blast with their name merged in.

4. Run the cadence calendar

Follow references/cadence-calendar.md. The shape of it:

• First 90 days: receipt instantly, personal thanks within 48 hours, a second human thanks in week 1 for gifts above your threshold, a welcome touch by day 21, a first impact note tied to their designation at day 30 to 45, an invitation or feedback ask at day 60 to 75, and a results report by day 90.
• Months 4 to 12: six non ask touches a year as the floor for small donors, six to eight for mid and recurring donors, eight or more, mostly personal, for leadership and major donors. Newsletters only count when they carry real impact content.
• The report before the ask is a hard gate. A donor who has not received results on their last gift does not go into the next appeal audience. Pull them, send the report, and include them in the following appeal.
• Log every touch in the CRM with date and type. An unlogged touch does not exist for the next person who works the file.

5. Report impact so the money is visible at work

Build every impact report, from a 3 paragraph email to the annual piece, on the same four parts:

• Gratitude: name the donor and the gift, in you language. The donor is the actor in the sentence, the organization is the instrument.
• One person first: lead with a single named person whose situation changed, with written permission for their name, story, and photo. If permission is not there, say the story is typical and change identifying details, or use a staff witness account instead.
• Then the numbers: how many served, what changed, over what period, and the cost basis if you state one. Only use numbers you can source from program records on request.
• Responsibility: one plain statement of how money was used, such as the share that went to programs, administration, and fundraising. Small, clear, and present in every flagship report. This is the part most reports skip and the part that builds trust with repeat donors.
• Close with what happens next and a named contact. No ask in a standalone report. The annual report outline is in references/message-examples.md.

6. Earn the second gift, then the upgrade

• Ask for the second gift only after the report gate in step 4 clears. Anchor the amount near their first gift and name the same kind of specific use. Example copy is in references/message-examples.md.
• Offer monthly giving to proven second time donors, not to cold first time donors as the default pressure move. State the monthly amount, the annual total, what that total covers, and exactly how to pause or cancel. Published benchmark summaries put monthly donor retention far above one time retention, commonly in the 80 to 90 percent plus range, which is why a retained monthly file is worth careful, low pressure building.
• Care for monthly donors as their own program: watch failed payments weekly, run the rescue sequence in the message examples within 3 days, cap rescue follow ups at two, and never use guilt or dark patterns to stop a cancellation. A donor who leaves easily and feels respected is a future LYBUNT worth having. A donor trapped by friction is a complaint and a chargeback risk.
• Upgrade asks go to retained donors with a report history, once a year at most, tied to a named project with a priced outcome. Never upgrade pressure on a donor whose last report is overdue.

7. Recover lapsed donors in priority order

Define lapse on your giving cycle, commonly 12 months with no gift. Work the lists in this order, and report reactivation separately for each list so you can see what is working:

1. LYBUNT: gave Last Year But Unfortunately Not This year. Highest return, work first and personally for larger gifts.
2. Recent SYBUNT: gave Some Year But Unfortunately Not This year, within the last 2 to 3 years.
3. Long lapsed: no gift in 2 plus years. Expect very low returns. Published summaries cite a return likelihood in the low single digits at this distance, around 2.2 percent in one database analysis. Budget effort accordingly and do not judge the program on this list.

Sequence for LYBUNT and recent SYBUNT, spaced at least two weeks apart:

• Touch 1, no ask: an impact update on the program they funded, or the lapsed survey in references/message-examples.md asking what changed. Donor voice research summarized in sector sources finds many lapsed donors are not angry: circumstances changed, priorities moved, or the relationship never got built. The survey sorts those apart so the next touch fits the reason.
• Touch 2: act visibly on what you learned. Changed circumstances gets patience and updates only. Giving elsewhere gets thanks and an open door. Never heard what my gift did gets the missing report, fast.
• Touch 3: the win back ask, anchored to their last amount and the result it produced last time. After this touch, non responders move to a low frequency updates only track. Stop.

Fix data before blaming donors: check for merged duplicates, dead emails, and donors who gave through a spouse, a business, a donor advised fund, or an event page under a different record. A share of every LYBUNT list is a database problem wearing a fundraising costume.

Suppress with discipline: anyone who asks to stop contact is out the same day, donors who gave through a workplace or matching platform and never opted in to direct contact stay out of appeals, and long lapsed non responders stay out of paid acquisition lookalike seeds if your platform uses them.

8. Review quarterly, fix one leak at a time

Each quarter, rerun the retention report, compare on unchanged definitions, and pick the single worst leak: first 90 days, monthly payment failures, mid tier silence, or LYBUNT growth. Assign it an owner, a fix, and the number it should move by next quarter. Stewardship programs fail by drift, with ten small intentions and no owner, far more often than they fail by strategy.

Output Contract

A stewardship job delivers, as the task requires:

• A baseline memo: overall retention, first time retention, dollar retention, monthly retention if applicable, LYBUNT and SYBUNT counts, each with the period and definition used, plus the single worst leak named.
• A tier matrix for the file: bands, acknowledgment standard, reporting promise, and personal contact per tier, with a named owner per row.
• A dated cadence calendar for the next 12 months, with the first 90 day sequence spelled out per new donor cohort, channel and owner on every touch, and every ask marked and counted separately from stewardship touches.
• Finished message copy, not outlines, for each touch being launched: thank you, welcome, impact note, report, second gift ask, monthly welcome and payment rescue, lapsed survey, and win back. Each checked against Operating Rules.
• A lapsed recovery plan: list sizes in priority order, the three touch sequence with dates, suppression rules applied, and the reactivation target stated per list as a range based on the organization own history where it exists.
• A quarterly review note: what moved, what did not, and the one leak being fixed next.

Operating Rules

• Never invent numbers, stories, or donor details. Impact figures come from program records, quotes and stories need the person permission, and a composite or typical story must be framed as one. An unverifiable claim gets cut, not rounded into confidence.
• Benchmarks set expectations, they do not grade the program. FEP figures, Burk findings, and monthly retention ranges in this skill are sector context with sources in the research notes pattern: cite them as ranges, grade progress against the organization own trailing years, and never promise a donor or a board a specific lift from a thank you call or any single tactic.
• A thank you contains no ask, ever. A report contains no ask. If leadership wants an appeal, it ships as its own piece, after the report, clearly separate.
• Respect contact preferences absolutely and immediately: channel, frequency, anonymity, and full suppression. Stewardship never overrides an opt out, and a lapsed donor who declines is thanked and left alone.
• Handle donor data as sensitive personal data: minimum access, no donor lists in public documents or unsecured spreadsheets, no sharing or selling of donor information, and payment details only inside the payment processor, never in notes or email.
• Keep the IRS acknowledgment wording accurate for US gifts of 250 dollars or more, per the IRS page on written acknowledgments: https://www.irs.gov/charities-non-profits/charitable-organizations/charitable-contributions-written-acknowledgments and IRS Topic No. 506: https://www.irs.gov/taxtopics/tc506 . Outside the US, check the local receipting rules before adapting templates. Flag, do not guess, any tax question a donor asks: refer them to their own adviser.
• Write plainly, in the donor language, at a reading level a tired person can follow at midnight. Short sentences, concrete nouns, no fundraising jargon in donor facing copy: say lapsed only internally, never to the donor.
• Test every number the calculator prints against the raw counts once by hand before it goes in a board document. A retention rate with the wrong base year is worse than no rate at all.