A payment is past its due date. A coach's credential is expiring or has lapsed. A team has fewer players going than it needs this week. A registration document has sat unreviewed for over a week. A family that played last season has not signed up this season. A division is over capacity, or under half full. Each one becomes an item with the names behind it and a severity, so the urgent ones come first.
Approving does not invent a new way to send. A payment reminder uses the billing reminder. A credential reminder uses the compliance reminder. A short-team alert goes to the team's coaches. A returning-family invitation goes to the family. Items that only the club can act on, such as a document waiting for review, open the screen where you fix it and send nothing.
Filter the queue, see exactly how many messages would go out, and approve them together. If the number has changed since you looked, nothing sends and you are asked to look again. There is a limit on how many a club can send in an hour, so a mistake cannot become a flood.
The queue refreshes when you open it and again every night. A problem that goes away is marked resolved, and one that comes back is reopened. Directors can opt in to a weekly digest that arrives only when something is open.
No. It builds the queue and suggests an action. Nothing is sent until a director approves an item or a group.
The club's directors, meaning club administrators and anyone given the athletics manage permission. Other members who open the screen see no rows.
No. A reminder about an invoice is claimed before it is sent, so the director and the nightly reminder cannot both send it, and a family already told about an expiring credential is not told again.
League health is a club's view. A returning-family invitation looks at the club's own divisions.
A short call about your divisions, your fields and the tools you use today, not a generic pitch.