How to Run a Chess Academy: The Operating Calendar

Running a chess academy means operating seven recurring loops: student intake, batch placement, classes, game syncing and homework, parent updates, fee collection, and a retention review. Each loop has a natural home in the week, and the academies that run calmly are the ones that pin every loop to a fixed slot on the calendar instead of doing each task whenever it becomes urgent.

This guide is about operating, not founding. If you are still choosing a venue, registering the business, or filling your first batch, start with our guide to starting a chess academy and come back here once classes are running. Operating is a different discipline: the founding decisions are made once, but the seven loops above repeat every single week for as long as the academy exists. The quality of an academy is the quality of its most neglected loop. A brilliant coach with chaotic fee collection bleeds families just as surely as a tidy administrator who never reviews student games.

The most useful way to see the whole job is a week in the life of a well-run academy. The table below is the operating calendar this entire guide expands on. Days are illustrative: shift them to match your class days, but keep the principle that each loop happens at the same time every week, owned by a named person. The demo academy referenced throughout this post runs exactly this shape with two coaches and three batches.

Notice what the calendar removes: decisions. Nobody wonders when homework gets set, when parents hear from the academy, or when fees go out, because the answer is always the same as last week. That predictability is also what parents experience from the outside, and it is the single biggest difference between an academy that feels professional and one that feels like a hobby. The rest of this guide walks the loops in roughly calendar order: batches and scheduling, fees, attendance, parent communication, retention, and finally the tooling question of when a spreadsheet stops carrying all of this.

Group students into batches by playing strength, not age, cap each batch where one coach can still review individual games, and freeze the timetable for a full term. A nine-year-old at 1200 and a fourteen-year-old at 600 need different lessons, and mixing them serves neither.

Strength banding is practical because ratings are cheap to obtain. Online platforms rate players with Elo-derived systems [5], so even a complete beginner has a usable number within a few dozen games, and your Monday assessment game fills the gap before that. The bands below are a starting point, not a law: the real constraint is that everyone in the room can learn from the same position on the demonstration board.

Two scheduling habits save the most pain. First, leave one deliberate buffer slot in the week, usually Saturday, that carries no regular batch: it absorbs make-up classes, assessment games, and the occasional rescheduled session without disturbing anything else. Second, promote students between batches only at term boundaries, with a quick word to the parent about why. In the demo academy, Batch B2 meets Tuesday and Thursday and has kept that slot for three terms; the stability is the point, because families plan school pickups, tuition, and sport around your timetable. Our batch scheduling guide goes deeper on coach loading and timetable design, and the make-up class guide covers what happens when life interferes with the schedule.

Most academies charge a flat monthly or quarterly fee per batch level, billed in advance on one fixed date, and collect through payment links or recurring mandates so that collection never depends on chasing. The fee cycle is a loop on the calendar like any other: invoice day, reminder day, reconciliation day.

Collection is where discipline pays most visibly. Pick one invoice date, send every invoice that day, send one polite reminder three days later, and have a named person make the personal call on day seven. For Indian academies, UPI AutoPay removes most of this work: the parent approves a recurring mandate once and the bank debits the fee automatically each cycle [4]. In the demo academy, moving from ad hoc reminders to this fixed cycle, with a ₹4,500 monthly fee per intermediate student and an automatic receipt on every payment, produced 96% on-time collection this term. The receipt matters as much as the debit: a parent who has a dated receipt for March never has a dispute about March.

What to charge is its own decision, shaped by your city, your coach costs, and what the local market bears; our fee structure guide works through that pricing question properly. For operations, the only rule that matters is consistency: one price list, one invoice date, one escalation path, applied identically to every family, including the ones you know socially. Exceptions made quietly for one parent become entitlements for all of them within a term.

Mark attendance in the first five minutes of every class, in front of the students, against a roster whose numbers parents see reflected in their weekly update. Attendance destroys trust only when it lives in a private notebook and surfaces for the first time during a fee dispute.

The mechanics are simple and the discipline is everything. The coach marks the register while students solve the warm-up puzzles, so it costs no teaching time. An absence is logged the same day, not reconstructed at month end from memory, because reconstructed attendance is exactly the kind of number a parent will dispute. And every absence triggers a defined consequence the family already knows: either it lapses, or it converts into a make-up credit with an expiry date, redeemable in the Saturday buffer slot. Our attendance tracking guide covers register design and edge cases, and the make-up class guide covers the credit ledger in detail.

The second-order benefit is early warning. Attendance is the first signal that slips when a student is losing interest, usually a full term before anyone says the word quit. A register you actually maintain becomes the input to the retention review later in this guide; a register you back-fill at month end is just paperwork.

Send one structured update per family on a fixed day each week, and confine ad hoc conversation to a published office-hour window. Parents do not need more messages from a chess academy; they need predictable ones that always contain the same things: attendance, homework, and progress.

In practice this conversation happens on WhatsApp, because that is where the parents already are. WhatsApp Business adds labels, quick replies, and away messages built for exactly this kind of small-business communication [3], which is enough structure to run the Friday update loop without the chat swallowing your evenings. The discipline that makes it sustainable is the template: every update, every week, in the same order, so a parent can read it in thirty seconds and a coach can write it in two minutes.

1. 1What the batch worked on this week, in one sentence a non-player can understand.
2. 2Attendance: sessions attended out of sessions held, plus any make-up credit issued or redeemed.
3. 3Homework: what was set, and whether last week's came back.
4. 4One concrete moment from the student's own games, good or instructive.
5. 5What happens next: the following week's topic, or an upcoming event.

The weekly update is the heartbeat; the monthly progress report is the deeper document, with rating trend and the coach's actual assessment, and our progress reports guide covers how to write one that parents keep. The trap to avoid is the unstructured group chat as the academy's only channel: group chats are fine for logistics broadcasts, but individual progress belongs in an individual thread, where the message history doubles as the academy's record of what each family was told and when.

Run a monthly retention review: list every student whose attendance has slipped, whose rating has been flat for a term, or whose homework stopped coming back, and act on each name that week. By the time a parent calls to pause classes, the decision was made a month earlier.

The review works because the warning signs are already in records you keep for other reasons. Attendance comes from the register. Homework completion comes from the Wednesday game-syncing loop: shared Lichess studies make structured between-class material free to set [1], so a student who stops opening them is telling you something. Rating trend comes from synced online games, and a plateau deserves a response rather than silence: a fifteen-minute engine review of one recent loss, with Stockfish doing the evaluation [2], gives the student visible evidence of what to fix while the rating refuses to move. For stronger juniors, a concrete goal does the same job; working toward a first FIDE-rated event [6] reframes a flat online rating as preparation rather than stagnation.

Each flagged name gets one of three actions: a conversation with the student, a call to the parent before they call you, or a batch change at the next term boundary. The pre-emptive parent call is the highest-value habit in this entire guide. Calling to say you noticed Aarav missed two sessions and here is the plan converts a quiet exit into a renewed commitment more often than any discount will. The full pattern of why families leave, and the scripts for those calls, is in our guide to why students quit chess academies; the operating takeaway here is simply that retention is a scheduled loop, not a reaction.

Spreadsheets stop being enough when the loops start referencing each other faster than one person can copy between tabs: in practice, somewhere around two coaches, three batches, or fifty students. Below that line, a disciplined sheet runs chess academy operations perfectly well, and you should not pay for software out of aspiration.

The breaking point is not volume, it is joins. An absence on Tuesday should create a make-up credit, appear in Friday's parent update, and adjust nothing on the invoice; a payment should generate a receipt and close a reminder. Each of those is one manual copy in a spreadsheet, performed by a tired human at 9pm, and every miss lands in front of a parent. When you notice the same fact being typed into a third place, or a second coach asking which tab is current, the calendar has outgrown the tool. The honest comparison of costs and switching effort is in our spreadsheets versus academy software guide, and our list of questions to ask before buying academy software keeps any vendor conversation grounded.

Whatever tooling you choose, the operating calendar from the first section is the real system. Software can hold the register, run the fee cycle, and draft the Friday updates, but it cannot decide that intake happens on Monday and retention review happens at month end. Set the calendar first, run it manually until it hurts, and then let tools take over the loops you already understand.