Education management platform or school management system: which does your institution need?
The assumptions built into school software, how to test any product against a week of your own work, and the questions worth putting to vendors.
Education technology
The questions to ask any vendor before a coaching or test preparation centre signs up, how to run a fair trial, and our own answers for SkoolBro.
Most software demos look alike. The screens are tidy, the sample data is neat, and every feature you ask about seems to exist. The differences show up later, with your own exceptions: the learner who joins on the 18th, the family with three children, the tutor who teaches at two branches, the mock test the whole centre sits on a Sunday. A written checklist lets you ask every vendor the same questions and compare the answers fairly. That includes us, so this checklist ends with SkoolBro's own answers.
The example is made up, and its numbers are illustrations. Orbit Coaching Centre has three branches, 22 batches, 14 tutors and about 340 learners preparing for school exams and entrance tests. Today it runs on a spreadsheet per branch, a fee register at each desk and a lot of phone calls. The owner has a shortlist of three systems and two weeks to choose.
Write down the problems you want the software to solve, in your own words. Orbit's list was short: fees chased by phone at three desks, marks kept in tutors' notebooks, parents calling to ask about results, and no way to see all three branches without visiting them. Every question you put to a vendor should trace back to a line on that list. A feature that solves none of them is no reason to pay more.
Then list who will use the system and what each person needs: the owner, the branch managers, the person at each front desk, the tutors and the parents. If tutors find it slow on a phone, they will not use it for attendance, however good the reports look.
Coaching centres group learners in ways that school software does not always expect. Ask each vendor to show you the answers with your own batches.
The first question matters most for centres where learners choose subjects one by one. If your learners mostly study in fixed groups, it matters much less.
Test preparation centres should press on mock tests in particular: whether each section of a mock can be marked separately, and whether a learner's results across many tests can be seen together on one screen.
Ask the vendor to walk through one complete fee month with your fee rules, from issuing invoices to the month-end total. A single payment screen tells you little about how the month works.
Parents should be able to see attendance, results and fees without phoning the desk. Ask what the parent view shows, whether parents can message the centre, and whether a notice can go to one batch only.
On data, ask where the records are stored, who at the vendor can open your records and when, whether sensitive details such as identity numbers are encrypted, and whether there is a log of who changed what. Ask how you get all your data out if you leave. If the system has AI features, ask what information goes to which AI provider, whether names are removed first, and whether the AI can change records or only read them.
On price, ask what you are paying for: learners, branches, staff logins or features. Ask what happens if you pass a limit in the middle of a term, and whether the trial needs a card.
A demo runs on the vendor's sample data, so it cannot show how a system copes with yours. Orbit ran each shortlisted system the same way, at one branch, over two weeks.
Score every system on the same sheet, against the problem list you started with. Give the tutors' and desk staff's opinions as much weight as the owner's, because they are the ones using it every day.
These are our own answers, for the product as it stands today. SkoolBro's screens use school words, so in the answers a batch is a class section, a tutor is a member of staff, a test is an exam with a paper for each subject, and a branch is a campus.
| Question | SkoolBro today |
|---|---|
| One learner in two batches at once | No. Each learner is in one batch per session. A batch can hold several subjects, each with its own tutor. |
| Weekend timetables | Yes. Periods, rooms and a weekly timetable per batch, on any day of the week. One list of periods per campus applies to every day, so weekend times must not overlap weekday ones. |
| Several branches | Yes. One account holds every branch, and each person's access can be limited to the branches they work at. |
| Marks, results and positions | Yes. Tutors enter marks for their batches, papers are locked, and published results show grades and positions in the batch. Exam analysis compares subjects and batches. |
| Online tests and question banks | Not built. |
| One learner's marks across many tests | Each test has its own results. There is no single chart across tests yet. |
| Monthly and one-time fees, sibling discounts | Yes. Fees per level with monthly or one-time items, concessions approved by a second person, printable vouchers and a receipt for every payment. |
| Parents paying online | Not yet. You record payments by method: cash, bank transfer, card, mobile wallet or cheque. |
| Text messages and WhatsApp | Coming. Email and in-app notices work today. |
| Parent view | Yes. A portal with attendance, timetable, results, homework and fees, plus messages with staff. |
| Moving in | Imports for learners, staff and unpaid fee balances from CSV or Excel. |
| Data protection | Each organization's records are kept apart, with roles, two-step sign-in, an audit log, encrypted identity numbers, and support access only when you allow it and for a limited time. |
| AI | A read-only assistant answers questions from your own records, and names are replaced with placeholders before anything reaches Google's Gemini. AI agents for routine work are on our roadmap. |
| Trial | 14 days, with no card needed. |
More detail is in the security section and the pricing section, and our article on how each organization's data is kept separate covers the data protection side. If you are weighing a school system against a broader one, read about the difference between an education management platform and a school management system.
Long enough to run one full fee month and at least one weekly test with real batches, which usually means two to four weeks. Sample data in a demo will not show how a system copes with your exceptions.
A clean spreadsheet of learners with parents' phone numbers and batches, a list of batches with tutors and times, your written fee rules, and each family's unpaid balance on the day you switch.
Ask how mock tests are recorded, whether each section can be marked separately and whether you can compare batches on the same test. If you need online tests, ask to see one running with real learners.