Donor follow-up

Separate the three jobs

A payment record tells you what the giving system recorded. A receipt or acknowledgment is a document your finance reviewer checks. A personal thank-you is a relationship message. One may arrive automatically while another still needs work. Before building a new routine, ask what your current giving tool already sends and look at a real sample with private details removed. Grantkeeper can organize the records and draft personal notes from approved facts. It does not decide tax wording or whether a particular acknowledgment meets a filing requirement. Keep those questions with the person who handles your organization’s finance and donation records.

Start with a narrow export

Choose a clear period, such as the gifts recorded since the last review. Include the stable gift ID, gift date, recorded amount, fund label, preferred donor name and contact choice. Add the acknowledgment or personal-note status when your system records it. Leave payment details, private care notes and unrelated family information out. If you use a church giving tool, an authorized staff member can export the needed fields. A file lets Grantkeeper read that snapshot; it does not give live access to the giving account. Keep the export date in the filename and in the follow-up log so the next review uses the right period.

Check identity before drafting

Use the donor system’s identifier when matching gifts to notes. A shared surname or email address can belong to more than one person, and a household may have several gifts. Do not merge records from similar names alone. Ask who should be addressed and whether a gift was intended to remain anonymous. A first-gift note also needs reliable history: a short export cannot establish that someone has never given before. Grantkeeper should leave uncertain matches in a review queue. A staff member resolves them in the original system, then supplies the checked facts for the note. That avoids thanking the wrong person or disclosing another donor’s gift.

Write from a checked program update

A useful personal note names the gift or program, thanks the person plainly and shares a short approved update. Avoid assigning an exact result to one gift unless your records support it. A pantry served a recorded number of households during a period; that does not mean a particular donation bought a specific number of meals. Give Grantkeeper the wording your program lead has checked. Ask it to keep the note brief and omit a new fundraising request if that is your intended message. The director or donor contact reviews the draft for names, tone and facts before sending it from the usual account.

Keep contact choices visible

A gift is not a newsletter subscription. Keep the person’s recorded contact choices beside the proposed follow-up. Mailchimp exports separate contact statuses; Constant Contact also distinguishes permission status. Preserve those fields instead of flattening every person into one mailing list. Grantkeeper can prepare text and a review list from an export, but the owner checks the audience in the sending tool. Do not re-add someone who has unsubscribed while trying to fix a missing thank-you entry. If the record is unclear, ask the donor contact to resolve the preferred route. A phone call, posted note and email have different practical needs.

Record what actually happened

The log needs a gift ID, follow-up type, owner, actual send date and a short outcome. Drafted and sent are different states. If a board member makes a thank-you call, record the completed call rather than inventing an email send. Keep replies with the appropriate donor record, especially corrections to a name or contact preference. When comparing gifts against the log, treat a missing entry as a possible gap. Someone may have sent a note without recording it. Grantkeeper can list those possible gaps for review; it should not trigger a second message just because one spreadsheet cell is blank.

Handle corrections through finance

Refunds, duplicate transactions, missing amounts and conflicting addresses belong in a separate review queue. Preserve the original gift ID and the source of each question. Ask your finance lead which record is current before drafting another acknowledgment. For gifts with a named purpose, keep the donor’s wording next to the recorded fund and ask about mismatches rather than choosing an accounting treatment. Grantkeeper gathers and organizes those questions; it does not value donated goods, decide deductibility or issue advice on receipt obligations. After finance resolves the record, update the follow-up log with the checked result so the same problem does not recur next week.

Keep a source trail

Keep the original files beside the working draft. Give each file a clear date and keep later corrections as new versions. A sentence that contains a number should point to a record that another person can open. If a source is missing, keep the question visible rather than filling the space with a plausible answer. Remove private details that the reader does not need. A public update, a staff task list and a finance working paper can use the same checked fact, but they need different access. Test folder permissions with the person who will receive the finished work.

Leave a useful handoff

Finish with the next action, its owner and the date someone will check it. Save the reviewed version where the team already looks for this work. Tell the next person what changed and which questions remain open. Do not mark a task complete because a draft exists. Completion means the person responsible has confirmed the actual result, such as a checked document, a corrected record or a message that was sent. At the next review, start with unresolved items rather than rebuilding the whole process. This keeps a small team’s routine manageable when a volunteer is away or a staff role changes.

Related recipes: First gift welcome, Thank-you gap check, Receipt review queue. Integrations: Mailchimp, Constant Contact, Google Sheets.