Every January, development offices discover what their database looked like in December. By then it has already sent the receipts.
I understand why cleanup gets pushed to the new year. November is full, December is fuller, and scrubbing records feels like the least urgent thing on the list. But December is when your database works hardest. It sends the year-end appeal, generates the acknowledgments, and supplies the numbers your board will see in January. Every flaw in it gets multiplied by your busiest month.
So do it now. Two focused weeks, before the first year-end gift lands, are enough to fix the problems that cause the most damage.
Week one: duplicates and addresses
Run a duplicate report. Most donor systems have one. Sort by last name and ZIP code, then by email. You’re looking for the same household entered twice: once by the gala registration form, once by the online donation page, once by a well-meaning volunteer. Merge carefully and keep the gift history together.
Why it matters this month: duplicates mean one family gets two appeals, which looks careless, and their giving gets split across two records, which hides how loyal they are. A donor who gave $500 a year for six years can look like two people who each gave occasionally. Nobody upgrades a donor they can’t see.
Clean up households. Decide how you address couples and families, write it down, and apply it. Check for spouses who have separated or died since last year. Sending a joint appeal to a recent widow is the kind of mistake that ends a relationship. Spend an hour with your notes and the obituaries your staff have flagged.
Update addresses. If your appeal goes by mail, ask your mail house to run the list for address updates before it prints. Then mark the returned mail from last year and stop sending to it.
Fix the salutations. Sort by the informal salutation field and scan it. You’ll find blanks, “Dear Friend” where you know the person well, and names that changed. A year-end letter that opens with the wrong name doesn’t get read past the first line.
Week two: acknowledgments
Year-end gifts arrive fast, and every one needs a timely, accurate thank-you. Make sure your system can produce one before the rush.
Know the rules. Under IRS guidance, a donor needs a written acknowledgment from you to deduct any single gift of $250 or more. It should include your organization’s name, the amount of a cash gift (or a description, not a value, of a non-cash gift), and a statement on whether you gave anything in return. If a donor paid more than $75 and received something in return, such as a gala dinner, you owe them a written disclosure with a good-faith estimate of its value. The IRS publication on this, Publication 1771, is short and readable. Confirm the details for your situation with your auditor or tax advisor.
Test your templates. Run each acknowledgment letter for a sample of real gifts: a cash gift, a stock gift, a gift with event benefits, a gift from a donor-advised fund, and a gift made in honor of someone. Read every one. Check the merge fields, the signature, and the tax language. Then fix the template, not the letter.
Decide on speed. Set a standard, such as every gift acknowledged within 48 hours, and assign who handles the gifts that arrive Dec. 31.
Build the January report now
Here’s the part people forget entirely. In January, your board, your head of school or executive director, and your finance office will all ask for the same numbers: total raised, number of donors, retention, and how it compares to last year.
Build those reports now, while you have time to check them. Run them on last year’s data and make sure the numbers match what you reported then. If they don’t, find out why. Usually it’s a definition problem: one report counts pledges, another counts payments; one counts households, another counts individuals.
Write down the definitions you settle on. That page, sometimes called a data dictionary, is the most useful document in your development office, and most offices don’t have one.
Your two-week checklist
- Run a duplicate report and merge the obvious matches.
- Review households, deceased records, and salutations.
- Update addresses and suppress returned mail.
- Test every acknowledgment template with real sample gifts.
- Set an acknowledgment turnaround standard and assign coverage for Dec. 31.
- Build and test the January board report on last year’s data.
- Write down how you define a donor, a gift, and retention.
None of this is glamorous. All of it shows up in how a donor experiences your organization: one letter instead of two, the right name, a prompt and accurate receipt. Good data serves the human story. In December, it is the human story.
Free toolkit. Score your development office in five areas and find out what to fix first. The free toolkit also includes a weekly rhythm worksheet for small shops, a grant go or no-go scorecard, and a one-page gift coding data dictionary. Get the Development Office Self-Audit →
If your database needs more than two weeks of attention, our CRM and Metrics work starts with exactly this kind of cleanup.
– Mary-Ellen
Sources
- Charitable Contributions: Substantiation and Disclosure Requirements, Publication 1771 (IRS)
- Charitable contributions: Written acknowledgments (IRS)
Featured photo: Photo by Rodrigo Rodrigues | WOLF Λ R T on Unsplash.



