Industries

Departmental autonomy is the architecture, whether or not it was designed.

Universities run federated systems because faculties are genuinely autonomous. MENTARA works with that structure rather than proposing central control.

Discuss an education priority Read the detail

More in Industries

The sector's actual constraint

Higher education institutions typically operate a student information system, a learning platform, research systems, finance and HR, plus a substantial number of departmental systems adopted independently by faculties with real autonomy over their own operations.

Central IT strategies frequently propose consolidating this. Those proposals rarely succeed, because the autonomy is genuine, is often constitutionally protected, and the faculties have their own funding. An approach that requires centralisation as a precondition will not get past the first committee.

The failure mode

The student experience is fragmented because the institution is.

A student encounters the institution as one organisation and experiences it as a dozen systems with separate logins, inconsistent data and contradictory information about their own status. Each system is reasonable within its department; the aggregate is what the student judges.

Fixing this by consolidating systems is generally not available. What is available is an integration and identity layer that presents coherence over a federated estate — considerably less satisfying architecturally, and far more likely to actually happen.

The second pattern is that funding cycles and academic calendars constrain change more tightly than in most sectors. There are narrow windows when significant change is possible, budget is frequently annual and use-it-or-lose-it, and a programme that misses its window waits a full year. Sequencing around this matters more than in almost any other sector.

Priorities

Where the work usually sits.

01Coherence over a federated estateIntegration and identity that present one institution to students without requiring departmental consolidation.

02Student data and reportingConsistent definitions across departments for statutory returns and internal decisions — usually a definitions problem before a technical one.

03Identity and accessLifecycle across applicants, students, staff, researchers and alumni, including the transitions between them that most systems handle badly.

04Research data and complianceManaging research data with the funder, ethics and retention obligations attached to it.

05Calendar-aware sequencingPlanning delivery around academic and funding cycles, because missing a window costs a year.

06Legacy SIS constraintsAn honest assessment of what the student information system limits before building around assumptions it cannot support.

Questions

What buyers ask.

Do you implement student information or learning platforms?

No, and we hold no partner status with those vendors. We work on integration, identity, data and architecture around them.

Can you work within public procurement rules?

Where an institution is subject to public procurement, the same constraint applies as in the public sector generally: MENTARA is not on framework agreements, which limits direct engagement. Below-threshold work or subcontracting under a prime are the practical routes.

Where MENTARA fits best.

Scope

We fit integration and identity architecture, data definitions, and assessment work sized to a single budget cycle.

Student information system replacement, large platform implementations and framework-based procurement sit outside what we can take on today.

MENTARA was incorporated in July 2026 and has no published client work in this or any sector, so the quality of the thinking on this page — and in a first conversation — is what there is to judge us on.

Where this connects

Services

Workforce model

Permanent Recruitment