How to run availability at a rugby club without losing your mind
The WhatsApp group was never built for taking a register. How to set up selection and availability for the season so it stops eating your week.
Ask any club coach what takes up most of their week and it won't be the training session. It'll be finding out who's available.
It's the invisible job nobody mentions when you take on a team: post the fixture, wait for replies, count who's in, chase the ones who haven't answered, count again because three have changed their minds, and on Friday night still not know whether you've got a front row.
Why the WhatsApp group falls short
It isn't that WhatsApp is badly made. It's made for something else.
A group is a conversation, and availability is a list. When you mix the two, the same three things happen every time:
- Replies get buried. Someone writes "I'm in" and thirty messages later nobody can find it, you included.
- You have to count by hand. And counting by hand through a sixty-message thread is exactly where the mistake creeps in that leaves you with fourteen players.
- Silence goes unnoticed. On a list, an empty slot jumps out. In a chat, someone saying nothing looks exactly like the noise.
A WhatsApp poll fixes just enough: it gives you a tally. But it gets buried like everything else, it doesn't nudge anyone who hasn't voted, and it has no idea which fixture it's about or who's actually in the squad.
What actually works
The fix isn't to stop asking. You have to ask. What you need to get rid of is all the manual work that comes after asking.
A list, not a conversation
Availability has to live with the fixture: Saturday's game with its kick-off time, its ground and its list of replies right next to it. If you have to open something else to see who's coming, you've already lost.
A count that updates itself
Every reply that comes in changes the number. You don't count anything: you just look.
Let it do the chasing
This is the one that saves the most time and gets the least credit. An automatic reminder twenty-four hours before for anyone who hasn't replied gets rid of ninety percent of the "are you coming or not?" messages. And a reminder three hours before for those who said yes cuts down last-minute no-shows, which are the ones that really wreck a session.
A detail that changes decisions
Saying you're coming and turning up aren't the same thing, and hardly any tool tells them apart.
On Tuesday a player replies "in". That's an intention. On Saturday the coach takes the register and marks who's actually on the pitch. That's a fact.
If you keep the two separately, by the end of the season you have the only figure that helps you make decisions: each player's real attendance. Not the ones who say they'll come, the ones who come.
Both numbers matter, but only one decides who plays.
Where to start
If you're going to change how you do it, don't do it in January in the middle of the league. Do it in pre-season, with one team, and let it run for a month before bringing in the whole club.
And one practical thing: don't ask anyone to learn a tool. If a player has to do more than open a notification and tap a button, they won't, and you'll be back in the WhatsApp group within two weeks.
In Kanteo availability works exactly like this: you post the fixture, each player replies in two taps, the count updates itself and the app chases whoever's missing. Set up your club for free and try it with one team before bringing anyone else in.
