Set your lineup from real availability, not guesswork

Availability first, lines second

The temptation is to build the lineup you want and then check whether those people are free. It is the wrong order, and it costs captains an evening of rework every time someone in line one turns out to have a flight. Collect availability first, look at who you actually have, and build lines from that pool.

Doing it in this order also makes the partnership decisions easier, because you are choosing between real options rather than negotiating with people who were never available in the first place.

What to ask for in a match-week poll

Keep it to the single match date, but split it by start time if your league runs staggered courts. A player who can make the 8pm line but not the 6pm is a yes you would otherwise lose.

• The match date, with each scheduled start time as a separate slot.
• A deadline two or three days before lineups are due.
• A description that names the level, opponent and venue, so nobody answers about the wrong week.
• A note on whether travel or a warm-up time is expected, which changes some answers.

Reading the grid like a captain

A yes with a comment is worth more than a bare yes, and a maybe three days out is usually a no. Treat your confirmed pool as the yeses only, and build one contingency line from the maybes rather than counting them into the main lineup.

If the grid shows more players available than you need, that is not a problem to solve on the night — it is the moment to rotate someone in who sat out last week, using the season's grids as the record of who has been available and waiting.

Confirming the line without another thread

Once the lineup is set, lock in the date and send the confirmation from the dashboard straight to WhatsApp, iMessage or email with a calendar invite. Players can mark whether they are still coming, so a late dropout surfaces as a change of status rather than a missed message at 9pm the night before.