Industry OS & Portals · Education

School portal development for campus groups

Schools rarely need a new student information system invented from scratch. They need the records, academics, fees, and family communication that already exist on paper and in spreadsheets to live in portals each role can log into.

What we walk into

The state of play in education

  • Attendance in one spreadsheet, fees in another, results in a third — and no single view of a student
  • Fee reminders sent by hand over WhatsApp, with no record of who was told what
  • Every campus in a group running a slightly different process and file format
  • Teachers entering the same marks twice because the report card lives outside the records system

Outcomes

What changes

  • School Management OS
  • Ops portals
  • Play Store family apps

Broader sector context lives on Education software, and the full engagement is described on Industry OS & Portals.

Scope

What the build covers

Role-based portals

Separate surfaces for owners, admin staff, teachers, parents, and students, each scoped to what that role is allowed to see and change.

SIS as the spine

Students, guardians, staff, classes, and sections modelled once on Edument.app, so attendance, exams, and fees all read the same records.

Fee operations

Vouchers, due dates, partial payments, and notices delivered as email PDFs and WhatsApp messages with a trail of what was sent.

Migration from spreadsheets

Existing student, guardian, and fee history imported and reconciled before go-live, so last term's numbers still add up.

Rollout

How it sequences

  1. 01

    Records first

    Import students, guardians, staff, and the current fee ledger. Nothing else works until the records are trusted.

  2. 02

    Staff before families

    Admin and teaching staff go live on attendance, marks, and fees for a term while parents stay on existing channels.

  3. 03

    Open the family portal

    Parents and students get access once the data they would see is already correct — which is what stops the support queue forming.

FAQ

Questions buyers ask first

Do we have to replace our current system in one go?

No. We start with records and one operational area — usually attendance or fees — and add modules per term. Running the old process alongside for the first cycle is normal and expected.

Can each campus keep its own branding and rules?

Yes. A group runs one tenant per campus with shared student and staff models, so head office reports across all of them while each campus keeps its own theme, fee structure, and timetable.

What about the parent mobile app?

That is a separate track. Families adopt the app far better once staff operations are live, so we sequence it after the portals — see school app development for how that build runs.

Find your Industry OS

Tell us how your education operation runs today and we will scope the first release.

Start project