New

Now in Claude, ChatGPT, Cursor & more with our MCP server

Back to docs
accreditation12 min

Course Evaluation, Learning Outcomes and the Bologna Process (EHEA)

How to turn course-evaluation data into EHEA accreditation evidence: mapping intended learning outcomes, ECTS workload, the QF-EHEA/Dublin descriptors and ESG 2015 standards to concrete evaluation outputs — with an honest note on when a traditional survey tool is enough.

Koji Education Team

Product

Short answer: In the European Higher Education Area (EHEA), accreditation is built on a small set of shared reference points - intended learning outcomes, the qualifications framework (QF-EHEA and its Dublin descriptors), and ECTS credits that express student workload. The European Standards and Guidelines (ESG 2015) then ask institutions to design programmes around those outcomes and to monitor, periodically, whether the outcomes are actually achieved. Course evaluation is one of the few instruments that lets a programme show the student-side evidence for that: whether the workload matched the ECTS allocation, whether teaching and assessment let students demonstrate the intended outcomes, and whether follow-up action was taken. This guide maps the Bologna reference points to concrete evaluation outputs, and shows where a structured, AI-moderated approach like Koji produces audit-ready, longitudinal evidence - with an honest note on where a traditional survey tool is already enough.

Why the Bologna reference points matter for accreditation

The Bologna Process created a common architecture so that a degree earned in one of the EHEA's participating countries is legible and comparable across the others. Three of its tools do almost all the work that an accreditation panel cares about:

  • Intended learning outcomes (ILOs). Programmes and modules are described not by what is taught but by what a graduate should know, understand and be able to do. Constructive alignment - the idea that teaching activities and assessment should both point at the same stated outcomes - is the pedagogical backbone of this.
  • The Framework for Qualifications of the EHEA (QF-EHEA). The three-cycle structure (bachelor / master / doctorate) is anchored by the Dublin descriptors, which set out generic outcome expectations for each cycle across five dimensions: knowledge and understanding; applying knowledge and understanding; making judgements; communication; and learning skills. National qualifications frameworks reference back to this so that "level" means roughly the same thing everywhere.
  • ECTS credits. In the European Credit Transfer and Accumulation System, one full-time academic year corresponds to 60 ECTS, and one credit conventionally represents 25-30 hours of total student workload. The ECTS Users' Guide 2015 ties credits explicitly to learning outcomes and to estimated student workload - not to contact hours alone.

The ESG 2015 turns these reference points into internal-quality-assurance obligations. Standard 1.2 (Design and approval of programmes) requires that programmes are designed to meet their objectives "including the intended learning outcomes," that the resulting qualification refers to the correct QF-EHEA level, and that programmes "define the expected student workload, e.g. in ECTS." Standard 1.3 (Student-centred learning, teaching and assessment) asks that assessment let students "demonstrate the extent to which the intended learning outcomes have been achieved." Standard 1.9 (On-going monitoring and periodic review) asks institutions to review the workload, progression and completion, and student satisfaction, and to communicate any resulting action "to all those concerned." (Source: ENQA, Standards and Guidelines for Quality Assurance in the EHEA, 2015.)

Read together, these standards make one demand that averages on a Likert survey cannot satisfy on their own: show that the intended outcomes were achievable given the real workload, and that you noticed and acted when they were not.

The evidence gap: what a rating scale cannot tell a panel

Most legacy course-evaluation instruments were built to produce a satisfaction score per instructor. That is useful for a personnel file, but it is weak evidence for an outcomes-and-workload story. A panel reviewing a programme against the ESG typically wants to see three things that a five-point mean does not contain:

  1. Workload reality vs. the ECTS design. A module credited at 5 ECTS assumes roughly 125-150 hours of student effort. If students consistently report double that - or a fraction of it - the credit allocation is mis-specified, which is a genuine Standard 1.2 finding. "Workload was about right (3.8/5)" hides the distribution and the reason.
  2. Whether assessment actually surfaced the outcomes. Standard 1.3 asks whether students could demonstrate the ILOs. That is a qualitative claim about the fit between assessment tasks and outcomes, not a satisfaction number. You need students to explain which outcomes felt untested or unfairly tested.
  3. The closed loop. Standard 1.9 explicitly wants action to be planned, taken, and communicated. The hard part of accreditation is almost never collecting feedback; it is producing a traceable record that a theme led to a change and a later cohort was re-measured.

Mapping Bologna reference points to course-evaluation outputs

The table below maps each reference point to the concrete evaluation output a programme can put in a self-evaluation report, and to how an AI-moderated interview approach differs from a static survey.

Bologna / ESG reference pointWhat the panel wants to seeTraditional SET survey outputAI-moderated evaluation output (e.g. Koji)
Intended learning outcomes (constructive alignment, ESG 1.2/1.3)Evidence students could demonstrate the stated ILOsMean agreement with "the course met its objectives"Probed accounts of which outcomes felt achievable/assessed, coded to each ILO
ECTS workload (ECTS Users' Guide 2015; ESG 1.2)Whether real workload matched the credit allocationSingle workload Likert item, mean onlyFollow-up questions distinguishing overload, front-loading, and mis-estimation, with distribution
QF-EHEA level / Dublin descriptorsOutcomes pitched at the right cycle (e.g. critical judgement at master's)Not typically capturedThematic evidence on depth of judgement, autonomy, and communication demands
Student-centred learning (ESG 1.3)Students took an active role; teaching adaptedFixed items on "engagement"Open, standardized probing of participation and pedagogical fit
On-going monitoring & periodic review (ESG 1.9)Action taken and communicated; re-measurementYear-on-year mean comparisonClosing-the-loop tracker linking theme -> action -> next-cohort re-measure
Public information on outcomes (ESG 1.8)Clear account of what changed and whyManual report writingAuto-generated thematic summaries suitable for a QA report

Where AI-moderated evaluation genuinely helps

Koji shares the same AI interview engine as the main koji.so research platform, adapted for education. Three properties of that approach line up with the Bologna evidence demands:

  • Standardized probing. Every student is asked the same core questions, but the AI moderator can follow up ("you said the workload was heavy - was that the reading, the assessment timing, or the group work?") in a consistent way. That produces comparable, reason-level data on workload and outcomes without a human interviewer introducing variation. It mitigates - it does not eliminate - the interviewer-variance problem that makes qualitative evidence hard to standardize across cohorts.
  • Automatic thematic analysis mapped to outcomes. Instead of a QA officer hand-coding hundreds of free-text comments before a site visit, themes are extracted and can be organized against the programme's stated ILOs and workload design. This shortens the distance between "we collected feedback" and "here is the outcome-level evidence."
  • Longitudinal, closing-the-loop records. Because actions can be logged against themes and re-measured in the next cohort, the platform produces the traceable theme -> action -> effect record that Standard 1.9 asks for, across years, rather than a folder of disconnected annual PDFs.

Frame these precisely: the tool standardizes moderation, automates first-pass analysis, and documents the loop. It does not judge whether your ILOs are pitched at the right QF-EHEA level - that remains an academic judgement for the programme team and the panel.

When a traditional survey tool is enough

Honesty matters with this audience, so here is the counter-case. If your programme's evaluation needs are genuinely served by a few standardized Likert items, your response rates are healthy, and your QA office already has a reliable manual process for coding comments and documenting actions, a mature survey platform (EvaSys, Explorance Blue, Qualtrics) will meet the ESG requirements perfectly well - and several of these tools have deep, long-standing integrations with European student information systems and strong accessibility conformance. AI-moderated evaluation earns its place when open-ended, reason-level evidence is the bottleneck: when panels keep asking "but why was the workload wrong?" and your averages cannot answer, or when hand-coding qualitative comments across many modules and years has become the constraint. Choose the tool that removes your bottleneck, not the one with the longest feature list.

A practical checklist for outcomes-and-workload evidence

  1. Tag every evaluation item to an ILO or to the ECTS workload design so that responses can be aggregated by outcome, not just by instructor.
  2. Capture workload as a distribution and a reason, not a single mean, and compare it against the credited hours.
  3. Ask at least one question that lets students say which outcomes felt untested or unfairly assessed (Standard 1.3 evidence).
  4. Log actions against themes and record the cohort in which each action takes effect.
  5. Re-measure the same theme in the next cycle and keep the before/after pair - that pair is the closed loop.
  6. Write the periodic-review narrative from the thematic summaries, referencing the QF-EHEA level and ECTS design explicitly.

Frequently asked questions

Does the Bologna Process require a specific course-evaluation tool?

No. The Bologna reference points (learning outcomes, the QF-EHEA and ECTS) and the ESG 2015 describe what programmes must demonstrate, not which software to buy. Any tool that lets a programme collect outcome- and workload-relevant feedback, act on it, and document the follow-up can support accreditation. The tool affects how easily you assemble that evidence, not whether it is required.

How do course evaluations provide learning-outcome evidence?

Under ESG Standard 1.3, assessment should let students demonstrate the intended learning outcomes. Evaluation evidence complements assessment data by capturing the student view: which outcomes felt achievable, well taught and fairly assessed, and which did not. Tagging evaluation items to specific outcomes lets you aggregate by outcome rather than only by instructor.

What does ECTS workload have to do with course evaluation?

ECTS credits express estimated student workload - roughly 25 to 30 hours per credit, and 60 credits per full-time year. If students consistently report workload far above or below the credited hours, the allocation is mis-specified, which is a genuine ESG Standard 1.2 finding. Capturing workload as a distribution and a reason, not a single mean, makes this visible.

Which ESG 2015 standards do outcome-and-workload evaluations support?

Most directly Standard 1.2 (design and approval, including intended learning outcomes and expected ECTS workload) and Standard 1.3 (student-centred learning and assessment). Standard 1.9 (on-going monitoring and periodic review) then requires that workload, progression and satisfaction are reviewed and that resulting action is communicated to all concerned.

Is AI-moderated course evaluation GDPR-compliant for EHEA accreditation?

It can be, provided data handling, consent and retention are documented. Because EHEA institutions operate within the EU, GDPR compliance is expected. Koji is built EU-first for this reason; confirm specifics such as data residency and processing terms with any vendor in writing.

Related Resources