How to manage campus issues so they don't get lost

The problem: reports arriving from everywhere

On many campuses, the same issue can arrive through four different channels: an email to the porters, a generic web form, a comment at a service desk or a complaint in the institutional suggestions box. Each channel has its own owner and pace, and they rarely meet.

The result is familiar: the person who reported doesn't know whether anyone read it, the maintenance team gets duplicates or reports with no location, and management has no clear picture of which spaces cause the most problems.

What quality frameworks expect

No Spanish national law literally requires a complaints and suggestions box. But the quality frameworks of the university system do expect one:

  • The European ESG 2015 guidelines to standard 1.3 ask institutions to have appropriate procedures for dealing with students' complaints. Standard 1.6 includes physical facilities among the resources that must be adequate and accessible. (ESG 2015)
  • ANECA's AUDIT model guide (2024) includes "management of claims, complaints, suggestions and compliments" in its Criterion 3, and Criterion 5 asks universities to channel stakeholder participation in managing material resources and services.
  • In degree accreditation renewal, ANECA's ACREDITA guide provides for the panel to access the suggestions and complaints box before the visit. (ACREDITA guide)

In other words, having a box is not enough. What a quality system values is being able to show that reports are handled and lead to improvements.

Five keys to a process that works

1. One entry point per space

If each space has its own access point (for example, a QR code on the door of the sports hall or the library), the report arrives with its location. No more "in the second-floor toilets" without knowing which building.

2. A few clear categories

Maintenance, cleaning, safety, accessibility, equipment. With five or six categories, reports reach the right team without anyone forwarding them.

3. No personal data required

Many people won't report if they have to identify themselves. A private reference lets them follow up without giving a name or email, and it also reduces the personal data that must be protected.

4. Visible follow-up for the reporter

A status (received, reviewed, in progress, resolved) and a short reply change perceptions: the community sees that reporting works. The team's internal notes must stay separate.

5. Data by space to make decisions

Counting reports and ratings by space and period shows where problems concentrate and brings data, not impressions, to the quality committee or management. Exporting them to a spreadsheet makes it easy to include them in the quality assurance report.

What about the maintenance system we already have?

Many universities already use a computerised maintenance management system (CMMS) for work orders. A community reporting process does not replace it: it is the public face, where the community reports and where improvements are published. The technical work can stay in the internal tool.

How Universitas Campus solves it

Universitas Campus brings these five keys together: a QR code per space, configurable categories, reports with no personal data required and a private reference, public follow-up and published improvements, and reports by space with CSV export. It costs €250 a month per university, with no setup fee.

You can try the demo with a fictional campus or download the product sheet to share with your team.

Shall we talk for 30 minutes?