Most membership organisations in the UK are small. NCVO counts 166,000 voluntary organisations across the UK, and micro and small organisations make up 80% of the sector. In most of them, membership runs on whoever put their hand up for it: a membership secretary with a spreadsheet, a form tool, a shared drive and a payment link, held together by memory and goodwill.
Money is tight as well. In this year’s Charity Digital Skills Report, 63% of charities say squeezed finances are their biggest barrier. So when a small organisation starts looking at membership management software, the real question is rarely about features. It is whether one tool can take over the jobs that currently eat the membership secretary’s evenings.
This checklist follows the life of a membership, from the first application to the AGM, and sets out what your software should handle at each stage. For each one, it compares the usual patchwork with what a single member portal does instead.
Why the patchwork stops working
The patchwork usually starts sensibly. Someone sets up an online form for applications. Responses land in a spreadsheet. Documents go in a shared folder, and dues arrive by bank transfer or through a payment link. Each tool does its one job well enough.
The trouble is the gaps between them. Every new member has to be copied from the form into the spreadsheet, added to the mailing list, given the folder link and matched against a payment. Each copy is a chance for the records to drift apart. After a year or two, nobody is quite sure which list is the real one.
Then the membership secretary steps down, and the whole system turns out to live in one person’s inbox and one person’s head. Small organisations feel this most, because the role changes hands more often and there is rarely a paid member of staff to hold things together in between.
A good piece of membership software closes those gaps by keeping the person, their membership, their payments and their paperwork on one record. The checklist below is a way of testing whether it really does.
The checklist: running a membership, stage by stage
1. Joining: people come in on your terms
Every organisation admits members differently. A residents’ association might take anyone who lives on the estate. A private members’ club or a professional institute might want to read every application first. Your software should handle both, and let you change your mind later without rebuilding anything.
Look for an application form you build yourself, with the questions that matter to you: dates, dropdowns, file uploads and agreements, with required fields that nobody can skip. If you review applications, every approve or decline should be recorded with a reason, and approving someone should put them straight onto the right membership tier with the access that tier allows. If you would rather not review anyone, open registration should let people sign up and walk straight in.
Many organisations also need new members to complete more than one step: accept the terms, then fill in their details, then sign a declaration. Ordered onboarding lines those forms up so nobody skips one and nobody gets in until they have finished.
With the patchwork, this is a form response, a row in a spreadsheet, a manual welcome email and a folder link that may well get forwarded to someone who never joined.
2. Consent and acceptances, stamped as they happen
Your members accept your terms, your privacy policy and often a code of conduct. The question you will eventually be asked is which version they accepted, and when.
Membership software should store every acceptance with the date and where it came from, so the proof exists without anyone filing it. When you update a policy, the people it affects should be asked to accept the new version before they carry on, while the record of who accepted the old one stays intact.
The same goes for forms. Answers should be frozen the moment they are given, so editing a form next year does not quietly rewrite what members told you last year. When something material changes, you should be able to ask everyone to complete the current version and keep their older responses on file against the version they were made under.
A tick box on a form does none of this. It tells you someone ticked something, at some point, on whatever the form said at the time.
3. Membership tiers and dues that match up
Most organisations run more than one kind of membership: full and associate, individual and household, student and concession. Some tiers are not offered to the public at all, such as honorary or life membership, which only the committee hands out.
Your software should let you define your own tiers, choose which one new arrivals start on, and keep some tiers off the public list so only your team can assign them. If you retire a tier, the people already on it should carry on as before. Members should also be able to move between the tiers you allow without emailing you, with their access and billing following the change.
Then there are dues. Put a price on a tier and the software should collect it when it falls due, with renewals, lapses and reinstatements handled against the member’s own record. Because the tier also decides what each member can see, who has paid and who has access stop being two separate questions.
Compare that with the familiar routine: bank transfers arriving with no reference, someone ticking names off by hand, and an answer to who is paid up that is always a week out of date.
4. Annual declarations that come round on their own
A lot of membership admin repeats every year. Volunteers re-confirm their safeguarding training. Members of a professional body log their continuing professional development. Coaches upload a certificate that expires on its own date.
Look for recurring goals that renew themselves. Each one holds for its period and then comes round again, so nobody has to remember to send the reminder and nothing quietly falls out of date. You should be able to see every member against every requirement in one view, filter it down to whoever is overdue, and export it when somebody asks for evidence.
For professional bodies, CPD tracking belongs here too: members record what they have done, attach their evidence, and the portal counts it towards the hours you require in each period.
5. Members-only content that reaches the right people
Minutes, newsletters, handbooks, rules and resources all need a home. In the patchwork, that home is a shared folder, and its link is the only lock on the door.
Membership software should let you mark every page, document, event and announcement as public, open to all members, or limited to particular tiers. Anyone without access should not see it at all. When someone leaves or lapses, their access should change with their membership rather than depending on someone remembering to revoke a link.
Announcements are worth checking separately. You should be able to schedule one to go live on a set date and come down on another. If the portal sends email, it should come from your own address with your name and logo, so members recognise it and it does not look like a stranger writing in.
6. Events and paid tickets
The AGM, the annual dinner, the training day and the summer social all need bookings, and many of them need payment. Running them on a separate ticketing platform leaves you with another login, another set of fees and another list of names to reconcile against your members.
Your software should let you publish events with ticket types, capacity limits and sale windows, take payment at the point of booking, and keep capacity, attendance and payment on one record. Members should see the events they hold tickets for and the ones still open in one place. Discount codes for particular event categories, with your own limits on who can redeem them and for how long, are the details that make a members’ event feel like a benefit of joining.
7. A member directory members control
Members often want to find each other, especially in networking groups, alumni associations and professional bodies. The old answer was a printed or emailed list, which is out of date the day it goes out and hard to justify under data protection law.
A directory inside the portal fixes both problems. You choose which fields appear and which tiers can look, and members decide whether they appear in it at all. When someone leaves, they drop out of the directory without anyone editing a document.
8. AGM votes with a result on record
Votes on resolutions, committee elections and changes to the rules need to be fair and checkable. An online survey anyone with the link can answer is neither.
Look for polls and formal votes where you decide which tiers get a say and when voting closes. The count should be done for you, and the result kept on record, so the minutes can point to it and nobody has to trust a show of hands on a video call.
9. A record of who agreed to what
Sooner or later someone asks a question you can only answer with a record. When did this member join? Who approved them? When did their address change, and who changed it? What exactly did they agree to?
Good membership software keeps a full record of who agreed to what as people use it. Every meaningful action should be logged with the person, the time and what changed, and each member’s record should show a readable history of changes with the values before and after. You should also be able to export everything in full whenever you like, because your members’ data belongs to you.
In the patchwork, answering any of those questions means searching old email threads and hoping the person who did it still remembers.
10. A clean handover when the role changes hands
Membership secretaries, treasurers and chairs all move on eventually. The test of your setup is whether the next person can pick it up on day one.
Your software should let you invite colleagues by email and decide what each one can do, with safeguards that stop anyone granting themselves more access than they have. Private internal notes on a member’s record, visible to your team and never to the member, keep the context that used to live in somebody’s head. When everything sits in one place, handing over the role means handing over a login, not a box file.
How to use this checklist when comparing membership software
Start by scoring your current setup against the ten stages above. Be honest about which ones are handled by a person rather than a system. The stages that depend on someone remembering are the ones that break first when that person is busy, ill or gone.
As FormaPortal, we suggest starting with whichever stage costs your volunteers the most hours, and judging any tool on that first. For most small organisations, that is joining and dues, because they touch every member every year.
When you talk to suppliers, a few questions sort the options quickly:
- Can members join through open registration, through an application you review, or both?
- Does every plan include the full feature set, or are records, payments and events held back for the expensive tiers?
- What does the provider charge on payments, and is that quoted before or after card processing fees?
- Can you export all of your data, in full, whenever you like?
- Does the portal run on your own domain and send email from your own address?
Seen together, the ten stages describe what good member portal software does: one journey from application to tiers, members-only content and subscription payments, with the record kept as it goes.
Membership management software for small organisations: where to start
Membership management software for small organisations should do one thing above all: take the copying, chasing and reconciling off your membership secretary. If a tool still leaves you moving names from a form into a spreadsheet, matching payments by hand or reconstructing who agreed to what from old emails, it has not replaced the patchwork. It has joined it.
Use the checklist as a scorecard. A tool that covers joining, consent, tiers and dues, recurring declarations, members-only content, events, a directory, votes, a full record and a clean handover is doing the whole job. The FormaPortal team recommends giving each candidate the same real task, such as admitting a new member and taking their first year’s dues, and watching how many places that task has to touch. One is the right answer.