Exeter University Module Grades: Where GradeHack Started
Exeter University module grades were the first dataset GradeHack ever filed for, back in 2018. Here's what that pilot found and what it's grown into.
Max Beech · Founder
In 2018, as an undergrad at Exeter, I filed my first Freedom of Information request asking for module-level grade distributions in Computer Science. I wasn't building a company. I wanted to know whether it was worth taking ECM3428 over the alternative in my final year.
The request came back with real data. That data changed which module I took. That's the entire origin story of GradeHack.
What the original Exeter request asked for
The 2018 request was narrow and specific: mark distributions for a handful of Computer Science optional modules, broken down by cohort year. No names, no individual results — just aggregated distribution data, which universities are obliged to disclose under the Freedom of Information Act unless a specific exemption applies (most commonly s.40, personal data, or s.38, where disclosure would cause harm).
Exeter's response confirmed what every student suspects but can never prove: modules on the same degree, at the same year level, with broadly similar workload on paper, had meaningfully different first-rates. Some computer science modules at Exeter ran distributions where a much larger share of students cleared the First boundary than others.
What that pilot proved
The 2018 Exeter pilot proved two things that shaped everything GradeHack has built since:
- The data exists and is genuinely disclosable. Universities aren't hiding module-level grade data illegally — they're just not proactively publishing it, and almost nobody asks.
- Students act on it when they see it. Given real distribution data, students make different, more deliberate module choices than they would relying on handbook descriptions and secondhand opinion.
You can read the full methodology behind how these requests are filed, and what universities can and can't lawfully withhold, in FOI requests for university grade data.
What the data looked like, banded
We don't publish raw percentages from any cohort, including the original Exeter data, on public pages — our privacy threshold excludes any cohort under 10 students regardless of source. Banded, the shape of the original finding looked like this:
| Module type | First-rate band | Cohort size |
|---|---|---|
| Established, coursework-heavy CS module | High | Large |
| Newer, exam-heavy CS module | Low | Medium |
That gap — a genuine, data-backed gap between modules that looked interchangeable on paper — is the entire commercial thesis GradeHack is built on.
From one pilot to a national dataset
What started as one student's FOI request to one university has scaled into FOI requests filed to universities across the UK, covering multiple subjects beyond Computer Science — see our guides for economics, law, and psychology optional modules for how the same pattern shows up elsewhere.
The core insight hasn't changed since 2018: module choice moves your degree classification more than almost anything else you control, and almost nobody has the data to choose well. See does module choice affect degree class for the maths behind why.
Access the data
If you're at Exeter, or anywhere else in the UK, and choosing between optional modules right now, join the GradeHack waitlist to access FOI-sourced grade distribution signals for your subject, the same kind of data that changed my own module choice back in 2018.
How to use historic module data responsibly
The Exeter pilot is a useful example of what aggregated data can reveal, not a shortcut to a current module choice. Course structures, assessment formats and cohorts change. Use historic results to spot questions worth investigating, then confirm the current module specification, prerequisites and assessment pattern with the department.
The privacy rule matters too: small cohorts should not be reverse-engineered from percentages or published as identifiable results. GradeHack uses banded public signals for that reason. For the wider context, read how other students perform in the same modules.
FAQ
What year did GradeHack's first FOI request go to Exeter?
- It asked for mark distributions across a handful of Computer Science optional modules, broken down by cohort year, to help decide between two final-year module options.
Does GradeHack publish raw Exeter grade percentages?
No. Public pages only show banded signals, such as low/mid/high First-rate bands, and exclude any cohort under 10 students, regardless of what the original FOI response disclosed. See our methodology for the full privacy threshold.
Has GradeHack expanded beyond Exeter and Computer Science?
Yes. The same FOI-request process now covers universities across the UK and multiple subjects, including economics, law and psychology.
Can I request data for my own university and course?
The best way to get early access is to join the GradeHack waitlist — data is released progressively as FOI requests come back from universities across the UK.
Read next
- FOI data3 min read
Best University for Computer Science UK: What the Data Actually Says
Searching for the best university for computer science UK? League tables miss the module-level data that actually predicts your degree outcome. Here's what to check instead.
25 July 2026Read - FOI data3 min read
Kent University Module Grades: The FOI Data So Far
Kent university module grades are now live on GradeHack. Here's what the banded FOI data shows, and why smaller catalogues can still be worth checking.
24 July 2026Read - FOI data3 min read
Warwick Module Grades: What the FOI Data Shows
Warwick module grade data is now live on GradeHack. Here's what the FOI-sourced distributions reveal about optional module choice at Warwick.
22 July 2026Read