Start with the problem you are paying to solve
Most disappointing software purchases began with a feature list rather than a problem. Before you look at any product, write down the two or three places where staff time is being lost or information is being reconciled by hand: perhaps a register that has to be re-keyed, reports assembled from three spreadsheets, or families who cannot find a message.
That short list is what you test every product against. A system that impresses in a demonstration and does not touch those problems has not earned a place on the shortlist.
Know which kind of system you are buying
The vocabulary is used loosely, and vendors position themselves in the gaps. These are the working meanings.
| System | What it is mainly for |
|---|---|
| Student information system | The record of who the students are, their enrolment, attendance, grades and family contacts. |
| Learning management system | Delivering and collecting classwork: assignments, resources, submissions, feedback. |
| School management platform | Running the school: records, timetable, communication, reporting and often finance, in one place. |
| Curriculum and assessment platform | Planning what is taught and recording what was learned against a framework. |
The core every school should test
Whatever a school teaches, a short list of capabilities carries most of the value. For each, ask to see it done rather than described.
- Student and family records: can you add, change and find a student and their guardians in seconds, and does the change appear everywhere?
- Attendance: is the register quick for a teacher, and does it feed reports and family communication without re-entry?
- Timetable and calendar: can it handle your real complexity, such as shared rooms and part-time staff?
- Assessment and reporting: can a report be produced from what teachers already recorded, with a review step before families see it?
- Communication: can staff reach families individually and in groups, and can families reply in a way you can manage?
- Admissions and fees, if you need them: do they connect to the student record or sit apart from it?
One record or many: the test that matters most
The most valuable property of a school platform is that a student exists once. When they do, changing a name, a class or a guardian's email changes it for attendance, grades, reports and messages together. When they do not, the school pays for it in reconciliation.
The test is quick. In the demonstration, ask the presenter to rename a student and a guardian, then show you where the change appears. Ask which modules hold their own copy. The answer tells you more about a system than any brochure.
Roles, permissions and privacy
A school holds sensitive information about children, so the permission model is not a detail. Check that a teacher sees only their own classes, that a parent sees only their own children, that leaders see what they need, and that a change to a record is logged with who made it.
Ask where data is stored, how long it is kept, how a record is deleted on request, and what the vendor does with it. The laws that apply differ by country, so ask what the vendor commits to in the contract rather than accepting a general assurance.
Families and students: portals, language and devices
A platform is judged partly by whether families actually use it. Look at the parent view on a phone, check that messages arrive somewhere a parent will see them, and ask how a family whose first language differs is served.
Ask, too, whether there is a native app or a web application, because it affects both the experience and what you have to support. Neither is wrong, but a claim of a mobile app should be checked rather than assumed.
AI features: what to ask
Many products now advertise AI. The questions that matter are what the AI can see, where requests are processed, who approves output before a student or family sees it, and whether each request is recorded. The fuller checklist is in how AI is changing school management, and the risks and benefits are weighed in AI-powered school management: benefits and challenges.
Getting data in, and getting it out
The cost of a system is often set at the edges. Ask what can be imported, in what format, and whether history comes across or only current records. Ask whether an import can be undone.
Ask, before signing, how you would leave. Can you export students, staff, grades, attendance and reports in a form you can use? A vendor confident in the product will answer this plainly, and one that changes the subject has told you something.
How skodle helps
This section names our own product, so weigh it accordingly. The checklist above is the test to put to us as well.
skodle is a single web platform with one login and role-based portals for staff, students and families. Behind it sit curriculum planning with IB programme structures, assessment and a gradebook, portfolios, reports and transcripts with a draft, approval and publish flow, daily attendance, timetable and calendar, behaviour and wellbeing, announcements, messaging and forums, homework and courses, parent-teacher meetings, staff professional development, fees, payroll and a general ledger, and analytics for leaders, with AI drafting and a read-only copilot included in every plan. Staff, students and families each work in their own portal, and significant actions are recorded in an activity log. See the product overview and skodle AI, or start the free trial and run this checklist on your own data.
The limits, in the order they are likely to matter. The curriculum engine is built around the IB programmes, so a Cambridge syllabus or CBSE scheme is not modelled the way an MYP unit is, although the school structure, assessment, attendance and reporting layers are shared. Attendance is daily rather than period by period. There is no library, transport, canteen or inventory module, and no native mobile app. Integrations with other systems are catalogue entries rather than working connectors, so anything you keep runs beside skodle. An import brings in students and staff only, not historical grades or attendance, and cannot be undone. There is no single export of a whole school's data, though individual records such as attendance, reports and transcripts export. Admissions is a stage-by-stage lead tracker rather than an application record with documents. Fees, payroll and the ledger are newer, so confirm those flows in a demonstration.
Pricing is per user, per month: $2 per user for up to 150 users, $3 from 151 to 500 users and a custom plan above 500, with parents at half the rate and every feature in every plan. Every new school starts with a free 30-day trial, so the fair test is your own data. See pricing.
What it costs, beyond the price list
Pricing models differ: per student, per user, per campus or a flat licence. Compare them on your own numbers, including staff, students and families, and ask how the price changes as you grow.
Then ask about everything the price list leaves out: implementation and training, charges for messages or storage, payment processing fees if you collect fees online, and any usage limits on AI. A low headline price with several of those added is not cheaper than a higher one that includes them.
A scorecard you can copy
Score each product from one to five against your own priorities, weight the rows that matter most to you, and record the evidence for each score.
| Criterion | What good looks like |
|---|---|
| Fit to your problems | Solves the two or three problems you wrote down, shown on your own data. |
| One record per student | A rename in one place appears everywhere, shown live. |
| Permissions | Each role sees only what it should; changes are logged. |
| Families | Easy on a phone; messages reach them; the language need is met. |
| Data in and out | Import path clear; export of your records demonstrated. |
| AI, if you want it | Clear on what it sees, where it goes and who approves output. |
| Total cost | A price for your size including everything you would need. |
| Support and implementation | A named person, a plan and a date for going live. |
Warning signs in a demonstration
A demonstration is a performance, so watch for what is avoided.
- Only sample data is shown, never a real class of yours
- The presenter cannot rename a student and show where it changes
- Answers to data and export questions are promised in writing later
- Features are described that cannot be found on the screen
- Price is available only after a long sales process
