Groups of schools

One group. Connected campuses.

Give each campus the flexibility to operate, with a shared management view across your school group. Align reporting and key processes as your organisation grows.

Illustrative platform view · Example data

Designed for your team

Connected operations. Clearer oversight.

  • Central oversight with branch-level workflows
  • Compare operational performance across campuses
  • Standardise core processes and reporting
  • Plan phased migration and training for each location
Your operating priorities

Group-wide understanding. Campus-level responsibility.

A consistent foundation

Agree shared record structures and core workflows across the group while defining local responsibilities.

Comparable reporting

Use common definitions and reporting periods when reviewing admissions, attendance and financial performance.

Phased adoption

Plan campus migration, validation and training in manageable waves.

A practical path forward

From first conversation to a confident rollout.

Understand your school

Map your existing systems, data, priorities and team responsibilities.

Connect your workflows

Configure the right modules and agree integration and migration requirements.

Support your people

Validate the setup, train each user group and agree a go-live plan.

For every person in your school

Different responsibilities.
One connected community.

A growing school group needs both central understanding and practical campus ownership. Define a consistent foundation, then give each community the access and workflows it needs.

Group leadership & boards

See across the group

Bring campus information into an authorised group view using common reporting definitions.

  • Comparable admissions, attendance and fee trends
  • Group-wide priorities and follow-up
  • Reporting periods and access agreed centrally
Campus principals

Lead the campus with context

Keep daily accountability close to the school while giving leadership a clear view of local priorities.

  • Campus operations and academic visibility
  • Staffing, timetable and school services
  • Exceptions assigned to responsible teams
Teachers

A focused classroom workspace

Let teaching staff work with their assigned classes and subjects without adding unnecessary group-level complexity.

  • Class schedules and attendance
  • Assignments, marks and reports
  • Communication for the families they support
Parents & students

A familiar school experience

Create a consistent approach to school access while respecting each family’s campus and student relationships.

  • Relevant school and child information
  • Academic updates and school notices
  • Configured fees and campus services
Shared services

Coordinate finance, HR and resources

Align common processes where it makes sense and make local responsibilities explicit.

  • Agreed fee and financial reporting structures
  • Staff records, payroll and leave workflows
  • Purchasing and resource visibility
IT & implementation teams

Scale through a controlled rollout

Plan data, permissions and onboarding across campuses in manageable stages.

  • Shared data definitions and migration checks
  • Campus-level permissions and role training
  • Integration, hosting and support planning
A connected journey

Every handover.
A little more connected.

Configure the platform around your people, your school policies and the outcomes you want to review.

01

Agree the group foundation

Define shared data, reporting measures, access boundaries and campus responsibilities.

02

Pilot with one campus

Validate everyday workflows, migrated records and the school-community experience.

03

Roll out in phases

Train each campus, check readiness and align go-live with its academic calendar.

04

Compare and refine

Review adoption and operational performance using the same definitions across schools.

Keep your school connected

Works as part of the bigger picture.

Planning your implementation

A few practical questions.

Can campus teams keep their own responsibilities?

Define branch-level access and workflow ownership alongside the group’s central reporting requirements. The configuration is agreed before rollout.

How should we begin a multi-campus implementation?

Start with common data definitions and a representative campus. Validate migration, reporting and training before expanding the agreed approach.

A smarter school starts here

More time for education.
More possibilities with AI.

Let’s explore what a connected school could look like for you.

Book your personal demoA conversation built around your school.