Chess progress reports for parents, with examples

A chess progress report for parents brings together evidence, the coach's interpretation and a next step. Identify the reporting period, show where attendance and game records came from, explain one learning theme, and finish with a specific practice task the family can understand before the next lesson.

Keep the report focused on this child and this reporting period. A general paragraph about chess benefits does not explain what happened in lessons, and a row of identical skill scores gives the family little to act on. Use a short example from a game or classroom task, then explain why it matters. Avoid promising a future rating. Use a format a parent can read on a phone and respond to without needing a second document. Our progress report template provides a fill-in-the-blanks structure for attendance, learning notes, and the next practice task.

Give the next step enough detail to be useful at home. Fifteen minutes of rook endgame practice twice a week is clearer than improve endgames; two slow games with a review afterward is clearer than play more chess. Match the task to the child's available time and what the coach has seen in lessons. At the next report, return to that task: did the child attempt it, what changed, and does the same focus still make sense? A parent can then follow the coaching plan across several months rather than receiving disconnected comments.

Three worked chess progress report examples follow: a beginner's first monthly report with no rating, an improver's monthly report with a labelled rating movement, and a term-end report that traces a season. All three use the same five blocks in the same order (header, evidence, themes, narrative, one next step). Every name belongs to Demo Chess Academy, a made-up academy, and the counts are illustrative, not a real child's record. The fill-in version of that structure is the free printable progress report template.

The beginner report carries no rating, because a rating for a child two months into the game is mostly noise, and the evidence leans on attendance and habits instead. The themes could only describe Isla, which is the proof of attention a parent is paying for, and the next step is small enough that a parent who does not play can prompt it at home.

The improver report shows the rating as a labelled start-to-end change rather than one bare number. Lichess calculates ratings with the Glicko-2 method [6], a different pool from the academy rating and from a FIDE classical rating, so a report names the pool it quotes and never merges them. Read the same report in three layers:

• Evidence: the rating change around the Junior Swiss, 4 of 5 classes, one make-up pending, and the game of 14 October. A parent can check every one of these on the child's profile.
• Coach interpretation: the plan was right and the check of forcing replies was missing. That sentence is the coach's judgment, so it sits in the narrative and is not presented as a measurement.
• Next action: one task, with a date to look again, which is the next report.

Examples two and three follow the same student, so you can see how a month rolls into a term. A term-end report keeps the same five blocks but widens every window: it goes out two or three times a year, can run to one or two pages, and joins monthly snapshots into one arc. Rating readings at several dates let a parent see the trajectory instead of a single change, and a dip, had there been one, would be named and explained here rather than hidden.

Engine-generated player reports are a different genre from these coach reports. The 1000ELO sample report is built around blunders per game, average centipawn loss and hanging pieces [7], and the MyChessBot demo shows a skill profile and a training plan for a fictional player of about 1500 [8]. Both are written for a player improving on their own; an academy report to a parent needs the coach's read on the child, with engine output as one source of evidence.

Give monthly reports a fixed deadline, a named owner, and a repeatable way to gather the records. If the founder also teaches, schedules classes, and collects fees, writing can be squeezed between those tasks. Reserve time for it in the working week. Decide when the evidence is ready, when the coach reviews the draft, and who follows up on reports still waiting. A report scheduled for the first Saturday needs preparation before Saturday; leaving the whole batch until that morning makes the deadline depend on an uninterrupted block of spare time.

Start with the work required for one student. You need the attendance record, recent games, the relevant rating history, and notes on the lesson focus before writing a useful summary. For a batch of fifteen, a five-minute review per student is 75 minutes; a ten-minute review is two and a half hours. Those are planning examples, so time your own process before assigning the work. Include correction and approval in that estimate. If the coach repeatedly has to search for a missing register or ask which account belongs to a child, fix that record problem before shortening the narrative.

Keep brief lesson notes during the month so the report can describe something specific. Mateo is making good progress and should practise tactics leaves a parent wondering which tactics and what progress the coach saw. A note about spotting an undefended piece in a particular game gives you a starting point. Record the game or position, the skill involved, and the follow-up task while the lesson is still fresh. At report time, choose the example that best explains the month rather than trying to recreate each lesson from memory. The aim is a useful account of the child's learning, not a longer report.

Separate evidence collection from coaching judgment. Attendance comes from the class register. Games and rating movement can come from a student's linked account; Lichess provides game and rating data through its API [2]. Give the coach that evidence before asking for the narrative. The coach then checks the figures, chooses the learning theme, and sets one next step. Keep a place to flag missing or uncertain records, so a draft cannot quietly turn an incomplete month into a confident claim. Our guide to running a chess academy covers how reporting fits alongside attendance, schedules, and family communication.

Every number in a progress report should come from a system of record, never from memory or estimation. There are three systems that matter: the attendance register for classes, the synced game platform for games and ratings, and the engine for move quality. If a number cannot be traced to one of those three, it does not belong in a document a parent will keep.

Lichess provides an API for games, rating history, and player information [2], allowing those records to feed a report without retyping screenshots. For Chess.com students, use the imported game history and check that the account belongs to the child. Move-quality notes should be tied to the analysed game and position, using Stockfish engine output [4]. Keep the analysis settings and the move reference with the record so the coach can review an apparent blunder before repeating it to a parent. If the game is missing or the account cannot be matched, leave the figure unreported and explain what the coach can still say from lessons.

Check attendance before approving the report. A parent may query a session because they remember dropping the child off or arranging a make-up class. The register should distinguish a scheduled lesson, an absence, a cancellation, and a recovery session, so the coach can explain the total. Resolve a disputed entry with the person who taught that class. Do not reconstruct the month from chat messages while writing the report. Our guide to attendance tracking covers the register routine; for reporting, use the recorded dates and make the period clear beside the number.

• Attendance: read from the class register, recorded on the day of each class.
• Games played and rating movement: read from the synced Lichess or Chess.com account [2].
• Accuracy, blunders, and key moments: read from Stockfish analysis of those synced games [4].
• Fees and receipts: read from payment records, and kept out of progress reports entirely so money and progress stay separate conversations.
• Coach narrative: the only part written fresh, because judgment is the one thing no system of record can produce.

Say what is missing, and make no claim the record cannot support. A class with no attendance mark is not recorded, which is different from absent. A rating with no earlier reading from the same pool supports no claim of change. A month with no reviewed game supports no claim that tactics or endgames improved. Missing is not zero, and a gap in the register is a record problem to fix, not a number to estimate.

Fix the record, then correct the report. If the missing register turns up before the deadline, replace the placeholder with the real figure. If it does not, send the report with the placeholder and a date for the correction, because a parent who sees the gap named trusts the other numbers more than one who finds it later. Do not fill a gap with last month's figure, an average or a guess, and do not leave a blank that a parent could read as zero.

Present ratings as an estimate of playing strength over time, alongside evidence from lessons and games. Elo models relative strength using game results [1]. A child can learn a useful skill during a month in which their rating falls, so describe what the coach observed before interpreting the chart. Name the rating pool and time control, and compare like with like. Explain a movement through the games available rather than assuming a rise proves better teaching or a dip means the child has stopped learning.

Be explicit about which rating you are reporting. A Lichess rapid rating, a Chess.com blitz rating and a FIDE classical rating are three different numbers on three different scales, and they are not interchangeable. FIDE publishes its official rating list on the first day of each month [9], so an over-the-board rating changes at most twelve times a year however much a student plays, while an online rating can move every evening. FIDE also lists a rating only for players at 1400 or above [9], so many young players have no FIDE rating at all. A report that says the rating went up without naming the pool and time control is technically true and practically misleading. Our guide to showing parents rating progress covers the charts and framing that make this legible.

Explain the limits of the rating line before a parent has to ask. Results depend on the opposition and the games played [1], so choose evidence the coach can discuss: a correctly played rook ending, fewer missed undefended pieces in the games reviewed, or a better time-management decision. Say how many games the observation covers, and give the family a practice task that follows from it, with the rating as context rather than the verdict on the month.

Start with a monthly report as the cadence, with brief class notes between reports when useful. Give the system or administrator responsibility for assembling records, the teaching coach responsibility for the narrative, and one named person responsibility for delivery. Adjust the schedule to the programme: a short holiday course may need an end-of-course note, while tournament preparation may need a review after an event. Tell families what to expect and include reporting time in the coach's workload, so the promised date is realistic.

Assign the work explicitly. The administrator can check attendance dates and account links; the coach who teaches the student should write or approve the learning notes and next task. Name the person who sends the completed report and follows up on a parent reply. One workable rhythm is to send a batch's reports on the first Saturday of the month, with a list showing which drafts are approved and which are waiting. Use that kind of checklist to notice a missing report before the deadline. If the coach is away, agree who can review the evidence and whether the family needs a revised delivery date.

Choose the delivery channel with families. WhatsApp Business provides messaging tools [3], but the useful choice is the channel parents have agreed to use for their child's updates. Keep individual progress in a private thread or guardian account. Our guide to WhatsApp for chess academies covers the channel rules and when to add a private guardian portal for the records a group chat cannot hold. Check how a parent finds an earlier report and who sees their reply. A familiar channel helps only when the family can identify the child, reporting period, and person to contact.

The workflow has four stages: the system gathers evidence, an AI drafts the narrative around injected numbers, a coach edits and approves in a queue, and only approved drafts go to families. The order is the point. The model never invents a number, because attendance, games and ratings come from the records described above, and a named person stands between every AI draft and every parent.

Take an illustrative month with twelve of twelve classes attended, eighteen synced rapid games and two reviewed mistakes in a rook endgame. The draft can organise those details, but the coach decides whether they describe the important learning theme, and checks the date range, the positions and whether the homework follows from them. Review each child's draft on its own even when the reports share a structure, and remove praise that has no example behind it. The two sections that follow give the review checklist and the stop rules that make this consistent across a batch.

app.chesscore.io/updates

ParentsMüller family

PASearch⌘K

Parent updates · this week

14 of 14 sent

MU

Müller family

Receipt · October fee

ME

Mensah family

Weekly recap · Kofi M.

HA

Haddad family

Schedule change · Sat 4 PM

WhatsApp Business · connected

Weekly recap · Lucas M.

Lucas attended Thursday's class and won 2 arena games. His September report is in your portal.

Receipt · October fee

$180 received via card AutoPay. Receipt saved.

9:42 AM

Recap approved by Coach Elena

Open the guardian portal

Own login · nothing to install

Approved updates only · WhatsApp and parent portalEvery change logged · audit trail

ChessCore, which we build, keeps AI-written report text in an approval queue: the draft waits in a list with the records it was built from, and no AI-drafted report reaches a parent until a person approves it. Automatic monthly reports are a separate path. When an academy switches them on, ChessCore emails guardians a report built from attendance and rating data, with no AI text and no engine analysis, and it counts only the attendance marks that were entered, so an unmarked class is not turned into an absence. Before treating a report as ready, check that the child has a linked guardian email and the guardian's consent for parent communications. Class reminders and fee reminders also go out automatically on a schedule the academy turns on, with no AI text. The approval-queue section of our guide to AI guardrails in coaching software covers what should happen when nobody reviews a draft.

app.chesscore.io/reports/october-batch-b2

ReportsOctober · Batch B2

PASearch⌘K

October progress report · Lucas M.

1 of 14 drafts for Batch B2

AI draft · awaiting you

Lucas attended 4 of 5 classes this period and played 18 rated games, moving from 1310 to 1342.

His endgame conversion improved clearly. Next month the focus is back-rank defense, based on the mistakes tagged in his last three games.

Highlighted numbers come from your attendance and rating records. The AI cannot change them.

Goes to the Müller family after approval

EditApprove & send

Draft 1 of 14 · waiting for your approvalEvery change logged · audit trail

Evaluate any tool that claims this workflow against three questions. Can an AI draft reach a parent without a named person approving it? Are the numbers injected from records, or does the model write them? Is there a trail showing who approved each report and when? The evidence layer, game sync from Lichess and Chess.com plus attendance from the register, is what separates a reporting system from a text generator [2], and the AI layer should be judged on its guardrails before its prose.

Check five things in order, because the early checks make later edits pointless if they fail: the period and student, every number against its record, every claim against a number or a note, the tone for this particular month, and the single next step. The draft assembles records; coaching judgment still decides what the report says and whether the evidence supports it.

1. 1Period and student: confirm the date range and the child's name before reading a word, because a draft built on last month's records is wrong in every line.
2. 2Every number against its record: attendance against the register, the rating against the named pool and time control, the game count against the synced list.
3. 3Every claim against a number or a note: if a sentence says the student improved at endgames, point to the game or the coach note that shows it, or cut it.
4. 4Tone for this month: a hard month needs a calm, honest register, not the default cheerful one, and a good month does not need superlatives.
5. 5One next step the coach will check: a specific task with a count and a date, written so next month you can see whether it happened.

If a draft fails the first two checks, fix the records and regenerate it rather than editing around the error. A report whose numbers were corrected by hand in the prose will disagree with the record the next time anyone looks. Before you spend time on wording, run the stop rules below, each of which blocks a different step in a well-built workflow.

1. 1No active data-collection consent for the student: no AI draft should be generated. Record the consent first.
2. 2No guardian email linked: delivery cannot queue, so add the contact before treating the report as ready.
3. 3No parent-communication consent: delivery requires it, so the report is not ready to send until it is recorded.
4. 4Missing attendance marks: count only marks that were entered, and never read an unrecorded class as an absence. Enter the mark, or add a coach note explaining the gap.
5. 5The approval screen: the send control stays disabled until narrative reviewed, numbers verified and ready to send are all confirmed.

Those confirmation steps are ChessCore's design, not an industry standard, and they do not replace reading. An automatic numeric-citation check compares the narrative's numbers with the report statistics, but it cannot tell you whether a sentence means what the record supports, so the review of meaning stays with the coach. Human review of consequential automated output is also a core control in the NIST AI Risk Management Framework, which treats how AI output is used and evaluated as part of managing its risk, and a parent-facing report qualifies [10].

Editing an AI draft means turning a fluent sentence back into a claim the record supports. The pattern repeats: the draft states an inference the data does not carry, and the coach rewrites it to the evidence plus a next step. The table uses made-up values from Knight's Gate, a made-up demo academy; the draft sentences are authored examples, not captured model output, and nothing in them is a measured result.

Naive, ungrounded drafts fail in four predictable ways, and each has a fix. Generic praise such as shows great enthusiasm could describe any student, so replace it with an observation the records support or keep the wording modest. Invented specifics, a tournament result that never happened or a rating the student never held, are caught by checking every number against its record. The wrong emotional register, a cheerful draft after a sixty-point drop and a lost playoff, is fixed by reading the draft with the child's actual month in mind. Omission reads best and checks worst: a draft can be accurate in every sentence and still leave out the two missed classes or the blank homework, because the model only writes what the records hand it, so compare the draft against the register before trusting its tone and add the missing line yourself.