For multi-campus groups

Central oversight, strict per-campus isolation

Standardize operations across campuses while keeping each institution’s data fully isolated — with consistent reporting and a repeatable onboarding playbook.

A day on the platform

What an ordinary day looks like

  1. 08:30
    Group operations head

    Three campuses, one screen: enrolment, attendance and fee realisation side by side — same definitions everywhere.

  2. 10:00
    Campus principal

    Runs her campus with full autonomy — her data isolated, her policies hers — while reporting stays comparable.

  3. 13:00
    Group IT lead

    Provisions a new campus: its own isolated environment, the group’s standard configuration, live in a day.

  4. 17:00
    Trustees

    The group pack reads the same numbers each campus sees — no reconciliation meeting required.

Before and after

What actually changes

Running on paper & spreadsheetsRunning on ez.school
Each campus on different software, numbers that never reconcileSame platform per campus, same definitions, comparable by construction
One shared database where campuses see each other’s dataStrict per-campus isolation — structural, not policy
Group reporting means spreadsheets emailed monthlyConsistent reporting patterns; consolidated governance on Enterprise
New campus onboarding takes a termProvisioned as its own environment with standard configuration, fast
Group policies drift campus by campusCentral standards with campus-level ownership where it belongs
Case study · Analytics & Insights

From four disconnected reports to one live cockpit

Representative scenario — illustrative

A three-campus group with 3,500 students prepares for its quarterly trustee review the same way every time: a clerk spends three days pulling attendance, results, fees and admissions into a slide deck the night before.

Doing it by hand

By the time the numbers reach the board they are weeks old and nobody can join them — the attendance figure in the deck disagrees with the one the coordinator quotes, and neither traces back to a record. A class group that has been slipping all term is only noticed at result time, when it is too late to intervene. Every hard question in the meeting ends with “we’ll check and revert”.

The cheap-ERP trap

The budget ERP shipped a “dashboard” of pie charts that only counted rows — students enrolled, fees collected — with no cross-module joins and no drill-down. It could not answer “which class group is both under-attending and under-performing”, so the office kept exporting each module to Excel and rebuilding the deck by hand. Six months in, the dashboard was a screenshot in an old email and the three-day scramble was back.

With ez.school

ez.school reads the operational records directly — no export, no stale copy — so the cockpit’s attendance number is the attendance number everywhere. Leadership opens one screen for enrolment trend, attendance by class group, result mix and fee realisation, drills from any figure to the records behind it, and exports the board pack the same way every term. Slipping cohorts surface while the term can still be saved.

The difference, side by side
By handOrdinary ERPez.school
Board prepThree-day manual deckStatic pies, no joinsLive cockpit, export on demand
One numberTwo versions, no sourceCounts rows, no contextSame record, drill to detail
Slipping cohortSeen at result timeInvisible across modulesCross-module, surfaced early
Hard questions“We’ll revert”Number can’t be tracedDrill straight to the record
The outcome
  • LiveFrom the records
  • 3 days → minutesBoard pack prep
  • TraceableEvery figure

The leadership cockpit — enrolment, attendance, results and fees read live from the same records staff work in every day.

Why ez.school

Built for how you operate

Complete campus isolation

Every campus runs on its own isolated database — no data is ever shared between campuses.

Consistent reporting

The same workflows and reports everywhere, so group-level comparisons are apples to apples.

Repeatable onboarding

Bring new campuses live with a guided, standardized sign-up-to-launch flow.

Security by default

Role-based access, activity logs and consent enforced uniformly across the whole group.

Adapts to your curriculum and grading

ez.school does not assume one board or one grading model. Configure scholastic and non-scholastic schemes, grade bands, weightages and result criteria to match how you actually assess — so it fits IB, Cambridge, CBSE, ICSE, state boards and university schemes alike, in your own currency and time zone.

Evaluation questions

Asked by multi-campus groups like yours

Is each campus’s data really separate?

Yes — structurally. Every campus runs as its own isolated environment with dedicated data. Cross-campus access is impossible by construction, not merely forbidden by policy.

How does consolidated reporting work then?

Per-campus reporting follows identical definitions, so numbers are comparable; consolidated group views and governance are part of the Enterprise plan.

Can campuses have different policies?

Yes. Each campus owns its sessions, fee structures and policies. Groups typically standardise the model and let campuses own the parameters.

How fast can we onboard an acquired school?

A new environment provisions quickly with your group’s standard configuration; data migration from its legacy system follows the assisted, parity-verified migration path.

Bring ez.school to your multi-campus groups

A guided walkthrough tailored to your institution, country and student strength.