Feedback loops fail when universities mistake policy for practice
Updated Sep 04, 2026
A student-feedback policy can survive for 25 years without becoming routine practice. Martin Boswell and Stephen Marshall's new Quality in Higher Education paper, "Closing the student feedback loop: a case study of a disconnect between well-meaning quality goals and the realities of meaningful change in an institutional quality culture", shows how that happens. For UK universities trying to close the loop in student voice work, the warning is stark: collecting comments, writing policy, and passing audits do not prove that students can see how their feedback was considered.
Context and research question
Universities commonly ask lecturers or programme teams to summarise student feedback, explain their response, and tell the current or next cohort what changed. On paper, this completes a sensible cycle from listening to action. In practice, the work crosses academic autonomy, staff workload, course ownership, quality processes, and communication with students. A requirement can therefore exist everywhere in policy while remaining optional in daily practice.
Boswell and Marshall examine that gap through a longitudinal qualitative case study of an anonymised, medium-sized New Zealand university called Dominion University. The study covers five external academic audit cycles from 1994 to 2019. Its evidence includes more than 3,000 pages, or over one million words, of audit reports, self-review documents, policies, procedures, and committee records, analysed before generative AI tools became available. The authors compare those records with 19 interviews involving current and former university staff, external agency staff, and consultants. Interviews lasted about 45 minutes and used open-ended questions.
The study asks why recurring audit recommendations failed to produce sustained implementation, and how the university's loosely coupled organisational culture shaped that outcome. That question transfers directly to UK higher education. It tests whether student voice is embedded as a quality-enhancement process or treated as a recurring compliance task.
Key findings
The university did not lack policy, advice, or external scrutiny. Auditors raised closing the student feedback loop in three of five quality cycles, alongside similar recommendations from consultants. In 2009, the university adopted a formal policy requiring course coordinators to summarise the previous cohort's feedback, comment on it, and outline resulting changes for the next cohort. Yet uptake remained far from universal. The central failure was implementation, not intention.
"the implementation was dependent on the academic staff choosing to implement a policy"
Staff and students saw the same process very differently. A 2006 institutional review found that 95% of students agreed or strongly agreed that course-evaluation summaries should be shared. By contrast, 44% of lecturers disagreed or strongly disagreed. More revealingly, 47% of lecturers said they always or usually told students about changes made in response to feedback, while only 15% of students thought this happened. For quality teams, that perception gap is evidence in its own right: recording an action does not mean the loop was visible to students.
Resistance was both cultural and practical. Interviewees described scepticism about student evaluations, concern about biased or hurtful comments, and anxiety about making results more public. They also identified operational barriers: the work of synthesising comments, removing personal remarks, acting after the current cohort had left, reconciling contradictory feedback between cohorts, handling courses taught irregularly or by different lecturers, and a lack of training or checks. A policy that ignores these conditions asks individual enthusiasm to compensate for weak institutional design.
External quality assurance repeatedly recognised the problem but did not secure the outcome. At one point, a later audit failed to follow up an earlier recommendation. In another follow-up, the university reported faster evaluation processing even though the recommendation concerned communicating responses to students. The authors argue that the institution could show activity without demonstrating widespread implementation. The quality process therefore reinforced declarations of progress more readily than it verified meaningful change.
The paper is careful about what the evidence cannot show. It notes that closing the loop is often assumed to increase student trust or future participation, but strong direct evidence remains limited. The case study also emerged from wider research on academic audit rather than a project designed primarily around students' experience of loop closure. Its strongest conclusion is narrower and still important: policy, audit, and goodwill were insufficient to make a student-centred practice routine across one institution.
Practical implications
First, UK universities should define closure as an observable process, not a policy statement. Each survey or evaluation route needs a named owner, a response deadline, a destination students can access, and a record of what was accepted, declined, or passed to another level. Sampling course pages and asking students whether they saw a response will reveal more than confirming that a policy exists. This gives quality teams evidence of implementation rather than evidence of intention.
Second, institutions should separate analysis, decision-making, and communication while keeping them connected. Teams need a consistent way to group open comments, distinguish repeated themes from isolated remarks, redact personal abuse, assign issues to the correct level, and preserve the source evidence behind each response. The same principles that support a defensible NSS open-text analysis methodology also make module-level responses easier to explain. This reduces the burden on individual lecturers and produces more consistent decisions across programmes.
Third, universities should audit the evidence trail, not only the presence of activity. A completed evaluation, a downloaded report, or a line in a course handbook is not proof that students received a meaningful response. Review samples should connect the original evidence to the decision, the owner, the action or reason for non-action, and the message returned to students. A student comment analysis governance checklist can help teams test those links before the next committee or external review. This makes quality assurance better at detecting stalled loops instead of rediscovering them years later.
Finally, institutions should support staff to interpret difficult feedback rather than treating resistance as a personal failing. Training, developmental discussion, clear escalation routes, and protection from abusive comments can make engagement safer and more useful. Student Voice Analytics can provide a reproducible view of recurring themes across large comment sets, but institutions still need people, authority, and resources to decide and communicate what happens next. The benefit is a feedback process that staff can use and students can recognise.
FAQ
Q: How can a university check whether student feedback loops are actually closing?
A: Define a small set of verifiable stages: feedback analysed, response agreed, owner assigned, decision recorded, and outcome communicated to students. Then sample courses and services across faculties, check the underlying evidence, and ask students whether they saw and understood the response. Measure completion and visibility separately, because an internal action record may still leave students unaware of what happened.
Q: What should institutions keep in mind before generalising from this study?
A: This is an in-depth case study of one medium-sized New Zealand university over 25 years. It explains organisational mechanisms but does not estimate how common they are across the sector. The research focused on academic audit, and most interview participants were staff or external quality professionals rather than students. UK teams should use the findings to test their own processes, not assume the same pattern or scale without local evidence.
Q: What does this paper change about student voice practice?
A: It moves attention from whether universities invite student voice to whether they build the conditions for a response. Surveys and comments only become part of institutional learning when teams can interpret them, decide what follows, document responsibility, and explain the outcome. Closing the loop is therefore not a final communication task. It is a governance test of whether student feedback can travel through the institution and produce an accountable response.
References
[Paper Source]: Martin Boswell and Stephen Marshall "Closing the student feedback loop: a case study of a disconnect between well-meaning quality goals and the realities of meaningful change in an institutional quality culture" DOI: 10.1080/13538322.2026.2686536
Request a walkthrough
Book a free Student Voice Analytics demo
See all-comment coverage, sector benchmarks, and reporting designed for OfS quality and NSS requirements.
- All-comment coverage with HE-tuned taxonomy and sentiment.
- Versioned outputs with TEF-ready reporting.
- Benchmarks and BI-ready exports for boards and Senate.
UK-hosted · No public LLM APIs · Same-day turnaround