Several schools, one platform.
Shared standards where they help, local autonomy where it matters.
Group, school and person are a hierarchy in the schema, which is why a roll-up needs no export.
Multi-tenant from the schema
Group, then school, then person. Built in from the start rather than added as a reporting layer.
Shared standards
Policies, curriculum models and assessment scales defined once, adopted locally, with variation recorded.
Real comparability
One definition of attendance, conversion and staffing ratio, so benchmarks compare performance rather than methodology.
One person, many schools
Staff working across sites hold one record, one contract history and one set of clearances.
Shared where it helps, local where it matters.
A group needs comparable data and a common standard. A school needs to run its own day. The tier model resolves that by putting group, school and person in a hierarchy from the schema up, so a policy can be set centrally and adopted locally, and a report can roll up without anyone exporting anything.
One definition of attendance.
The reason group reporting usually fails is that each school counts differently. Here the definitions live in the schema rather than in each school's habits, so a benchmark comparison is a genuine comparison and a board conversation is about performance rather than about methodology.
Full functionality
Every workflow below is specified with its trigger, its actor, the screen it happens on, the step sequence, the permissions and the edge cases.
01Group, school and person
- The hierarchy is in the schema, not added later as a reporting layer.
- A person can hold roles in more than one school without holding a second account.
- Group-level roles see across schools; school-level roles do not, unless granted.
- Every cross-school grant is time-bound and logged like any other.
02Shared standards
- Policies, curriculum models, assessment scales and skill frameworks defined once at group level.
- Adoption tracked per school, with local variation recorded rather than hidden.
- A group change propagates as a proposal for each school to accept, with the version history visible.
- Compliance positions comparable because the underlying definitions are identical.
03Consolidated reporting
- Roll, admissions pipeline, attendance, staffing and finance rolled up live rather than exported monthly.
- Drill from a group number into the school, the year group and the record behind it.
- Board packs generated at group level from the same records the schools run on.
- No spreadsheet reconciliation, because there is nothing to reconcile.
04Central admissions and marketing
- Group-level enquiry capture with routing to the right school by location, year group and availability.
- A family enquiring at one school is recognised at another rather than entered twice.
- Shared campaign tracking, so spend is attributed across the group correctly.
- Waitlist visibility across schools where the group's policy permits it.
05Cross-school people and procurement
- Staff working across sites hold one record, one contract history and one set of clearances.
- Recruitment run centrally or locally, with the same safer recruitment evidence either way.
- Supplier contracts, renewal dates and framework agreements held at group level.
- Purchasing power visible, because group spend is actually aggregated.
06Adding a school
- A new school is provisioned from the group standard rather than configured from nothing.
- Local variation applied deliberately and recorded, rather than accumulating by accident.
- Data migration handled as a governed project with reconciliation evidence.
- The founding school's operational reality is what the group standard was built from.
More of the platform
Enquiry to enrolment in one pipeline, with the lead funnel, assessment days and offers in the same place as the record they create.
One record per child, composed from every department, with pastoral, inclusion and safeguarding built into it rather than bolted on.
A register a teacher finishes in forty seconds, with statutory reporting, absence follow-up and roll call already computed.
See it running on real data.
A working demonstration on a live database, walked through by the people who built it. Forty minutes, no slide deck.