School Management Software Glossary

School Management System (SMS)#

All-in-one software that runs a school's daily operations: student records, class scheduling, attendance, fee collection and parent communication in one place. Aimed at the school itself rather than at classroom teaching. Sometimes called school administration software.

Student Information System (SIS)#

The database of record for students — enrolment details, guardians, attendance history, grades and documents. In large institutions the SIS is a standalone product; in software for smaller schools it's usually one module of a school management system.

In practice: if you run a tutoring centre or language school, you're rarely buying "an SIS" — you're buying a management system that includes one. See also student information systems with parent mobile access.

Learning Management System (LMS)#

Software for delivering the teaching itself: course content, assignments, quizzes, online lessons. Moodle and Google Classroom are LMSs. An LMS manages learning; a school management system manages the business around it. Many schools run one of each.

School ERP#

Enterprise Resource Planning applied to education — the same idea as a school management system, but the term usually signals a heavier product covering HR, payroll, inventory and accounting alongside academics. Common in large private schools and universities; usually overkill below a few hundred students.

Education CRM#

Customer Relationship Management for schools: capturing enquiries, tracking prospective students through trial lessons, and converting them to enrolments. A CRM manages people before they become students; the SIS manages them after. Increasingly the two are one pipeline in a single system.

In practice: see the longer guide to education CRM software.

Parent Portal#

A private login where parents see their child's attendance, grades, timetable, invoices and school announcements — instead of asking the office. May be a website, a mobile app, or both. The single most requested feature in school software, because it converts a stream of parent messages into self-service.

In practice: see the full guide to what a parent portal is.

Student Portal#

The same idea for the students themselves: their timetable, homework, materials and (for adult students) their own payments. In adult education — language schools especially — the student portal matters more than the parent portal.

Native app vs PWA vs web portal#

Three different things vendors all call "a mobile app." A native or store-installed app is downloaded from the App Store or Google Play and can send push notifications. A PWA (progressive web app) is a website installed to the home screen from the browser — no store listing. A mobile-responsive portal is simply a website that fits a phone screen.

In practice: ask which one a vendor means; the answers differ more than the marketing suggests. We compared what six platforms actually ship.

Fee Management / Tuition Billing#

The module that generates invoices, collects payments and tracks who owes what. The critical questions: does it invoice automatically on a schedule, can parents pay online, and can you see every outstanding balance on one screen?

In practice: see school finance and student billing compared.

Recurring Billing#

Charging the same fee automatically at an interval — monthly tuition being the classic case. Distinct from invoicing on a schedule, which still requires the parent to act each time. True recurring billing charges a stored payment method without anyone doing anything.

Pro-rata Billing#

Charging a partial fee for a partial period — the student who joins in week six of a twelve-week term pays half. Schools with rolling enrolment need this constantly; software built around an annual admissions cycle often can't do it.

Payment Gateway / Processor#

The service that actually moves the money — Stripe, PayPal, GoCardless. School software integrates with processors rather than replacing them. Two costs exist: the processor's fee (unavoidable everywhere) and any percentage the software vendor adds on top (very avoidable — check before signing).

In practice: see online fee payment processing compared.

Per-student-lesson pricing#

A software pricing model where the monthly fee scales with attendance: one student attending one lesson is one billable unit, so a group class of twelve costs twelve units per session. Cheap for one-to-one tutors, expensive for group teaching — the larger your classes, the more the same hour of teaching costs in software fees.

In practice: model it on your own class sizes with the cost calculator.

Rolling Enrolment#

Students joining year-round rather than in one September intake. Standard in tutoring centres and language schools; alien to software designed for K-12 admissions seasons. If you enrol year-round, this is the first thing to test in any demo.

Class Capacity#

The maximum students a class accepts, enforced by the system — the thirteenth enrolment into a class of twelve is refused, not silently accepted. Weaker systems record capacity but don't enforce it.

Waitlist#

A queue for a full class: when a space opens, the next student is offered it. Surprisingly rare — most school management platforms, including the market leaders, don't have one. If a vendor claims it, ask to see it demonstrated.

Conflict Detection#

The scheduler refusing to double-book a teacher, room or student. Real conflict detection blocks the clash as you build the timetable; the alternative is discovering it when two classes arrive at one room.

In practice: see class scheduling and student enrolment compared.

Attendance Tracking#

Recording who showed up, lesson by lesson. Matters beyond the register: attendance drives billing in per-lesson models, feeds safeguarding obligations, and is the earliest signal of a student about to drop out.

Timetabling#

Building the master schedule of who teaches what, where, when. Institutional software treats this as a once-a-year optimisation problem; tutoring and language school software treats it as a living calendar that changes weekly. These are different products wearing one name.

Onboarding / Data Migration#

Moving your existing students, classes and balances into the new system. Ask three things: is there an import tool, is onboarding help included or charged, and what does leaving look like — can you export everything back out?

In practice: most schools are migrating from a spreadsheet — see spreadsheets vs school management software.

Per-student vs flat pricing#

The two dominant pricing shapes. Per-student (or per-student-lesson) pricing scales with your size and punishes growth; flat or banded pricing (a set fee up to N students) is predictable. Neither is wrong — but model a full year at your real numbers before comparing headline prices.

Free trial vs demo#

A demo is a vendor showing you the software; a trial is you using it with your own data. Insist on the trial. Every system looks clean in a demo with someone else's tidy test school.