Best school management software for IB schools: a buyer's guide

Why IB schools need to evaluate differently

A general school management system handles student records, attendance, fees, timetables and exams. Those matter, and an IB school needs all of them. But they are the half of the job that looks the same in every school.

The other half does not. An IB school has to plan against a framework, run inquiry, assess against criteria, collect student reflection, keep portfolios, report on more than marks, and hold evidence for an authorisation or evaluation visit that may be years away. Software that treats those as add-ons to an administrative core will make each one a separate job.

So the question is not which platform has the longest feature list. It is which one understands that a unit plan, an assessment, a piece of student work, a report and a line of evidence for a visit are the same thing at different points in its life.

The workflow to hold in your head while comparing

Every capability below is worth something only in relation to the one after it. It is worth writing the chain down before any demo, because it is what a vendor's screens should map onto:

Curriculum → unit planning → learning experiences → assessment → student evidence → portfolio → progress report → family communication → Standards and Practices evidence.

In most schools each step happens somewhere else. Planning in a shared document, assessment in an LMS, portfolios in a third app, reports in the student information system, messages by email, and evidence for the visit in a folder of spreadsheets. Nothing there is broken. The cost is in the gaps: teachers spend their time moving information between systems rather than teaching, and the same fact is typed three times.

1. Curriculum planning, and whether it is structured

This is the one that decides whether everything downstream is possible. The question is not whether the platform stores unit plans — everything stores unit plans — but whether the framework is modelled as data or described in prose inside a document.

If a concept is a word typed into a template, no software can tell you which year groups met it. If it is a record the unit is linked to, coverage becomes a query and a gap becomes something the system can point at.

For PYP that means the programme of inquiry, transdisciplinary themes and central ideas as real objects. For MYP it means key and related concepts, global contexts, statements of inquiry and ATL. For DP it means course requirements and assessment components staying visible against deadlines.

• Ask them to run a coverage report live, rather than show you a planning screen
• Ask which units currently touch one named concept, across year groups
• Ask what happens to a unit plan when the framework it references is revised
• Ask whether a lesson inherits the unit's framework fields, or repeats them

2. Assessment that reaches the report on its own

IB assessment is not one thing. DP carries internal and external assessment; MYP works through criteria across a range of tasks; PYP's emphasis sits with feedback, student reflection and teacher self-assessment rather than formal marks. A gradebook built for percentages will fit none of them comfortably.

The test that matters is not the range of assessment types. It is whether a mark, once entered, arrives in the portfolio and the report card without anybody retyping it. Re-entry is where marking time goes and where errors get in.

• Watch someone enter one mark, then open the report it lands in
• Ask how criterion-based assessment is recorded, not just displayed
• Ask whether unmarked work is shown as unmarked or counted as zero
• Ask where student reflection lives, and whether it reaches the report

3. Portfolios, and whether the evidence connects to anything

Portfolios make learning visible, which is why they matter more in an IB school than almost anywhere else. Photographs, video, audio, written reflection and finished work all belong in one.

Storing files is the easy part, and most tools do it well. The question is whether an entry knows what it evidences. A stream of pleasant moments is not a record of learning: at a review, somebody has to say which central idea or objective a piece of work demonstrates.

The useful shape is: student reflection → unit → concept → ATL skill → assessment → report. If a portfolio entry cannot be attached to the outcome it proves, it will be re-described by hand in June.

• Open one child's entry and ask which outcome it evidences
• Ask what a parent sees, and who decides what is shared
• Ask whether evidence survives the year, or archives with the course

4. Reporting built from what already happened

IB reporting has to bring together assessment results, portfolio evidence, teacher comment, objectives, skills, student reflection and attendance. Assembling that by hand from several systems is what turns reporting week into reporting fortnight.

A report should be composed from records captured during the year rather than rebuilt from memory at the end of it. The difference shows in whether a teacher can produce a draft in a meeting, or needs a week's notice.

• Ask them to build a report in the meeting from evidence already recorded
• Ask whether a goal a student set in September appears unchanged in December
• Ask what a report looks like for a child who joined in February

5. Authorisation and evaluation evidence

This is the widest gap between generic school software and something built for the IB, and the one schools feel most sharply at the worst moment.

Evidence assembled in the fortnight before a visit is evidence about that fortnight. A visiting team can tell. The alternative is that artefacts link to the standards and practices they evidence as they are created, so the pack is a report you run rather than a folder you build.

The question worth asking every vendor is not whether they can store evidence. It is whether they can tell you which practices currently have nothing against them.

• Ask which practices have no evidence attached today
• Ask to see last year's evidence, not a blank template
• Ask what the visiting team actually receives, and in what format
• Ask who owns the evidence if you change supplier

6. AI, and what it is allowed to see

AI is genuinely useful for the repetitive parts of teaching — drafting a rubric, a first pass at report comments, differentiating a task. It is not useful, and is a real risk, when it acts without a person approving the result.

The question schools should ask is rarely whether a platform has AI. Every platform has AI. Ask instead what it can see, who decided that, and what record exists of what it looked at. An assistant that can read one school's data from another school's account, or that answers a question a teacher is not entitled to ask, is a safeguarding problem wearing a helpful interface.

• Ask who is recorded as the approver, and where that record lives
• Ask whether the AI can answer from another school's data, and how that is prevented
• Ask what is logged when the AI consults a student record
• Ask whether it answers from your curriculum or from a general model

What to compare, and why each one earns its place

A shortlist is easier to judge against a written list than against three demos remembered a week apart. This is the list we would use.

One platform or several: the honest trade

The case for one connected platform is not that specialist tools are bad. Most are good at what they do. It is that the seams between them are where the work accumulates: copying curriculum data, uploading the same evidence twice, exporting grades, importing reports, and searching four systems to answer one question.

The case against is equally real. A single supplier is a single point of failure, migration is a term of work, and no one platform is the best available version of every module it contains. A school with a beloved LMS and a working SIS may be better served by keeping both and connecting them.

The useful comparison is not licence cost. It is the total cost of the workflow — the subscriptions, plus the staff time spent moving information between them, plus the fortnight before a visit that gets spent assembling something a connected system would have accumulated.

Where skodle fits

skodle is built around the chain at the top of this article rather than around an administrative core with IB features added. Curriculum planning, assessment, portfolios, reporting, communication, school operations and authorisation evidence are modules of one system reading the same records.

Concretely, and only what exists today: PYP, MYP, DP and CP are each modelled on their own terms; units link to the concepts and objectives they deliver, so coverage is counted from the links; DP components — IA, EE, TOK, CAS, and the CP components — are tracked per student with predicted grades and due dates; portfolio entries attach to the outcome they evidence; and artefacts link to IB standards and practices, with an evidence package you can hand a visiting team.

Two corrections to how this is often described, including by us. Evidence linking is deliberate, not automatic — a person decides that this artefact evidences that practice, and no software should guess it on a school's behalf. And the accreditation model covers IB standards and practices across the four programmes; it is not a general multi-framework accreditation tool.

• PYP programme of inquiry, themes, central ideas and units as linked records
• MYP subject-group and interdisciplinary planning, ATL, criterion assessment
• DP and CP components tracked per student, with predicted grades
• Portfolios, reports and family portal reading the same records
• IB standards and practices with gap reporting and a visit-ready export

Where skodle is the wrong answer

A buyer's guide that ends with the author winning is an advertisement, so here is where we would tell you to look elsewhere.

If you need district-scale student information management — state reporting pipelines, transport routing at scale, complex multi-school fee structures — a full SIS will serve you better. If fundraising and advancement matter to your school, we do not do them, and you should keep the system that does. If sophisticated course tooling is central to how your teachers work, an LMS built for that will do it better. And we are younger than the established platforms, with a shorter track record behind us; that is a real consideration rather than one to talk anybody out of.

The strongest case for skodle is a school running one or more IB programmes where the curriculum, the evidence and the reporting are currently in different places, and the cost of that is being paid in teacher time.

Questions to take to every vendor, including us

If a vendor cannot answer one of these plainly, that is itself the answer. Ask for the artefact rather than the claim — every supplier says yes to 'do you support MYP'.

• Which programmes do you support, and can a coordinator move between two in front of me?
• Run a coverage report on your demo data now, please
• Enter one mark and open the report it lands in
• Which standards and practices currently have no evidence attached?
• Sign in as a parent and try to reach another family's child
• Show me one audit entry and the fields it carries
• Give me a sample export file before we sign, not a promise
• What is your written price at double our current roll?