Running a Multi-Coach Chess Academy Without Chaos

Adding a second coach means another person needs access to your teaching plans, student progress and parent context. If you have kept those details in your head, start writing them down before the first handover. A new coach may use a different level sequence or explain progress differently; agree the shared standard so a batch change does not confuse a child or their family. Parents should know who is teaching the next lesson and how that coach will continue the work already underway.

So the real problem of a multi-coach academy is not management headcount; it is making the academy's standard exist outside any one person. That means three things have to move from a founder's memory into shared, visible systems: the curriculum (what gets taught and in what order), the student record (where each child actually is), and the communication standard (what a parent receives and how often). Get those three externalised and a second, third, or fifth coach extends your academy. Skip it and each new coach quietly forks it into a slightly different one. This guide focuses on that transition; for the fee collection, enquiry handling, and scheduling groundwork that sits underneath it, our chess academy operations hub covers the rest of what running an academy day to day involves.

Chess Nexus, Chessy, CoachBoard and ChessPlay offer academy software for multiple coaches. Chess Nexus groups coach accounts under a central bill [6]; Chessy gives an institution admin access to coach calendars and a shared payments ledger [8]; CoachBoard's Academy plan combines four coaches and a 100-student pool [7]. Compare the account structure with how your academy assigns students, arranges cover and communicates with parents. Each coach still needs to know which students and tasks they are responsible for.

As of 2 October 2026, these platforms use different pricing models. Chess Nexus has coach-count tiers with a 100-student allowance per coach [6]. Chessy charges by active student [8], while CoachBoard combines a shared student pool with paid coach and student additions [7]. ChessPlay lists one flat $99 USD monthly fee for unlimited students, coaches and branches [9]. Model the bill at your expected roster and coach count, then ask who can change records, view fee information and send parent updates. A shared account does not decide those responsibilities for you.

Everything else in a multi-coach academy rests on one thing: a single place where each student's state is recorded, that every coach reads and writes. Without it, coaches keep private notes in private notebooks, and the academy becomes a set of silos that happen to share a name. The first time a regular coach is sick and a substitute opens nothing but a class register, the parent watches their child redo last month's material, and concludes the academy is disorganised, which it is.

A usable shared record holds, per student: current level and the curriculum stage they are on, attendance history, recent games and what was reviewed, the open coaching focus for the next few sessions, any tournament they are preparing for, and the parent-communication context (what was last shared, any sensitivities). In ChessCore, the academy management software we build, a student who has linked their Lichess account has that recent-games line filled in automatically, since Lichess publishes a public API for exactly this kind of sync [1], so no coach has to chase a parent for a game link before reviewing it. The point is not bureaucracy. The point is that a coach who has never met the student can open the record, read for ninety seconds, and continue the work rather than restart it. That ninety-second continuity is the entire difference between an academy and a roster of independent tutors.

• Current level and curriculum stage, so no coach repeats or skips material
• Attendance and recent games, so a substitute sees the same picture the regular coach does
• The open coaching focus, a line or two on what to work on next
• Tournament context, so prep does not stall when the usual coach is away
• Parent-communication notes, so the family hears one consistent voice

app.chesscore.io/students/aarav-r

StudentsAarav R.

PASearch⌘K

AR

Aarav R.

Batch B2 · Tue/Thu · joined Aug 2025

+155 this season

1395

Rapid · synced from Lichess

Games · 142Reports · 14FeesAttendance

Won vs. 1410 · French Defense

Best game

Missed fork on move 23

Homework set

Full history kept · survives coach changesEvery change logged · audit trail

Give each recurring responsibility one named owner, including parent updates, tournament entries and follow-up for a struggling student. We suggest writing the allocation down before you add another coach. Two people can contribute to a task, but one should check that it is complete and arrange cover when needed. The table below offers a starting allocation for a small academy with a founder and two or three coaches. Adapt it to your team and record who takes over during absences, rather than leaving the duty to whoever happens to notice.

The principle behind the table is that every student has one accountable coach for their progress and their parent, while shared infrastructure, the timetable, fees, the curriculum standard, has a single owner above the coaching line. This avoids the two failure modes that wreck multi-coach academies: the diffuse-responsibility gap, where shared duties evaporate, and the fragmented-family problem, where a parent gets contradictory messages from three coaches about one child. Pin each student to a primary coach, and the parent always knows whose name to expect.

Review the ownership table alongside each coach's workload once a month. Count preparation and parent conversations as well as classes; a coach supporting several students through difficulties may need more time than the roster suggests. Ask what is overdue and arrange cover before assigning new work. Tournament preparation needs its own checklist: confirm the event's entry deadline, who submits the entry and who checks the confirmation. Consult the organiser and relevant federation, such as the All India Chess Federation [2], for the event requirements, and use FIDE's rating information [4] when discussing rated play with parents. Keep those entry tasks separate from teaching preparation so the team can see both. Our guide to structuring batch scheduling and coach cover explains how to fit these responsibilities into the timetable.

Before another coach takes over a student, share the current curriculum stage, last-session note, next teaching focus and relevant parent context. Use the same handoff routine for a sick-day substitute, a batch change or a coach departure. The receiving coach should know what to continue and what to ask about before meeting the student. A short written template gives both coaches something to check, even when they cannot speak before class; leave time afterwards for the covering coach to record what happened.

A good handoff answers, for each student, the questions the receiving coach will hit in the first five minutes of class. Where is this child in the curriculum? What were we working on last session? What should I not do, the line that already failed, the topic that frustrates them, the parent sensitivity? And what does the parent expect to hear after this class? When those four answers travel with the student, a cover class feels to the parent like the regular coach was simply having an off-day; when they do not, it feels like starting over with a stranger.

1. 1Read the record first: a covering coach opens the student record before class, not the register, so they continue the open coaching focus.
2. 2Carry the last-session note: a single line on what was covered last time prevents the substitute from repeating it.
3. 3Flag the don'ts: note any topic, approach, or parent sensitivity the receiving coach should avoid, because surprises here cost trust fastest.
4. 4Match the parent voice: keep the communication tone and cadence the family already knows, so a cover class does not change the relationship.
5. 5Write back after class: the covering coach updates the record so the regular coach returns to continuity, not a gap they have to reconstruct.

We suggest keeping parent updates in the channel the family already uses with your academy. If that is WhatsApp [5], introduce the covering coach in the existing thread and explain who will send the next update. Agree which coach answers questions and who can see the conversation, so a parent does not need to repeat a concern to several people. A change of teacher is easier to understand when the timetable and contact arrangements are clear; tell families what is changing before the cover class where possible.

The permanent version of the handoff is a coach leaving, which is when an academy that kept everything in one person's head pays for it all at once. If a departing coach's students live only in that coach's notebook and that coach's WhatsApp chats, their exit takes a chunk of the academy with them. If those students live in the shared record, rehoming them is an afternoon's work: reassign the primary coach, hand over the records, send one warm note to each parent. Our pillar on running a chess academy covers the weekly scheduling that makes routine cover smooth, and the parent-portal approach that keeps families informed through any coach change.

app.chesscore.io/schedule

BatchesThis week

PASearch⌘K

Week of 9 June · all batches

0 conflicts

Mon

Tue

Wed

Thu

Fri

Sat

B2 · 5 PM

B2 · 5 PM

A1 · 5 PM

A1 · 5 PM

Arena

1:1 · 6 PM

Make-up credit · Zara M. · Sat 4 PM

Missed Wednesday · slot found automatically

Auto-slotted

Calendar invites synced to 31 families

Timing changes update everyone at once

Synced

Conflict check on · calendars synced for every familyEvery change logged · audit trail

A shared record solves continuity; it does not by itself guarantee that every coach teaches to the same standard. That requires a written curriculum, a light review rhythm, and a head coach who owns 'what good looks like'. The written curriculum does not need to be a textbook; it needs to be a clear sequence of what students learn at each level and the milestones that mark moving up, so two coaches teaching the same level are genuinely teaching the same thing. Without it, level names mean different things to different coaches and a parent moving batches finds their child mysteriously re-graded.

The review rhythm is how you catch drift early. A short monthly check, the head coach reading a sample of progress notes across coaches, watching a class occasionally, comparing how two coaches assessed similar students, surfaces inconsistency while it is still small. This is not surveillance; it is the same quality discipline any multi-person service needs. Pair it with the shared record's visibility into who is actually sending parent updates, and you can see at a glance which coach has gone quiet with their families before it becomes a retention problem you read about in a quit notice.

Finally, decide deliberately where AI fits, because a growing academy is exactly where the temptation to automate communication is strongest and most dangerous. Two rules keep it safe across every coach. First, whatever engine sits behind analysis should evaluate every position identically regardless of who is coaching, the way an open-source engine like Stockfish [3] does, so two coaches reviewing the same game work from one objective assessment rather than two opinions. Second, a human coach approves every message before it reaches a family: an AI draft can save a busy coach the blank-page tax and keep the academy's voice consistent, but the assigned coach still reads it and presses send, so the parent gets a real message about their real child rather than a templated blast. That is how you scale communication without scaling the spam that erodes trust, and our guide to how the AI approval queue keeps every draft accountable to a named coach covers exactly what that review step looks like.