Evidence in order, quality monitoring that stays up to date

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.

The technology we deliver

Evidence and quality portal

Custom development

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.

Three modules

01

Evidence repository

Documents organised by criterion, each with a named owner, a review date and version history.

02

Assigned review tasks and status

Who has to review what and by when, with the state of each item visible to the quality unit.

03

Traceable export

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.

First scope

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

  • The criteria or guide of the agency that applies to the selected degree.
  • Access to the documentation of that degree as it is today, in whatever state it is.
  • One contact person in the quality unit and one in the degree coordination.
  • A short session with whoever produces the indicators today.

Acceptance criteria

  • Every criterion of the selected degree appears in the map, with evidence attached or explicitly marked as missing.
  • Each item of evidence has an owner and a review date agreed with the unit.
  • Each indicator sheet names a single data source accepted by the unit that produces it.
  • The quality unit can run the review workflow once, on its own, during the handover session.

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 meeting
The sequence, step by step
  1. 01

    Criterion

    The agency criterion the institution has to answer

  2. 02

    Evidence

    The document or figure that supports it, with its owner

  3. 03

    Review

    The quality unit validates and records the version

  4. 04

    Report

    The report is assembled from what is already validated

If you continue: implementation

If the pilot convinces the institution, implementation extends the same structure to the rest of the catalogue, at the pace the teams can absorb.

  • Extension of the evidence model to the remaining degrees, faculty by faculty.
  • Connection with the systems already in use, where they expose the data.
  • Roles and permissions for quality unit, coordinators and reviewers.
  • Training of the teams and follow up of adoption during the first cycle.
  • Maintenance and the updates that changes in the criteria impose over time.
Example of application

Where artificial intelligence could help

These are custom developments we can propose, not features already deployed. In all of them a person reviews and approves before anything is used.

Proposing a classification of evidence

A model suggests which criterion each document relates to. The quality unit accepts or corrects the proposal. Nothing enters the file without that step.

Flagging inconsistencies before submission

Differences between the report, the annexes and the indicator sheets are listed for a person to check, not corrected automatically.

Drafting descriptive sections

First drafts of descriptive text built only from validated evidence, which the unit then rewrites and signs.

Related references

Internal reference, not for sale

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

Questions we are usually asked

Do we have to change our current systems?
No. The pilot works on the documentation as it is today. Any connection with existing systems is proposed afterwards, and only where those systems expose the data.
Does this guarantee a favourable accreditation result?
No, and we do not present it that way. The decision belongs to the agency. What the work provides is documentation that is organised, traceable and ready for review.
Who owns the result?
The institution. The structure, the documents and the definitions stay with you, and we agree in writing what happens with any tool at the end of the engagement.
Is personal data involved?
Only if the institution decides so. We agree the legal basis and the minimisation measures at the design stage and record them in the project documentation.
All client types

Shall we talk for 30 minutes?

Book a meetingor write to us