How to choose school management software

When you’re choosing school management software for a private school, course or kindergarten, the real question isn’t “what features does it have” — it’s “does the student’s record, the parent’s contact and the collection all actually live in one place.” This guide walks through the five things worth checking before you decide, and why each one works differently in education than it does in a generic business.

1. Don’t buy a system that models the student as a customer

A general-purpose CRM or accounting tool keeps the record as a “customer”, and the cracks show at the first demo once it’s stretched to fit a school: a parent with two children ends up with two separate customer cards, sibling discounts get calculated by hand, and moving a student between classes means re-entering the registration. What you want is a student card of its own, with one or two parent/guardian records attached to it and a sibling link. We cover this in Student registration and the parent record.

2. Does collection actually run on instalments and notes

School fees are almost never paid in one line — they run on a plan of nine or ten instalments, sometimes backed by a promissory note. The software you’re evaluating should build that plan from an amount, a count and due dates, allow each instalment to be paid in part, and match a bank statement line like “TRANSFER - PARENT NAME” to the right instalment. See Instalments and promissory notes for detail.

3. Are scholarships and discounts rule-based, or memory-based

Sibling discounts, staff-child discounts, early-registration discounts and the legally defined free-education ratio all need managing at the same time. The software should let you define these as a rule applied to the student card — relying on a hand-typed percentage is both error-prone and hard to defend in an audit. Detail: Scholarships and discounts by rule.

4. Attendance notification and KVKK-aware data handling

Attendance has to reach the parent, and reaching them has to leave proof behind — what an inspection asks for is the delivery record, not the intention. On top of that, student data such as a health report or a guidance note is a child’s personal data and needs extra care in how it’s handled. We cover both in Attendance tracking and parent notification.

5. You shouldn’t have to retype the data you already have

Most schools already hold a student record in e-Okul or MEBBİS (Turkey’s national school and higher-education data systems); retyping it into a new system by hand wastes time and risks the same student ending up as two separate records. The software should have an Excel/CSV import wizard that matches on a field such as student number, so nothing is entered twice.

A good import wizard shows a preview before it writes anything: how many rows are valid, how many failed, a downloadable report separating out the failed rows, and a way to re-upload just those. When the same student comes in a second time, the system asks whether to skip, update or create a new record — the choice is yours, data never quietly duplicates.

Example: a college with 320 students finds that during enrolment season, the front-office staff spend three full days moving data from spreadsheets into the panel by hand. With an import wizard, that drops to half a day, failed rows are reported one by one rather than as a single bulk failure, and the front office can spend the rest of enrolment season talking to parents instead.

6. Is role and permission separation clear

At a school, accounting sees the instalment and collection screen, a teacher sees attendance and grade entry, administration sees both — but sensitive fields like a health report or guidance note should open only for authorised staff. The software you’re evaluating should enforce this by role, with every access landing in Roles, permissions and audit trail; otherwise you can’t answer “who saw which record, and when” in an audit. That separation also matters during the enrolment-season rush, when temporary staff are less likely to stumble into a sensitive field by accident.

How this works in Rotenta

1. You open a student card in the Student module, with the parent/guardian and sibling link on the same screen.
2. You build the instalment plan in the Instalments and Promissory Notes module — from amount and count and due dates — and match a bank movement to the right instalment.
3. You define a discount rule in the Scholarships and Discounts module and apply it to the student card.
4. You set the absence threshold in the Attendance module per institution; once it’s crossed, the parent notification goes out automatically and the record is kept for audit.
5. You bring in your existing Excel/CSV data through the Data Import wizard, with a preview that reports failed rows separately.

Pricing is module-based; you can check the pricing page to see which modules fit your institution, or get in touch directly.

Frequently asked questions

Do a tutoring centre and a full private school use the same software?

Yes, both run on the same core; a tutoring/course profile leans on the exam-and-report-card module, a full school leans on attendance, and both share the same student card.

Does this work for a kindergarten or nursery?

Yes. Parent contact and collection are the same need; instead of attendance thresholds, fields like daily pickup information tend to matter more.

Does the system hold up during enrolment season?

Enrolment season (May through September) is known to be the heaviest period for school software, and capacity planning accounts for it.

Is there a live integration with e-Okul or MEBBİS?

No — there’s no official API for either, so data migration goes through the Excel/CSV import wizard.

How do we decide which modules to turn on?

You can work out what you need by getting in touch with us and keep only the modules you’ll actually use switched on.