Features
Solutions
Free tools
Resources

Same platform. Configured for how your institution runs

A university group and a pre-school need different settings, not different software. Programmes, fee structures, timetables, approval chains and permissions change. The student record does not.

Four set-ups. One student record

Pick the shape that matches yours and see what changes. The record stays the same in all four.

A university quadrangle on an autumn morning

Eleven campuses, one set of definitions

One system, a context per campus. Each keeps its own programmes, seat matrix, fee structure and admissions team; the group office sees one combined view where “application” means the same thing everywhere.

StructureCampus → school → department → programme, settings inherited down the tree
AcademicsOwn scheme, calendar and examination rules per campus
FeesCentral policy, local approval; concession chains differ per campus
ReportingGroup dashboards that drill down to campus and programme
Start hereAdmissions across all campuses first, then academics and finance campus by campus

See iVake running on your own data

Share your fee structure and programmes before the call, or sample data with student names removed. We set them up, so you see your own institution on screen rather than a demo account.

  • 45 minutes, your data. Not a generic tour of features.
  • Migration mapped on the call. We show exactly where your current records land.
  • A written rollout plan within two working days, with phases, owners and dates.
  • No pressure to switch everything at once. Most schools and colleges start with one department or one intake.