How to run a weekly game that survives the winter

Fix the slot before you fix the people

A game that moves around the week dies. Not immediately, and not because anybody objects, but because a moving slot means every week is a fresh negotiation, and a fresh negotiation needs somebody to run it.

Pick one slot. Same day, same time, same pitch, booked as a standing reservation if the venue will do it. The slot becomes a fact about the week rather than a question, and people plan around facts.

The test is whether somebody can answer "are we playing Thursday?" without opening their phone. If they cannot, the slot is not fixed yet.

Decide the minimum, and say it out loud

The number that matters is not how many people are in the group. It is how many have to confirm before the game is on.

Write it down and hold to it. For five a side, eight is a real game and ten is a good one. For seven a side, twelve. Below the minimum the game is cancelled at a stated time, not at the pitch, and the cancellation is announced rather than left to fade.

A group that plays 4v4 because six people showed up for a ten player booking has just taught everybody that turning up is optional. A group that cancels twice and then plays properly for a year has taught them the opposite.

One person confirms, everybody else replies

The most common failure is a chat where nine people say "I think I can" and nobody counts. Confirmation has to be a list, and the list has to have an owner.

It does not need software. A message on Tuesday morning with numbered names, updated in place, works fine. What matters is that at any moment there is one authoritative count and one person who maintains it.

Rotate that person by season, not by week. Weekly rotation means the job is never anybody's, which is the same as nobody doing it.

Record the result before you leave the pitch

This is the single habit that separates a group with a history from a group with a chat thread.

Nobody remembers on Monday who was on which team. They remember the score, sometimes, and they will argue about it. The record has to be made while people are still standing there, because that is the last moment the information exists.

It takes under a minute: who played on each side, and the score. Do it while the last two are getting changed and it never becomes a task.

Seasons, so the table can end

A table that runs forever has one problem: after eight months, the person at the top cannot be caught and the person at the bottom cannot catch up. Both of them stop reading it.

A season fixes that, and the length matters less than the fact that there is one. Three months is short enough that a bad run is survivable and long enough that one lucky Sunday does not decide it.

Close it properly. The final table gets kept, the winner gets named, and the next one starts at zero. The reset is the point: everybody who was out of it in week ten is back in it in week one.

Make the table per player, not per team

Amateur groups almost never have fixed teams. The same twelve people show up in different combinations every week, so a table of team results describes teams that existed for ninety minutes and will never exist again.

A per player table describes the thing that persists. Each player carries their own played, won, drawn, lost and points across the season, whatever shirt they were in.

The side effect is the one that keeps people reading: your own row moves every week, and it moves because of what you did, not because of which side you were put on.

The mistakes worth avoiding early

A weekly game survives on three things: a slot that never moves, one person who counts, and a result recorded before anybody goes home.