The School Management System Checklist: What to Require Before You Sign

Schools rarely choose a management system more than once a decade, which means few people on any selection committee have done it before. Vendors, on the other hand, run demos every week. The result is that decisions are often made on the strength of a polished presentation rather than on how the system will behave on a busy Monday morning in October.

This checklist is meant to shift that balance. Use it to structure your requirements, to guide demos and to compare proposals on substance.

First, be clear about what you are buying

The terms are often used loosely. A student information system (SIS) or school management system handles records, admissions, attendance, timetables, grades, fees and reports. A learning management system (LMS) handles courses, content, assignments, quizzes and online classes. Some products do both; some do one well and the other superficially. Decide which jobs matter most to you, and judge each product on those.

Core academic operations

• Attendance by day and by period, with quick entry on a phone or tablet
• Timetables that handle your real constraints: shared rooms, split classes, part-time teachers
• A gradebook that supports your grading scheme, weightings and term structure
• Report cards generated from recorded data, in your format and languages
• Behaviour and pastoral notes with appropriate access restrictions
• Support for more than one curriculum if your school runs national and international tracks

Ask the vendor to configure your actual grading scheme during the demo, not a sample one. If that takes a developer, you will need a developer every time your policy changes.

Teaching and learning

• Assignments with deadlines, submissions and feedback
• Question banks and quizzes with automatic marking where appropriate
• Lesson materials organised by subject, grade and unit
• Live classes and recordings for remote or blended learning
• Access that works well on low-cost phones and weak connections

Parents and students

For many families, the parent app is the school's digital face. It should make their lives easier, not add another channel to check.

• Same-day notification of absence or late arrival
• Grades, reports and teacher comments when the school chooses to release them
• Homework and upcoming assessments
• Fee statements and online payment
• Two-way messaging with clear rules about who can message whom
• Support for families with several children in one account

Administration and finance

• Admissions from enquiry to enrolment, including document collection
• Fee plans, discounts, sibling rates, instalments and VAT where it applies
• Integration with your accounting system, or exports it accepts
• Staff records, roles and permissions
• Transport routes and bus attendance if you run buses

Arabic and bilingual support

In the Gulf and in many schools in Türkiye, the system has to work properly in Arabic. That means more than a translated menu. Report cards must print correctly in Arabic, names must be stored in both scripts, search must find Arabic names regardless of spelling variants, and the interface must be laid out right-to-left without broken icons or misaligned tables. Ask to see an Arabic report card printed from the live system.

Data protection and security

School systems hold sensitive data about minors. Treat this section as non-negotiable.

• Where is the data hosted, and does that meet your local regulations?
• Is access controlled by role, and can you see who viewed or changed a record?
• Are backups automatic, tested and restorable within a defined time?
• Is data encrypted in transit and at rest?
• What happens to your data if you end the contract?

If a vendor cannot explain in plain words where your students' data lives and who can see it, that is your answer.

Reporting

School leaders and ministries ask for reports in specific formats, often at short notice. Check whether you can build your own reports, filter by grade, section and period, and export to formats your authorities accept. Ask how long a report on attendance across the whole school takes to generate.

Migration and onboarding

Moving from your current system, or from spreadsheets, is where many projects stall. Ask specifically:

1. Which historical data will be migrated, and who cleans it?
2. How will the migration be tested before go-live?
3. What training is included for administrators, teachers and parents?
4. Can you go live mid-year, or only at the start of a term?
5. Who do staff call when something does not work on the first day?

Questions to ask every vendor

• Can we speak to a school similar to ours that has used the system for more than a year?
• Which of the features we saw today are configuration, and which require custom development?
• How are new features prioritised, and can we request changes?
• What is included in the price, and what is charged per student, per module or per year?
• What is your response time for urgent issues during the school day?

Running a fair comparison

Give every vendor the same scenarios: enrol a new student mid-term, record a week of attendance, publish a term report in Arabic and English, send an absence alert, collect a fee instalment. Watch each one done live, by the vendor, on their system. Then have two or three of your own teachers try the same tasks. The system your teachers find easiest is usually the one that will actually be used.

Vega Education was shaped by this kind of feedback from schools and academies in Türkiye and the Gulf. If you are reviewing options, we are happy to run your scenarios on it, and to tell you plainly if another approach would suit you better.