Club call-ups without the WhatsApp chain

The team manager writes on Tuesday: «Saturday, 10am, municipal pitch, please confirm». By eleven at night there are thirty-one messages, four thumbs-up, two «I think so», a ninety-second voice note and a photo of somebody’s dog. On Saturday, eighteen turn up.

It isn’t anyone’s fault. A messaging group is built for conversation, and a call-up is a list of people each with a state. Two different things, and goodwill doesn’t turn one into the other.

The three failures every club has

1. The yes gets buried. Somebody confirms at 18:40. By 19:00 there are nine more messages about studs. That yes no longer exists in any usable sense: recovering it means scrolling, reading and counting.

2. Nobody knows who hasn’t answered. Which is the number that actually matters. The ones who say yes sign themselves up; the work is chasing the eight who never opened it. In a group chat, those eight are invisible.

3. A poll counts, but doesn’t name. WhatsApp polls help a bit and still don’t solve it: you get a number, it gets buried like everything else, it doesn’t nudge whoever hasn’t voted, and it isn’t attached to the event. Change the kick-off time and the poll still says what it said.

What a call-up has to do to be worth anything

Without naming a tool yet. If you build this in a shared spreadsheet and it works, go ahead:

• It lives with the event. Date, time, venue and answers in one place. If you have to open something else to know who’s coming, you’ve already lost.
• It has three states, not two. Yes, no, and hasn’t answered yet. The third one is where the work is, so it’s the one to see first.
• A no carries a reason. Not to police anyone: so the staff can tell «I’m working Saturday» from «my calf hurts», which are very different problems, and one of them belongs to the S&C coach.
• It goes to the right group. The senior side doesn’t need the colts’ fixtures. Call up the whole club and half of them learn to ignore notices, and from then on they read none of them.
• It reminds on its own. The day before, to whoever hasn’t answered, without anyone having to remember to chase.

The design mistake nearly everyone makes

Calling up forty and hoping twenty-three sign up is not the same as picking twenty-three and telling them. The second looks tidier and it’s a trap: it forces you to pick the squad before you know who is available, and you end up redoing it three times.

What works is calling up the whole category, seeing who can make it, and deciding afterwards. Availability is an input, not a consequence.

If the club has minors

Everything changes. The person answering isn’t the player, it’s the guardian; you need it on record who that is and what they have consented to; and a group chat with twelve kids and their parents is, on top of being ungovernable, a data-protection problem no club wants.

Whatever you build has to allow for the person who answers and the person who plays being different people.

And an honest test of whether your system works

Ten o’clock on Friday night, without opening your phone and without asking anyone: do you know how many are coming tomorrow, and who still hasn’t answered?

If the answer is «I’d have to check», it doesn’t matter what tool you use. You haven’t solved it yet.