Choosing a school management system is a decision your teachers, accountants and parents will live with every day for years. Most schools compare feature lists and then discover, after signing, that what mattered was something else: how fast a teacher can take attendance, whether parents actually open the app, or what happens to the data when the contract ends. This guide gives you a way to compare systems on the things that decide whether the project succeeds.
Start from your problems, not from a feature list
Before you talk to any vendor, write down the five or six situations that cost your school time or money today. For example: late fees that nobody chases consistently, attendance collected on paper and typed in at the end of the day, parents asking the office where the bus is, or a timetable that takes weeks to rebuild every term. Each problem becomes a test you can run during the evaluation. A system that looks impressive in a demo but does not solve your own list is the wrong system.
Also decide who will use the system every day. A tool that suits the head office but is slow for teachers will be abandoned within a term, and the school goes back to paper and group chats.
Questions to ask every vendor
Use the same questions with every vendor so the answers can be compared side by side.
- What is included and what is an add-on? Ask for the list of modules in the quote (attendance, fees, timetable, transport, canteen, clinic, e-learning) and which ones are priced separately.
- Who uses it and on which device? Can a teacher take attendance from a phone in under a minute? Is there a parent app on both iOS and Android, or only a web page?
- How good is the Arabic? Check right-to-left layouts, Arabic names on reports and certificates, and whether the parent app is fully Arabic, not just partly translated. If you also need English, check that you can switch per user.
- Does it meet local requirements? In Saudi Arabia, ask about ZATCA e-invoicing (Fatoora, Phase 2), Nafath and the PDPL. In Egypt, ask which payment channels are supported and how invoices and receipts are issued. Ask what is live today, not what is planned.
- Who owns the data, and can you take it with you? Ask how you export students, fees and grades if you leave, in which format, and how long the vendor keeps your data afterwards.
- How is existing data moved in? Ask whether you can import students and staff from Excel, who cleans the data, and whether someone reviews it with you before go-live.
- Permissions and security. Can you limit what each role and each branch sees? Is there an audit log of sensitive actions and two-factor sign-in? See our data protection checklist for what to verify.
- Training and support. Who trains your team, how long does onboarding take for a school of your size, and who answers when something breaks on the first day of term?
- Pricing. Ask how the price depends on students, branches and modules, what is charged once and what is charged yearly, and what happens to the price when you add a branch.
Run a pilot with your own data
A demo shows the best path. A pilot shows your path. Shortlist two or three systems and give each the same short script, played with real (or realistic) data from your school:
- Create a class, add students and parents, and import a list from your existing spreadsheet.
- Take attendance as a teacher on a phone, then see what the parent receives.
- Create a fee plan with instalments, record a payment and issue the invoice.
- Build next week's timetable, then mark a teacher absent and see how a substitute is proposed.
- Ask a question of the person who would use it most: the accountant, the registrar, the head of a grade.
Time each step and note where people hesitate. The system that your least technical colleague can complete without help is usually the right one.
A simple scorecard
| Area | What good looks like |
|---|---|
| Daily use | Teachers finish attendance in about a minute, from a phone |
| Parents | One app, fully Arabic, with attendance, fees and messages |
| Finance | Instalments, reminders, receipts and invoices in one place |
| Compliance | Local e-invoicing and privacy features that are live, not promised |
| Data | Export in an open format, clear retention terms |
| Setup | Import from Excel, a named person who trains and supports you |
| Price | A written quote that lists modules, students and branches |
Give each row a score from one to five for every vendor and weight the rows by how much each problem costs you. The goal is not a perfect number but a structured conversation between the owner, the principal and the accountant.
Red flags
- Features that exist only in a slide deck or a "coming soon" list.
- No way to see the system with your own data before signing.
- Parent communication that depends entirely on a third-party chat tool, with no record inside the system.
- Data that you cannot export in a usable format.
- A price that is only explained verbally.
Where Classti fits
Classti is a school management platform with a dashboard for the school, a parent app and a teacher app. You can read what each module does on the features page, see how it applies to your country in Saudi Arabia or Egypt, or compare it with the way you work today in Classti vs Excel and WhatsApp. Prices are prepared per school after a short demo, so the best next step is to book a demo and run the pilot script above on your own data.