Cricket club guide
Managing player availability across multiple cricket teams
Availability is easy for one team. It becomes much harder when a club has several senior grades, junior teams, shared player pools, two-day matches and players who can move between teams.
The mistake is treating availability as a weekly survey
Many clubs ask every player to confirm every week. That works, but it creates a second job: chasing the people who did not reply. For an active player, the useful information is often the exception: when they cannot play, are restricted, or are not yet certain.
Simple model
Available by default. Record what changed.
This keeps the weekly workload low while still giving selectors the information they need. It also lets families and players record future absences early instead of waiting for a weekly reminder.
Six principles that make availability useful
Use available as the normal state
For active players, requiring a fresh yes every week creates unnecessary work. Record the exceptions instead.
Separate unavailable from uncertain
An unavailable player and a player who is still waiting on work, injury or transport are different selection problems.
Allow restrictions
A player may be available only for one day, batting only, a particular time, or one team. A simple yes/no model loses useful information.
Support date ranges
Holidays, exams, work rosters and injury periods should be entered once and apply to the fixtures that fall inside that period.
Show availability inside selection
Selectors should not have to open another app or message thread to see whether a player can be picked.
Make clashes visible across teams
When players can appear in more than one grade or pool, the system should show where they are already committed.
Availability has to understand the club structure
A cascading senior competition, an independent junior team and a shared under-age player pool are not the same problem. Availability should stay attached to the player, while the selection workspace decides how that information is used across each structure.
This matters particularly when a player can move between senior grades, when junior players are shared between teams, or when a two-day match keeps an XI locked into the following week.
Put availability next to the selection decision
The final test is simple: when a selector looks at a player, can they immediately see whether that player is available, limited, in doubt or unavailable? If the answer requires checking another spreadsheet, group chat or app, the availability process is still disconnected.