Campus management: what a digital university needs

Campus management is the software a university uses to run its core processes in teaching and learning. Historically these were separate systems: one for applications, one for student administration, one for examinations, plus a learning platform for teaching. Every interface between them was a source of errors, every duplicate entry a drain on time.

Modern campus management starts from the lifecycle. A person becomes interested in a programme, applies, is admitted, enrols, takes modules, sits examinations, collects credits and receives a degree certificate. Each step produces data the next step needs. The fewer breaks in between, the fewer queries, errors and delays.

Which building blocks a university needs depends on size, study model and existing systems. A small private university offering distance learning has different priorities from a large campus-based one. The overview below shows the typical areas.

A university is an organisation with clear responsibilities. The examinations office may change grades, a lecturer may only grade their own examinations, a student may only see their own results. A good system models these roles in fine detail and logs sensitive access, for example to application documents or examination files.

When several institutions work on a shared platform — universities in an alliance, or a university with its continuing education academy — tenant separation comes in: each institution sees only its own data, even though the software is the same. That is not optional; it is a precondition for data protection and trust.

Hardly any university replaces everything at once. That is why open standards matter: LTI 1.3 embeds external learning tools securely in a learning platform and can pass grades back. SCORM packages and Common Cartridge carry course content, QTI carries questions, xAPI reports learning events to a learning record store. For sign-in, federated methods such as SAML and OpenID Connect let students use their university account everywhere.

For credentials, interoperability is gaining weight: degree certificates and certificates issued as W3C Verifiable Credentials can be checked automatically by employers and other universities. For exchanging student records between European universities there are dedicated standards that a university should consider when choosing a system.

Introducing a campus management system is an organisational project, not just an IT project. Processes that are cumbersome on paper do not automatically improve when digitised. It works best to clarify processes first — who decides what, with which documents, by when — and only then choose software to fit.

Legal questions are just as important: processing student data is governed by the GDPR and state law; external providers need a data processing agreement under Article 28 GDPR. State universities are required to make their digital services accessible. And where AI is used, for instance in evaluating learning outcomes or in admission, it may be a high-risk system under Annex III point 3 of the AI Act.

Big changes rarely fail because of the software but because of too many changes at once. It works well to start with one building block that brings noticeable benefit quickly — often online applications or digital examination management — and add further blocks once the first runs smoothly. Each new block should build on existing data rather than start a new data store.

Supporting people matters just as much. Staff in the registry and examinations office know the special cases that appear in no specification. Involving them early finds gaps before students find them. Training, an understandable handbook and a reachable help desk in the first semesters decide whether the new solution is accepted.