“Who was at practice on Wednesday? Let’s ask the captain”
The training slot keeps the line-up, and the misses are visible in the log and in the reports.
“Who was at practice on Wednesday? Let’s ask the captain”
The training slot keeps the line-up, and the misses are visible in the log and in the reports.
“A player disappeared for a week and we found out during a match”
An absence is filed with dates, and an automation reminds about the end of the term in advance.
“Feels like he plays less now. But there is nothing to point at”
Reports with points and the action log give numbers instead of feelings.
The day is split into slots of the step you choose and a player takes the time. Neighboring slots close for the interval you set, past time can be closed entirely, and times follow Moscow time for everyone.
The schedule no longer depends on who wrote in the chat first.
A player files a report for a period, the coach accepts it and awards points. The decision lands in the log and in the author’s notifications, and the total is visible in the profile and in the AI review.
Roster talks happen over numbers, not over memories.
A player files an absence with a reason and dates, the coach approves it. The mark shows in the profile and in the roster table, and a few days before the end an automation reminds both the player and the coach.
Nobody disappears silently and nobody is searched for blindly.
Filed absences are visible at once, and a rule finds those who disappeared without warning by checking the log.
Slots with neighbour blocking make it impossible to book two sessions at the same time.
Points from accepted reports and log records give the numbers, and the AI review folds them into a text with the same counters underneath.
Moscow time (UTC+3) — both the planner and the log — so the time matches for every player.
No. Inactivity records an agreed absence, but time in the position keeps running and penalties are not lifted.
It is a prompt for a conversation: the conclusions come from a language model, and the numbers under the review are rechecked in the log and the profile.
Yes: they are two units with their own positions, permissions and notification channel — the data never mixes.
Slot times follow Moscow time (UTC+3) for everyone, so the team has a single schedule no matter where people are.
The kind of community changes nothing: the panel fits any of them that has a structure and rules — the terms are renamed to match yours.