A tribute gift creates two thank-yous, not one. The donor needs a receipt and a thank-you. The family being honored, or the person the gift remembers, needs to hear that someone made a gift in that name. The donor letter usually goes out on time because it rides along with the rest of your acknowledgments. The second letter, the one the family is waiting for, is the one that slips, sometimes for weeks.
That delay is the part people notice. A grieving family that hears nothing, or hears about one gift but not another, remembers it. The good news is that most of the fix is process and data discipline, not software.
Where tribute acknowledgments usually break
When we look at how organizations handle tributes in Altru, the problems tend to fall into a few buckets:
- The acknowledgee was never captured. The gift is marked as a tribute and the honoree is named, but nobody recorded who should be notified or where to send it. You can’t send a letter to an empty field.
- The tribute lives in a note. “In memory of Grandpa Joe, please tell Susan” typed into a comment or memo field is invisible to any query. If it can’t be queried, it won’t make it into a letter run.
- Duplicate tribute records. The same honoree gets set up three times by three different staff, so gifts are split across records and the family gets three partial letters, or none.
- No one owns the second letter. Donor acknowledgments have a routine. Tribute notifications are often “whoever remembers,” which means they wait until someone asks.
- Gifts from online forms arrive incomplete. If your donation web form asks “Is this gift in honor or memory of someone?” but doesn’t collect the notification name and address, staff have to chase the donor afterward.
Tighten the data at the point of entry
Every downstream problem gets easier if the gift is entered completely the first time. A few habits make a big difference:
- Search before you create a tribute. Make it a rule that staff look up the honoree by name before creating a new tribute. For memorial gifts that come in clusters after an obituary, set up the tribute once and point everyone to it.
- Treat the acknowledgee as a real constituent. Put the person being notified into Altru with a proper address (and email, if you have it) rather than typing their details into a text field. That’s what lets a query find them later.
- Agree on a required minimum. Tribute type (honor or memory), honoree, acknowledgee, and whether the donor wants the amount shared. If any of those is missing, the gift goes into a short “needs follow-up” list rather than being saved and forgotten.
- Fix your web form questions. If your online giving form allows tributes, make sure it asks for the notification recipient’s name and mailing address in the same step. Whether your current Altru form can collect everything you need is worth testing yourself with a sample gift before relying on it.
Build a weekly run you can trust
The most reliable improvement is a simple, scheduled routine driven by a query rather than by memory.
One query for tribute gifts awaiting notification
Create a revenue query that returns tribute gifts in your date range along with the tribute name, tribute type, acknowledgee name and address, donor name, and whether the donor asked to keep the amount private. Save it with a clear name so anyone covering for you can find it.
Exactly which tribute and acknowledgee fields are available in Altru’s query views, and how acknowledgment status is tracked on tribute gifts, can vary with how your database was set up. Build the query in a test environment first, or check with Blackbaud support if a field you expect isn’t there.
A fixed day and an owner
Pick one day a week. One named person runs the query, sends the notifications, and marks them complete so the next run doesn’t pick them up again. If you can’t mark completion inside Altru the way you’d like, keep a simple log of the last date range you processed. The point is that nothing depends on someone remembering.
Group by tribute, not by gift
When ten people give in memory of the same person, the family would rather receive one letter listing the donors than ten separate envelopes over three weeks. Sort the query by tribute and decide whether you send a combined notice on your weekly run or individual ones. Either is fine; pick one and be consistent.
Get the letter itself right
- Never disclose the amount by default. Name the donor, say a gift was made, and leave the dollar figure out unless the donor explicitly said it’s okay.
- Use separate templates for “in honor of” and “in memory of.” A celebratory tone and a condolence tone don’t mix well in one letter with a merge field swapped.
- Close the loop with the donor. The donor’s own thank-you can mention that the family has been (or will be) notified. That one sentence heads off a lot of “did they get my message?” calls.
- Watch for deceased flags and bad addresses. Check that the acknowledgee isn’t marked deceased and that the address isn’t flagged as returned mail before the letter goes out.
Email or paper?
Many families still expect a printed card, especially for memorial gifts, and you won’t always have an email address for the acknowledgee. Email works well for the donor’s acknowledgment and for honor gifts where you do have an address. A practical mix: email the donor immediately, mail the family notification on your weekly run, and email the family as well when you have their address and the occasion suits it.
Speeding up the email side
Once your tribute query is solid, the email piece can be automated. Email Designer sends branded emails from Altru queries without manual exports, so a donor’s tribute thank-you, or a family notification when you have an email address, can go out on schedule from the same query you already maintain. Printed letters for families without email still follow your mailing routine.
Quick answers
Should tribute notifications go out before or after the donor’s thank-you?
Aim for the same week. The donor letter can go out first, but the family notification shouldn’t trail it by more than your weekly cycle.
What if the donor didn’t tell us who to notify?
Contact the donor once, quickly, and ask. If you can’t reach them, record that on the gift so it drops off your follow-up list instead of lingering.
