← Blog

Membership changes before the fee collection: who keeps the list up to date?

Membership changes before the fee collection: who keeps the list up to date?

Tuesday evening, quarter to nine. The treasurer of the tennis club wants to collect the membership fees on Thursday and opens the member list. Then he sees that the shared mailbox holds twelve changes. Two members have moved, a family is cancelling, a junior member is moving to a different category, and someone has given a new email address in a reply under a newsletter. Each change is five minutes of work, but searching takes more time than changing.

Almost every club knows an evening like this. The work is not difficult. It is scattered, and it goes wrong in the places where nobody looks.

Where the time really goes

Let's calculate with an example, not with a measured figure. Suppose that as secretary you receive twelve changes a month and each of them takes a quarter of an hour: reading, looking up the member, checking whether the national federation membership changes along with it, updating the list, confirming. That makes three hours a month, and more in the weeks before a fee collection, because everything comes in at once.

The hours are the least of it. More annoying is what gets left behind:

  1. a cancellation that is processed too late, so a direct debit still goes out to a former member
  2. a new email address that exists only in an email, so the invitation to the general meeting goes to the old address
  3. a junior member who stays a year too long in the wrong category and therefore pays the wrong amount

None of these mistakes is dramatic. Each of them costs a phone call, and a volunteer who wonders why he is doing this in the first place.

What an agent takes over

In the catalogue the role is called Club Secretary. It processes membership changes, prepares the general meeting from agenda to minutes, sorts the post from the federation and the municipality, and keeps the grant calendar. It costs 99 euros per month, excluding VAT, with 40 tasks per month included. For this workflow, every change becomes a task.

The agent reads the email, pulls out the change, looks up the member and prepares the modification. If a message is not unambiguous, such as a member writing that "we'll take a break next season", it does not turn that into a cancellation. It flags it and puts the question to you.

Why you approve an outcome

Many systems have you approve an intention in advance: "process changes from the mailbox". You say yes to a sentence. What then happens to the list, you only see once it has happened.

At Stilops, a test run comes first. It shows what would happen: twelve changes read, ten unambiguous, two flagged as doubtful. For each change you see the member, the old details and the new ones. Only when you approve that outcome is the change carried out. That costs you a few minutes of looking instead of a quarter of an hour of searching per change.

An example from this work. The message reads: "This is Jan, we've moved to Utrecht." The list contains two members with that first name. An intention reads "process address changes" and does not say which Jan. An outcome shows the name, the member number and the address, and asks you for confirmation.

What stays with you

Approving remains human work. At a club it is about members you know, about fees and about children's data. A cancellation that is processed wrongly, you only notice at the next collection. That is why you see in advance what changes, and per task you see what it costs.

It costs speed, because you still look at the outcome yourself. But looking at a ready-made list with two flagged doubtful cases is something different from opening twelve emails yourself.

Try it yourself

You can view the test run without an account or payment details, in the demo on the site. Choose a role that fits your own work, see what the outcome puts ready for you, and then judge whether it would help you on a Tuesday evening at quarter to nine.

Stilops only uses strictly necessary cookies (signing in, language preference, and in the demo your demo session and a counter against abuse) — no consent needed for those. We only count anonymously how many pages are viewed per day and which website visitors come from — without cookies and without storing anything about you. Analytics that follows you would only run after you agree here.