Friday, 8 PM. Game tomorrow at 10. You have a list somewhere in your notes, but Dan just wrote "can't make it", Tom still hasn't replied at all, and the reserve — the one who said "maybe" on Tuesday — hasn't confirmed either. You open the chat, scroll up, try to piece together the picture.
By 10 PM it turns out the reserve can't make it either. You start messaging the next person.
This isn't about players lacking discipline. It's about using a tool that was never designed for this job.
The List and Reality Are Always Two Different Documents
Any static system — notes, Google Sheets, a pinned message in a chat — reflects the state at the time of the last update. But the player list lives in real time: someone dropped out, someone changed their mind, someone asked if they can bring a friend.
Between "Tom wrote I'm in" on Monday and "Tom wrote sorry" on Thursday, four days and forty other messages passed. The spreadsheet doesn't know that. You have to know — and remember to update it.
The organizer doesn't maintain a list. The organizer is constantly reconstructing it — from messages, from memory, from "I think he said".
Every Cancellation Is a Chain of Manual Steps
A player writes "can't come". You see the message, open the file, find the row, update the status, check who's first on the reserve list, message them, wait for a reply. If they don't respond within an hour — you message the next person.
For one cancellation: 7–8 steps and 30–60 minutes in a waiting loop. In the week before a game, this can happen two or three times.
Telegram bots cut out some of those steps — the player taps a button, the bot updates the list. But a bot doesn't replace the organizer; it only automates one step out of eight. The rest — reminders, reserve management, an accurate picture before kick-off — still sits with you.
The Problem Isn't the Tool — It's Who Becomes the Bottleneck
Chat, spreadsheet, bot — all of these approaches share the same design: the organizer is the only person who knows the current state of the list and can change it.
A player can't check whether he's confirmed or on the reserve. A player can't drop out in a way that automatically moves the next person up. A player doesn't get a reminder unless the organizer writes one manually.
This is where the fatigue comes from: the organizer spends 30–40 minutes before every game not organizing, but recovering information he already had yesterday.
amator.app is built around a different model: players sign up and drop out themselves, the waitlist moves without the organizer's involvement, and the list stays current with no manual updates required.
Completely free. Follow the link and come play.