Membership sign-up and renewal, for groups run by volunteers.
Last updated 20 July 2026.
Reviewed on 20 July 2026 against ICO guidance on data minimisation, special category data and children's information, and the current text of the UK GDPR and Data Protection Act 2018 on legislation.gov.uk, including the seventh lawful basis added by the Data (Use and Access) Act 2025 and in force from 5 February 2026. To the best of our knowledge at the time of writing. Guidance changes, constitutions differ, and safeguarding practice varies by setting. For decisions about your specific organisation, talk to a solicitor, your designated safeguarding lead, or the ICO directly.
The short version.
Joining and paying are separate events. Treat them as one and you will end up with people who filled in the form and never paid, and people who paid by standing order who were never recorded anywhere.
Everything you ask has to be justifiable. The data minimisation principle in UK GDPR Article 5(1)(c) requires personal data to be adequate, relevant and limited to what is necessary. Information about somebody's health is special category data under Article 9 and needs a condition of its own, and an access requirement falls into the same territory where the answer reveals something about health or disability. Emergency contacts belong to people who never filled anything in. And a membership form that produces a list somebody then retypes into a separate record has done about half the job it was supposed to do.
This is general information for UK organisers, not legal advice. Membership sits across data protection, safeguarding, your own constitution and sometimes contract, and the right answer depends on facts only you know. Nothing here tells you what is lawful in your specific case. For decisions that affect your organisation, consult a solicitor, your designated safeguarding lead, or contact the Information Commissioner's Office directly.
1. Joining is not the same as paying.
Two events, one form, and the gap where members get lost
Ask a committee when somebody becomes a member and you will usually get two different answers in the same room. One person says when they send the form. Another says when the subscription clears. Your constitution or rules probably say something more specific, often that membership rights such as voting at a general meeting depend on the subscription being paid up. That distinction matters at exactly one moment, which is the moment somebody wants to vote, stand for the committee, or claim a member rate, and by then it is too late to decide. The practical problem is simpler than the constitutional one. A form and a payment are two records, they arrive at different times, they usually arrive through different channels, and unless something joins them together a person can exist in one and not the other. Every group has both failure modes: the enthusiastic new member who filled in the form in September and has never paid a penny, and the long-standing member whose standing order has run since 2019 and who has never appeared on any list because nobody wrote them down.
- Decide which act makes somebody a member and write it into your rules, rather than leaving it to custom
- Record the form and the payment as separate facts, so you can see who has done one and not the other
- Expect standing orders and bank transfers to arrive without any reference you can match
- Set a deadline after which an unpaid form is chased rather than quietly forgotten
- Agree what an unpaid member can and cannot do in the meantime, particularly around voting and member rates
- Do not let the mailing list become the de facto membership list. They drift apart within one season
What the gap looks like in practice.
By November the two lists differ by roughly a dozen people in each direction, and nobody knows which dozen. The treasurer sees payments from names that are not on the form list, because a spouse pays for both of them from one account. The membership secretary has forms from people whose payment has not landed, some of whom are waiting to be asked and some of whom have quietly decided not to return.
At the AGM in March somebody asks who is entitled to vote. There is no answer that anybody can defend, so the room does what every room does, which is to assume everybody present is a member and move on. That works right up until the year there is a contested decision.
2. What to ask, and what you are asking out of habit.
Every field needs a sentence explaining why it is there
The data minimisation principle in UK GDPR Article 5(1)(c) requires personal data to be adequate, relevant and limited to what is necessary in relation to the purposes it is processed for. That is a useful discipline rather than a bureaucratic one, because it forces a question most forms have never been asked: what would we actually do with this answer. Membership forms accumulate. A field gets added one year for a specific reason, the reason goes away, the field stays, and eight years later a volunteer is collecting home addresses for an organisation that has not posted anything since 2017. The test is not whether the information might one day be interesting. It is whether you have a present use for it, and whether you would be comfortable explaining that use to the person filling the form in.
Almost always justifiable
Name, email address, a phone number, membership category, emergency contact, and what the person wants to be involved in. These map directly onto things you do.
Justifiable if you use it
Access requirements, dietary needs for catered events, availability for rehearsals, relevant skills, and any qualification your activity genuinely requires.
Usually habit
Full date of birth for adults, home address where nothing is ever posted, occupation, employer, marital status, and a second phone number nobody would ever ring.
The fields groups ask for and cannot justify.
Full date of birth for an adult. Ask why, and the answer is usually that it is on the old form, or that it helps identify people with the same name. If what you actually need is to know whether somebody is over 18, or which age band they fall into for a subscription rate, ask that instead. A full date of birth is one of the most useful pieces of information an identity fraudster can have, and holding ninety of them in a spreadsheet on a laptop is a meaningfully worse position than holding ninety age bands. Children are a genuine exception, because age feeds directly into your safeguarding arrangements and supervision ratios. Separately, child performance licensing can come into play, but it bites on performances and paid activities rather than on membership as such, it is administered by the local authority for the area the child lives in, and plenty of groups never engage it at all. That is covered properly in the guide to auditions and casting.
Home address, when nothing is posted. Membership forms have collected addresses since before email existed, and the habit outlived the reason. If you send an annual newsletter by post, you need it. If you need it for Gift Aid declarations on donations, you need it, and there is a specific reason you can point to. If you communicate entirely by email and WhatsApp, you are holding ninety home addresses because a form template said to.
Occupation and employer. Occasionally there is a real purpose, such as a group that needs to know whether somebody works with children, or a society hoping to identify members who could help with legal or accountancy work. If that is the purpose, ask the specific question. Collecting job titles generally is data you will never use and will never delete.
Everything asked once for a specific year. The question about whether people could help at the 2019 anniversary gala. The one about transport to an away concert. These stay on forms for a decade. Reading your own form end to end once a year removes more unnecessary data than any policy will.
3. Emergency contacts: details for somebody who never filled in a form.
A necessary field with an awkward feature nobody mentions
If you run rehearsals, performances, workshops or trips, you need to be able to reach somebody when a member is taken ill or injured. That is a straightforward and defensible purpose, and it is why almost every membership form has the field. The awkward part is that the person named has not filled anything in, has not agreed to anything, and in a surprising number of cases has no idea their name and mobile number are in your records at all. Their details are still their personal data, and you did not get them from them. UK GDPR Article 14 deals with the information you provide to people whose data you obtained from somebody else, and the transparency principle in Article 5(1)(a) sits behind it. That is a duty, not a courtesy, and the relief from it runs through the exemptions in Article 14(5) rather than through custom. The one most often reached for is Article 14(5)(e), where providing the information would involve a disproportionate effort. It is not a blanket exemption for small organisations: Article 14(6) says whether the effort is disproportionate turns on factors including the number of people involved, the age of the data and any safeguards you apply, and Article 14(7) requires you to take appropriate measures to protect their rights if you rely on it, including by making the information publicly available. That assessment is yours to make on your own facts and to be able to justify. What the guide can say is that groups commonly pair whatever they conclude with two practical habits: say on the form that the member should tell the person they have been listed, and keep what you collect to the minimum that lets you make the call. A name, a relationship and one phone number does the job. A full address, a date of birth and a second contact does not.
- Collect a name, a relationship and one contactable number. Resist the urge to build a second record
- Put a line on the form asking the member to tell the person they have been named
- Say who can see the details and when they would be used, so it is clear this is not general contact data
- Keep emergency contacts out of any list that gets exported, circulated or printed for general use
- Review them at renewal. Relationships and phone numbers change more often than the rest of the form
- For under-18s, the nominated contact and the person with parental responsibility are not always the same person, so ask for both where they differ
4. Health, access and dietary information.
Special category data, collected on a form filled in at a rehearsal
Groups collect health information for good reasons. A dance school needs to know about an injury. A choir touring abroad needs to know about a condition that could become an emergency. A society running a residential weekend needs to know about allergies. The reasons are real, and the answer is not to stop asking. It is to understand what you have taken on. Information about somebody's health is special category data under UK GDPR Article 9, which prohibits processing unless one of the conditions in Article 9(2) applies, and that condition is required in addition to a lawful basis under Article 6. Article 6 now provides seven bases: consent, contract, legal obligation, vital interests, public task, legitimate interests, and the recognised legitimate interests basis inserted by section 70(2)(b) of the Data (Use and Access) Act 2025 and in force from 5 February 2026, which applies only to a closed list of purposes in a new Annex 1. Some Article 9 conditions also require a policy document under Schedule 1 of the Data Protection Act 2018. This guide cannot tell you which condition applies to your group, and any source that offers to without knowing your circumstances is overreaching. What it can tell you is the practical shape of a defensible approach: ask only what you need in order to keep somebody safe during your activity, say on the form exactly who will see the answer, and keep the answers separate from the general membership list.
- Ask a narrow question tied to your activity, not an open invitation to describe a medical history
- Dietary requirements for a catered event and a medical condition are different things. Do not collect them in one field
- Access requirements you can act on are worth asking about. Access requirements you cannot act on are worth being honest about instead
- State on the form who sees the answer: the committee, one named person, or whoever is leading the activity on the day
- Store health answers apart from the main membership record, and keep them out of exports and circulated lists
- Delete them when the activity they related to has finished, unless there is a continuing reason to hold them
- Special category data raises the stakes on a breach, so the fewer fields you keep, the smaller the problem
A worked example of narrowing a health question.
What people usually write
Please give details of any medical conditions.
That question has no boundary. It invites people to disclose things you have no use for, it produces answers you have no plan for, and it puts special category data into your records for reasons nobody wrote down. Some members will over-share and some will write nothing at all, which means you cannot rely on it either way.
What answers a real need
Rehearsals involve two hours of standing and occasional lifting of scenery. Is there anything we need to know in order to keep you safe during rehearsals and performances, or anything you would want the person leading the session to be aware of if you became unwell? Only tell us what you are comfortable telling us. Your answer is seen by the production manager and the chair, and by nobody else. We delete it at the end of the production.
The second version names the activity, explains why the question exists, limits who sees the answer, and states a retention period. It will get you fewer words and more useful ones, which is what you actually wanted.
5. Under-18 members: what changes.
A different signatory, a different set of obligations
For members under 18, the person completing and signing the form is normally a parent or carer with parental responsibility, and that shift changes several things at once. The contact details you hold are theirs as well as the child's. The agreement to your membership terms and code of conduct is theirs. Any photography permission is theirs, and should be a separate decision rather than part of the joining bundle. ICO guidance stresses that children's data needs particular care and must be kept safe and not given to anyone who should not have access to it. UK GDPR Article 8 sets a specific rule for consent where information society services are offered directly to a child, with the UK threshold at 13, but that provision is narrower than the general question of who signs a membership form and it does not answer it. Alongside data protection sits safeguarding, which is a separate obligation with its own requirements: who may contact a child directly, what the ratios are, who holds the register, and what happens on the night. Satisfying one does not satisfy the other, and in a youth theatre or a dance school the safeguarding side usually asks for more than data protection alone would.
- The parent or carer with parental responsibility completes and signs the form for under-18s
- Keep the child's details and the parent's details distinct, because they are used for different things
- Separate photography permission from the joining decision entirely. It must be genuinely refusable
- Ask how you may contact the young person, and follow your safeguarding policy on direct contact
- Where a child is old enough to have a view on optional things, ask them as well as their parent
- Plan for the transition to adult membership at 18, including who the record then belongs to
- Data protection compliance and safeguarding compliance are separate. Do not treat one as covering the other
Photography belongs on its own decision, not in the bundle.
The fix is structural rather than editorial. Two decisions, two places to record them, and a genuine path through the process for somebody who says no to the second. Granular options work better than a single yes or no, because most people are not absolutists: plenty of parents are happy with a photograph in a printed programme and not on a public social account. The photography question is covered properly in the guide to photo and media consent, including what to do about the full-cast photograph when one family has declined.
6. Membership terms and codes of conduct.
A link is not a record, and a living document is not a version
Most membership forms deal with the rules by putting a link on the page. Tick to confirm you have read our code of conduct, with the code living in a shared document or a page on the website. It looks fine, and it fails at exactly the moment you need it. What you have recorded is that somebody ticked a box next to a link. You have not recorded what was behind the link, whether they opened it, or which version was there that day. If the code has since been rewritten, and codes of conduct are usually rewritten precisely because something happened, then every previous sign-off now appears to point at wording those people never saw. It is also worth separating three acts that organisations habitually record identically. Having read something, acknowledging that you have understood it, and agreeing to be bound by it are not the same, and the difference is the first thing anybody will ask about when a code of conduct is invoked.
What you can usually prove
That a named person ticked a box on a particular date. Almost every organisation has this much, and it is the easy part.
What you usually cannot
Which wording was in front of them. Once the document is edited, older sign-offs stop describing what those people actually agreed to.
What fixes it
Freeze the wording shown at the moment of sign-off, give it a reference, and attach the record to that version rather than to a document that keeps moving.
The version problem, in the year it bites.
In 2026 a complaint arises about exactly that. The chair goes to the file. There is a signed form from a volunteer who joined in 2024, and a code of conduct document that now contains the social media section. There is nothing at all connecting the two, and the honest answer is that the volunteer signed a version that did not include the clause.
The organisation has not done anything wrong. It has done what almost every organisation does, which is to keep one living document and a pile of signatures. But the record cannot answer the question, and in a safeguarding matter the record failing is not a minor administrative problem.
Handled on paper this needs a discipline volunteer committees rarely sustain across handovers: date every version, keep every superseded version, record which version number each signature relates to, and re-issue for fresh sign-off whenever a material clause changes. It is entirely doable. It is almost never done.
7. Renewal is a data-cleaning exercise wearing a payment costume.
The one moment each year when the records can be made true
Committees think of renewal as collecting money, and it is, but the money is the least interesting thing that happens. Renewal is the only point in the year when every member is prompted to look at what you hold about them and tell you whether it is still right. Email addresses change. Phone numbers change. Emergency contacts stop being the right person. Access requirements change. Somebody moved house eighteen months ago and never mentioned it because nothing you send goes by post. Renewal is also the moment the membership list becomes true again, because it is the only time somebody has to actively confirm they are still involved. The accuracy principle in UK GDPR Article 5(1)(d) requires personal data to be accurate and, where necessary, kept up to date, and an annual prompt is the most practical mechanism a volunteer-run organisation has for meeting it. Treating renewal as a payment run wastes the one occasion where updating the record costs you nothing extra.
- Show people what you currently hold and ask them to confirm or correct it, rather than asking them to fill in a blank form again
- Re-ask the fields that go stale: contact details, emergency contact, access requirements, what they want to be involved in
- Do not re-ask the fields that do not change. Making people retype their name every year is how you lose responses
- Re-issue the code of conduct for fresh sign-off if it has changed materially since last year
- Record the renewal against the year, so you can see the shape of the membership over time rather than only today
- Use the non-responses. The people who do not renew are telling you something, and it is worth one polite question
The people who quietly lapse.
There are three separate problems in that, and they are worth pulling apart. The first is factual: your membership number is wrong, which affects everything from subscription income forecasting to what you tell a funder. The second is that you are still using their data for a relationship that has ended, which is exactly what the storage limitation principle in Article 5(1)(e) is about. The third is human, and it is the one worth acting on first: some of those people stopped coming for a reason you could have fixed.
Decide in advance what lapsing means. A renewal date, a grace period, one reminder, then a defined point at which somebody becomes a former member. At that point they come off member communications, lose access to member areas, and move into whatever you keep for former members. Say all of this on the form when they join, so the eventual removal is something they were told about rather than something that happens to them.
And send the one polite email asking whether they are coming back. Some will say yes. The ones who say no usually tell you something useful, which is the same reason it is worth asking your audience what they thought rather than guessing.
8. Retention: how long you keep a former member.
The honest current answer in most groups is forever, on a laptop
UK GDPR does not set retention periods. The storage limitation principle in Article 5(1)(e) says personal data must be kept in a form permitting identification for no longer than is necessary for the purposes it is processed for, and the accountability principle in Article 5(2) means the burden of justifying your period sits with you. That is a decision you make and record, not a number you look up. The status quo in most community organisations is not a decision at all. Membership records live in a spreadsheet that has been passed between four secretaries, contains every member since 2011, has never had a row deleted, and exists in several partial copies across personal laptops and email attachments. Nobody chose that. It happened because deleting things takes effort and keeping them takes none. The way out is to separate what you need from what you want. A full membership record, with contact details, emergency contacts and any health information, has a short useful life after somebody leaves. A minimal historical record, often just a name and the years somebody was a member, may reasonably be kept much longer, because societies genuinely do want to know who was in the 1998 production.
- Split the full record from the minimal historical record and give them different periods
- Health and access information should go first, usually as soon as the activity it related to has ended
- Financial records supporting subscriptions run on their own period, set against your governing document and any accounting, company or VAT obligations you actually have
- Set a period you can justify rather than one you have copied. One to three years for the full record is common
- Write it down, even as a single paragraph. Accountability means being able to show the reasoning
- Put the deletion in the calendar, because a retention policy nobody executes is not a retention policy
- Make handover explicit when officers change, so the records move rather than multiply
The spreadsheet on the secretary's laptop.
The membership list is a spreadsheet. It has been emailed between officers as an attachment for years, which means there are eleven versions of it in various inboxes and no way to tell which is current. It contains health information in a free-text column. It is on a personal laptop that is also used by other members of the household. When the secretary steps down, the handover is an email with the file attached, and the outgoing secretary keeps their copy indefinitely because nobody thought to ask them not to.
None of that is negligence. It is what happens when a job with real obligations attached is done by a volunteer in their evenings using the tools they already have. The improvements that actually stick are small: one authoritative copy rather than attachments, access that ends when a role ends, health information kept somewhere other than the main list, and a handover that includes deleting the old copy. Those four changes remove most of the risk without asking anybody to become an administrator.
9. A list of responses is only half a membership system.
Somebody has to turn an answer into a record, and that somebody is a volunteer
Most groups solve the form and stop. The form is fine. It asks sensible questions, people fill it in, and the answers arrive in a tidy list. Then a volunteer opens that list next to the membership record and starts copying. That step is where the work actually is, and it is where the errors are: names typed differently in two places, people entered twice, a payment matched to the wrong person, a new member who never made it across at all because the transfer happened in two sittings and the second one never came. It is also where the delay lives. Somebody who joined in September may not appear as a member until whenever the volunteer next had a free evening, which is why the answer to how many members do we have is so often as at whenever I last did the list. A form that produces a list to retype has done half the job. The half it has not done is the half that takes the time.
- Retyping is where duplicates, mismatched names and lost joiners come from, not carelessness
- The lag between joining and being recorded is invisible until somebody needs an accurate list
- Matching a payment to a person is a separate manual step again, and bank references rarely help
- Every extra place the same person is recorded is another place to update when they change their email
- Ask what happens to a response after it arrives, not just how good the form looks
- The test of a membership system is whether a new member exists everywhere they need to without anybody retyping anything
10. Where this gets broken.
The recurring failures, in roughly the order they happen
None of these come from carelessness. They come from membership admin being handled by whoever had time, in whatever tool was to hand, in an organisation where the committee changes every couple of years and the handover is an email attachment. Reading your own setup against this list will catch most of them before they matter.
- Treating a submitted form as membership, so people who never paid appear on the list and in the AGM figure
- Treating a payment as membership, so people who pay by standing order are never recorded anywhere
- Asking for a full date of birth from adults because the old form did, then holding ninety of them in a spreadsheet
- Collecting home addresses for an organisation that has not posted anything in a decade
- An open-ended medical conditions box with no stated audience, no retention period and no plan for the answers
- Keeping health information in the same list that gets exported and circulated to the whole committee
- Recording an emergency contact who has never been told they are one, along with far more detail than a phone call needs
- Bundling photography permission into the terms somebody must accept in order to join
- A code of conduct behind a link, so the record shows a tick next to a document that has since been rewritten
- Not distinguishing between having read something, acknowledging it, and agreeing to be bound by it
- Rebuilding the whole form at renewal instead of showing people what you hold and asking them to correct it
- Never defining what lapsing means, so former members stay on lists indefinitely
- Keeping every member since 2011 in one file because nobody ever decided to delete anything
- Passing the membership list between officers as an email attachment, leaving copies everywhere
- Retyping form responses into a separate membership record, and losing people in the gap
A practical checklist for a community organisation.
2. Read your own membership form end to end and delete every field you cannot write a one-sentence reason for.
3. Replace any full date of birth for adults with the narrower question you actually need, such as an age band or a confirmation of being over 18.
4. Narrow your health question to your activity, state who sees the answer, and give it a retention period on the form itself.
5. Cut emergency contact details back to a name, a relationship and one number, and ask members to tell the person they have been listed.
6. Separate photography permission from joining, and check that somebody who declines can still complete the process unchanged.
7. Version your membership terms and code of conduct. Date every version, keep superseded ones, and make each sign-off point at the version that person was shown.
8. Turn renewal into a confirm-or-correct exercise rather than a blank form, and re-issue the code of conduct for fresh sign-off if it has changed.
9. Define lapsing: a due date, a grace period, one reminder, and a point at which somebody becomes a former member with a defined record.
10. Set retention periods for the full record and the minimal historical record separately, write them down, and put the deletion in the calendar.
11. Make the handover of membership records an explicit item when officers change, including deleting the outgoing officer's copy.
When to take proper advice.
You are collecting health, disability or other special category data and have not identified which Article 9 condition you are relying on, or whether you need an appropriate policy document under Schedule 1 of the Data Protection Act 2018.
You have under-18 members and your safeguarding arrangements have not been reviewed by somebody qualified to review them. Speak to your designated safeguarding lead first, every time.
Your constitution, rules or articles are unclear about what makes somebody a member, and a contested vote, election or decision is coming.
You are a registered charity where membership carries governance rights, in which case the constitutional position and the charity regulator's expectations both matter. See the charity ticketing guide for the adjacent territory.
You have had a data breach involving membership records, or a member has asked for a copy of everything you hold about them and you are not confident you could find it all.
For any of these, consult a solicitor, your designated safeguarding lead, or the Information Commissioner's Office, which publishes detailed guidance and runs a helpline for small organisations.
If your organisation matches one of these patterns.
If you are an amateur dramatic society where membership, subscriptions and casting all interact, and where the same people are members, ticket sellers and audience, the join between the membership record and everything else is the part that hurts. See notes for amateur theatre groups.
If you are a choir or orchestra taking annual subscriptions from a stable adult membership, the renewal cycle and the payment reconciliation are the whole problem. See notes for choirs and orchestras.
If you are a dance school where most members are under 18 and enrolment happens termly rather than annually, parental consent, safeguarding and the transition to adult membership all matter more than the form itself. See notes for dance schools.
If you are a school running clubs, ensembles and productions alongside everything else, membership data sits next to pupil data and the expectations are higher. See notes for schools.
If you are a church or parish where membership is informal and the boundary between congregation, volunteer and member is blurred, deciding what you are actually recording comes before deciding what to ask. See notes for churches.
If you are a village hall committee with a small membership and a large number of hirers, be clear about which of those you are keeping records on and why. See notes for village halls.
If you are a theatre with a friends or supporters scheme sitting alongside ticket buyers, the overlap between the two lists is where the duplicates and the awkward emails come from. See notes for theatres.
Where tooling makes a difference.
Those are the two questions worth asking of any system. Does a new joiner become a member record without anybody copying anything, and if the code of conduct changes tomorrow, does last year's sign-off still point at last year's wording? Seaty's surveys and forms freeze the exact document shown at the moment of sign-off and give it a reference, distinguish between asking somebody to read, acknowledge or agree, and show a membership column on form responses so people who are not yet members can be promoted in bulk rather than retyped. Whichever route you take, that is the bar to hold a system to.
Related guides and policies
Get the membership record right while the group is small.
Sources & further reading
ICO guidance
A guide to the data protection principles (ICO)
A guide to lawful basis (ICO)
What is valid consent? (ICO)
Special category data (ICO)
Children's information (ICO)
Advice for small organisations (ICO)
UK legislation
UK GDPR (Regulation (EU) 2016/679) (legislation.gov.uk)
UK GDPR Article 5: principles relating to processing (legislation.gov.uk)
UK GDPR Article 6: lawfulness of processing, as amended (legislation.gov.uk)
UK GDPR Article 9: processing of special categories of personal data (legislation.gov.uk)
UK GDPR Article 14: information where data is not obtained from the data subject, as amended (legislation.gov.uk)
Data Protection Act 2018 (legislation.gov.uk)
Data Protection Act 2018, Schedule 1: special categories of personal data (legislation.gov.uk)
Data (Use and Access) Act 2025: data protection and privacy changes (gov.uk)
Safeguarding
Working together to safeguard children (gov.uk)
Keeping children safe in education (Department for Education, gov.uk)
