Running a weekly pickup game that never falls apart
- The short answer
How do I organise a weekly pickup game so it actually happens?
Publish the minimum number of players the game needs and show the live count against it, cap the list at the court capacity with an ordered waitlist behind it, and send one confirm-or-drop message 24 hours before. Set a cancellation call time, usually the evening before, and cancel out loud when the number is short rather than hoping.
Every other kind of gathering degrades gracefully when people do not turn up. A dinner with six instead of eight is still a dinner. A five a side with six players is not a game, it is six annoyed people standing on a pitch you have already paid for.
That single fact should shape how you run it. Sport is the one social event where the headcount is a hard threshold, and almost everything that goes wrong with a weekly game comes from that number being invisible until kickoff.
Publish the minimum, and show the count against it
Most organisers ask "who is in on Thursday?" into a group chat. The replies arrive scattered across two days, the count lives in the organiser's head, and nobody else knows whether the game is close to on or nowhere near it.
Say the number instead: 8 minimum, 12 ideal, 14 cap. Then keep the running total somewhere everyone can see. This changes behaviour more than any reminder does, because "we are on 7, need 1 more" is a message people act on, and "who is in?" is not.
A visible count turns every player into a recruiter. A count in your head leaves the whole job with you.
| Game | Minimum to play | Ideal | Hard cap |
|---|---|---|---|
| Five a side football | 8 (4v4) | 12 | 14 with rolling subs |
| Basketball, one court | 6 (3v3) | 10 | 12 |
| Badminton, two courts | 4 | 8 | 12 with rotation |
| Running club | 2 | Any | None |
| Seven a side football | 10 | 14 | 16 |
The waitlist is the feature that keeps regulars
Once your game is good it will fill. Without a waitlist, spots go to whoever happens to read the chat first, which systematically favours the people on their phones and quietly pushes out the shift worker who checks at 9pm.
- Order matters and should be visible. "You are 2nd on the list" is information someone can plan an evening around. "The game is full" is not.
- Promote automatically when someone drops. The gap between a drop-out and a replacement is where games lose players; if it takes you an hour to notice and repost, the person who would have taken it has made other plans.
- Close the waitlist at kickoff minus two hours. After that, anyone still hoping should be told plainly to plan something else.
- Track who keeps missing out. If the same person is third on the list four weeks running, offer them a guaranteed spot next week. That is how a regular is made, and it costs you nothing.
Flaking, and the one message that fixes most of it
People who say yes on Sunday for a Thursday game are not lying. They are answering a question about an abstract future evening, and by Thursday the evening is real and it contains a late meeting and rain.
The single highest-return thing you can do is send a confirm-or-drop message roughly 24 hours before. Not a reminder. A re-ask: "Thursday 7pm, we are on 11. Still in? Drop out now if not and I will fill it."
Open the list the same day each week
Sunday evening for a Thursday game. Predictability does most of the work: regulars start expecting it and reply without being chased. A game that opens at a random time each week is a game you have to sell every week.
Show the count from the first reply onwards
Everyone should be able to see 5 of 8, 7 of 8, full plus 3 waiting. The number climbing is what makes people commit; the last two or three spots fill fastest when the total is visible.
Send the confirm-or-drop 24 hours out
One message to the confirmed players only. Make dropping easy and blameless at this point, because a drop 24 hours out is a solved problem and a drop at 6:50pm is a ruined game.
Set and honour a cancellation call time
Pick a fixed moment, usually the evening before or noon on the day, and decide then. Say the rule out loud when you set the game up so nobody is surprised by it.
Send the address and time the morning of
Pitch number, entrance, what colour shirt to bring. Anything sent when the game was created has long since scrolled away.
Post the split and the payment detail once
The total, the number of players, the amount each, and where to send it. Repeating this every week is what makes collecting money feel like nagging.
Be realistic about what this achieves. A confirm-the-day-before message typically converts most of the soft yeses into either a firm yes or an early drop, which is the whole point: you are not trying to eliminate drop-outs, you are trying to move them 24 hours earlier so the waitlist can absorb them.
Splitting court and pitch hire
Hire is a fixed cost, so the per-player price falls as the game fills. That creates an unpleasant trap: if you divide the bill by whoever turned up, the people who came get punished for other people flaking.
| Method | How it works | The catch |
|---|---|---|
| Divide by attendees | 10 turned up, 6 each | A thin week costs the loyal players most |
| Fixed price per head | Always 6, surplus banked | Simplest to run; needs a visible kitty |
| Charge on confirmation | You confirm at 24h, you owe it | Fairest, most admin, best for oversubscribed games |
For a weekly game, fixed price per head is almost always the right answer. Set it slightly above break-even at your typical turnout, keep the surplus as a kitty, and use the kitty to absorb thin weeks, replace the ball and cover the odd no-show. Say the balance out loud once a month so the money never feels like it is going somewhere private.
Cancelling well
Organisers hang on too long because cancelling feels like failure. It is the opposite: a game cancelled the night before costs everyone nothing, and a game cancelled at 6:45pm costs eight people their evening and you the pitch fee.
- Decide at a fixed time, not when you feel like it. The evening before for a weeknight game. Check the count, check the forecast, call it.
- Cancel on the number, not the vibe. You published a minimum. If you are below it at the call time and no waitlist can fill it, cancel.
- Say it plainly and take the blame off everyone. "We are on 6, need 8, so Thursday is off. Same time next week." No guilt-tripping, no list of who dropped.
- Cancel the booking immediately. Most venues refund or credit with 24 hours notice and nothing at all on the day.
- Reopen next week as normal. One cancelled week kills a game only if the organiser goes quiet afterwards.
Why a group chat struggles with this specifically
Group chats are fine for banter and bad at state. A recurring game has state: who is confirmed this week, who is on the waitlist, who has paid, what the count is right now. In a chat, that state exists only as a scrollback you have to reconstruct by reading forty messages.
It also grows in the wrong direction. A weekly game accumulates a shifting cast of friends of friends, and adding each of them to a permanent chat means they now get every message forever, which is why people mute it and then miss the confirm-or-drop.
The honest version: for six players who all know each other, a chat is fine and an app is overhead. Past about ten players, or once you are paying for a pitch, a link with a live count and a waitlist saves the organiser real time every week.
Common questions
How many players do you need for a five a side game?
Eight is the realistic floor, giving you four against four, though the game is better at ten or twelve with rolling subs. Publish that minimum when you open the list and cap it around fourteen, because beyond that too many people are standing on the side and a player who paid full price for twenty minutes on the pitch does not come back next week.
How do I stop people flaking on a weekly game?
Send a confirm-or-drop message to the confirmed players about 24 hours before, and make dropping out at that point completely blameless. The goal is not to eliminate drop-outs but to move them a day earlier, where a waitlist can still fill the gap. A yes given four days ahead is an intention, not a commitment, so re-ask once and treat that answer as the real one.
How should you split the cost of pitch or court hire?
Charge a fixed price per head set slightly above break-even at your usual turnout, and keep the surplus as a visible kitty for thin weeks and new balls. Dividing the bill by whoever showed up sounds fairest but punishes the loyal players on the weeks people flake, since the hire cost is fixed regardless of how many turn up.
How do I run a waitlist when the court is full?
Keep it ordered and visible, so someone knows they are second rather than just knowing the game is full, and promote the next person automatically the moment a confirmed player drops. Close it about two hours before kickoff and tell the people still on it plainly so they can make other plans. If the same person misses out three or four weeks running, give them a guaranteed spot.
When should I cancel a pickup game?
Set a fixed call time when you create the game, usually the evening before for a weeknight fixture, and decide against your published minimum rather than against how you feel. Cancel out loud, without blaming anyone, and cancel the venue booking straight away since most refund or credit with 24 hours notice and nothing on the day.
Is a group chat good enough for organising a weekly game?
For six regulars who all know each other, yes, and anything more is overhead. Past roughly ten players or once money is involved it stops working, because a chat holds conversation rather than state: the current count, the waitlist order and who has paid all have to be reconstructed by scrolling. A shifting cast also means adding occasional players to a permanent group they then mute.