Running a Sunday League Availability Rota (So You Never Start With Ten Players)

A typical Sunday league squad has 18 to 22 registered players and needs 13 or 14 on a match day. On paper that is comfortable. In practice, at any given weekend, three or four are working, two are injured, one is at a wedding and one has simply gone quiet. A squad of 20 with a 65 per cent turnout rate gives you 13 players, which is fine until two of those 13 pull out on Saturday evening. Over a 26-game season, the difference between a team that averages 14 available and one that averages 11 is roughly nine points, in our experience, before anyone has kicked a ball.

The problem is not that players are unreliable. It is that most teams ask the question too late, in the wrong place, and with no consequence for not answering. A message in a group chat on Thursday evening gets buried by Friday lunchtime. The fix is a rota that asks once, early, for the whole season, and then only chases the gaps.

Once the league publishes fixtures, usually in late August, send the full list of dates to every player and ask for a simple answer against each one: Y, N or ?. Give them a week. Most people know already which weekends they are away, working or on a stag do, and they will tell you if you ask while it is easy. You will get 60 to 70 per cent of the season filled in from this single request, and the remaining question marks are the only thing you need to chase from then on.

Ask for three other things at the same time: who can drive and how many seats they have, who is happy to run the line, and who has a car boot big enough for the kit bag. These answers feed the roles rota in Step 3 and save you asking every week.

This is the heart of the system: players down the side, fixture dates across the top, one cell per player per game. Y means confirmed, N means out, and ? means not yet answered. The example below shows eight players across the first six fixtures of a season; a real one runs to the full squad and every date. The bottom row is the count of Y answers, which tells you at a glance which weekends need work.

Two things stand out immediately. The 27 September away game has ten confirmed and no first-choice keeper, so that fixture needs attention three weeks out, not three days. And Ross has four question marks, which is a conversation, not a chase. A table like this turns the season from 26 separate panics into one document you glance at on a Monday.

The second table nobody builds and everybody needs. Kit washing, running the line, teas, driving and holding the subs board are jobs that fall on the same two people every week until they quit. Rotate them across the season and write the rotation down. The rule we suggest is that nobody does the same job two weeks running, and nobody does kit more than once in five. Match the job to the person: the linesman should be someone not starting, and the kit should go home with whoever lives nearest the launderette or has a big enough machine.

Notice that the linesman on 13 September is Jay, who has already said N for that game. That is deliberate: someone who cannot play can often still turn up for an hour, and being asked to do something useful keeps them attached to the squad. The same principle works for the shift-swap logic in a workplace rota, which we cover in handling shift swaps fairly.

Set one deadline and keep it every week: availability for Sunday confirmed by Wednesday 8pm. Not Thursday, because that leaves you one working day to find replacements. Not Tuesday, because people genuinely do not know their weekend by then. Wednesday gives you three evenings to fill gaps and still lets people change their minds early in the week.

Chasing should be individual, not broadcast. A message to the group saying "still need three" gets zero replies because everyone assumes someone else will answer. A message to Marcus saying "you're a ? for Sunday, can you confirm either way" gets a reply in minutes. Chase only the question marks, and only once. If a player has not answered by the deadline, treat them as N and tell them so. After two or three weeks of being left out for not replying, most people start replying.

Somebody will drop out on Saturday night every third week. Plan for it rather than resenting it. The rota should always carry two names beyond the 14 you need: a first reserve and a second reserve, told on Wednesday that they are on standby and will get a call on Saturday if needed. A reserve who knows they are a reserve is far more likely to keep the day free than one who has been told nothing and assumes they are not wanted.

Ringers, meaning players brought in from outside the registered squad, need one clear rule agreed before the season: they play only when you are below 13 after the reserves have been used, they never start ahead of a registered player who turned up, and they are registered with the league before they step on the pitch. Most county FAs require a player to be registered before kick-off, and fielding an unregistered player costs you the points and sometimes a fine, so the ringer rule is as much about the league as it is about fairness.

Track dropouts as well as availability. A player who says Y and then cancels late three times in a season is worse for the team than one who honestly says N. A simple tally column on the season table, counting late withdrawals, gives you the evidence for that conversation without it becoming personal.

If you carry 14 or 15 to a game, three or four of them start on the bench, and if it is always the same three, you will lose them by Christmas. Keep a running count of minutes or starts per player and make sure that, over any four-week window, everyone who has been available for all four games has started at least two. Rolling subs in most Sunday leagues make this easy to honour; if your league does not allow them, plan the substitutions before kick-off rather than in the heat of the second half.

Be explicit about the exception. A cup semi-final is not the week for a fairness rotation, and players accept that if they were told at the start of the season that the strongest eleven starts in knockout games. What they will not accept is a fairness policy that silently disappears whenever the manager is nervous.

The entire system takes about 40 minutes a week once the season table exists. Monday: update the table with last week's dropouts and minutes, then look at the next three fixtures for any column under 13. Tuesday: message the question marks individually for this Sunday. Wednesday 8pm: close the list, name the 14 plus two reserves, confirm the roles rota and post the meeting time. Thursday and Friday: nothing, unless a reserve needs promoting. Saturday evening: one message to the 16 confirming kick-off and lifts. That is it.

If you run a sports club alongside a day job, the same habits transfer. The techniques in covering annual leave in small teams are the availability table with a different name, and the fairness rule in Step 6 is the same one that keeps a 4-on-4-off rota from collapsing when one team is always given the bank holidays.