Member administration with one register and every role

The problem is rarely the register, it is the copies

Most associations have a member list. The problem is that they have it several times: the treasurer's spreadsheet, the coach's team list, the mail program's recipient group and the website login. When someone moves or leaves, one of them gets corrected and the rest quietly drift apart.

Member administration is therefore less about keeping a list and more about there being only one list, with everything else reading from it.

Roles decide who sees what

A shared register requires controlled access. A coach should see their team's participants and contact details, not the association's finances. A treasurer should see payment status. The board should see what it is responsible for, without every volunteer gaining access to all personal data.

Roles and permissions are not an optional extra here. They are what makes it defensible to keep everything in one place at all.

Self-service keeps the register current

The most effective measure is letting members correct their own details. A new address, a new phone number, a new consent for photos. Then the register is updated by the only people who know when something changed.

Joining and leaving belong in the same place: a member signs up themselves, dues are collected automatically, and leaving takes effect everywhere at once.

GDPR is part of the job, not an afterthought

Member details are personal data, and the association is the data controller. In practice you must be able to answer who has access, how long you keep it, and what you do when a member asks for access or deletion.

That is easier to answer when the data sits in one governed place than in spreadsheets on five private computers. There is more on this in our guide to GDPR for associations.

Joining and leaving are two dates, not a deletion

The most common misstep in member administration is deleting a member who has left. That also removes the answer to how many members the association had last year, who was on the team in 2024, and whether the person paid what they owed. The association loses its own history in order to tidy up.

A membership has a start date and an end date. A departed member stands as resigned with a date, not as non-existent, and is therefore still counted in the season they belonged to. Deletion is something else: it is the act GDPR gives a person the right to ask for, and the association must be able to perform it deliberately, not as housekeeping in a list.

Extracts are what the register is actually used for

Nobody opens a member register to look at it. They open it to get hold of a subset: everyone on the U15 team, everyone in arrears, everyone who has not given photo consent, everyone over 18 with a vote, everyone who joined after New Year.

That is where a spreadsheet stops being enough, and also where many systems disappoint. If the association can store a field but cannot filter on it, the field is decoration. So the requirement is not that the register can hold your fields, but that it can search them, and that the result can become something: a mailing list, a collection, an attendance list.

With us the fields are the association's own and they are searchable, precisely because a field you cannot filter on might as well have been a free-text note.