Writing a Course Evaluation Policy: The Governance Framework Quality Reviewers Expect

When a review panel or accreditation team asks how your institution assures teaching quality, one of the first documents they expect to see is not a spreadsheet of scores — it is your course evaluation policy: the governing document that states what you evaluate, when, who is responsible, how results are used, and how students see that their feedback changed something. Under the Standards and Guidelines for Quality Assurance in the European Higher Education Area (ESG 2015), Standard 1.1 requires institutions to have a public policy for quality assurance that is part of their strategic management; a course evaluation policy is the operational expression of that standard for the student-feedback cycle. This guide sets out what belongs in that policy, how each component maps to accreditation expectations, and where an evaluation platform supports — but never replaces — the governance you must own.

The honest headline first: a policy is an organisational instrument, not a software feature. No platform can write your governance for you, decide who owns the closing-the-loop obligation, or set your publication rules. What good software can do is make the policy enforceable and auditable — consistent instruments, complete cycles, action tracking, and evidence that survives a site visit. Keep those two things separate and you will pass review; conflate them and a panel will notice that your "policy" is really just a tool's default settings.

Why accreditors ask for the policy, not just the data

Course evaluation scores answer "what did students say". A policy answers the questions a reviewer actually cares about under the ESG:

• Is the approach systematic? ESG 1.9 (on-going monitoring and periodic review) expects programmes to be monitored through a defined cycle, not ad hoc surveys.
• Is it student-centred? ESG 1.3 expects student feedback to inform student-centred learning and teaching.
• Is information managed responsibly? ESG 1.7 (information management) expects reliable collection, analysis and use of data.
• Is it public and owned? ESG 1.1 expects the policy to be public, and to be developed and implemented through appropriate structures and stakeholders — including students.

A panel reads the policy to check that your evaluation is designed, not accidental. Missing or vague policy is one of the most common conditions attached to a positive review outcome, because it signals that good practice depends on individuals rather than on the institution.

What a course evaluation policy must contain

A defensible policy covers ten components. The table maps each to the reviewer expectation it satisfies.

Policy component	What it states	Accreditation expectation it meets
Purpose & principles	Why you evaluate (enhancement, not only accountability); formative and summative aims	ESG 1.1 policy scope; student-centred ethos (1.3)
Scope & cadence	What is evaluated (every module? every cycle? new staff?) and how often	ESG 1.9 systematic monitoring
Roles & responsibilities	Who runs it, who acts on it, who signs off (module leader, programme director, QA office, students' union)	ESG 1.1 appropriate structures
Instrument governance	Core question set, how items change, approval route	ESG 1.7 reliable information
Response-rate expectations	Target rates, reminder protocol, how low-N results are handled	Data-quality credibility
Confidentiality & anonymity	Anonymity guarantees, small-cohort suppression thresholds	ESG 1.7; GDPR minimisation
Data protection & retention	Lawful basis, retention windows, anonymisation	GDPR Art 5; ESG 1.7
Reporting & access	Who sees what, at what aggregation, when	Responsible reporting (Linse 2017)
Closing the loop	Required actions, feedback to students, escalation of "courses of concern"	ESG 1.9; the enhancement expectation
Review of the policy	When the policy itself is reviewed and by whom	ESG 1.1 policy as living document

Two of these components are where policies most often fail review. The first is closing the loop: a policy that collects feedback but does not require a documented response, visible to students, will not satisfy an enhancement-led reviewer (see our guide on whether closing the loop actually matters). The second is low-N and confidentiality: a policy that publishes means for a class of four exposes individuals and invites a data-protection finding; the policy must state suppression thresholds and confidentiality guarantees explicitly.

Governance structures the policy should name

A policy is only credible if it names the bodies that own it. In most European institutions that means:

• A programme committee or board of studies that receives module-level evaluation and agrees actions.
• A faculty or institutional quality committee that receives aggregated, cross-programme reporting and monitors trends (our institution-level reporting guide covers the longitudinal evidence this body needs).
• Student representation in the design and review of the policy — the ESG treat students as partners in quality, not only respondents.
• A named data controller function (usually the DPO's remit) for the personal data the process generates.

The policy should show the flow of evidence up these structures and the flow of decisions back down. That closed loop is the single most persuasive thing a self-evaluation report can demonstrate.

Mapping policy requirements to concrete outputs

Where an evaluation platform earns its place is in making the policy operate consistently and producing the artefacts a review needs. The mapping below shows how policy commitments become evidence — the standardisation, action tracking and longitudinal reporting a modern platform such as Koji is built to produce.

Policy commitment	Evidence a reviewer wants	Platform output that supports it
"Every module is evaluated each cycle"	Coverage report across all modules	Automated scheduling and completeness dashboard
"Instruments are standardised"	The approved core question set, applied uniformly	A governed, reusable core instrument (bias-aware, consistent moderation)
"We act on feedback"	Documented actions per module, dated	Closing-the-loop / action-tracking log
"Students see the response"	"You said, we did" evidence back to cohorts	Action summaries published to students
"We monitor trends over time"	Multi-cycle, cross-cohort comparison	Longitudinal cohort reporting
"We protect small cohorts"	Suppression of low-N results	Threshold-based reporting controls
"We retain responsibly"	Retention schedule applied	Retention/anonymisation controls (see the retention guide)

The consistency point matters most for accreditation. A policy that promises standardised, bias-aware instruments but is delivered through a dozen hand-built departmental surveys cannot demonstrate comparability. Koji's model — an AI-moderated, standardised interview applied uniformly, with automatic thematic analysis — is designed to make the "standardised instrument" and "we act on it" commitments verifiable rather than aspirational. The same AI interview engine underpins user and customer research on the main koji.so platform; in the education context it is pointed at the course-experience cycle.

Where software is not the answer

Being precise about the limits keeps this honest, which is what evidence-driven QA leaders expect. A platform does not:

• decide your governance — which committee owns actions, or how students are represented in policy design;
• set your academic-freedom safeguards — how evaluation evidence may (and may not) be used in probation, promotion or performance decisions (a live issue under the EU AI Act, and one your policy must address);
• write your confidentiality thresholds — those are institutional judgements, informed but not made by a tool; or
• substitute for the triangulation the ESG expect — student evaluation is one strand alongside peer review, external examining and outcome data.

If your institution already has a mature, well-governed evaluation policy operated through an existing platform that produces coverage, action and longitudinal evidence, changing tools will not improve your review outcome — refine the policy instead. A tool change helps when the policy is sound but undeliverable: standardisation promised and not achieved, closing-the-loop required and not evidenced, or qualitative depth expected and not captured by a static Likert form.

Building or refreshing the policy: a short sequence

1. Anchor to your framework. State explicitly which ESG standards (and national agency requirements — QQI, NVAO, German Akkreditierungsrat, and so on) the policy serves.
2. Draft the ten components above, with students and academic staff at the table.
3. Set measurable commitments — coverage targets, response-rate protocols, action deadlines — so the policy is auditable, not decorative.
4. Name the structures that own each stage and the data-controller function.
5. Decide what your platform must produce to evidence each commitment, and procure or configure against that list.
6. Set a review date for the policy itself and record it.

Do this and your self-evaluation report writes itself: the policy states the intent, and the platform's coverage, action and longitudinal outputs are the evidence that the intent is real. Our self-evaluation report guide shows how to assemble that narrative.

Frequently asked questions

What is a course evaluation policy and why do accreditors want one?

It is the governing document that states what your institution evaluates, when, who is responsible, how results are used, and how students are told what changed. Accreditors want it because ESG Standard 1.1 requires a public quality-assurance policy; the course evaluation policy is the operational expression of that standard for the student-feedback cycle. It demonstrates that good practice is systematic and institution-owned, not dependent on individuals.

Which ESG standards does a course evaluation policy address?

Primarily ESG 1.1 (policy for quality assurance), and in operation ESG 1.3 (student-centred learning and teaching), 1.7 (information management), and 1.9 (on-going monitoring and periodic review of programmes). National agency requirements sit on top of these.

Can course evaluation software write our policy for us?

No. A policy is a governance instrument that only your institution can own — deciding who acts on feedback, how students are represented, and how evaluation evidence may be used in staff decisions. Software makes a good policy enforceable and auditable through standardised instruments, action tracking and longitudinal reporting, but it cannot substitute for the governance itself.

How does a policy handle small classes and confidentiality?

The policy must state anonymity guarantees and a suppression threshold — a minimum number of responses below which results are not reported at individual level — to protect students in small cohorts and satisfy GDPR data-minimisation. This is a policy decision the institution makes; the platform enforces the threshold you set.

How often should the course evaluation policy itself be reviewed?

Treat it as a living document. Most institutions review the policy on a defined cycle (commonly every two to three years) or when a national framework changes. The ESG expect the policy to be developed, implemented and periodically reviewed through appropriate structures with student involvement; record the review date in the policy so a panel can see it is maintained.

Does having a policy replace triangulation with other evidence?

No. Student course evaluation is one strand of quality evidence. The policy should position it alongside peer review, external examiner reports and outcome data, and state how the strands are brought together — the ESG expect this triangulation rather than reliance on student ratings alone.

Related Resources

• Turning Student Feedback into ESG / ENQA Accreditation Evidence
• Does Closing the Feedback Loop Actually Matter?
• Institution-Level Evaluation Reporting for Quality Audits
• Course Evaluation Data Retention: How Long to Keep Records
• The Self-Evaluation Report (SER): Turning Evidence into Accreditation-Ready Documentation
• Interpreting and Reporting Student Ratings Responsibly