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.

Student comment analysis governance checklist for UK HE

Updated Nov 06, 2026

A student comment report should be easy to explain, reproduce and hand over. Agree who owns the data, who reviews the analysis and who approves the audience for each output before work starts.

Use this checklist as a working document for your institution’s existing approval process. Give each item a named owner, a link to the relevant record and a status. The worked example can help colleagues agree what a traceable output looks like before any institutional text is shared.

1. Agree the question and scope

Record the survey, questions, collection period and population. Write down the decision the analysis will support and which team will use it. Keep a copy of the inclusion rules for blanks, duplicates, withdrawn responses and comments outside the agreed scope.

A useful acceptance statement is specific: “The programme board will receive a topic summary, counts, reviewed examples and a list of questions for course teams.” Agree the delivery date and review window alongside that statement.

2. Map the data journey

Record Owner to name What the record should make clear
Source register Survey or data owner Files, fields, questions, period and permitted purpose
Transfer and storage plan Institutional data protection and technical leads Approved route, processing locations, access and retention
Analysis specification Analyst or supplier lead Categories, versions, inclusion rules and denominators
Review log Named quality reviewer Examples checked, disagreements and resulting changes
Release decision Report owner Audience, permitted detail, approval and review date

List raw text, working copies, exports and backups separately. Check the actual arrangements with institutional colleagues and the provider, including any subprocessors. Agree how access ends and how completion of the retention process will be recorded.

3. Define the analysis precisely

Keep the taxonomy and its version with the report. Record whether counting happens at sentence, comment or respondent level, how mixed comments are handled and how a headline measure is calculated. The glossary gives teams a shared vocabulary.

Record classification coverage separately from the result of accuracy checks. Review examples from common categories, ambiguous comments and unclassified text. Log disagreements and the decision taken, so the next analyst can follow the same reasoning.

For a repeat analysis, retain the input version and the model, rules or prompt version used. Where the process changes, document what can still be compared. Our NSS methodology illustrates a published version and comparison policy.

4. Match the output to its audience

Agree what an analyst, a course team, a committee and a public reader may see. Review identifying details in examples, including combinations of circumstances that could reveal someone even after their name is removed. Apply the institution’s rules for small groups and restricted information before release.

When a result needs aggregation, select a grouping that still answers the question. Keep distinct questionnaire periods separate where comparability changes; combining years solely to increase a count can obscure the experience being reported.

5. Make the handover usable

Give the recipient the report, definitions, version record, approved evidence route and a named contact for questions. Keep the internal review log with the project. Make the public-facing narrative direct and useful, with the method available through a clear link.

Record each agreed action with its owner, deadline and review question. The closing the feedback loop pathway helps connect that reporting work to a response students can see.

Before commissioning work

Bring this checklist to a discussion of Student Voice Analytics, or use it to assess an internal workflow. The NSS buyer’s guide turns the same questions into an evaluation record: ask to see the output, the evidence behind it and the work your team will still need to do.

Talk to the team

Contact Student Voice Analytics

Book time with the team to map current survey coverage, governance requirements, and handover timelines.

Contact sales Email info@studentvoice.ai

UK-hosted · No public LLM APIs · Average response time < 1 working day.

Related Entries