Coaching institutes are judged on two things parents can see: whether their child attends, and how they rank. Everything the software does should make those two visible without a phone call.
The batch is the unit
A coaching institute does not have classes; it has batches. Each has its own timetable, its own faculty, its own test series and often its own fee plan. Students move between them. Software that assumes a fixed class structure creates work rather than removing it.
Admissions, students, attendance, fees with UPI links and receipts, tests and report cards, certificates, ID cards, a parent portal and a full LMS — configured for how your institute runs.
Start free See the demoThe four loops that matter
- Attendance - per batch, per session, with an alert to the parent when a student misses.
- Tests - marks, rank within the batch, and a trend the student can see.
- Fees - instalment schedule, reminder before each due date, UPI link, receipt on payment.
- Communication - one channel, used sparingly, that parents actually read.
How MizUp EOS handles it
MizUp EOS covers admissions and enquiries, student 360 records, batch attendance with timetable, tests and report cards including ranks, fees with UPI links and receipts, certificates with QR verification, ID cards and a parent portal.
Admission enquiries are captured and followed up in MizUp CRM; attendance alerts, test-result notices and fee reminders go out on the official WhatsApp Business API through MizUp CLM; faculty attendance and payroll run in MizUp BMS.
What it costs
Free plan available; paid plans from Rs 10 per learner per month. See EOS pricing.
Where to start
Batches, attendance and the two-absence alert. Tests and fees follow easily once attendance is honest. Explore MizUp EOS.
Where coaching institutes usually go wrong
- Forcing batches into a class structure. Students move between batches and timings. Software that assumes a fixed class creates work every time they do.
- Attendance marked at the end of the week. By Friday nobody remembers Tuesday, and the alert that would have mattered is four days late.
- Ranks published without context. A rank alone demoralises the middle of a batch. A trend shows improvement, which is what keeps students going.
- Instalments on a fixed calendar date. A student who joined on the eleventh has instalments on the eleventh. Forcing the first creates a parallel register.
- Fee reminders that ignore payment. Chasing a parent who paid yesterday is the fastest way to lose their goodwill.
- Enquiries and students in separate systems. The admission is then typed twice and the counselling history disappears.
A realistic first thirty days
| Week | Focus | What good looks like |
|---|---|---|
| Week 1 | Batches and fee plans | Batches with timetables; fee schedules tied to enrolment dates rather than the calendar. |
| Week 2 | Daily attendance | Marked per session, taking under a minute per batch. |
| Week 3 | Two-absence alert | Sent the same evening, stopping on reply. |
| Week 4 | Tests and ranks | Marks recorded per test with a visible trend per student. |
The two-absence alert is the highest-return automation in a coaching institute. Build it before anything involving tests or reports.
The numbers worth watching
| Metric | Why it matters | How to read it |
|---|---|---|
| Attendance percentage per batch | The leading indicator for results and for dropouts | Weekly, per batch. |
| Two-absence alerts sent and replied | Whether intervention is happening | Replies per alert. |
| Fee collected before due date | Cash position | Compared instalment on instalment. |
| Test participation rate | Often a better early warning than marks | Students attempting divided by enrolled. |
| Dropouts by batch and month | Where the retention problem actually is | With a reason recorded. |
Results are made of attendance
Every coaching institute sells outcomes and manages attendance, and the link between the two is stronger than most institutes measure. A student who misses four sessions in a fortnight is rarely recovered by extra effort in the last month.
That is why the two-absence alert matters more than the test module. It reaches a parent while the reason is still ordinary — a viral fever, a family trip, a scooter that broke — and while the student can catch up without shame.
Ranks are the other half, and they need more care than institutes usually give them. Published as a bare number they discourage precisely the students who need encouragement. Published as a trend alongside the batch average, they become useful information rather than a verdict.
Get attendance visible and ranks contextual, and the fee reminders largely take care of themselves.
How this fits with the rest of your stack
A coaching institute runs an admissions funnel, a teaching operation and a fee ledger, usually in three places with a WhatsApp group bridging them.
On MizUp, CRM captures and works the enquiry, EOS holds the student, batch, attendance, tests, ranks and fee ledger, CLM sends attendance alerts, result notices and fee reminders on the official WhatsApp Business API, and BMS runs faculty attendance and payroll.
The confirmed admission moves from CRM to EOS without re-entry, which during an intake of two hundred students is several days of somebody's life.
Batch changes are the real stress test
The scenario that breaks most coaching software is routine: a student in the morning batch moves to the evening batch in October. What happens to their attendance history, their test records, their rank position and their fee schedule?
A system that attaches records to the batch loses the history. A system that attaches everything to the student but ignores batches cannot produce a batch-level attendance report, which is the report faculty actually use. The workable design keeps the student as the record and the batch as a dated association, so history follows the student while reports still roll up by batch.
It matters because batch changes are common. Students move for timing, for level, for a faculty preference, or because a parent changed their mind about the commute. An institute of three hundred students will see dozens of moves in a year.
Worth testing during evaluation: move a student mid-term and ask to see their attendance percentage, their rank trend and their remaining fee schedule. If any of the three breaks, the system will create manual work every month.
Related reading
- Coaching institute management, end to end
- Admission CRM for coaching institutes and schools
- Attendance percentage calculation
- WhatsApp Business API for education
Frequently asked questions
What is different about coaching institute software?
Batches, not classes. A student belongs to a batch with its own timetable, test series and fee plan, and may move between batches mid-course.
How are instalment fees handled?
As a schedule against the student, with reminders before each due date and a UPI link on the notice.
Can it handle test series and ranks?
Yes - marks per test, with rank within the batch, published to the student and the parent.
Do parents get updates?
Attendance alerts, test results and fee reminders can go out on the official WhatsApp Business API, which is where parents actually read them.
Does it connect to admission enquiries?
Yes. Enquiries are worked in [MizUp CRM](/crm) and the confirmed admission becomes a student in EOS without re-entry.
