mycourse.fyi brings module feedback, end-of-year course surveys and NSS and PTES reminders into a single hub. AI groups what students say, staff answer it in public, and students can see exactly what changed because of them.
How is this module going so far?
Students are asked for feedback by modules, courses, the institution and the national surveys, usually through different systems with no visible result. mycourse.fyi puts it all behind one front door, targeted to who each survey is actually for.
Short, sentiment-first check-ins while a module is still running. Coordinators set the cadence. A single “I'm happy with everything” tap clears every open pulse at once.
Every level, every moduleEnd-of-year surveys for each year of study, built on NSS-aligned themes: teaching, assessment and feedback, resources, organisation, support and student voice.
First year to final yearTimed reminders that link out to the national surveys, with a mark-as-done step and a careful, regulator-compliant opt-out flow.
Final-year undergraduates and taught postgraduatesMost feedback disappears into a spreadsheet. Here every comment is grouped, owned, answered and shown back to the students who raised it.
Surveys reach the right students automatically, from the student record and straight inside the VLE.
AI clusters free text from pulses and course surveys into themes with sentiment and representative, scrubbed quotes.
Coordinators summarise their modules. Course leaders respond to themes, log actions and build action plans.
“You said, we did” lands on the student's own dashboard and in reps' committee digests, with a notification when it does.
The biggest complaint about feedback is that nothing happens. Every published reply and every completed course action appears on the dashboard of the students it affects, next to the module or course it is about.
Lecture slides published late
Students in several groups want slides before the session so they can annotate them.
Fair point. From week 7 slides are on the module page by 9am the day before each lecture.
Module coordinator · week 6 · Resolved
Response rates rise when finishing a survey feels like progress. Rewards count taking part, never what a student said.
Ten levels from Newcomer to Legend, with points scaled to the effort each survey takes.
Tiered badges for firsts, streaks, early responses and completing a whole term, with a celebration when they unlock.
Friendly comparison by cohort without anyone being named or identifiable.
Staff dashboards nest like Russian dolls. Each person starts at their own scope and can drill down to a single year of a single course.
Designed by academics who have chaired the committees, chased the response rates and written the action plans. Every feature exists because someone in a university needed it.
Chase lists for low-response cohorts, action plans for recurring themes and a record of closed loops, ready for quality review.
Each module knows when it has enough new comments to be worth summarising, and nudges the coordinator rather than nagging.
Non-technical staff edit questions, survey windows and reminder messages from the browser. No forms vendor, no code.
Course and school reps get a digest of themes and staff responses across their remit, with a “still needs attention” filter for committee meetings.
Past surveys, results and themes stay browsable, and course leaders can attach previous NSS and PTES findings to their course.
Excel downloads from any survey, chase or action-plan view, plus a secured feed for institutional reporting tools.
Free text is screened for welfare concerns and escalated to designated handlers, without ever identifying the writer.
Staff roles, enrolments and module changes reconcile from the student record, so access follows people as they move.
Keyboard and screen-reader tested, reduced-motion aware and comfortable on a phone.
| Students | Their own surveys, progress and every response to feedback on their modules and course. |
|---|---|
| Course and school reps | Themes and staff responses across their course and year, or their whole school. |
| Module coordinators | Pulses, themes and summaries for the modules they run. |
| Course leaders | Course surveys, themes by year, actions and action plans for every course they lead. |
| Heads, deans and quality teams | The nested dashboard for their school, faculty or institution, with rep and roster management. |
| Administrators | Survey editor, reminders, data sync, safeguarding queue and VLE configuration. |
Who took part and what they said are stored separately. No record anywhere holds both, so feedback cannot be traced back to a student even by the people running the system.
Staff and students use their institutional login.
Courses, modules, enrolments and staff roles sync automatically.
An LTI 1.3 block shows feedback due and recent replies on each module page.
Deploys into your own Azure or Google Cloud tenancy.
Pilots can run with no data feeds at all, then switch on single sign-on, student record sync and the full survey suite when you are ready. Each institution gets its own private instance on mycourse.fyi.