Small-sided football has a specific organizational problem, and it isn't the football. A weekly futsal or 5-a-side game needs an exact number of people, the pitch has to be paid for whether or not they turn up, and the whole thing usually runs on one person's willingness to chase a group chat every week. This is what that job actually involves, and how to make it take two minutes instead of two evenings.
Why small-sided games are harder to organize than a full team
An 11-a-side club has slack in it. Turn up with fourteen and you have subs; turn up with twelve and you play. A 5-a-side game has none: ten players is a game, nine is a game with a rolling sub problem, and eight means someone is playing the whole hour with no rest and one team is a man down. The margin between a good game and a bad one is one person.
That's compounded by how these groups are made up. A club has a registered squad. A weekly futsal game has a roster of eighteen names, of whom about ten play in any given week, and the ten are different every week. There's no obligation, nobody is being selected, and a dropout at 6pm on the day of a 20:00 kick-off is completely normal behaviour.
So the organizer ends up doing three jobs at once: filling the game, holding the booking, and collecting the money. All three are made harder by the fact that the only tool most groups have is a group chat, which is very good at conversation and very bad at counting.
The number is the whole job
Everything else — the pitch, the money, the teams — follows from knowing how many are actually coming. Get that right on Monday and the rest of the week is easy.
Filling the game without asking every week
The default approach is to post "who's in for Thursday?" and then count emoji. It fails in a predictable way: some people answer immediately, some answer if reminded, some never answer but always turn up, and one person replies "maybe" and is never heard from again. By Wednesday you have a thread of forty messages and no reliable total.
The fix is to make the answer structured rather than conversational. When each player responds in, out or unsure against a specific session, you get a count instead of a conversation — and, just as usefully, a list of who hasn't answered at all. Those are the people worth a nudge; everyone else has already told you.
Setting the game up as a recurring session removes the weekly ask entirely. The Thursday game exists for the rest of the season, everyone gets it automatically, and your job shifts from chasing answers to watching a number.
- Set the game once as a recurring weekly session rather than posting it each week
- Keep a roster bigger than the game — sixteen to eighteen names for a ten-player game is normal
- Nudge only the no-responses, not the whole group
- Let people mark themselves unsure; a real maybe is more useful than a polite yes
Handling the 6pm dropout
Someone will drop out on the day. This is not a discipline problem to be solved, it's a fact of amateur sport to be planned around. The question is only whether the group finds out in time to replace them.
In a group chat, a dropout is a message that lands among other messages, and whether it gets seen depends on who happens to be looking at their phone. In practice the organizer reads it, works out the group is now on nine, and starts messaging people individually — which is the worst possible use of the two hours before kick-off.
A better arrangement is that dropping out is an action, not a message: the player changes their answer, the count drops, and everyone who might fill the space sees it at the same time. Keeping a waiting list of people who wanted in but missed out turns the dropout into a straight swap rather than a scramble.
Let the reminder do the chasing
An automatic nudge to anyone who hasn't answered, sent the day before, removes most of the last-minute uncertainty without you sending a single message.
Splitting pitch hire without being the bank
Almost every regular small-sided game has one person who pays the venue and then collects it back. It's the single most corrosive part of organizing: the amounts are small, the chasing feels petty, and over a season the organizer is usually out of pocket by more than they'd admit.
The cleanest arrangement is to charge per session against the people who actually played, rather than running a kitty. A kitty needs bookkeeping and someone to trust; a per-session charge is self-evident — you played, you owe a tenth of the pitch.
Collecting it in the same place the game is organized removes the awkwardness entirely. Players pay online, the ones who haven't get reminded automatically, and the organizer stops being both the fixture secretary and the debt collector.
- Charge per session rather than running a kitty — less bookkeeping, no trust required
- Split against confirmed players, so no-shows don't get a free game at everyone's expense
- Let people pay online or mark a cash payment, and confirm it yourself
- Turn on automatic reminders so the chasing isn't coming from you personally
Futsal, 5-a-side and everything in between
Futsal proper is five-a-side on a hard court with a low-bounce ball, rolling subs and a formal squad, usually in a league. Casual 5-a-side is whatever the leisure centre has free at eight o'clock. Between them sit 6-a-side and 7-a-side leagues, work teams, and the weekly cage game that has run for eleven years and has no name.
Organizationally they're the same problem at different intensities. A futsal league side needs availability per fixture and a squad list; a casual game needs a weekly count and a way to split the hire. Both need announcements that don't scroll away and a record of who's paid.
If you run more than one — a league team on Sunday and a knockabout on Thursday, say — keeping them as separate groups matters more than it sounds. The overlap in players is rarely complete, and nothing kills engagement faster than notifications for a game someone was never going to play.
