A donor database for small charities beats memory

Aug 29
3 min read

Updated: 2 days ago

Introduction

In a great many small charities, the donor list lives in a spreadsheet on one person's laptop, supplemented by what the chair remembers about who gave what and why.

This works until that person steps back, and then years of relationships disappear at once. Nobody knows who the regular supporters are, who gave last Christmas, or which of the twelve people at the fundraising dinner had promised to think about a legacy. A donor database is not an administrative luxury; it is the only thing that makes the relationships survive the people managing them.

1. A donor database for small charities exists to outlive individuals

That is the purpose, before any feature list.

The test is simple: if the person who currently knows everything left tomorrow, could someone else pick up the relationships? If the answer is no, the tool you are using is not sufficient regardless of what it costs.

2. Record fewer fields and record them consistently

Ambition here is the enemy of use.

Name, contact details, consent status, gift history with dates and amounts, source, and a notes field. A system with forty fields, thirty of them empty, tells you less than a simple one that is actually filled in.

3. Capture how each donor arrived

The field most often missing and most useful.

Event, appeal, referral, website, a friend. Without it you cannot tell which activities produce donors who stay, and every debate about where to spend next year comes down to opinion.

4. Treat consent as a data field, not a memory

This is an obligation with real consequences.

Record what each person agreed to receive, when, and how. Data protection rules vary by market, and the practical requirement everywhere is that you can show the basis on which you are contacting somebody.

5. Log the conversation, not just the transaction

The notes field is where the value accumulates.

One asked about volunteering. Another gives every year in memory of someone. A third said to come back in the autumn. This is precisely the knowledge that vanishes with a departing volunteer, and it takes seconds to type.

6. Choose a tool you can actually maintain

The best system is the one that gets updated.

A well-organised spreadsheet with agreed rules beats an unused donor management platform. Consider cost, whether more than one person can access it, whether you can export everything, and whether it will still make sense to the person after you.

7. Make sure you can get your data out

Ask this before you put anything in.

Export in a standard format, without paying for the privilege, at any point. A system that holds your records hostage turns a switch into a rebuild, and small organisations change tools more often than they expect.

8. Protect it properly

A donor list is personal data about real people.

Access limited to those who need it, strong authentication, no untracked copies on personal laptops, and a real backup that has been tested by restoring from it. Check what your local rules require rather than assuming.

9. Use it, or it will rot

An unused database becomes wrong quite quickly.

Pull a list from it monthly for something practical: thank-yous due, lapsed donors, monthly gifts that failed. A system consulted regularly gets corrected; one that is only written to becomes unreliable within a year and is then abandoned.

Set a rule that anything agreed with a donor gets recorded the same day. The gap between a good conversation and a note nobody wrote is where most of the loss happens, and it is a habit rather than a system problem.

Conclusion

Build the records so they survive the people who hold them, because relationships lost with a departing volunteer cannot be reconstructed.

Keep the fields few and fill them consistently, always capture how the donor arrived so you can judge your activities, treat consent as recorded data rather than memory, write down what was said and not only what was given, choose a tool your organisation can realistically maintain, confirm you can export everything before committing, protect personal data with limited access and a tested backup, and pull practical lists from it every month so it stays accurate.