Membership database: what to record so renewals do not depend on memory
A membership database has one job: knowing who is current and who is about to lapse. The fields, the renewal cycle, and the reports worth having.
Donor management is retention work, not filing. The fields that predict a second gift, the ones that waste effort, and how to keep the history usable.
Donor management is the work of knowing who gave, why, and what happened next — so that a first gift has a chance of becoming a second. Most small organisations can produce a list of donations and almost none can produce a list of donors who gave last year and not this one. The first is bookkeeping; the second is the entire job, and it needs a record rather than a spreadsheet of transactions.
Donor management becomes manageable when the list stops being one list.
A donor who has given twice is several times more likely to give again than a first-time donor. That single fact should decide where the effort goes: second-gift conversion before new acquisition, almost always.
One row per donor with gifts, contacts and consents attached is the shape that answers the questions that matter — who lapsed, who upgraded, who has not been thanked. Ettex Records holds that, with the gift history on the donor row rather than in a separate sheet, and Ettex Mail sends the acknowledgements from the same data so nobody is copying names between systems. Where the donor completed a form to give, Ettex Forms delivers the submission onto the record instead of into an inbox.
Retention rate by segment, second-gift conversion within ninety days, average gift by source, and lapse count over the last quarter. Total raised is a result, not a measure — it tells you what happened without telling you what to do. A membership database has the same problem in a different shape: renewal rate is the number that matters, and gross subscriptions is the number that gets reported.
For as long as the relationship plus any statutory retention on the financial side. Keep consents indefinitely with their dates — proving when someone opted in is the point of holding them.
Once you process payments, claim tax reliefs, or run multiple appeals with attribution, yes. Below that, a register plus your payment provider's reports covers it — see nonprofit fundraising crm for where the line sits.
They see the aggregate, and the named major relationships they are asked to help with. Full access for everyone on the board is a data protection problem waiting to happen.
A membership database has one job: knowing who is current and who is about to lapse. The fields, the renewal cycle, and the reports worth having.
Work order tracking fails on status, not on software. The states worth having, the fields that make them meaningful, and when a register is not enough.
A maintenance report should answer what is failing, what it cost and what to do next. The four views worth producing, and the data they need.