Introduction · The digital foundation
The digital foundation of an association: five systems that should be one
Member register, subscriptions, sign-ups, communication and numbers. Most associations have all five layers — in five separate tools that nobody asked to fit together.
An association needs five things: a member register, a way to collect subscriptions, sign-ups for activities, a channel out to members, and numbers the board can trust. When those five things live in five separate systems, the board's time does not go into the work — it goes into moving information between systems and working out which one is right.
This series takes the five layers one at a time: what the layer has to do, what it costs to keep it in a spreadsheet, and what changes when it connects to the other four. Start here, then read part 1 on the member register.
What is the foundation made of?
Five layers, in the order they build on each other. Each layer has its own part in the series.
1. The member register. Who is a member, with what status, role and consent. Everything else points back here. Part 1.
2. Subscriptions and payment. What membership costs, who has paid, and when it reaches the books. Part 2.
3. Activities and booking. Sign-ups, payment for participation, waiting lists, and the courts, rooms and teams that have to be allocated. Part 3.
4. Communication. News, newsletters, messages and minutes — reaching the right recipients. Part 4.
5. Insight. Membership development, arrears, attendance and churn, based on numbers nobody has to assemble by hand. Part 5.
Why do the seams cost the most?
Each individual tool does its job. The spreadsheet can list members. The bank can receive money. The mail client can send. The problem sits between them.
A new member signs up through a form. Now it has to be entered in the spreadsheet, on the mailing list, on the team list and in the accounts — four places, by hand, by someone who also has a job. A member leaves, and is removed from three of the four. Six months later the association sends an invoice to someone who is not a member, and a newsletter to someone who asked to be deleted.
This is not carelessness. It is the predictable consequence of maintaining the same fact in several places. The more lists, the more places they can disagree.
Signs the foundation is split
- Nobody can state the member count without opening two files first.
- The treasurer reconciles the bank account against a list someone else maintains.
- Activity sign-ups arrive as replies to a post or an email.
- The newsletter goes to a list last updated around a general meeting.
- Handing over to a new board means forwarding files and explaining where they live.
In what order should you change?
From the bottom. The register first, because the other four layers read from it. If you start with subscription collection, you are invoicing from a list you do not trust — and then you move the error into the accounts.
An order that works for most associations: register, then subscriptions, then activities, then communication, and finally insight. Insight comes last, not because it matters least, but because numbers only become trustworthy once the four layers beneath them are one dataset.
Each step is useful on its own. You do not have to change everything in one weekend, and you should not do it in the middle of the subscription season.
Who owns the foundation when the board changes?
The most fragile thing in an association is not the system. It is the volunteer who knows how it fits together. When the treasurer stops after eight years, both the access to the files and the explanation of why they look the way they do walk out of the door.
A foundation split across personal spreadsheets and private mail accounts cannot be handed over — it can only be rebuilt. When everything sits in the association's own system with roles instead of people, a handover is a matter of moving a role from one member to another.
That is the test of whether the decision to clean up outlasts the current board.
Before you move anything
Three questions that decide how hard this gets
Who owns the current member list, and when was it last reviewed? What information do you have consent to keep? And who on the board should see what, once you no longer share a single file?
Those three answers determine the work — not the choice of system.
Frequently asked questions
Is one platform overkill for a small association?
The number of members does not decide it — the number of handovers does. An association with 60 members where three different volunteers maintain three lists has more duplicated work than one with 400 where everything sits in one place.
Can we keep our current bank and bookkeeping?
Yes. The foundation is about where member and payment information originates and connects, not about who keeps the books. Payments can be captured in the platform and posted onward.
What if we only need one of the five layers?
Then start there, but take the register as your starting point. The other layers can be switched on later, and they read from the same register when you need them.
What do we do about the systems we cannot drop?
Keep them, but decide which system is authoritative. As long as one list is the source and the others read from it, there is no conflict to clean up afterwards.
How long does a change take?
The setup itself is hours. What takes time is cleaning up the list you are moving — duplicates, leavers who were never removed, and fields nobody can explain any more.
Continue to part 1: the member register
Part 1 is about the layer everything else reads from: one member register with roles, status and self-service instead of spreadsheets and mailing lists.