A school runs on four records: the student, the fee, the attendance and the result. Most schools hold each in a different place, and most of the administrative load comes from keeping them in agreement.
What the software has to cover
- Admissions and enquiries - the funnel before the student joins.
- Student records - one profile, from admission to transfer certificate.
- Fees - structures, dues, UPI collection, receipts, concessions.
- Attendance - daily and period-wise, with alerts to parents.
- Timetable - and the substitution that follows an absence.
- Exams and report cards - marks, grades, publication.
- Certificates and ID cards - serial numbered and verifiable.
- A parent portal - so the office phone stops being the interface.
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 demoFees are where the time goes
Fee collection consumes more administrative hours than anything else in a school. The fix is not a better register; it is raising the due against the student, sending a payment link, and generating the receipt automatically when it is paid.
Once that loop closes, the monthly reconciliation disappears and the defaulters list is a filter rather than an exercise.
How MizUp EOS handles it
MizUp EOS covers admissions and enquiries, student 360 records, fees and receipts with UPI links, attendance with timetable and homework, tests and report cards, serial-numbered certificates with QR verification, ID cards and a parent portal - in one system.
Staff attendance, leave and payroll run in MizUp BMS on the same organisation, admission enquiries can be worked in MizUp CRM, and parent messaging goes out on the official WhatsApp Business API through MizUp CLM.
What it costs
MizUp EOS has a free plan and paid plans from Rs 10 per learner per month. See EOS pricing.
Where to start
Admissions and fees in term one; attendance and exams in term two. Trying to do all four at once is how implementations stall. Explore MizUp EOS.
Where schools usually go wrong
- Buying modules before loading the fee structure. Fees drive most of the administrative load. Load them first or you will load the students twice.
- Attendance that parents never see. Marked attendance nobody is told about is a record, not a communication. The alert is where the value is.
- Report cards built in a spreadsheet. Every term, by the same person, with the same formula that only they understand.
- Certificates without a serial. A transfer certificate that cannot be verified is a document employers and colleges increasingly do not accept at face value.
- A parent portal nobody told parents about. Adoption is a communication problem, not a software one. Launch it the way you would launch an event.
- Every module in term one. Admissions, fees, attendance, exams, certificates and a portal at once is how implementations stall.
A realistic first thirty days
| Week | Focus | What good looks like |
|---|---|---|
| Term 1 | Admissions and fees | Fee structures, then students, then dues and receipts. Reconciliation stops being a monthly job. |
| Term 1, later | Attendance | Daily marking with a parent alert on two consecutive absences. |
| Term 2 | Exams and report cards | Marks, grades and publication. The spreadsheet retires. |
| Term 2, later | Certificates and portal | Serial-numbered certificates with QR verification; parent portal launched properly. |
Two terms is a realistic timeline for a school and a two-month timeline is not. Schools that compress it usually end up running the old register in parallel for a year.
The numbers worth watching
| Metric | Why it matters | How to read it |
|---|---|---|
| Fees collected before due date | The clearest financial return | Compare term on term. |
| Reconciliation hours per month | What the office actually gets back | Measured before and after. |
| Attendance alerts replied to | Whether parents are engaged | A high reply rate is a good sign, not extra work. |
| Parent portal logins | Adoption, honestly measured | Unique parents per month. |
| Certificates issued with verification | What an accreditation visit asks about | Share serial-numbered. |
The office is the customer
School software is usually evaluated by a principal and used by an office. The two have different criteria, and the office wins in practice, because a system that makes their day harder will be bypassed within a term.
That is why fees come first in every sensible rollout. Fee collection and reconciliation is the single largest consumer of administrative hours in most schools, and automating it buys the goodwill that the rest of the implementation needs.
It also explains why parent communication should be introduced as something that reduces phone calls rather than as a feature. Every question a parent can answer from a portal or a message is a call the office does not take.
Sequence for the office and the rest follows. Sequence for the brochure and it stalls.
How this fits with the rest of your stack
A school is one organisation with two populations — students and staff — and most institutions end up with two vendors and a manual bridge between them.
On MizUp, EOS holds admissions, students, fees, attendance, exams, certificates and the parent portal, BMS holds staff attendance, leave and payroll against the academic calendar, CRM works admission enquiries, and CLM carries parent communication on the official WhatsApp Business API.
Fee reminders read the same ledger the receipts come from, which is why they stop on their own once a parent has paid.
What a parent actually wants to see
Schools tend to build parent portals around what the school holds rather than what a parent asks. The result is a login with nine sections, of which parents use two.
The two are almost always the same: what is due, and is my child attending. Fees with a clear due date and a payment link, and attendance with an alert when something changes. A parent who can answer those two questions without calling the office has everything they need most weeks.
Marks matter intensely but episodically — around results, and rarely between. Timetables matter at the start of a term. Everything else is the school's convenience dressed as a parent feature.
Building for those two first has a practical consequence: adoption happens, because the portal is useful on the day it launches rather than in the term after the next one.
Related reading
- School fee management explained
- Bonafide certificate format
- Transfer certificate format
- HRMS for schools and colleges
Frequently asked questions
What should school management software include?
Admissions and enquiries, student records, fee collection with receipts, attendance, timetable, exams and report cards, certificates and ID cards, and a parent portal. Anything less and a spreadsheet survives somewhere.
How does online fee collection work?
Fees are raised against the student, a UPI link or QR goes to the parent, and the receipt is generated automatically when payment lands. Reconciliation stops being a monthly job.
Can parents see attendance and results?
Yes, through a parent portal, and notifications can go out on WhatsApp for attendance alerts and result publication.
Does it handle transfer and bonafide certificates?
Yes - serial-numbered certificates with QR verification, so a certificate can be checked rather than trusted.
How long does it take to set up?
A term is realistic if you load students and fee structures first and switch on exams in the following term.
