Most schools don't fail at buying software — they fail at getting anyone to use it. The system looks great in the sales demo, then six months later fees are back in a spreadsheet and attendance is back on paper. The difference between adopted and abandoned usually comes down to a handful of practical questions you can ask before you commit.
1. Does every role get its own view?
A school is at least five different jobs: administrators, teachers, students, parents and support staff. If they all log into the same crowded dashboard, most of them will stop logging in. Look for genuinely role-based portals — a teacher should see their classes and attendance, a parent should see their child's fees and results, and neither should have to navigate past the other's tools.
2. Can it run your actual fee structure?
Fees are where school systems most often break. Before any demo, write down your real cases: sibling discounts, scholarships, mid-term admissions, transport fees, late-payment fines, partial payments. Then make the vendor enter your cases live. If the system can't model your fee structure on day one, it never will.
3. How long does attendance actually take?
Attendance happens every class, every day — it's the highest-frequency action in the whole system. If marking a class takes a teacher more than 30 seconds, multiply that friction by 200 school days and watch adoption collapse. Ask for a stopwatch demo.
4. Are exams and report cards flexible enough?
Every school grades differently: term weightings, grace marks, custom grade boundaries, subject groups. A good system lets you define your scheme once and generates report cards automatically. A bad one makes you export to Excel "just for the report cards" — which quietly becomes exporting to Excel for everything.
5. Where does your data live, and can you leave?
You're storing children's personal information, so this section is non-negotiable:
- Data encrypted in transit and at rest
- Role-based access control (a teacher can't see fee records; a parent can't see other children)
- Regular automated backups
- Export — you can take all your data with you if you ever switch systems
6. What does onboarding actually look like?
Ask three concrete questions: Who imports our existing student records? How long until teachers are trained? Who do we call in week two when something is confusing? A vendor who answers precisely has done this before; one who waves at "documentation" has not.
The one-line test
If you remember only one thing: pick the system your least technical teacher will still be using in March. Features you never use don't count.
We built CampusCore around exactly this checklist — five role-based portals, real fee-structure flexibility, fast attendance and clear reporting. If you run a school, take a look or ask us for a walkthrough.