Universitas engagement platform
An internal platform in daily use by the Universitas team. There is no public demonstration of it.
Specified, built and operated by Universitas
We work with quality units, vice rectorates and degree coordinators so that the documentation of each programme has an owner, a place and a review date, and so that the next report starts from what is already recorded.
A bespoke evidence and quality portal for your institution, built around the criteria of the agency that evaluates you. It is delivered as working software, not only as a diagnostic report.
The result we work towards: one evidence map per criterion, with a named owner and a review date for each item, so that preparing a report becomes a review of what already exists instead of a search.
Documents organised by criterion, each with a named owner, a review date and version history.
Who has to review what and by when, with the state of each item visible to the quality unit.
An export of the evidence set for a report or a visit, showing where each item came from and when it was reviewed.
Example of a bespoke solution
The proposed deliverable is a quality portal where each indicator, document and responsible person sits in one place, ready for review. The functional example on the Services page shows that type of solution with fictitious data; it is an example, not a product delivered to a client.
One review or accreditation process and one team. The portal goes live for that scope, with real documentation, before anything is extended.
What we need from you
Acceptance criteria
What already exists and what is built for you
Existing building blocks: Patterns we have already built and operate: structured repositories, review workflows and multilingual content.
Configuration and adaptation, subject to fit: Configuration to your agency criteria and connection to the systems you already use, subject to a technical fit check.
Custom development: The evidence model, roles and exports specific to your institution are developed for this project.
Scope, price and calendar are agreed in writing before the pilot starts, based on the degree chosen, the agency that evaluates it and the state of the documentation we receive. Cost depends on the number of users, the integrations required, data migration, languages and support. The proposal confirms price and calendar before any work begins.
Book a meetingThe agency criterion the institution has to answer
The document or figure that supports it, with its owner
The quality unit validates and records the version
The report is assembled from what is already validated
If the pilot convinces the institution, implementation extends the same structure to the rest of the catalogue, at the pace the teams can absorb.
These are custom developments we can propose, not features already deployed. In all of them a person reviews and approves before anything is used.
A model suggests which criterion each document relates to. The quality unit accepts or corrects the proposal. Nothing enters the file without that step.
Differences between the report, the annexes and the indicator sheets are listed for a person to check, not corrected automatically.
First drafts of descriptive text built only from validated evidence, which the unit then rewrites and signs.
An internal platform in daily use by the Universitas team. There is no public demonstration of it.
Specified, built and operated by Universitas