When the Accreditor Stops Checking Your Programmes and Starts Checking Whether You Can Be Trusted To

Bottom line: A quiet but decisive shift is running through European quality assurance. Instead of accrediting every programme one by one, systems in Germany, the Netherlands and elsewhere increasingly assess whether a university's own internal quality-assurance system is trustworthy enough to be handed that job. Pass, and you accredit your own programmes for years at a time. The consequence is under-appreciated by evaluation teams: under institutional or system accreditation, your course evaluation loop stops being a routine chore and becomes the load-bearing evidence that your internal QA actually works. An auditor is no longer asking "is this programme good?" They are asking "does your feedback machinery reliably detect problems and fix them?" A satisfaction mean that lands in a spreadsheet nobody reads is not neutral in that conversation — it is the exact failure the model exists to find.

What institutional and system accreditation actually change

In the older, programme-by-programme model, an external panel inspects each degree and awards a seal. In the newer model, the external check moves up a level to the institution's quality management itself.

In Germany, system accreditation (Systemakkreditierung) makes the subject of assessment "the internal quality assurance system" of the higher education institution. A university that secures it — valid for eight years — earns the right to award the Accreditation Council's seal to its own self-assessed study programmes. Crucially, the accreditor requires that the quality-management system provides for regular evaluations of study programmes and the teaching-and-learning areas, involving students, external academic experts, representatives of professional practice, and graduates. Feedback is not an optional extra in that model; it is a named component of the thing being certified.

The Netherlands runs a parallel logic. Its institutional quality assurance assessment (instellingstoets kwaliteitszorg, ITK), operating under the 2018 Accreditation in Moderation Act (Wet accreditatie op maat), is a periodic external assessment of the internal quality assurance in place at an institution. A positive ITK decision earns a lighter-touch, limited framework for subsequent programme assessments. NVAO frames the central question sharply: how does the institution — and every organisational level within it — "work cyclically, sustainably, and collaboratively on the assurance, improvement, and development of its teaching?" That word cyclically is the whole game: it is the closed feedback loop, and it is what the panel comes to verify.

Both models rest on the European Standards and Guidelines (ESG) Part 1, which put internal quality assurance — ongoing monitoring, periodic review, and acting on what you find — at the centre of what a trustworthy institution does. When accreditation certifies your system, ESG Part 1 stops being aspirational language and becomes the audit checklist.

Why this makes course evaluation the load-bearing evidence

Under programme accreditation, weak evaluation could hide. A panel focused on curriculum content and staffing might never stress-test whether your feedback loop closes. Under institutional or system accreditation, that loop is precisely what is on trial. The auditor's questions change in kind:

• Not "what did students say?" but "how do you know what students said, across the institution, reliably enough to act on?"
• Not "is this module rated highly?" but "when a module rates poorly, what happens next, who owns it, and can you show us the case history?"
• Not "do you run surveys?" but "does your evaluation system detect problems early enough to fix them, and can you evidence the fix?"

A satisfaction mean answers none of these. Worse, a pile of unread means is affirmative evidence against you: it demonstrates collection without closure — the appearance of a quality loop with no actual loop. This is why the ESG-facing critique of thin feedback matters more, not less, under system accreditation, and why the statistical weakness of averaging Likert scores becomes a governance liability rather than a methodological footnote. The regulator has stopped grading your programmes and started grading your capacity to grade your own — and a broken feedback instrument is the most visible crack in that capacity.

"But this is just more bureaucracy" — the counterargument

A reasonable objection from a sceptical dean: system accreditation is a compliance burden that rewards documentation over teaching, and building an elaborate feedback apparatus to satisfy an auditor is exactly the box-ticking that gives quality assurance a bad name. Won't this just generate more forms?

It can — if you build the apparatus for the auditor. But the deeper point cuts the other way. The institutional model is, at its best, an attempt to stop treating quality as an external inspection to be survived and start treating it as something the institution genuinely owns. The NVAO framing — cyclical, sustainable, collaborative — describes a quality culture, not a filing system. An evaluation loop that actually detects a struggling cohort in week five and fixes the problem is not bureaucracy; it is the point. The failure mode the sceptic rightly fears — feedback collected to be filed, never acted on — is the same failure the accreditor is hunting. Done honestly, satisfying the model and improving teaching are the same task. The bureaucracy appears only when you fake the loop instead of closing it, and a faked loop is what an experienced peer panel is trained to spot. The constructive move is to make evaluation genuinely formative and to treat students as partners in the loop rather than as data sources.

What a system-accreditation-ready evaluation loop looks like

• Closure you can evidence. For a sample of problems, be able to show the whole arc: signal detected → owner assigned → action taken → re-measured. The case history is the artefact the panel wants.
• Reliable, institution-wide collection. Idiosyncratic, faculty-by-faculty survey designs undermine the claim that you systematically monitor quality. Consistency is itself evidence.
• Timeliness. A loop that only closes annually cannot demonstrate that you "detect problems early enough to fix them." Formative, mid-cycle collection is the difference between monitoring and post-mortem.
• Genuine multi-voice input. German system accreditation explicitly expects students, external experts, professional-practice representatives and graduates in the loop — so triangulate rather than relying on one survey.
• Analysis that surfaces patterns. An auditor assessing a system wants institution-level and programme-level trends, not a shoebox of module means.

Where Koji fits

Koji is built to make the loop the accreditor is looking for both real and demonstrable. Its AI-moderated conversational interviews produce richer signal than a rating — probing why a cohort is struggling so the "action taken" step is targeted rather than guessed. Automatic thematic analysis turns institution-wide open-text into the programme- and institution-level patterns a system audit expects, instead of unread comment boxes. Six structured question types give you consistent, comparable instruments across faculties — the standardisation that itself evidences a system. Formative, mid-cycle collection lets you show problems caught early; closing-the-loop action tracking produces the exact detected-to-resolved case histories a panel asks for; and programme- and institution-level reporting speaks to an auditor assessing the whole. Because the AI moderator is standardised and bias-aware, "we systematically monitor quality" stops being a claim and becomes something you can put on the table, and the platform is built for GDPR/AVG-compliant data handling.

Koji does not accredit you, and it does not replace the professional judgement of a peer panel — nor should it. What it does is turn your course evaluation from the weakest link in a system-accreditation case into demonstrable evidence that your internal quality assurance genuinely closes the loop. The same conversational interview engine powers the main Koji platform for general user and stakeholder research, which quality units also use to consult staff and external stakeholders as part of the same evidence base.

Frequently asked questions

What is the difference between programme accreditation and institutional or system accreditation? Programme accreditation inspects each degree individually. Institutional or system accreditation instead assesses whether the university's own internal quality-assurance system is trustworthy; if it is, the institution accredits its own programmes under a lighter external framework.

What is German system accreditation (Systemakkreditierung)? It is an accreditation of a university's internal quality-assurance system, valid for eight years, that grants the right to award the Accreditation Council's seal to the institution's own self-assessed programmes. It requires the QA system to include regular programme evaluations involving students, external experts, professional-practice representatives and graduates.

What is the Dutch instellingstoets kwaliteitszorg (ITK)? It is a periodic external assessment of an institution's internal quality assurance under the 2018 Accreditation in Moderation Act. A positive outcome earns a lighter-touch, limited framework for subsequent programme assessments; the central question is whether the institution works cyclically, sustainably and collaboratively on its teaching quality.

Why does this shift make course evaluation more important? Because the accreditor is now assessing your feedback loop itself, not just your programmes. An evaluation system that collects data but never acts on it is direct evidence that your internal quality assurance does not close the loop — exactly the failure the model is designed to catch.

Does building this loop just mean more bureaucracy? Only if you build it for the auditor. A loop that genuinely detects and fixes problems is the point of the model; the failure the accreditor hunts — feedback filed and never acted on — is the same failure that makes evaluation feel like box-ticking. Done honestly, satisfying the model and improving teaching are the same task.

---

When the accreditor certifies your system, your feedback loop is the evidence. See how Koji for Education helps you build a course evaluation loop you can put in front of a peer panel.