The branch secretary's laptop
The north west branch has an energetic volunteer secretary who runs an evening talk every month and a summer social. She keeps a spreadsheet of branch members, built from a list head office sent three years ago, plus people who have come to events since. She sends invitations from her personal email, takes bookings by reply, and tallies numbers for the venue.
When she steps down, her successor inherits a partial spreadsheet, or nothing. Head office does not know which members attended which events, CPD certificates are requested one by one, and some members complain that they receive invitations from branches they left when they moved. Other branches do things entirely differently.
Why branch activity is invisible
Branches are the most local and personal part of membership, but they run on volunteers' own tools.
- Branch member lists are copies that go out of date.
- Invitations go from personal email accounts.
- Bookings are taken by reply and counted by hand.
- Attendance and CPD are not recorded centrally.
- Handover between volunteers loses history.
- Each branch works differently, so there is no picture across the body.
The root cause is that branches have never been given tools that connect to the central membership record.
What the disconnect costs
Volunteers spend their limited time on admin instead of on organising good events, and some step down because of it. Members receive inconsistent communications, sometimes from branches they no longer belong to. Personal data sits on volunteers' own devices, which is something your own data policy will have a view on.
Head office cannot report on branch activity, cannot credit CPD for branch events, and cannot see which regions are thriving or struggling.
How we build branch tools
- Branch volunteers get their own login with access limited to their branch.
- They see the current members in their branch area, drawn live from the membership record, with only the details your policy allows.
- Events are created from a simple form: title, date, venue, capacity and CPD hours, and appear on your website's events page.
- Invitations go to branch members from a central sending service, with the branch name, and members' contact preferences are respected.
- Members book online, and the volunteer sees the booking list and numbers for the venue.
- Attendance is recorded by QR check-in or a list tick, and feeds CPD records and certificates.
- Head office sees events and attendance across every branch, and handover to a new volunteer is just a change of login.
| Branch task | Before | With branch tools |
|---|---|---|
| Member list | Old spreadsheet | Live list for the branch area |
| Invitation | Personal email | Central sending, branch-branded |
| Bookings | Replies counted by hand | Online booking with numbers |
| CPD for attendees | Certificates on request | Automatic from check-in |
| New secretary | Starts from scratch | Same tools, full history |
Branch volunteers keep the personal touch. The tools only take away the admin that sits behind it.
Branch life afterwards
The branch secretary creates next month's talk in a few minutes and sends the invitation to current branch members. Bookings arrive in a list she can check on her phone. On the night, members check in with a QR code, and certificates go out automatically. When she hands over, her successor logs in and sees the branch's events, attendance and contacts.
Head office can see, for the first time, which branches are most active and where support is needed. When a branch has no secretary for a while, head office can run its events from the same tools until a new volunteer steps forward.
Recognise your branches here?
- Branch secretaries keep their own member lists.
- Invitations go from personal email accounts.
- Branch attendance is not recorded centrally.
- Handover between volunteers loses everything.
- Head office cannot see branch activity.