Course Evaluation Evidence for Euro-Inf (Informatics & Computing) Accreditation

Euro-Inf is the pan-European quality label for informatics and computing degree programmes, administered by the European Quality Assurance Network for Informatics Education (EQANIE) and awarded through authorised national agencies (for example ASIIN in Germany, which also hosts the EQANIE secretariat in Düsseldorf). For computing faculties, Euro-Inf sits alongside national institutional accreditation as a discipline-specific mark of quality — and, because "where Informatics is indicated, Computing is also understood," it covers computer science, software engineering, information systems and related programmes. This guide explains exactly how student course-evaluation data becomes credible Euro-Inf evidence — and, honestly, where it does not.

Answer first: the Euro-Inf Framework Standards and Accreditation Criteria contain two sets of criteria — a set of five General Criteria and a set of six Programme Outcome categories. Course-evaluation evidence belongs mainly under General Criterion 5, Quality Management, which requires that students are involved in quality assurance, that programmes are regularly monitored and reviewed, and that survey results are fed back into programme development. Course evaluation does not, by itself, prove that students attained the programme outcomes — that requires outcome-based assessment evidence. Used correctly, course evaluation is the engine of your continuous-improvement narrative; used as a proxy for outcome attainment, it weakens your self-assessment report.

How the Euro-Inf framework is structured

Developed within the Euro-Inf Project and aligned throughout with the Standards and Guidelines for Quality Assurance in the EHEA (ESG 2015), the framework describes an accredited informatics programme in two parts.

A. The five General Criteria (valid for both First and Second Cycle degrees):

1. Programme Design and Development — learning outcomes, labour-market/stakeholder needs, curriculum.
2. Programme Management and Implementation — admission, workload and ECTS, teaching methods/didactic concept, assessment.
3. Resources — academic staff, student support, facilities and finance.
4. Programme Information and Transparency — rules and regulations, certification and documentation.
5. Quality Management — the QM policy and programme monitoring and review.

B. The six Programme Outcome categories (the subject-specific learning outcomes an informatics graduate must attain):

• Underlying Conceptual Basis for Informatics
• Analysis
• Design and Implementation
• Economic, Legal, Social, Ethical and Environmental context
• Informatics Practice
• Other Professional Competences

Keep these two halves separate in your mind. The General Criteria ask whether your quality system works. The Programme Outcomes ask whether your graduates can actually do informatics. Course evaluation is strong evidence for the first and irrelevant to the second.

Where student course feedback fits

Under Euro-Inf, student feedback appears in two distinct ways.

1. As the core of Criterion 5, Quality Management

This is the home of course-evaluation evidence. Two sub-criteria matter most:

• 5.1 QM-Policy (mapped to ESG 1.1). The framework requires that "quality management policies are in place… All relevant stakeholders, in particular students, are involved in the quality assurance activities" and that "the results of quality management activities are communicated back to the relevant stakeholders." Reviewers are directed to ask, literally, "What feedback loops exist?" and "Do stakeholders consider that improvements have been made?"
• 5.2 Programme monitoring and review (mapped to ESG 1.1 and 1.9). Programmes must be "regularly monitored, reviewed and updated," considering (among other things) the needs of stakeholders and the effectiveness of teaching and assessment. The self-assessment prompt is explicit: "To what extent are results from surveys and analysis fed back into programme development activities?" — and the suggested evidence is "quantitative and qualitative statistical data from evaluations."

That single phrase — qualitative statistical data from evaluations — is the whole game. A Euro-Inf panel is not impressed by a dashboard of satisfaction scores; it wants to see that student feedback is collected, genuinely analysed (including the open text), and demonstrably fed back into decisions.

2. As the "student view" running through Criteria 2 and 3

Euro-Inf repeatedly asks how students and staff view specific aspects of the programme, and lists "results from internal quality assurance activities" as evidence:

• 2.3 Teaching Methods / Didactic Concept — "How is it ensured that all staff members use a student-centred teaching approach?"
• 2.4 Assessment — "How are exam types and exam organisation viewed by students and staff?"
• 3.2 Student Support — "How is the support viewed by the students and staff?"
• 3.3 Facilities — "How do students and staff view the facilities available?"

Well-structured course evaluation feeds all four. This is why a tool that captures why — not just a 1–5 rating — is worth more at accreditation: it produces usable evidence for teaching, assessment, support and facilities in a single instrument.

What course evaluation does NOT prove

Here is the honest boundary. The six Programme Outcome categories — a graduate's ability to analyse, to design and implement, to reason about the legal/ethical/environmental context, and so on — are demonstrated through outcome-based assessment: examinations, programming projects, capstones, theses and rubrics mapped to the Euro-Inf Objectives-Module-Matrix. How students rated a module tells a panel nothing about whether they attained these outcomes. Conflating "students were satisfied with Databases" with "students attained the Design and Implementation outcomes" is one of the most common weaknesses in a self-assessment report. Treat outcome attainment and course evaluation as two separate, complementary evidence streams.

Criterion-to-output mapping

Euro-Inf expectation	Concrete evaluation output	What it evidences
5.1 Students involved in QA; results communicated back	Termly evaluation with a documented "you said / we did" report to students	An active, visible feedback loop
5.1 "What feedback loops exist?"	Standardised, bias-aware instrument applied across all modules	A systematic (not ad-hoc) QA process
5.2 Surveys fed back into programme development	Action log linking findings → changes → later-cohort results	Closing the loop, demonstrably
5.2 "Qualitative statistical data from evaluations"	Automatic thematic analysis of open text with ranked themes and quotes	Credible qualitative evidence at scale
2.3 / 2.4 Teaching & assessment viewed by students	Module-level feedback on teaching approach and assessment	Student-centred learning (ESG 1.3)
3.2 / 3.3 Support & facilities viewed by students	Items/themes on support services and computing facilities	Fitness of resources
Longitudinal monitoring	Cohort-over-cohort trend reporting	Sustained improvement, not a one-off
GDPR / data handling	EU data residency, anonymity thresholds, retention controls	Defensible processing of student data

Closing the loop — the artefact that wins

For Euro-Inf, "closing the loop" means showing the chain from finding to action to result: student feedback identified an issue, the programme made a documented change, and a later cohort shows the effect. The practical artefact reviewers look for is an action log that links each significant finding to a decision and to a subsequent outcome. A table of averages cannot show this; a maintained record of what changed because of feedback can.

How Koji helps with Euro-Inf Quality Management evidence

Koji runs AI-moderated student interviews each term with consistent, bias-aware moderation, probes answers in the moment to capture why, performs thematic analysis automatically across all responses, reports longitudinally across cohorts, and tracks closing-the-loop actions in an audit-friendly form — with EU-focused data handling. For an informatics faculty preparing a Euro-Inf self-assessment, that maps directly onto Criterion 5: it produces the "qualitative statistical data from evaluations" the framework asks for, and the documented feedback loop that 5.1 and 5.2 demand. The same AI interview engine powers customer and user research on the main Koji platform (koji.so).

The honest limit: Koji strengthens your Quality Management and student-view evidence. It does not measure programme-outcome attainment and is not a substitute for outcome-based assessment of the six Euro-Inf outcome categories. Present it as the engine of your continuous-improvement narrative, not as proof that graduates can design and implement systems.

When existing tools or manual processes may suffice

If your programme is small, you already read every open comment by hand, and your action log is genuinely maintained, a simple survey tool plus disciplined follow-up can satisfy Criterion 5 — the framework rewards a functioning loop, not a particular vendor. The case for a conversational, analysis-automating tool grows with scale (many modules, hundreds of responses, multiple languages) and with how much your current comments go unread. Choose the lightest process that produces credible, closed-loop evidence.

Related Resources

• Course Evaluation Evidence for EUR-ACE Engineering Accreditation — the engineering sibling of this guide (ENAEE).
• Student Feedback as ESG Accreditation Evidence — the ESG foundations Euro-Inf builds on.
• Course Evaluation Evidence for ASIIN Accreditation — the agency that hosts EQANIE and awards Euro-Inf in Germany.
• Closing the Feedback Loop: Course Evaluation Evidence — building the action log reviewers look for.
• Course Evaluation Evidence for German Accreditation — the national context for many informatics programmes.

Frequently asked questions

Does course evaluation count as evidence of Euro-Inf programme outcomes? No. The six Euro-Inf Programme Outcome categories (Underlying Conceptual Basis, Analysis, Design and Implementation, the Economic/Legal/Social/Ethical/Environmental context, Informatics Practice, and Other Professional Competences) are demonstrated through outcome-based assessment — examinations, programming projects, capstones and rubrics — not through how students rated a module. Course evaluation evidences the Quality Management criterion (student involvement, monitoring, closing the loop). Conflating the two is a common weakness in self-assessment reports.

Where does student course feedback fit in a Euro-Inf accreditation? Mainly under General Criterion 5, Quality Management. Euro-Inf expects students to be involved in quality assurance, programmes to be regularly monitored and reviewed, and survey results to be fed back into programme development. Course-evaluation data — especially rich qualitative evidence with a visible action trail — is direct evidence that this loop functions. Student feedback also supports the "student view" prompts under teaching (2.3), assessment (2.4), support (3.2) and facilities (3.3).

What does 'closing the loop' mean for Euro-Inf? Showing the chain from finding to action to result: feedback identified an issue, the programme made a documented change, and a later cohort shows the effect. An action log linking findings to changes to subsequent results is the practical artefact reviewers look for under Criterion 5.

How does Koji help with Euro-Inf Quality Management evidence? Koji runs AI-moderated student interviews with consistent, bias-aware moderation, probes answers in the moment, performs thematic analysis automatically, reports longitudinally across cohorts, and tracks closing-the-loop actions — with EU-focused data handling. It produces the "qualitative statistical data from evaluations" the framework requests and documents the feedback loop, but it does not measure programme-outcome attainment or replace outcome-based assessment.

Is numeric satisfaction data enough for a Euro-Inf accreditation visit? No. Numeric satisfaction scores show sentiment, not learning, and are vulnerable to known biases. Euro-Inf reviewers want a systematic, documented loop: standardised collection, credible qualitative evidence, longitudinal trends, and an action trail — and, separately, outcome-based evidence that students attain the six programme outcomes.