Best school management software for Cambridge schools: what to evaluate

Why a Cambridge school's software problem is an exams problem first

Most comparisons of school management software are written about planning and reporting. In a Cambridge school those matter, but they are not where the year goes wrong. The exams office is.

Cambridge assessment is externally administered against fixed deadlines, on a timetable set by the administrative zone the school is allocated to by its location. Entries are made through Cambridge International Direct, either keyed in or uploaded as a data file. Miss a deadline and the cost is a late fee at best; get an entry wrong and a candidate can sit papers and receive no result at all.

So the first question to put to any vendor is not about unit planners. It is what the software does on the day the exams officer builds the entry file, and what it does the day results are released.

Four stages in one school, and the joins between them

A full Cambridge pathway runs Early Years, Primary, Lower Secondary, IGCSE, then AS and A Level. Each has a different shape: the early stages are curriculum frameworks the school teaches and assesses itself, while the later ones are syllabuses with external examinations attached.

That matters because a system built around one of those shapes handles the other badly. A platform designed for external syllabuses will have nowhere sensible to put Primary teaching. A platform designed for internal planning will treat an IGCSE syllabus as a folder of topics rather than a set of assessment objectives with components behind them.

The join is where the value is. A school should be able to follow a learner from a Primary Checkpoint result through Lower Secondary into an IGCSE option choice, and see that as one record rather than three systems and a spreadsheet.

Entries, option codes, and the thing that actually goes wrong

This is the part that generic school software almost never handles, and the part a Cambridge exams officer will judge a platform on.

Entries are made against a syllabus using an entry option code, and that code determines which components a candidate sits. Components cannot be entered individually, and a candidate entered for a combination that is not one of the published options is not eligible for a result. Carry-forward entries, where a candidate keeps a previously achieved component result, add a second way for this to go wrong quietly.

Ask a vendor to show you the entry stage end to end. If the answer is that the school exports a spreadsheet and the exams officer retypes it into Direct, that is a legitimate answer, but know that you are buying a planning system rather than an exams system, and budget the exams officer's time accordingly.

• Ask how syllabus and option codes are stored, and who keeps them current each series
• Ask what happens when a candidate changes option after entries open
• Ask whether carry-forward entries are represented, or handled outside the system
• Ask what the export into Direct looks like, and who checks it
• Ask how the administrative zone and its deadlines reach the school calendar

Checkpoint, and what a school does with the results

Cambridge Primary Checkpoint and Lower Secondary Checkpoint are marked by Cambridge International and come back as feedback reports and a Statement of Achievement. They are optional at school level, which means a school choosing to run them is choosing to do something with the data.

The test series have expanded, so a school now has more than the two windows it may be used to planning around. Cambridge's own published timetable for the current cycle is the authority on series and deadlines, and it is worth checking rather than assuming last year's calendar still holds.

The software question is narrow and practical: can the feedback report data be brought back in and read against the school's own assessment record, or does it live as a PDF in a shared drive? A Checkpoint result that never meets the school's own data is a report to parents and nothing more.

Schemes of work and assessment objectives

For the taught stages, the useful test is the same one that applies to any curriculum: is the framework stored as data, or described in prose inside a document?

If a learning objective is a line of text in a scheme of work, nobody can answer which classes have covered it. If it is a record that a unit and an assessment both point at, coverage becomes a query and a gap becomes something the system can surface in October rather than in May.

For IGCSE and A Level the equivalent is the syllabus assessment objectives. A platform that lets a teacher tag a task to an assessment objective, and then reports on the spread across a cohort, is doing something a document cannot. One that stores the syllabus as an attachment is storing a file.

• Ask whether learning objectives are records, or text inside a template
• Ask for a coverage report across a year group, run live rather than described
• Ask what happens to a scheme of work when the syllabus is revised for a new series
• Ask whether assessment objectives can be reported on across a cohort

Coursework, mocks and grade thresholds

Several Cambridge syllabuses carry internally assessed components that the school marks and Cambridge moderates. That is a workflow with deadlines, sampling and internal standardisation attached, and it needs somewhere to live that is not email.

Mocks are the other half. Schools run them to predict, to set intervention and to make entry decisions, which means mock marks need to sit against real grade boundaries to mean anything. Cambridge publishes thresholds per syllabus and series, and grade scales differ between syllabuses, so a platform that hard-codes one scale across the school will misreport somebody. Cambridge's published syllabus and threshold documents are the authority here; software should read them rather than assert them.

• Ask how internally assessed components are marked, sampled and moderated
• Ask whether mock marks can be converted using a threshold the school enters
• Ask how the platform represents different grade scales in the same school
• Ask where predicted grades are recorded, and who is accountable for them

Reporting to families across four very different stages

A Cambridge parent in Primary wants to know how their child is progressing against what is being taught. A Cambridge parent in Year 11 wants to know whether their child is on track for the grade they need. Those are different reports, and a school running the full pathway has to produce both without maintaining two systems.

The practical test is whether a report is composed from records captured during the year, or assembled from memory at the end of it. The difference shows in whether a teacher can produce a draft during a meeting or needs a week's notice.

Registration, quality standards and the approval visit

A school becoming a Cambridge International School goes through a registration process with an approval visit attached, against quality standards covering areas such as the school's curriculum and teaching, its facilities and its examination security. Registration can be granted with conditions, meaning approval subject to further work on curriculum planning, staff development or exam security before the restrictions lift.

Cambridge's own registration guidance is the authority on the current steps, the standards and the fees, and it is the document to work from rather than a summary. What software can contribute is narrow but real: if the school's curriculum planning, staff development records and policies are already held as records rather than assembled for the occasion, the visit is a conversation about what exists rather than a project to produce it.

The administrative half every school also needs

Everything above is the Cambridge-specific half. The other half is the same in every school, and it is where most of the daily use actually happens: admissions, student records, attendance, timetabling, fees, behaviour, communication with families and the parent portal.

It is worth being honest with yourself about the balance. A school whose real pain is fee collection and parent communication should not choose a platform on the strength of its syllabus modelling, and a school losing a fortnight a year to entries should not choose one on the strength of its fee module.

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 worth taking into each one.

Questions to take to every vendor

Ask for the artefact rather than the claim. Every supplier will say yes to a question about supporting Cambridge; far fewer can show it running.

• Show me an IGCSE syllabus in your system, with its components and option codes
• Build an entries file in front of me, and show me what happens when an option is invalid
• Run a coverage report against assessment objectives for one cohort, now
• Show me a Primary report and a Year 11 report generated from the same records
• Where does a Checkpoint feedback report land, and what can we do with it?
• Show me one internally assessed component from marking to moderation sample
• Sign in as a parent and try to reach another family's child
• Give me a sample export file before we sign, not a promise of one
• What is your written price at double our current roll?

Where to start if you are still on spreadsheets

Plenty of good Cambridge schools run on documents and a well-organised exams officer, and that is not a failure. It stops working at a predictable point: when the number of syllabuses times the number of candidates exceeds what one person can hold in their head, or when that person leaves.

If that is where you are, the cheapest useful first step is not a platform purchase. It is writing down the entries process as it actually happens, including the checks that currently live in somebody's habits. That document is what you should evaluate software against, and it is also the thing that protects the school on the day the exams officer is unavailable.