Every cricket captain knows the same Thursday night feeling. The match is Saturday. You have eight confirmed, four maybes, and seven people who have not replied at all. So you send another message to the group chat, then chase three people privately, then guess the XI on Friday night anyway.
That is not a discipline problem. It is a system problem. WhatsApp was not built to count availability, and a group chat buries the one answer you need: who is actually coming?
1. One place for availability, not five chats
If availability lives in WhatsApp, Facebook, text messages, and a phone call from last week, no one knows the true count. Pick one place and make it the only place that counts. In Aatago, each event has one RSVP list for that team: Going, Maybe, or Can't go. Players answer from Home, right where they see the next match. Rule to tell your team once, clearly: "If it is not in Aatago, it does not count for selection."
2. Set a deadline, and make it visible
No deadline means no urgency. Set an availability deadline 48 to 72 hours before the game, so you have time to pick an XI, arrange transport, and call up a reserve. In Aatago, the Home RSVP panel shows the effective availability deadline for each upcoming event, and players can answer inline. Once a result is entered for a match, that match is closed: you are no longer chasing availability for a game that already happened.
3. Chase only the non-responders, not everyone
Messaging the whole team again annoys the eight who already said Going, and the seven who have not replied still do not feel singled out. In Aatago, admins see "N players haven't RSVP'd" for a team event, with a Nudge all button that reminds just those players. Once nudged, it shows as Nudged, so a second admin does not chase the same people twice. Private beats public: "Hey, Saturday XI is being picked tonight, are you in?" gets a faster answer than another group message.
4. Treat Maybe as a real answer, with a follow-up time
Maybe is not a no, and it is not a yes. When a player picks Maybe, ask for one thing: "Can you confirm by [deadline]?" If they cannot confirm by then, pick as if they are out, and keep them as first reserve. Count only Going players for your first XI. Maybes are your reserves, in the order they confirmed.
5. Use unavailability blocks for the long term
Some players are not flaky. They are on holiday, injured, on shift, or away for exams for three weeks. In Aatago, unavailability blocks mean a player who is away does not get counted as a non-responder for those dates, and captains stop chasing someone who already told you they cannot play. In a club with a shared roster pool, a player unavailable for the 1st XI but free for the 2nd XI can be used where they are actually available, instead of being lost for the weekend.
6. Pick the XI from the squad, not from memory
A published XI ends arguments. Aatago teams enroll in formats (T20, 40-over, and so on), pick a squad per team per format, and set a captain and vice-captain per format, because a T20 captain is often not the same person as the 40-over captain. The published XI for a match comes from that squad, with (C) and (VC) shown. Publish the XI as soon as the deadline passes.
7. Review response time, not just the final count
If the same three players always reply last, that is information. Aatago's availability report tracks who responded and how quickly, so a captain can see the pattern instead of guessing who is unreliable. Use it to have one quiet conversation, not to shame anyone in the group.
The system, in one week: Monday, fixture posted and deadline set. Wednesday, reminder to non-responders only. Thursday, deadline passes and XI is published from Going players, Maybes are reserves. Saturday, you arrive knowing who is coming. Sunday, result is entered, Cricinfo-style, with Player of the Match, and the match is closed.
What Aatago does, and does not do, here
Aatago handles schedule, RSVP and availability, nudges to non-responders, published XI, results, stats and club leaders, dues tracking, and team chat and announcements, all in one place for a club. It does not do live ball-by-ball scoring, and it does not process dues payments. It tracks dues and reminds only the people who owe, and players see only their own dues. Players never pay for Aatago. Only clubs pay: Free for 1 team, Team CA$99/yr (US$72/yr), Club CA$199/yr (US$145/yr), League custom, with a 30-day full-Club trial and no card required to start.
Next step: Try it for one team for one month. Set one deadline, nudge only the non-responders, and publish the XI on time. If Saturday feels calmer, roll it out to the rest of the club from the shared roster pool. See also: How to collect cricket club fees and dues online in Canada.