Industries · Education
Every campus, one operating picture.
Education groups grow campus by campus, and every campus brings its own stack. We consolidate enrolment, academic and financial data into one governed layer — so the group sees its position during the term, not after it.
Before and after
What changes when
the data finally talks.
Today's friction
- Enrolment pipeline tracked in spreadsheets, campus by campus
- Cohort performance visible only after the term has ended
- Cross-campus consolidation done manually every reporting cycle
- Each campus running a different student and finance system
- Fee collection status lagging weeks behind reality
- Parent and student communication depending on manual follow-up
With Ontilus
- A live enrolment funnel from enquiry to confirmed intake
- Cohort performance visible during the term, when it can still change
- Group consolidation generated continuously, not assembled quarterly
- One governed data layer over every campus system, old or new
- Fee and collection telemetry current to the day
- Automated communication journeys with consent tracked per contact
What we build
Engineered for Education.
Every system is bespoke to your entity structure. These are the modules this sector almost always needs.
Enrolment pipeline
Every enquiry, visit and offer in one funnel — conversion tracked by campus, programme and intake.
Cohort analytics
Attendance, progression and performance by cohort, surfaced while intervention is still possible.
Cross-campus consolidation
Group reporting where every subsidiary runs a different stack — reconciled, not re-keyed.
Fee & finance telemetry
Billing, collection and ageing live across entities, with exceptions routed for follow-up.
Communication journeys
Enrolment nurture, fee reminders and parent updates that fire themselves, on schedule.
Capacity planning
Intake demand against seats, staff and rooms — forecast ahead of the academic year.
Questions
Education,
answered.
The questions operators in this sector ask first. If yours isn't here, ask us directly — we answer scoping questions before there's a contract in sight.
Talk to usWhat can Ontilus consolidate across multiple campuses?
Enrolment pipelines, cohort performance and operational reporting across campuses that run different systems, consolidated into one governed layer so group-level questions have one answer instead of one per campus.
How does enrolment pipeline visibility work?
Every enquiry is tracked from first contact through to enrolment, with stage, source and owner attached. That makes conversion visible by campus, by programme and by intake, instead of only after the intake has closed.
Can it track cohort performance over time?
Yes. Cohort outcomes are tracked across intakes and campuses on consistent definitions, which is what makes a genuine comparison — this intake against last, this campus against another — possible.
Does student data stay isolated between campuses and entities?
Yes. Access is role-scoped by entity and campus, with hard isolation between legal entities and full audit trails. Group reporting is served from governed aggregates rather than by opening one campus's records to another.
Do all campuses have to be on the same student system first?
No. Different systems per campus is the usual starting point. Ontilus integrates through APIs where they exist and sync agents where they do not, and consolidates from there.
Related
Where this shows up
in the work.
The engineering behind this sector, in systems already running and in writing.
How we deploy
Live in 12 weeks.
Proven before it scales.
We pilot on one entity and validate against your own close reports before anything goes group-wide. See the full deployment approach →