Ireland's Regulator Doesn't Grade Your Courses. It Checks Whether Your Course Evaluation Actually Works.

Ireland's higher-education regulator does not read your course-evaluation scores. Quality and Qualifications Ireland (QQI) does not accredit your individual modules, does not rank your programmes, and will never tell you that a 4.2 is good and a 3.6 is a problem. What it does, through its CINNTE cyclical review cycle, is check something far harder to fake: whether your internal quality assurance — including the course evaluation you already run — actually works and actually changes anything.

That shifts the question every Irish institution should be asking. It is not "are our satisfaction scores high?" It is "can we prove our evaluation system leads to action?" If you cannot, high scores will not save you at review, and low scores will not sink you.

What CINNTE is — and what it deliberately is not

CINNTE — the word means "certain" or "definite" in Irish — is QQI's cyclical review cycle for higher education institutions. It rests on a statutory foundation, the Qualifications and Quality Assurance (Education and Training) Act 2012, which gives QQI its mandate for external quality review.

The mechanics follow the internationally recognised model set out in Parts 2 and 3 of the European Standards and Guidelines (ESG 2015): the institution produces a self-evaluation report (the ISER), a team of external reviewers conducts a site visit, a public review report with findings and recommendations is published, and — crucially — a follow-up procedure checks what the institution actually did about those recommendations.

Notice what is absent. There is no external re-marking of student work. There is no programme-by-programme accreditation verdict. There is no league table. As QQI itself frames it, the purpose is "to provide an independent external review of the effectiveness and implementation of a higher education institution's internal QA policies and procedures." The object under review is your system, not your courses.

The consequence nobody puts in the survey RFP

If the regulator reviews the effectiveness of your internal quality assurance, then your course-evaluation process is not a data-collection exercise. It is a piece of evidence about whether your institution can be trusted to assure its own quality.

That reframes what "good" course evaluation means. A system that collects thousands of responses, computes departmental averages, files them, and does nothing is — from a CINNTE standpoint — a failure, no matter how high the averages are. It demonstrates the opposite of what the review is looking for: a closed loop. QQI's own thematic analyses of completed reviews repeatedly flag enhancing student engagement in quality assurance as an area for improvement — a signal that "we send surveys" is not the same as "students shape decisions."

The evidence a cyclical review actually rewards is the evidence of use:

• feedback collected, analysed, and turned into a specific change;
• that change communicated back to the students who raised it ("you said, we did");
• and the whole loop documented well enough that an external reviewer can trace it.

This is the same logic that drives the UK's TEF and Scotland's enhancement-led review, and it is why closing the loop is the part of course evaluation most institutions under-build. The data collection is the easy 20%. The analysis, the action, and the traceable follow-up are the 80% a regulator can see straight through to.

But isn't reviewing the "system" just a softer, vaguer standard?

The reasonable objection: programme accreditation at least produces a hard verdict — pass or fail on defined criteria. Reviewing a "system" sounds like it lets an institution talk its way through with good documentation and management-speak while teaching quietly stagnates.

There is something to this. A process-focused review can be gamed by an institution that is excellent at writing self-evaluation reports and mediocre at teaching. External reviewers see a curated visit, not an ordinary Tuesday. And a well-documented feedback loop on paper is not proof that students experienced change.

But the criticism cuts less deeply than it first appears, for two reasons. First, cyclical review is harder to fake than a one-off accreditation, not easier: it examines the loop over time and follows up on whether recommendations were implemented, so a paper-only system tends to unravel at the follow-up stage. Second, the alternative — a periodic programme-accreditation verdict — creates its own pathology: institutions optimise intensively for the accreditation window and relax between visits. A model that asks "is your internal QA continuously effective?" at least points the incentive at the everyday. The honest position is that neither model guarantees good teaching; the system-review model simply makes it harder to hide a broken evaluation culture behind good scores.

Which is exactly why the quality of the underlying evidence matters so much. A cyclical review can only reward a loop that genuinely closes — and a loop cannot close around evidence too thin to act on.

Where Koji fits: evidence a reviewer can trace

CINNTE asks you to demonstrate that course evaluation leads to action. Most legacy tools make that demonstration almost impossible, because a Likert mean tells you that students were dissatisfied but not what to change — so there is nothing specific to act on, and nothing specific to report back.

Koji for Education is built for the loop the regulator inspects. Its AI-moderated conversational interviews probe beyond the number to the actionable specifics — not "assessment: 3/5" but which assessment, what about it, and when it went wrong — so the analysis stage has something concrete to work with. Automatic thematic analysis turns open-text at scale into named, recurring issues rather than an unread pile of comments. Quality scoring keeps careless and duplicate responses from distorting the picture. Built-in action tracking records the change made in response to a theme, and programme- and institution-level reporting assembles exactly the traceable, "you said, we did" evidence trail an ISER needs — while formative, mid-cycle collection means the loop can close within a term, not across review cycles. Because the AI moderator is standardised and bias-aware, the evidence is consistent across departments, avoiding the human-moderator inconsistency that makes qualitative evidence hard to defend under external scrutiny. As always, Koji surfaces and helps you act on what students say; it does not claim to eliminate bias, and no tool honestly can.

QQI will not grade your courses. It will ask whether you can be trusted to. The institutions that answer confidently are the ones whose evaluation produces evidence a reviewer can follow from student comment to documented change. (Teams that also run staff or general research can use the same interview engine on the main Koji platform.)

Preparing an ISER or building the evidence trail CINNTE looks for? See how Koji for Education makes your feedback loop traceable.

Frequently asked questions

What is a QQI CINNTE review?

CINNTE — "certain" or "definite" in Irish — is Quality and Qualifications Ireland's cyclical review of higher-education institutions. It provides an independent external review of how effectively an institution implements its own internal quality-assurance policies and procedures, under the Qualifications and Quality Assurance (Education and Training) Act 2012.

Does QQI accredit individual courses or rank universities?

No. CINNTE reviews the effectiveness of an institution's internal quality-assurance system, not individual modules, and produces findings and recommendations rather than a ranking or a programme-level accreditation verdict.

What does a CINNTE review process involve?

It follows Parts 2 and 3 of the European Standards and Guidelines: an institutional self-evaluation report (ISER), a site visit by external reviewers, a published review report with findings and recommendations, and a follow-up procedure that checks what the institution actually did about them.

What does this mean for course evaluation?

Because the review examines whether internal QA works, course evaluation must demonstrably lead to action. High satisfaction scores that never produce change are evidence of a failing loop; a documented "you said, we did" trail is what a reviewer rewards.

How does Koji help with CINNTE preparation?

Koji produces the traceable evidence a cyclical review looks for: conversational interviews that yield actionable specifics, thematic analysis of open text at scale, action tracking that records the change made, and reporting that assembles a documented feedback loop for an ISER.