Course Evaluation Evidence for Italian Accreditation (ANVUR AVA & OPIS)

In one line: In Italy, collecting students'' opinions on their courses is not optional — it is required by law and is a necessary condition for periodic accreditation. ANVUR''s AVA system expects you to run the student opinion survey (OPIS), feed the results into the programme''s quality documents, have the Joint Teacher-Student Committee scrutinise them, and act on what they reveal. Course evaluations are the most direct evidence you have for that expectation — provided they are standardised, well-documented, and tied to a closed quality loop. This guide maps the Italian requirements to concrete outputs and shows where conversational, AI-moderated evaluation strengthens the evidence.

This is a buyer''s and practitioner''s guide for Presidi della Qualità, Nuclei di Valutazione, coordinatori di corso di studio, and quality offices at Italian higher-education institutions. It is vendor-aware but framework-first.

The Italian accreditation framework in brief

Italy''s quality-assurance system is called AVA — Autovalutazione, Valutazione periodica, Accreditamento (Self-assessment, Periodic evaluation, Accreditation) — and is administered by ANVUR (Agenzia Nazionale di Valutazione del Sistema Universitario e della Ricerca). The current model is AVA 3, whose guidelines for the periodic accreditation of institutions and study programmes were issued by ANVUR and align with the evaluation areas of Ministerial Decree DM 1154/2021. The system is aligned with the European Standards and Guidelines for Quality Assurance (ESG 2015); ANVUR is an ENQA member and EQAR-registered.

The collection of attending students'' opinions is mandated by Article 1, paragraph 2 of Law 370/1999, and the reform initiated by Law 240/2010 made the student opinion survey a necessary requirement for the purposes of periodic accreditation of both universities and study programmes. In other words, OPIS is not a nice-to-have you bolt on for the site visit — without it, a programme is not accreditable.

Accreditation works on two levels:

• Accreditamento iniziale — initial accreditation of a new programme or campus against minimum requirements.
• Accreditamento periodico — periodic accreditation (typically on a multi-year cycle) in which a CEV (Commissione di Esperti della Valutazione, including at least one student evaluator) conducts a documentary review and a site visit, assessing the institution and a sample of programmes against ANVUR''s quality requirements.

Who does what: the AVA actors

Italian QA distributes evaluation responsibilities across defined bodies, and the evidence chain runs through all of them:

• Presidio della Qualità di Ateneo (PQA) — the institution''s quality-assurance presidium, which organises and oversees OPIS administration and ensures the data flows into the right documents.
• Commissione Paritetica Docenti-Studenti (CPDS) — the Joint Teacher-Student Committee, which examines OPIS results and the programme''s quality documents and produces an annual report (Relazione Annuale) flagging strengths and critical issues. This committee is where the student voice is formally weighed.
• Nucleo di Valutazione (NdV) — the internal evaluation board, which reports annually to ANVUR on the effectiveness of the QA system, including how student opinions are collected and used.
• Corso di Studio (CdS) — the programme itself, responsible for drafting the SUA-CdS, the Scheda di Monitoraggio Annuale (SMA), and the Rapporto di Riesame Ciclico (RRC).

Where course evaluation evidence is required

Several AVA artefacts are difficult to complete credibly without robust OPIS data:

• OPIS (rilevazione delle opinioni degli studenti). The questionnaire must include the core questions ANVUR defines in its operational sheets (Schede 1 and 3), administered to attending students. This is the raw evidence base.
• SUA-CdS (Scheda Unica Annuale del Corso di Studio). The annual programme card, whose quality-management section reports on student opinions (historically section B6) and graduate opinions (B7). OPIS results are summarised and commented here.
• CPDS annual report. The Joint Committee must analyse student opinions and the adequacy of how the programme monitors and improves teaching — a task that depends on the interpretability of the OPIS data, not just its existence.
• SMA (Scheda di Monitoraggio Annuale). A short, critical commentary on ANVUR''s quantitative indicators (student careers, attractiveness, internationalisation, graduate employability, satisfaction). Evaluation evidence contextualises the numbers.
• RRC (Rapporto di Riesame Ciclico). The Cyclical Review covers the whole training project across a student cohort''s path, is built on the R3 quality requirements, and must state problems and the solutions to be implemented in the next cycle. This is where closing the loop is documented.

ANVUR''s R3 requirement and the quality loop

The requirement most directly tied to course evaluation is R3 — Qualità dei Corsi di Studio (quality of study programmes). Its sub-dimensions move from defining the educational demand, through the design of the student learning experience, to resources, and crucially to R3.D — monitoring and review: the programme must show that it systematically monitors itself, identifies critical issues, and revises accordingly. OPIS sits at the heart of R3.D, because student opinion is the most direct signal of the experienced quality of teaching — and the CEV will look for evidence that the signal led to action.

Mapping requirements to concrete Koji outputs

The table below maps common AVA expectations to evidence artefacts. The left column is framework-neutral; the right shows what a modern, conversational evaluation tool produces. Traditional survey tools can satisfy much of the left column too — the difference is depth, standardisation, and how directly the evidence closes the loop.

AVA / ANVUR expectation	Concrete evidence needed	Koji output
OPIS collected for all attending students (Law 370/1999)	Standardised survey run consistently across courses and cohorts	Standardised, repeatable AI-moderated interviews per course, run every term
Interpretable student opinion for the CPDS report	Specifics behind the ratings, not one-line comments	Probed responses themed with representative quotes and prevalence
SUA-CdS quality section (student opinions)	A clear, commentable summary of what students said	Auto-generated thematic summaries, exportable for the SUA-CdS
R3.D monitoring and review	Evidence the programme identifies and acts on critical issues	Action tracking linking themes to interventions
Cyclical Review (RRC) closing the loop	Proof that problems led to solutions and were re-checked	Longitudinal re-evaluation across the cohort''s path
Periodic accreditation site visit (CEV)	Comparable, audit-ready evidence across years and programmes	Standardised cohort reporting with consistent instruments

Why conversational evaluation strengthens the Italian file

The recurring weakness CEVs find is rarely the absence of OPIS — administration is mandatory, so the survey almost always exists. The weakness is the gap between collecting opinions and demonstrably acting on them, and the thinness of the qualitative signal the CPDS has to work with. Two structural problems make that link hard with traditional Likert-only instruments:

1. Thin, ambiguous comments. A low score on "il carico di studio è accettabile" tells the CPDS something is wrong but not what to change. Koji''s AI moderator asks a neutral, standardised follow-up — which assessments, at which point in the semester, and what would have helped — turning a complaint into an actionable, citable finding that maps directly onto R3.D.
2. Standardisation gaps. Because every Koji interview applies the same probing logic to every student, the evidence is comparable across cohorts and years — exactly the longitudinal picture the Cyclical Review and the periodic-accreditation CEV ask for, and far harder to assemble from free-form comment boxes.

Koji also supports formative (mid-semester) collection, not only end-of-course OPIS, so you can document a genuine improvement cycle within an accreditation period rather than a single annual snapshot. Mid-course consultation is one of the better-evidenced ways to actually improve teaching — see mid-semester feedback and consultation.

Koji runs EU-first with GDPR-aligned data handling, on the same AI interview engine as the main Koji platform used for customer and user research — relevant when your Responsabile della Protezione dei Dati (DPO) reviews processing terms.

When a traditional tool is the better choice

Be honest with the CEV and with yourself. The OPIS questionnaire defined by ANVUR is a fixed, numeric instrument by design, and you must run it regardless of vendor. If your immediate gap is simply administering the mandated ANVUR questions at institutional scale, producing the standard numeric indicators, or feeding a central dashboard, an established survey platform (EvaSys, Explorance Blue, Qualtrics) — or even your existing tooling — may be the pragmatic fit, and many Italian atenei already run one. Conversational evaluation earns its place where qualitative depth and a demonstrable closed loop are the weak points in your AVA file — typically the Cyclical Review, programmes flagged by the CPDS, and the R3.D narrative for the site visit. A hybrid model — incumbent for the mandated OPIS battery, Koji for depth on priority programmes — is often the realistic path.

A practical checklist for Italian QA teams

• Confirm OPIS is administered to all attending students with the ANVUR-defined questions, and that response rates are documented.
• Verify the data flow: OPIS → SUA-CdS quality section → CPDS annual report → SMA → Cyclical Review.
• Identify where the CEV is most likely to probe: R3.D monitoring and review, and evidence that feedback led to change.
• For priority programmes, add probed, standardised evaluation that produces traceable themes and action items the CPDS can cite.
• Document the loop end to end: opinion → CPDS observation → CdS decision → change → re-evaluation.
• Keep exports audit-ready for the periodic-accreditation documentary review and site visit.

Related Resources

• Turning Student Feedback into ESG / ENQA Accreditation Evidence
• Turning Course Evaluations into NVAO Accreditation Evidence (Netherlands & Flanders)
• Course Evaluation Evidence for German Accreditation (Programm- & Systemakkreditierung)
• Course Evaluation Evidence for the UK TEF and QAA Quality Review
• How Many Responses Do You Need for a Reliable Course Evaluation?

Sources: ANVUR (Agenzia Nazionale di Valutazione del Sistema Universitario e della Ricerca); Law 370/1999 art. 1 c. 2; Law 240/2010; AVA 3 accreditation guidelines and Ministerial Decree DM 1154/2021. Verify the current AVA 3 documents and your atene''s specific procedures, as ANVUR updates the model and operational sheets periodically.

Common reviewer questions — and how evidence answers them

Periodic-accreditation CEVs and your own Nucleo di Valutazione tend to probe the same pressure points. Preparing answers backed by evaluation evidence is what turns a self-assessment from a description into a demonstration.

• "Show us that student opinion led to a change." Reviewers know OPIS is mandatory; they doubt the loop closes. Have at least two worked examples per priority programme where a documented theme produced a concrete change (a reworked assessment calendar, a restructured module) and a subsequent re-evaluation confirmed the effect. This is the single most persuasive artefact for R3.D.
• "How does the CPDS use the data?" Show that the Joint Committee''s annual report cites specific, interpretable findings — not just average scores — and that its observations were taken up by the programme.
• "Is workload realistic?" Point to probed feedback on assessment timing and density, not just an average on a workload item. Evidence that names which deadlines clustered and when students struggled answers the question directly.
• "Is your quality system effective over time?" Show comparable, longitudinal data across cohorts and programmes, with consistent instruments, so the panel sees trends rather than isolated annual snapshots.

Documentation tips for the self-assessment

Keep evaluation evidence audit-ready year-round rather than assembling it under deadline pressure. Maintain a per-programme evidence folder containing the instrument used, response rates, the thematic summary, the action items raised, the CPDS and CdS minutes referencing them, and the follow-up re-evaluation. Standardised, exportable reports make this far less labour-intensive and let your Presidio answer a CEV follow-up on the spot. The goal is a clear, traceable chain — opinion, observation, decision, action, re-evaluation — repeated consistently across the programmes in scope.