Skip to content
ScholaRise § Multi-campus

One trust

Multi-campus.

Many campuses, one set of numbers — each campus kept independent, and the whole trust rolled up from the same records you already run on.

  • Tenant
  • Branch
  • Session
  • Roll-up
§ I One trust

Many campuses, one set of numbers.

Campuses 3, one login Roll-up live Across years kept correct

Rendered in the ScholaRise app palette · figures illustrative — the structure and computed fields are real.

§ II The argument

A trust should not choose between one number and three.

The governance reality

Most trusts that grow past one campus end up with a copy of their software per campus — separate logins, separate numbers, and a finance team that re-keys every campus into a spreadsheet on the last day of the month to find out how the trust actually did. ScholaRise takes the opposite shape: one account, with tenant, branch and academic-session scoping woven through every screen. Each campus stays its own — its students, fees and attendance never silently mixed with a sibling's — while the trust roll-up sums the very same records into one view. The campus number and the trust number are reconciled because they are the same number, read at two altitudes.

What it does
  • One trust, many campuses

    A single ScholaRise account holds every campus under one trust. One login reaches the campuses you're entitled to — no separate instances to license, host or keep in sync.

  • Each campus stays its own

    Branch scoping runs through the whole platform. Students, classes, fees, attendance and reports for one campus stay that campus's — never silently mixed into a sibling's.

  • Cross-campus staff

    A coordinator who works across two campuses is one record with access to both — granted branch by branch, so what they can see and do is decided per campus, not all-or-nothing.

  • Per-branch permissions

    Access is decided per campus and logged. The same person can hold finance rights at one branch and read-only at another — and every grant leaves an audit trail behind it.

  • Trust roll-up reporting

    Read one campus at a time, or all of them at once. The trust roll-up consolidates students, fees and attendance into a single view — same figures, just summed across campuses.

  • Independent fee setup

    Fee heads, terms and gateway credentials are configured per campus. A city campus and a feeder campus charge what each charges — and feeder relationships still link siblings for concessions.

  • Correct across years

    The academic-record model stamps a student's campus, class and section per session. Promote a cohort or transfer a child between campuses, and last year's record stays exactly as it was.

  • One platform, three apps

    Every campus runs on the same web, iOS and Android apps. A trustee switches campuses from a phone; an accountant runs one branch from the desk. The campus switcher is everywhere the data is.

How it fits
  • 01 / 04

    Branch and session are the platform's spine. Every screen already scopes by campus and academic year — multi-campus isn't a bolt-on tier, it's the default everything is built on. One campus or twelve, the integrity rules are identical.

  • 02 / 04

    It reads from the one ledger. The roll-up doesn't re-enter anything. It sums the same fee, attendance and enrolment records each campus already runs on — so the trust number and the campus number are the same number, reconciled by construction.

  • 03 / 04

    It travels on the same web, iOS and Android apps. There's no separate head-office console. A trustee switches campuses from a phone, a branch accountant works one campus from the desk — same login, same data, scoped to what each person may see.

  • 04 / 04

    Within reach of Sol, the AI agent. The assistant that answers questions across the school answers across the trust too — campus-aware, so a question can mean this campus or all of them, without learning a fourth tool.

Where this comes from

We run our own three campuses on one account. The roll-up is how we read our own trust.

Book a demo Available across India
The next step

See ScholaRise in your school.

A real walkthrough with someone who actually runs a school — we'll map what fits your campus today and what's worth phasing in over the next year.

The walkthrough

Length
30 minutes, no slides
Run by
Someone who runs a school
Available
Across India · web, iOS & Android
Module
Multi-campus
Platforms
Web · iOS · Android
Scope
Tenant · Branch · Session
Reporting
Per-campus + roll-up