From Satisfaction to Skills: Mapping Course Evaluation onto Europe's ESCO Taxonomy

Short answer: The typical end-of-module survey measures satisfaction, not skill formation — yet the question European programme directors increasingly have to answer is whether their courses build the competences graduates need in the labour market. The European Commission already maintains a common language for those competences: ESCO, the multilingual classification of European Skills, Competences, Qualifications and Occupations. Mapping your evaluation instrument onto ESCO turns vague "graduate attributes" into measurable, comparable, accreditation-relevant evidence — and it surfaces skills gaps while students can still act on them. This is harder than adding a Likert item, and we will be candid about where it breaks down.

Why satisfaction is the wrong unit

The headline numbers on European graduate outcomes are not flattering to a satisfaction-only model of quality. Cedefop, the EU agency for vocational education and training, estimates that around 29% of the EU adult population experiences a qualification mismatch — mostly overqualification — and that roughly a quarter of tertiary graduates work in jobs below their qualification level. Graduates who finished after the 2008 crisis were nearly twice as likely to be overqualified in their first job as those who graduated in the 1990s. A module can score 4.5 on "I was satisfied with this course" and still leave a cohort short of the competences employers are screening for. Satisfaction and skill formation are different constructs, and only one of them shows up in a graduate's career.

This is the deeper version of an argument we make in beyond satisfaction: measuring skills, not student happiness and course evaluation and graduate employability. The missing ingredient is a shared vocabulary for the skills themselves — so that "communication" in your programme means the same thing as "communication" in a job posting, in an accreditation report, and at the partner university across the border.

What ESCO is, and why it is the right backbone

ESCO is maintained by the European Commission's Directorate-General for Employment, Social Affairs and Inclusion. As of version 1.2 (updated December 2025) it describes 3,039 occupations and 13,939 skills and competences, translated into 28 languages — all official EU languages plus Icelandic, Norwegian, Ukrainian and Arabic. It was built to give education, employment services and employers a single, machine-readable vocabulary so that a skill learned in Lisbon is legible to an employer in Helsinki.

That multilingual, occupation-linked structure is exactly what course evaluation lacks. Recent research demonstrates the mechanism: a 2026 study in Education Sciences mapped a communication-studies curriculum onto ESCO and cross-referenced it against live job-vacancy skill signals, exposing which employer-demanded competences the programme did and did not cultivate. Cedefop's skills-intelligence work does the same at sector scale. If labour-market analysts can map demand to ESCO, programmes can map their evaluation evidence to the same backbone — and finally compare what they teach against what the market rewards in a common currency.

What ESCO-aligned evaluation looks like in practice

The goal is not to bolt 13,939 skills onto a survey. It is to select the handful of ESCO skills each module claims to develop and ask students — and later, graduates and employers — about those specifically:

• Tag each module to a small set of ESCO competences it is designed to build (say, "use data analysis tools," "communicate technical information to non-specialists").
• Evaluate against those tags, not against generic satisfaction. "Did this module improve your ability to communicate technical information to a non-specialist audience?" is answerable and decision-useful in a way that "Was the course well organised?" is not.
• Triangulate across the cycle: students at the end of the module, graduates via tracer studies, and employers in the feedback loop — all speaking the same ESCO vocabulary, so the three perspectives are comparable rather than three disconnected surveys.
• Aggregate to the programme level, where employability actually lives, as we argue in programme-level vs course-level evaluation.

The payoff is evidence that does double duty: it improves teaching and speaks directly to accreditation and quality-assurance bodies, which increasingly expect programmes to demonstrate alignment between intended learning outcomes, delivery, and labour-market relevance.

But critics argue this reduces education to a job-training checklist

This is the strongest objection and it is a good one. Four honest responses:

1. Skills frameworks can be reductive. Mapping a humanities seminar to occupational skill codes risks flattening exactly the critical, creative, and civic capacities that resist tidy classification. The mitigation is to treat ESCO as one lens, not the only one — it includes transversal skills (critical thinking, collaboration) precisely so that programmes are not forced to justify themselves purely in vocational terms. ESCO should augment a programme's educational aims, not overwrite them.

2. Self-reported skill gain is biased. "Did this course improve your skill X?" invites the same self-report and reference-bias problems that dog all evaluation. True. Self-reported competence is a signal, not a measurement — which is why it must be triangulated with graduate destinations and employer judgement rather than trusted alone.

3. Taxonomies drift and oversimplify. ESCO is updated but never current with a fast-moving labour market, and a single occupation can be served by many skill bundles. Use it as a stable shared reference, not as ground truth about any individual graduate's prospects.

4. It can become surveillance-by-metric. Tying every module to skill codes could invite crude ranking. The defence is the same as everywhere in good evaluation: report distributions and themes, not league tables, and keep the purpose formative.

None of these objections argues for going back to a satisfaction score. They argue for using the framework with judgement.

How Koji helps

A static Likert survey cannot really ask whether a student can "communicate technical information to a non-specialist" — it can only ask them to rate it 1–5. Koji's AI-moderated conversational interviews can probe it: when a student claims a module built a competence, the moderator asks for a concrete example of when they applied it, turning a self-rating into evidence. Koji's six structured question types (open-ended, scale, single- and multiple-choice, ranking, yes/no) let you attach ESCO-tagged competences to the right format — ranking which skills a module developed most, or open-ended probing on transfer to practice — and its automatic thematic analysis clusters open-text responses against your competence framework so you can see, across a cohort, which ESCO skills students felt the course built and which it did not. Programme- and institution-level reporting aggregates that to where employability decisions are made, and because the same engine is used for employer and graduate research on the main Koji platform, the student, graduate, and employer voices can be collected against one shared vocabulary. Koji surfaces and standardises the evidence; it does not claim to certify a graduate's skills, and all of it is handled in a GDPR/AVG-compliant, EU-appropriate way.

If your evaluations still stop at satisfaction, ESCO is a ready-made, EU-native way to ask the harder question. Explore how Koji for Education can map your feedback onto the skills that follow students into the labour market.

Why accreditors increasingly expect this

This is not only a labour-market nicety; it is moving toward an accreditation expectation. The European Standards and Guidelines (ESG 2015) ask programmes to design qualifications around intended learning outcomes that reflect societal and labour-market needs, and national agencies increasingly want evidence that those outcomes are actually achieved, not merely declared. A satisfaction score cannot supply that evidence. A competence-tagged evaluation can: it lets a programme show, in the same vocabulary an external reviewer and an employer both understand, which intended skills students report developing and where the gaps sit. Mapping to ESCO also future-proofs the evidence against the EU's wider skills agenda — microcredentials, the European Skills Agenda, and graduate-tracking initiatives all lean on the same shared classification — so the work you do for one accreditation cycle compounds rather than being rebuilt each time the framework shifts.

The bottom line

Europe already has a common language for skills; most course evaluations simply do not speak it. Mapping evaluation onto ESCO will not turn a degree into a training scheme, but it will replace "were you satisfied?" with "what can you now do?" — and give programme directors, accreditors and employers a shared, comparable answer.