Skip to content
Qentak — The Education Operating System

QENTAK FOR MULTI-CAMPUS SCHOOL GROUPS

Keep each campus close. See the group clearly.

Connect campus operations and shared services through agreed standards, local responsibilities, and a group view that preserves the meaning behind the numbers.

Education leaders reviewing priorities across institutions
THE PEOPLESet the standards

Agree common records, responsibilities, and reporting definitions.

01 / 03

START WITH THE REAL WORK

The daily pressures facing multi-campus school groups.

01

Comparable information

Agree definitions and reporting periods before comparing campuses with different structures or calendars.

02

Local decisions, clear boundaries

Distinguish what a campus can configure and approve from decisions reserved for the group.

03

Joined-up shared services

Coordinate finance, HR, procurement, and learner transfers across campus boundaries with accountable ownership.

WHAT TO LOOK FOR IN YOUR SETTING

Standardize definitions before comparing institutions.

A group needs a coherent view of enrollment, educational activity and operations while each campus retains its local calendar and responsibilities. Shared reporting does not require every school to have an identical daily process.

A representative operating decision

Choose one measure and compare two campuses. Agree the population, reporting period and permitted local differences before discussing performance; otherwise a polished dashboard can conceal incompatible definitions.

BUILT AROUND YOUR STRUCTURE

Academic structure for multi-campus school groups.

Map the group, legal or operating entities, campuses, academic divisions, shared services, and calendars. Shared identifiers and definitions connect information while campus structures can remain distinct.

Explore the capability directory

A DAY IN YOUR SETTING

Group insight with local responsibility

An illustrative workspace. Choose an item to explore its next conversation.

3campus views
2shared-service actions

ILLUSTRATIVE TASK · MULTI-CAMPUS SCHOOL GROUPS

Campus review

Compare the same reporting period and definitions.

Discuss the handover: who confirms this step, what information is needed, and which team acts next?

Capabilities that belong in this conversation.

THE LEARNER JOURNEY

Multi-Campus School Groups: the learner journey.

An illustrative workflow to shape your institution’s demonstration.

  1. 1

    Set the standards

    Agree common records, responsibilities, and reporting definitions.

  2. 2

    Operate locally

    Let campus teams manage the work assigned to them.

  3. 3

    Review across campuses

    Compare like-for-like indicators and investigate the context behind exceptions.

  4. 4

    Coordinate action

    Assign support, approve shared investments, or manage a learner transfer.

ONE INSTITUTION. DIFFERENT PERSPECTIVES.

What each team needs in multi-campus school groups.

Group executive

Comparable campus indicators and strategic actions.

Campus principal

Local priorities, staff responsibilities, and learner context.

Shared-services lead

Cross-campus requests, approvals, and service follow-up.

Explore responsibilities by role
School board members discussing a campus plan in a timber meeting roomQentak for Multi-Campus School GroupsSet the standards → Review across campuses

SEE HOW THE WORK CONNECTS

Qentak for Multi-Campus School Groups

Connect campus operations and shared services through agreed standards, local responsibilities, and a group view that preserves the meaning behind the numbers.

  1. 01

    Set the standards

    Agree common records, responsibilities, and reporting definitions.

  2. 02

    Operate locally

    Let campus teams manage the work assigned to them.

  3. 03

    Review across campuses

    Compare like-for-like indicators and investigate the context behind exceptions.

Illustrative workflow · Shape the details around your institution.

BEYOND THE CLASSROOM

Coordinate the operations behind learning.

Consider consolidated budgets, shared purchasing, staff across campuses, central admissions, inter-campus transfers, and local billing. Map legal-entity boundaries before assuming financial consolidation.

CONFIGURATION & GOVERNANCE

Agree the details before rollout.

Define inherited settings, local overrides, group and campus roles, reporting measures, transfer rules, and approval thresholds.

Specify which records remain campus-restricted, when group access is justified, and how delegated administration is reviewed. Consolidated reporting does not require unrestricted access to every learner record.

Discuss security and control

Follow the work from another perspective.

Related institution solutions.

A supported change, step by step.

Select two campuses with meaningful differences. Test shared identifiers, local configuration, delegated access, a transfer, and consolidated reports before adding the rest of the group.

Planning questions for multi-campus school groups.

Must all campuses use identical settings?

Identify a shared core and deliberate local differences. Calendars, curricula, reporting scales, or approval paths may need different treatment.

How should we compare campuses fairly?

Use agreed definitions, comparable periods, and relevant denominators. Review differences in intake, program mix, and operating context before making a decision.

YOUR CONTEXT COMES FIRST

See the journey for multi-campus school groups.

Bring your people, processes, and priorities into the conversation.