A pre-school is not a small school. The academic machinery barely applies, and the thing parents care about most is the one thing school software usually treats as an afterthought: knowing their child is fine.
Keep it to four things
- Admissions - enquiry, visit, admission, with the fee structure attached.
- Fees - a schedule per child, a reminder before the date, a UPI link, a receipt.
- Attendance - marked in the morning, with the parent told.
- Daily update - arrived, ate, slept, mood. Short, once, every day.
Anything more becomes work the staff will quietly stop doing by week three.
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 consent rule
Photographs and updates go to one parent on one thread, with consent recorded at admission. Group broadcasts where every parent sees every child are the single most common mistake in this sector, and the one most likely to end badly.
How MizUp EOS handles it
MizUp EOS covers admissions and enquiries, student records, fees with UPI links and receipts, attendance, certificates and ID cards, and a parent portal. Daily notices and attendance alerts go out on the official WhatsApp Business API through MizUp CLM, one thread per parent, with quiet hours enforced.
Staff attendance, leave and payroll run in MizUp BMS on the same organisation.
What it costs
Free plan available; paid plans from Rs 10 per learner per month. See EOS pricing.
Where to start
Admissions and fees first, then the daily update. Attendance follows naturally once staff are already in the app each morning. Explore MizUp EOS.
Where pre-schools usually go wrong
- Buying school software. A pre-school does not need report cards, board results or a timetable module. It needs four things done reliably.
- Photos in a parent group. Every parent seeing every child is the mistake most likely to end badly, and it is entirely avoidable.
- Consent assumed at admission. Photograph consent should be explicit, recorded, and revocable. It costs one checkbox.
- A daily update that grows. It starts as three lines and becomes a paragraph, and within a month staff stop sending it.
- Fee reminders that feel like chasing. A reminder three days before a due date is administration. A reminder after is a conversation nobody wants.
- Attendance recorded but not communicated. A parent who drops their child at nine wants confirmation at nine, not a record they can look up.
A realistic first thirty days
| Week | Focus | What good looks like |
|---|---|---|
| Week 1 | Admissions and fees | Enquiry to admission with the fee structure attached; instalments per child with a payment link. |
| Week 2 | Attendance and arrival note | Marked in the morning with a short confirmation to the parent. |
| Week 3 | Daily update | Three fields, once a day, per child. Keep it to a template staff can complete in seconds. |
| Week 4 | Consent and review | Photo consent recorded per child; check with staff what has quietly stopped being done. |
The week four review matters more here than anywhere. Pre-school staff are with children all day and any process that takes more than a minute will have been abandoned by then.
The numbers worth watching
| Metric | Why it matters | How to read it |
|---|---|---|
| Daily updates sent | Whether the habit survived | Share of enrolled children receiving one, weekly. |
| Fees collected before due date | The financial return | Compared month on month. |
| Parent calls to the office | What the communication is replacing | Counted before and after. |
| Consent records complete | A safeguarding basic | Share of children with recorded photo consent. |
| Re-enrolment rate | The measure that matters most | Children returning the following year. |
Reassurance is the product
A pre-school is selling a parent the confidence to leave. Everything the software does should serve that, and anything that does not is a distraction competing for the attention of staff who are supervising three-year-olds.
That is why the daily update outperforms every other feature, and why it must stay short. Three fields sent reliably every day are worth more than a detailed report sent twice a week and then not at all.
It is also why consent and one-thread-per-parent are non-negotiable rather than cautious. A single misdirected photograph in a pre-school is not a data incident, it is a trust event, and trust is the entire business.
Keep the scope small, protect the daily habit, and re-enrolment takes care of itself.
How this fits with the rest of your stack
A pre-school needs less software than anyone tries to sell it, and the little it needs has to work every single morning.
On MizUp, EOS covers admissions, the child record, fee schedules with UPI links and receipts, attendance and the parent portal, and CLM sends the arrival note and the daily update on the official WhatsApp Business API — one thread per parent, with quiet hours enforced.
BMS handles staff attendance, leave and payroll. That is the whole stack for most pre-schools, and two of the three are usually enough in year one.
The consent conversation, done once
Pre-schools handle more sensitive material than they generally realise: photographs of small children, daily notes about eating and sleeping, and occasionally information about a family situation. None of it is regulated the way clinical data is, and all of it matters to the parents involved.
The practical approach is to settle it at admission rather than case by case. Record whether photographs may be taken, whether they may be shared with that child's parents only, and whether the school may use any image in its own marketing — three separate questions that schools often collapse into one.
Keeping them separate protects the school more than the parent. A parent who agreed to daily photos on their own thread has not agreed to appear in a brochure, and discovering that distinction after publication is an expensive conversation.
Record it once, keep it on the child record, and make it revocable without a discussion. Parents rarely revoke; what they value is knowing that they could.
Related reading
- School management software in India
- School fee management explained
- WhatsApp Business API for education
- Admission CRM for coaching institutes and schools
Frequently asked questions
What do pre-school parents want most from software?
Reassurance. A daily note that their child arrived, ate and slept matters more than any report card.
How are fees usually structured?
Term or monthly, often with an admission fee and optional add-ons like transport or meals. A schedule per child with a UPI link handles it.
Is attendance different at this age?
It is simpler - present or absent, with an arrival note. The value is in telling the parent quickly rather than in the record itself.
Should photos be shared?
Only with explicit consent, and never in a group where every parent sees every child. One thread per parent is the safe pattern.
Does it need a full ERP?
No. Admissions, fees, attendance and communication cover almost everything a pre-school needs.
