Every school management system demos well. The presenter drives, the data is clean, and nothing you see has to survive a Tuesday in October. The purpose of this checklist is to get you past that hour and into the questions that actually decide whether the system works in your school two years from now.
Work through it in order. The early questions are the ones that are expensive to get wrong, because they are structural: no amount of good will from a vendor fixes an architecture that keeps your student records in one place and your teaching in another.
1. Ask how many systems you are actually buying
This is the first question and most schools ask it last. A نظام معلومات الطلاب holds the record: who the student is, which grade and class they sit in, their attendance, their fees, their transcript. A نظام إدارة التعلم holds the teaching: assignments, the gradebook, discussions, live lessons.
Most schools end up buying these separately and then paying, in money and in staff hours, to keep them agreeing with each other. A student transfers class in the SIS on Monday and is still in the old gradebook on Friday. A fee is paid and the portal does not know. Every one of those is a synchronisation failure, and they never fully stop.
What to ask: is this one system on one database, or two products with a connector between them? If the answer involves the words “integration” or “sync”, ask what happens when the sync fails, who notices, and how long the two sides can disagree before somebody spots it.
In SCL there is no connector, because there are not two products. The record and the teaching are the same system, and what looks like the SIS or the LMS is only which modules a user’s permissions expose.
2. Test the permissions model with your hardest case
Every vendor will tell you permissions are flexible. Do not ask in the abstract. Bring your three most awkward real people to the demo and make the presenter build them live:
- A head of department who also teaches, and needs oversight of their department but not of anyone else’s.
- A school nurse who must see medical details for every child and must never see a grade.
- A finance officer who works across the whole school on fees and has no business in academic records at all.
None of those three fit a standard role, and a system that ships a fixed list of roles will force you to over-grant access to make them work. That is how schools end up with twelve people who can technically see everything.
What to ask: can permissions be defined per group, per screen, and per action? SCL splits every module into read, write, modify and delete, granted to groups you define yourself, which is what makes the nurse case ordinary rather than a special request.
3. Check reporting against your curriculum, not a generic template
Report cards are where a mismatch between your school and your software becomes visible to parents, which makes them the least forgiving part of the system. A platform built for one national curriculum will make every other curriculum look like a workaround.
What to ask: bring last term’s actual report card and ask them to reproduce it. Not something like it. If your school runs more than one curriculum across divisions, ask to see two different ones from the same system, because that is the case that breaks generic templates. SCL produces American, British, Egyptian and IB شهادات الدرجات from the same student record.
4. If you run the IB, test the IB specifically
IB support is the single most common gap between what a school needs and what a general-purpose platform provides, and it is usually discovered after signature. Percentage gradebooks and criterion assessment are different mental models, and bolting one onto the other produces something neither teachers nor coordinators trust.
What to ask: can a teacher assess against criteria with band descriptors rather than converting to a percentage first? Can a coordinator see curriculum coverage across a division? Are unit and lesson planning connected to what is actually assessed, or is planning a separate document nobody opens after September? SCL carries criteria and band descriptors per division and subject, ATL skills, and standards mastery, with the detail on the IB schools page and the planning side in the مركز المناهج.
5. Ask what happens in year two
Almost every demo shows you a school mid-year. Very few show you the rollover, and the rollover is where thin systems fail. At the end of the year you need students promoted to the next grade, classes rebuilt, subjects and grading carried forward, leavers marked as leavers without their history evaporating, and last year’s records still readable.
What to ask: show me the promotion process. Ask specifically what carries over automatically, what has to be rebuilt by hand, and whether a promotion that goes wrong can be run again safely. Ask to see a student who left two years ago and confirm their record is still intact and still attached to the right academic year.
6. Make them show you the migration, not describe it
“We will handle the migration” is not an answer. It is the single biggest hidden cost in changing systems and the reason many schools stay on software they dislike.
What to ask: ask to see the import tool with your own data, even a sample of thirty rows. Ask what happens when a row is wrong: does the system tell you which row and which column, or does it fail with one unhelpful message? Ask whether a partly-bad file imports the good rows and leaves the rest, or refuses the whole file. There is a right answer for your school and you need to know which behaviour you are getting.
We wrote the long version of this separately, because it deserves its own answer: migrating student records to a new SIS.
7. Check what families actually receive
Parents judge your school by the software you give them, not the software your staff use. A strong back office attached to a weak parent experience is a reputational problem, and it arrives quietly in the form of parents phoning the office for things they should be able to see themselves.
What to ask: open the parent app on a phone during the demo, not the desktop version. Can a parent with three children in different grades move between them easily? Can they see attendance, grades, fees and messages without a second login? Ask the same of the student side.
8. Ask where your data lives and who has touched it
Two separate questions, both worth asking plainly. Where the data physically sits matters for your own regulatory position, and per-school deployment is a different answer from one shared multi-tenant database.
The second question is accountability. When a parent disputes a mark, or a record changes and nobody admits to changing it, you need the system to answer rather than your staff. SCL keeps access logs against records, and administrators can see active sessions with their location and browser and revoke any of them.
What to ask: can you show me who last opened this student’s record? Can I end somebody’s session right now from the admin side?
9. Check the languages, and the direction they run in
If any part of your community works in Arabic, this is not a nice-to-have. Right-to-left is not a translation problem, it is a layout problem, and software that was translated without being laid out for it will look wrong in ways that are hard to unsee.
What to ask: switch the interface to every language you need, in front of you. SCL ships in Arabic, English, French, German and Spanish.
10. Ask what it connects to
No school system is the only system. The realistic question is not whether it integrates with everything, but whether it integrates with the specific things you already run and refuse to give up.
What to ask: name your single sign-on provider, your payment gateway and your timetabling tool, and ask about those three by name. SCL supports single sign-on, online payment gateways, timetabling and locked-down exam browsers, listed on the integrations page, and its الجدول الدراسي syncs both ways with aSc TimeTables rather than importing once and drifting.
11. Ask how you get your data back out
Ask this while they are still selling to you, because it is the question with the least comfortable answer and you will never have more leverage than you do now.
What to ask: if we leave in three years, what do we take, in what format, and does it cost anything? A vendor confident in their product answers this without flinching.
The checklist, short enough to take into the room
- One system or two products with a connector between them?
- Build my head of department, my nurse and my finance officer, live.
- Reproduce last term’s report card exactly.
- If we run the IB: criteria and band descriptors, not percentages converted.
- Show me end-of-year promotion, and a student who left two years ago.
- Import thirty rows of my real data, including a few bad ones.
- Open the parent app on a phone, with a parent who has three children.
- Who last opened this record, and can I revoke a session now?
- Switch to every language we need, including right-to-left.
- My SSO, my payment gateway, my timetabling tool, by name.
- If we leave, what do we take and what does it cost?
A note on price
You will notice there are no numbers in this checklist. SCL does not publish plans, because what a school pays depends on its size and what it runs, and a table of tiers would tell you less than a conversation. If you want a figure for your school, talk to us and we will give you one.
The more useful advice on cost is this: the licence is rarely the expensive part. The expensive parts are the migration, the training, and the staff hours spent every week reconciling systems that were never designed to agree. Price those three when you compare, and the comparison changes.