Student-Staff Liaison Committees and Course Evaluation: Turning Survey Data into Closing-the-Loop Committee Evidence

When an accreditation panel asks for evidence that student feedback leads to change, your course evaluation scores are not the answer. The answer is the paper trail of what a committee did with them. In UK and Irish higher education that committee is usually the Student-Staff Liaison Committee (SSLC) - known as the Staff-Student Consultative Committee (SSCC) in much of Scotland, and by local variants elsewhere in Europe. It is the forum where evaluation data becomes a documented decision, and it is the most under-used source of closing-the-loop evidence in most quality systems.

This guide explains what an SSLC contributes that a survey platform cannot, maps its outputs to accreditation requirements, and shows how to build an evidence trail that survives an audit. It complements our guides to closing the feedback loop and student feedback as ESG accreditation evidence.

What an SSLC is, and why accreditors care

An SSLC is a standing committee, typically at programme or department level, on which elected course representatives meet teaching and administrative staff on a regular cycle. Its business is exactly the material course evaluation produces: what is working, what is not, and what will change. Course representatives are not incidental - the QAA UK Quality Code expects providers to support, train, and resource student representative systems so that this dialogue happens at course level.

Accreditors care because SSLCs are where two ESG 2015 standards are actually satisfied in practice. Standard 1.1 (Policy for quality assurance) expects students to participate in quality processes. Standard 1.9 (Ongoing monitoring and periodic review of programmes) states that programmes should be reviewed with the involvement of students and that any action planned or taken as a result should be communicated to all those concerned. An SSLC is the mechanism that both involves students and records the communication of action. Ireland national approach through NStEP and Scotland student-partnership model make the same expectation explicit.

The evidence gap: data versus decisions

Course evaluation software is very good at producing data: response rates, rating distributions, and analysed open-text themes. Accreditation does not reward data. It rewards decisions traceable to evidence. The gap between the two is the SSLC.

A dashboard showing that satisfaction with assessment feedback fell is a metric. A committee minute recording that the SSLC discussed that fall, agreed to introduce rubric-based feedback and a two-week turnaround, and reported back to students the following term - that is evidence. Panels ask for the second thing. Institutions that present only the first are repeatedly marked down for a weak closing of the loop. The software and the committee are complements, not substitutes: the platform surfaces the signal; the committee converts it into an auditable act.

Mapping SSLC evidence to accreditation requirements

Accreditation expectation	The committee artefact that satisfies it	Supporting course-evaluation output
Students participate in QA (ESG 1.1)	SSLC terms of reference; elected reps on the membership list	Response-rate and coverage reports showing whose voice is represented
Programmes monitored with students (ESG 1.9)	Cyclical SSLC agendas tied to each evaluation round	Per-module theme and trend reports feeding the agenda
Action is planned and taken	Minuted action log with named owners and deadlines	Baseline metrics the actions are meant to move
Action is communicated to all concerned (ESG 1.9)	A "you said, we did" report circulated to the cohort	Next-cycle results showing whether the action worked
Standing, data-informed dialogue (QAA Quality Code)	Trained course reps; a recurring meeting record	Evaluation data supplied to reps before each meeting

The right-hand column is where a modern platform earns its place: it must deliver committee-ready outputs - per-module themes, longitudinal trends, and coverage data - early enough to shape the agenda, not weeks after the meeting.

Building a closing-the-loop evidence trail: a worked example

A defensible trail for a single issue looks like this:

1. Signal. The evaluation platform reports that open-text themes for a second-year module cluster around unclear assessment criteria, and the quantitative item on assessment clarity sits below the faculty median.
2. Agenda. The theme is placed on the next SSLC agenda, with the analysed data circulated to course representatives beforehand.
3. Discussion and decision. The minute records the discussion and a specific, owned action: publish marking rubrics one week before submission, effective next semester.
4. Action log. The action enters a tracked log with an owner and a due date, visible to the next meeting.
5. Communication. A "you said, we did" note goes to the cohort and is published on the programme page - satisfying the ESG 1.9 requirement to communicate action to all concerned.
6. Verification. The following cycle evaluation shows whether the assessment-clarity item recovered, closing the loop with data rather than assertion.

Every step produces a dated artefact. Assembled, they are precisely what a self-evaluation report or periodic review needs to demonstrate that the loop actually closes.

Small cohorts and confidentiality: an honest caution

SSLCs create a specific risk that quality offices must manage. In a small module, discussing a single critical comment in an open committee can identify the student who made it - or the member of staff it concerns. Two disciplines protect the process. First, report aggregate themes to the committee, not verbatim individual comments, and apply a minimum-response threshold below which module-level data is not tabled. Second, keep personnel matters - feedback that names or effectively identifies an individual member of staff - out of the SSLC and into the appropriate confidential channel. The committee is a forum for improving the course, not for appraising a person. Getting this wrong does not just breach confidentiality; it deters honest participation and corrupts the evidence.

Where the committee ends and the software begins

It is worth being clear about the limits of any platform, including Koji. Software cannot convene a committee, negotiate a decision, or take institutional responsibility for an action. Those are human, governance acts. What software can do is remove the reasons committees fail to close the loop: data that arrives too late, open text nobody has time to read, and actions that vanish because no one tracked them.

Koji contributes on each front. Its AI-moderated interviews probe why a rating is low, so the committee receives a diagnosed theme - assessment criteria are unclear because the rubric appears after submission - rather than a bare score, making the agenda item actionable. Automatic thematic analysis means reps and staff walk into the meeting with the qualitative picture already synthesised. And built-in action tracking gives the committee the dated, owned log that becomes accreditation evidence. The same AI interview engine underpins general customer and user research on koji.so; in education its job is to feed the committee, never to replace it.

Related resources

• Closing the Feedback Loop: Course Evaluation Evidence
• Student Feedback as ESG Accreditation Evidence
• Course Evaluation Evidence for UK TEF and QAA Review
• Annual Programme Monitoring: Course Evaluation Evidence
• Course Evaluation Policy and Governance Framework

Frequently asked questions

What is a Student-Staff Liaison Committee (SSLC)?

An SSLC is a standing programme- or department-level committee where elected course representatives and staff meet on a regular cycle to discuss what is working on a course and agree changes. It is called a Staff-Student Consultative Committee (SSCC) in much of Scotland and has local variants across Europe.

Why is an SSLC important for accreditation?

It is where student feedback becomes a documented, owned decision. ESG 2015 Standard 1.9 requires that action from programme monitoring be planned, taken, and communicated to all concerned - the SSLC minute, action log, and "you said, we did" note are the artefacts that evidence this.

Does course evaluation software replace the SSLC?

No. Software produces the data and the action-tracking log; the committee produces the decision and takes institutional responsibility. Accreditors want the committee decision trail, so the two are complementary.

How should small-cohort comments be handled in an SSLC?

Report aggregate themes rather than verbatim individual comments, apply a minimum-response threshold before module data is tabled, and route any feedback that identifies an individual member of staff into a confidential channel rather than the open committee.

What outputs should a platform give an SSLC?

Committee-ready per-module theme summaries, longitudinal trends, and response-coverage data - delivered before the meeting so they can shape the agenda, not after it. Automatic qualitative analysis matters most, because unread open text is the usual reason loops fail to close.

How does this differ from closing the feedback loop generally?

Closing the loop is the whole cycle of collecting, acting, and communicating. The SSLC is the specific governance forum where that cycle is enacted and recorded at course level - the place the auditable evidence is actually generated.