A captain's week before an away match
The seniors' captain has a home match against a neighbouring club next Wednesday and an away one the Wednesday after. He needs eight players for each, plus reserves. He posts in the section's group chat. Twelve people reply with a thumbs up, which could mean available or could mean they read it. Three ring him. Two tell him in the bar and he forgets one.
When he has picked a team, he tells the office so the tee times can be blocked, the kitchen so the post-match meal can be ordered, and the players, who ask about lift shares for the away fixture. A player drops out on Tuesday night and the whole round of messages starts again.
Why selection eats so much time
Availability is collected in places that are made for chat, not for answers. A group chat thread with sixty messages is a poor record of who can play on which date.
Most clubs run several teams across the season, each with its own captain, and players are eligible for more than one. Nobody can see that the same player has been asked for the scratch team and the handicap team on the same day.
And the details after selection go to three or four people by separate messages. Changes rarely reach all of them.
Away fixtures add their own layer. The host club needs your team names and handicaps by a deadline, players need directions and a start time, and someone has to organise lifts. None of that sits anywhere except the captain's phone, so when the captain is ill or on holiday, the vice-captain starts from nothing.
What that costs the club
| Problem | Effect |
|---|---|
| Availability by group chat | Captains unsure who can actually play |
| Players asked for two teams | Clashes discovered late |
| Team sheets sent separately | Tee times and meals for the wrong numbers |
| Late withdrawals | Scrambling for reserves the night before |
| Volunteer captains overloaded | Hard to find people to take the job on |
Team selection is the captain's decision, and so it should stay. What wears captains out is everything around it.
How we take the admin out of team selection
- Each team has a squad list and a fixture list. For every fixture, squad members get a text or email with a one-tap reply: available, not available or maybe, with an optional note.
- Replies build an availability grid for the captain, across all fixtures, showing each player's handicap index from the club's records where appropriate.
- If a player is marked available for two teams on the same date, both captains see a warning.
- The captain picks the team and reserves on the grid. Selected players get a confirmation with the tee time, dress code, travel and meal details.
- The confirmed team is passed to the office for the tee sheet block at home fixtures, and to the kitchen for meal numbers.
- If a player withdraws, the captain sees it immediately and can offer the place to a reserve with one tap.
Results can be recorded against each fixture too, so the season's record builds up without a separate spreadsheet.
The next fixture
The captain sends the availability request on Monday for the next four fixtures. By Wednesday most of the squad has replied. He picks the team from the grid in a few minutes, and the office, the kitchen and the players all have the details. When someone drops out on the Tuesday night, the first reserve accepts from a phone and the kitchen's number stays right.
- Clear availability, not a chat thread
- No player promised to two teams at once
- Team details reach everyone at the same time
- Late changes handled in minutes
Signs your captains need this
- Availability is collected by group chat, calls and conversations in the bar.
- Captains keep their own spreadsheets or notebooks.
- Clashes between teams are found out late.
- The kitchen and tee sheet get team details separately.
- It is hard to find volunteers willing to captain a team.