Running a Test-Prep School: Scheduling and Payments

A test-prep school runs on the harshest calendar in education: enrollment in autumn, peak season in winter, graduation in spring — and no room for “we’ll fix it later”. In a single season the school lives through a full cycle: marketing, enrollment, teaching, retention and graduation. That’s exactly why operational mistakes cost more here than anywhere else — there is no second chance this year.

Below is a practical plan for building the operations side of a prep school — whether you prepare students for Ukraine’s NMT, for school-leaving exams or for university entrance tests — so the season passes without late-night spreadsheet reconciliation.

What does a typical test-prep school look like?

Usually three or four subjects: the national language, mathematics, history, English. Each subject has its own teachers, its own groups (often split by preparation level), its own schedule. A student may attend one subject or several at once.

This is where spreadsheets start to crack: four subjects’ schedules in different tabs, a “two-subject bundle” payment on a separate row, and “how many active students do we even have?” requiring manual consolidation. The reliable accounting model is: each subject is a separate product with its own groups, and the student is one profile with a lesson balance per track. Then the schedule, the finances and the analytics assemble into one picture with no duplication.

How do you handle seasonal enrollment and the “September list”?

A quirk of prep courses is that students sign up in advance: in August, parents agree on an October start. Keeping those students in your phone’s notes is a reliable way to lose some of them.

It’s far better to keep them in the database with a waiting status: the person is recorded, the start date is fixed, but they don’t mix into the active roster or skew your statistics. Before the start date the system reminds you to reach out — and the “September list” stops depending on the administrator’s memory. In Mimiao, a waiting student also doesn’t take up a seat in your plan limit until they actually start.

One lead pipeline for the whole enrollment season

Prospective students arrive from Instagram, the website, referrals and parent chats. Keep every inquiry in one lead pipeline with its source, subject and next step instead of scattering contacts across inboxes.

Schedule a consultation or trial lesson from the lead card, keep follow-ups visible, and place students who will start later into the waiting list. Once they accept, convert the lead into a student without entering the same contact data again. Your teaching team can still use its own entry-test methodology or external tools; Mimiao keeps the operational history around that decision.

Payments: lesson packages and debts you see coming

Prep-course payment is almost always package-based: 8 or 16 sessions a month per subject. The simplest reliable model is a lesson balance: a payment adds sessions to the balance, a delivered lesson deducts one. When the balance runs low, the system warns in advance — and the next package’s invoice goes out before any debt exists.

Two rules worth fixing before the season starts:

1. Payment reminders are sent by the system, not the administrator. The awkward “you still owe for October” conversations are best delegated to automation — it isn’t shy and doesn’t forget.
2. Financial records are never edited after the fact. At season’s end, when you tally the results, you’ll thank yourself for a ledger where every payment has its history.

Parents of graduates: fewer routine calls

A prep school’s customer is almost never the student — it’s the parents. And their core need isn’t “photos from class”; it’s confidence that the child is attending and doing the work. A parent portal covers that without phone calls: the schedule, per-lesson attendance, homework feedback, course progress and invoices with a Pay button. A new-invoice notification is built in, and an absence-alert recipe can be enabled from the Studio plan.

For the school it’s a double win: fewer routine conversations — and noticeably more trust, because transparency persuades better than any promise.

A pre-season checklist

• Products and groups per subject created; teacher rates set.
• “Starting in September” students recorded with waiting status and start dates.
• Lead sources connected; consultations, trial lessons and follow-ups have clear owners.
• Payment rules and reminders switched on before the first lesson, not after the first debt.
• Parents invited to the portal at enrollment, not later.

The prep season is won not by whoever works more, but by whoever’s routine runs itself. To see what that looks like in a real system, start with a free 14-day trial or take a walk through the demo school.