Your database already knows which appeal worked. It just can’t tell you, because nobody coded the gifts the same way twice.
Gift coding is the least loved job in a development office and one of the most consequential. Every report your board sees, every retention rate, every “should we mail again in spring?” conversation depends on four small labels attached to each gift. When those labels are consistent, a few clicks answer real questions. When they aren’t, someone spends a weekend in a spreadsheet, and the answer still comes with an asterisk.
Here’s a scheme a small shop can keep straight, and a one-page template to hold it in place.
The four codes, and the question each one answers
Most donor databases use some version of these four. The names differ from system to system. The jobs don’t.
Fund. Where does the money go? The fund tells your finance office how the gift can be spent: general operating support, a scholarship fund, a building project, an endowment. This is the code your auditor cares about, and it should match the funds in your accounting system exactly. Donor restrictions live here. Since the accounting standard update known as ASU 2016-14, nonprofits report net assets in two classes, with donor restrictions and without them, so your fund list needs to make that distinction obvious.
Campaign. What larger effort does this gift count toward? A campaign is a fundraising goal with a time frame: this fiscal year’s annual fund, a capital campaign, a special project. One campaign can collect gifts to many funds.
Appeal. What specific ask prompted the gift? The fall letter, the spring email, the gala paddle raise, a board member’s personal outreach. Appeals are how you learn what works.
Source. How did the gift arrive? Online form, check by mail, stock transfer, donor-advised fund, payroll deduction, event registration. Source tells you about channels and processing, not about persuasion.
The most common mistake I see is using one code to do another’s job. A fund called “Gala 2027” mixes up where the money goes with what prompted it. An appeal called “Online” confuses the ask with the channel. Keep each code answering only its own question, and the reports almost write themselves.
A coding scheme a small shop can keep
Consistency beats cleverness. A scheme with twelve codes that everyone uses correctly is worth more than one with two hundred that only its author understands.
Funds: few and stable. Match your chart of accounts, and keep the list short. Most small organizations need an unrestricted operating fund, one fund for each restricted purpose donors regularly give to, and an endowment fund if you have one. Add a fund only when finance adds one.
Campaigns: one per effort, per fiscal year. Use a pattern that sorts well: the effort, then the fiscal year. AF-27 for the fiscal 2027 annual fund. CAP-ARTS for a multiyear capital campaign for an arts building. Close each campaign when its time frame ends.
Appeals: one per ask, named so a stranger could guess it. Pattern: fiscal year, season or month, channel, short name. 27-FALL-MAIL for the fall letter, 27-DEC-EMAIL-3 for the third December email, 27-GALA-PADDLE for the paddle raise. If a single mailing goes out in two versions, give each its own appeal code so you can compare them.
Sources: a fixed list nobody edits. Online, check, cash, stock, donor-advised fund, wire, payroll, event, other. Eight to ten values cover almost everything. Lock the list so it can’t grow by accident.
Three rules hold the scheme together:
- Every gift gets all four codes. No blanks. If you don’t know the appeal, use a single catch-all code (27-UNSOLICITED, say) and review those gifts monthly.
- New codes are created by one person. Everyone else requests them. This is the single best defense against “Fall Appeal,” “fall appeal 2026,” and “FA26” all meaning the same thing.
- Codes are never renamed after gifts are attached. Close them and create new ones instead, so last year’s reports still match last year’s board minutes.
What good coding lets you ask
When the four codes are clean, questions that used to take a weekend take minutes:
- How much did the fall letter raise, and from how many donors, compared with last year’s?
- What share of annual fund dollars came online versus by mail?
- Which appeals brought in first-time donors?
- How much restricted money arrived that finance needs to track separately?
- Did the second December email raise enough to be worth sending again?
That last question is the one that changes behavior. Most offices keep doing things because nobody can prove they don’t work.
The one-page data dictionary
Write it all down. A data dictionary is a short document that says what each field means, what values are allowed, and who decides. It’s the difference between rules that live in someone’s head and rules that survive a staff transition.
Copy this template, fill it in, and keep it where everyone who enters gifts can find it.
| Field | What it answers | Allowed values or pattern | Example | Who can add values | Notes |
|---|---|---|---|---|---|
| Fund | Where the money goes | Matches chart of accounts | Scholarship Fund | Finance, with development | Note whether restricted |
| Campaign | What effort it counts toward | EFFORT-FY | AF-27 | Development director | Close at end of time frame |
| Appeal | What ask prompted it | FY-SEASON-CHANNEL-NAME | 27-FALL-MAIL | Development director | Separate codes for test versions |
| Source | How it arrived | Fixed list | Donor-advised fund | Nobody (locked) | Review list once a year |
| Gift date | When it counts | Date received, not date entered | 2027-12-31 | n/a | Year-end mail rule set with finance |
| Soft credit | Who else gets recognition | Linked record | Spouse, board solicitor | Gift processor | Never changes the gift amount |
Below the table, add three short lines:
- Owner. The one person who approves new codes.
- Review date. When the dictionary is checked each year.
- Catch-all codes. The codes used when you don’t know, and who reviews them monthly.
That’s the whole page. Print it, tape it next to whoever processes gifts, and update it whenever a rule changes.
Starting from where you are
If your current codes are a tangle, don’t try to recode ten years of history. Pick a start date, usually the beginning of your next fiscal year, and apply the new scheme from that day forward. Map old codes to new ones in a simple crosswalk so you can still compare year over year. Fix history only where a report your board relies on depends on it.
Then hold a thirty-minute training for everyone who touches gifts: staff, the volunteer who helps with mail, the business office. Walk through the dictionary, process five real gifts together, and answer questions. Repeat it whenever someone new joins.
Good data serves the human story. Gift codes are how you find out which parts of that story your donors are responding to.
If your database needs more than a new coding scheme, our CRM and Metrics work can help you set the rules and make them stick.
– Mary-Ellen
Sources
Featured photo: Photo by Ilya Semenov on Unsplash.
