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.

Reviewing participation and inclusion in computer science

Updated Nov 06, 2026

computer science

A computer science inclusion review can begin with a practical task: setting up a development environment, contributing to a team project or asking for help in a laboratory. Ask students where participation becomes difficult and inspect the process they describe.

The NSS open-text methodology explains the year, population and topic measures used in our public evidence briefs. The review below focuses on decisions a programme team can examine locally.

Check the starting assumptions

Review the preparation a task expects. Make clear which skills are prerequisites and which will be taught. Test the supported software and equipment route, including the option available when a student's own device is unsuitable.

Invite students to describe the step at which they need help. Avoid assuming prior experience from a student's background or confidence in discussion.

Make group participation visible

Explain the shared task, individual responsibilities and assessment model before the project begins. Provide ways to contribute through discussion, writing and the agreed technical workflow. Check that team tools are accessible through the university's usual review process.

Name a tutor contact for a stalled task or exclusion concern. Keep sensitive individual circumstances out of group contribution records.

Review access to academic help

Ask whether students can find the contact route, use the available appointment or written channel, and understand the reply. Check referrals between teaching and specialist services so a request has a clear owner.

Offer feedback routes beyond the students already active in societies or representative meetings. Record the setting and specific barrier, rather than turning a small set of accounts into a claim about a whole group.

Check the change

Choose a concrete response, such as revised setup instructions or a different project check-in. Ask students to try the revised route and report what remains unresolved.

The belonging and support pathway connects these questions with student accounts. The assessment pathway supports review of participation expectations in assessed work.

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