Skip to main content

Discuss your survey

Tell us what you need to understand from your student feedback. Name and email are required; the other fields are optional.

Include your survey, reporting question or deadline. Please leave student comments and identifying student details out of this enquiry.

We’ll use these details to respond to your enquiry. You can also email info@studentvoice.ai.

King's module evaluation guidance sets deadlines for responding to student feedback

Updated Nov 06, 2026

King’s College London makes the response to module feedback part of the process students can expect. Its student guidance, updated in September 2026, sets out collection points and the follow-up from staff.

The timetable matters

An Early Check In typically takes place within the first two weeks of a module. Formal implementation of the Mid-Module Review is expected in September 2027, although some staff already use it. The end-of-module evaluation provides a later review of the experience.

King’s expects staff to respond to early and mid-module feedback by the next class or within ten days. An end-of-module summary should follow within four working weeks of the survey closing, including satisfaction scores and the module lead’s response. Staff should explain what can change and the reasons when a request cannot be adopted.

Give each collection point a different purpose

For another institution reviewing its process, our suggestion is to work backwards from the decision. An early check can establish whether students have the instructions and resources needed to begin. A mid-module conversation can address something the current cohort can still experience. An end-of-module review can inform the next delivery.

Write that purpose into the question and the response plan. Before opening a survey, identify who will review the comments, when the team will discuss them and where students will see the outcome.

Separate quick fixes from wider decisions

A broken link may have a clear owner and immediate remedy. Conflicting preferences about teaching format may need a discussion of learning aims and different needs. Record the type of response alongside the issue rather than treating every comment as the same kind of action.

For each theme, keep a short record: what students described, what was checked, what the team decided and when it will be revisited. A useful student update links directly to the changed resource or explains the next stage of investigation.

Check whether the response reaches students

Ask students where they would find the response and whether it explains the issue they raised. Retain the record for the next module review, so a new survey does not restart the same discussion without context.

The module evaluation pathway connects this example with related practice. The closing the loop pathway helps plan the response, while the worked analysis example illustrates how mixed comments become separate topics for review.

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.
Book a free demo Prefer email? info@studentvoice.ai

UK-hosted · No public LLM APIs · Same-day turnaround

Related Entries