One operating system across every campus.

Leadership dashboards, campus autonomy, and consistent admissions and finance workflows.

Many campuses, one governance layer

Groups need shared policy, reporting, and audit visibility—not HQ overriding each campus’s calendar, currency, or assessment rules. RunMyCampus keeps local execution on every campus while leadership sees the network clearly.

Who owns what

Groups need a shared standard without overriding each campus. The line between the two is set up front.

The group sets and sees

  • Grading templates and fee rules rolled out to campuses
  • Enrolment, attendance and revenue roll-ups across entities
  • Audit-ready exports and administrative logs
  • Staff and family identity that moves across campuses

Each campus keeps

  • Daily operations
  • Its own academic calendar
  • Its own currency and fee collection
  • Its own portals and branding

What teams do with it

  1. Central policy, local execution

    Roll out grading templates and fee rules while campuses retain daily operations.

  2. Roll-ups leadership need

    Enrollment, attendance, and revenue visibility across entities.

  3. Unified identity

    Staff and families move across campuses without duplicate profiles.

How you move over

  1. Define hierarchy
  2. Import each campus
  3. Validate cross-campus reporting

How Migration Cloud imports an export →

Ready for the next step?

See the platform with your roles and campuses in mind. Read what the trust center publishes →