Reporting covers the built-in set every school needs, scheduled delivery of a report to whoever should receive it, drill-down from any figure to the rows behind it, and complete structured export. The report library is deliberately small.
This is the reporting mechanism. Which numbers are worth acting on is a different question, answered on the data-driven decisions page.
A report library with two hundred entries is a symptom. It means nobody could decide which numbers mattered, so every request became a new report, and now nobody can find the four that get used.
A collection percentage that cannot be opened is a number to be argued with. One that opens onto the families behind it is a number to act on — and, more importantly, a number somebody can check. Most disputes about a figure are resolved by looking at what went into it.
Complete structured export on demand, without asking us. Your data should be readable without us, and the moment that promise is tested is when a school is unhappy — which is exactly when a support ticket is the wrong mechanism.
Phrased the way they arrive, answered so each one stands on its own.
Yes, and export anything you would rather analyse in a spreadsheet or a BI tool. The built-in set stays small on purpose.
Yes, to a named person on a cadence — a Monday collection summary to the bursar, a monthly board pack to the trust.
No. Other schools’ data is theirs, and comparison across differing boards and catchments would mislead. Comparison is against your own history.
Checked by the Implementations desk on 6 September 2026. Corrections go in the page, dated, rather than quietly.
Pricing is on the page, in the open, with the counting rule written next to it. Nobody has to book a call to find out what it costs.
See pricingForty minutes with an implementation engineer — your classes, your fee heads, your grading scheme, entered as we go. No slides, no sample school.