Approval queue

In practice

Approval queues appear anywhere a chess academy's software drafts something AI-generated for a parent to read: monthly progress reports, post-game review summaries, fee reminders, and weekly recaps. A batch's Friday recap and an individual student's progress report can sit in the same queue, each waiting on the coach who taught that batch rather than on whoever is logged in. Academy owners run into the term while comparing coaching platforms, since not every vendor builds one, and while training new coaches on the review workflow during onboarding. The queue is distinct from a guardian portal, which is the parent-facing side where an approved message actually lands; the queue itself is coach-facing and never visible to families. It is also distinct from a game review queue, which feeds finished Stockfish summaries into the same approval step rather than replacing it. Federation and admin terms like FIDE ID or AICF registration sit outside an approval queue entirely; those are record-keeping fields, not AI output. The queue only holds drafts awaiting a human decision, never sent history, so a coach cannot use it to look up what a parent already received. For the full argument on why an approval queue is non-negotiable rather than a nice-to-have, and how ChessCore separates database-backed numbers from AI-written narrative inside each draft, read the linked guide below.