My Thoughts on the Computing Curriculum Review
Friday 23rd October 2026
Later this month, the dust will finally settle on the Curriculum and Assessment Review, and we will get our first real look at the future of KS4 Computing. Following the recommendations from the review panel and the Department for Education's pledge to replace our current, hyper-theoretical Computer Science GCSE with a broader "Computing" qualification, the computing education community is holding its breath to see what the actual syllabus looks like.
Sitting in the classroom every day gives me mixed feelings about this. Change is desperately needed, yes. How we change, however, matters just as much.
Get this right, and we fix a broken qualification. Get it wrong, and we risk trading a broken subject for a watered-down checklist of basic IT skills. From my perspective in the classroom, if the Department for Education and the BCS want a curriculum fit for the 2030s, here is what I think needs to be part of the discussion.
What We Have Heard So Far
Before diving into what I think should be in the course, it is worth looking at the whispers circulating through staff rooms and subject specialists right now. Since the BCS (The Chartered Institute for IT) was tasked with helping shape the new content, several strong rumours and policy signals have emerged about what is on the table:
- The 10% Assessment Trim: In line with the wider Curriculum Review recommendations, exam time across GCSEs is looking at an approximate 10% reduction to ease pressure on pupils and staff. This has sparked plenty of debate over whether NEA practical coursework will make a return in Computing.
- Computing as the "Main Vehicle" for Digital Literacy: The DfE has indicated that the Computing curriculum will become the primary home for essential digital skills, whilst pushing online harms to RSHE and misinformation to Citizenship.
- A New Post-16 Pathway: Alongside the revamped GCSE (planned for a phased rollout starting around 2028/2029), the government seems to be actively exploring a brand-new Level 3 qualification in Data Science and AI to sit alongside A-Levels and the newly proposed "V-Levels".
In my opinion, these ideas are promising. However, to make this work on the ground, we have to confront why the current system broke in the first place.
Why the Current Setup isn't Working
Before we write a single line of a new specification, we have to be honest about who the current GCSE serves, and who it locks out. When the old ICT GCSE was scrapped in favour of Computer Science, the total number of pupils taking any computing qualification at KS4 plummeted. Inadvertently, we created a "Missing Middle" where thousands of students who did not want to become software engineers were suddenly left without crucial digital skills.
Worse still, the students who did stay were overwhelmingly from a single demographic. The data says it all really:
- Schools Dropping the Subject: Because of specialist teacher shortages, brutal grading boundaries, and low uptake, a huge number of schools have removed Computing from their options blocks altogether. Data from the Royal Society and King's College London shows that roughly one in three secondary schools do not even offer GCSE Computer Science, and provisional 2026 figures show overall entries dropping by another 7% year-on-year (a loss of over 10,000 students in just two years).
- The Gender Divide: According to data from the Royal Society, the Raspberry Pi Foundation, and the BCS, girls consistently make up only around 21% of GCSE Computer Science entries, dropping to 15% at A-Level. Research from the Gender Balance in Computing programme highlights that girls frequently see the current curriculum as abstract and disconnected from real-world impact. They often underestimate their own programming abilities despite outperforming boys when they actually take the subject.
- The Poverty Penalty: Students eligible for Free School Meals (FSM) are significantly underrepresented. Furthermore, schools with the highest proportions of disadvantaged pupils are statistically much less likely to offer Computer Science as an option in the first place.
- Intersectional Gaps: King's College London’s SCARI Computing project showed the reality of our classrooms. It noted massive disparities across ethnicity, gender, and socioeconomic background, and highlighted how "tech bro" stereotypes actively put teenagers off choosing the subject.
It is vitally important that we make the subject relevant to their actual lives going forwards.
Bridging the Gap Between KS3, KS4, and KS5
To me, one of the biggest structural flaws in secondary computing right now is the disconnect between Key Stage 3 and Key Stage 4.
In KS3, the National Curriculum is built on three distinct pillars: Computer Science, Information Technology (Digital Media), and Digital Literacy. Students spend Years 7 to 9 doing a bit of everything: they might code in block-based environments or Python, design graphics and web pages, and learn how to use technology safely and effectively.
Then they hit Year 10. Suddenly, two of those three pillars are cut off. If they pick GCSE Computer Science, the creative digital media and practical literacy strands vanish, replaced entirely by binary shifts, Von Neumann architecture, and learning about IDEs. If they pick a vocational IT qualification, the programming disappears instead.
Broad at GCSE, Specialised at A-Level
I believe the new GCSE Computing course must flow naturally from all three KS3 strands. By building on digital literacy and creative media alongside computer science across both KS3 and KS4, we actually prepare pupils for further education, university, and modern apprenticeships. Whether a teenager goes on to study biology, takes an apprenticeship in engineering, or goes straight into work at 18, they need to know how to handle data, design a coherent digital document, and create basic workflows.
We do not lose challenge by doing this. My view is that we should keep the GCSE broad, creative, and foundational, and let students narrow and specialise at A-Level (or through the proposed Level 3 Data Science and AI qualification). Computing GCSE should not force them to train strictly as software engineers or IT technicians. Computing has become way more broad than that.
A Compulsory Digital Literacy Core
To truly fix the gap in digital skills, I think we need a Digital Literacy qualification that is completed alongside GCSEs for everybody. This enforces the idea that Digital Literacy skills and learning should be compulsory all the way to the end of KS4 for all pupils.
In an ideal world, this would be a dedicated hour on the timetable. We often assume these skills are picked up elsewhere, but subjects like PSHE, Science, and Maths are not teaching them; they are merely expecting pupils to already know how to use them. It is important that pupils are actively learning digital skills all the way to the end of KS4.
It will mean that pupils going on to further studies, apprenticeships, or otherwise will be better prepared with more skills. Whether they opt for the full Computing GCSE or not, a baseline of digital competency is no longer optional in the modern world.
Broader without Watering It Down
While it seems like most of us are cheering for a broader GCSE, I think we have to ask an uncomfortable question: how do we broaden the appeal without watering down the challenge?
There is a real danger of "dilution". Stripping away proper algorithmic thinking just to make room for basic media literacy and document formatting does our students a massive disservice.
To me, the solution is not to make the subject easier; it is to rethink what a challenging computing course looks like, and allow courses to offer unique, practical focuses:
- AI for Schools: Moving beyond basic "AI awareness", students should be able to explore how machine learning models are trained and tested using safe, closed environments designed for schools, without risking student data privacy or creating safeguarding concerns.
- Game Development: Using game creation to teach coordinates, physics, logic states, and object-oriented programming in 2D and 3D spaces. Framing it as game development helps to engage the pupils in higher level concepts without even realising it.
- Digital Media and Design: Blending web development, graphics, and accessibility design so students see how code and design powers visual projects.
I think that Excel is the biggest example of this. We can teach proper systems thinking through the tools that actually run the modern world, and that’s Excel (or equivalent). I think it is time to start treating Excel as the world's most popular functional, reactive ‘programming language’.
When you build a complex tracking system using array formulas, nested XLOOKUP functions, and dynamic PivotTables, you are programming. You are handling variables, data types, and Boolean logic. Teaching students how to build automated data spreadsheets bridges Computer Science and Digital Literacy without losing any of the challenge.
Pair that with an overhaul of how we teach databases. Right now, teenagers write SQL queries into a void, searching a fictional table of early-2000s video rentals. Instead, let us combine SQL statement writing with a visual database tool like Microsoft Access. Let students visually link table relationships, see errors happen in real time, write the SQL behind the scenes, and link those queries to working forms and reports. Make data something they can actually see and use.
AI Prompting as a Creative Skill
The BCS and government reviews have rightly argued that AI literacy must be a foundational skill in the reformed curriculum, covering how AI works, how to check its outputs, and its ethical risks.
I would push that a step further. Having spent my research Master's degree exploring prompting, prompt chaining and the affect it has on outputs, I can tell you that working with AI is not just a passive skill. Prompting is an active, creative process.
Writing a single prompt to summarise an essay takes little skill. Building a multi-step prompt chain, where an AI generates a draft, checks its own output against a set of rules, spots its own flaws, and improves the result, is proper algorithmic thinking.
Imagine a simple classroom project across a few lessons where students design a structured prompt workflow to generate a short story or character dialogue for a game. They have to give it clear system rules, test where it goes wrong, and refine how it evaluates its own writing. Suddenly, computing becomes a subject for anybody and everybody and we’re teaching kids skills that translate to the real-world and where it’s heading.
Decolonising the Curriculum
Compared to History or English Literature, GCSE Computer Science often feels completely detached from human culture. If we want to fix the representation gaps highlighted by the SCARI project, I think we need to broaden and humanise the story of computing:
- Global Foundations: Algorithms did not fall out of the sky in 1940s Britain. Our students should know that the very word algorithm comes from the 9th-century Persian scholar Al-Khwarizmi. They should see how binary logic links back to ancient Indian texts (Pingala) and traditional African divination systems like Ifá, whilst looking at modern tech innovation thriving in places like Nairobi and Bangalore, rather than just California.
- The Physical Reality of Tech: A broader curriculum also needs to look at hardware honestly. Before writing a line of code, students should trace the lifecycle of the iPad or PC on their desk, from cobalt mining to global e-waste sites. We can link hardware ethics directly to software: teach them that messy, inefficient code demands more processing power, drains batteries, and forces people to upgrade their hardware sooner, and what impact this has on countries and the environment.
Building a Curriculum That Can Keep Up
One of my biggest worries with any new GCSE specification is how quickly it will go out of date. The current Computer Science specification was largely locked in over a decade ago, long before generative AI or modern super-fast chips were part of everyday life. Because changing a GCSE specification takes years of government reviews and exam board rewrites, teachers are often stuck teaching outdated tech while the real world moves on.
If we want this new Computing GCSE to last, I think it needs to be built to evolve:
- Focus on Concepts, Not Specific Tech: Instead of writing specific, rigid technologies into the fixed exam criteria, the core specification should focus on underlying principles that do not change (like how data flows, how systems talk to each other, and how to test if a tool is working properly), while letting teachers swap in modern tools as they emerge.
- Regularly Updated Project Briefs: If we bring back coursework or practical projects, exam boards can update the set scenarios every year. That means if a major new technology shifts the industry in 2029, students can explore it in their practical work straight away without waiting until 2035 for a curriculum review.
Ditch the Paper Coding
Finally, none of this works if we still lock students in a sports hall for three hours to write Python code with a biro. To me, writing perfect code on paper is like assessing a swimming GCSE by asking students to write an essay about water. Unfortunately, we still have qualifications that are examined completely without the use of a computer.
I think we need two major shifts in how we grade the subject:
- The DT / Art Portfolio Model: Make a proper chunk of the GCSE an ongoing design portfolio, much like Design & Technology or Art. Let students evidence their progress as programmers, build a working database, game, or physical computing project and document how they developed it from start to finish.
- Failure and Debugging as an Assessed Skill: In the real world, programming is rarely about getting it right the first time; it is about what you do when your code breaks. Research shows that fear of failure and "getting the syntax wrong" disproportionately puts girls off coding early on. So let us reward resilience. Give students a broken, buggy program and make their debugging part of their grade: assessing how they find the fault, test different fixes, and explain what went wrong.
We have a once-in-a-decade opportunity with this review. In my view, we do not have to choose between a narrow, overly academic subject for the few and a watered-down IT course for the many. By connecting our KS3 strands, using real-world data tools, bringing in creative AI and design projects, sharing a wider global history, and building a flexible assessment model that can move with the times, we can create a GCSE Computing qualification that is challenging, relevant, and genuinely open to everyone.
Sources
-
(Nov 2025 / 2026 updates). Curriculum and Assessment Review (Final Report & Government Response). Building a world-class curriculum for all, outlining the replacement of GCSE Computer Science with a broader Computing GCSE, the 10% reduction in exam volume, and the exploration of a Level 3 Data Science and AI qualification.
Review Details -
(2021–2024). The SCARI Computing Project. The Future of Computing Education and associated demographic reports investigating how computing provision, timetabling, socioeconomic status, ethnicity, and "tech bro" stereotypes impact uptake at GCSE and A-Level.
Read the SCARI Project -
(2024–2026). System Upgrade Required. Provisional Summer 2026 exam entry statistics showing a 7% year-on-year decline in GCSE Computing entries (down to 83,330) and highlighting that one in three secondary schools do not offer the subject at GCSE.
View the Reports -
(2025–2026). Policy briefings on Reformed school curriculum. Will feature AI, media literacy and a new Computing GCSE and the integration of AI awareness and digital literacy into the national computing framework.
Read Briefing -
. Gender Balance in Computing. Research series examining barriers to female participation in KS4/KS5 computing, confidence gaps, and the impact of real-world, contextual project-based learning on girls' engagement.
Access the Research -
(2022–2026). Research review series: computing. Analysis of the Curriculum and Assessment Review regarding the drop in overall KS4 computing numbers following the withdrawal of GCSE ICT, and computing's role as the primary vehicle for digital literacy.
Read the Review -
(Jan 2026). AI Skills for Life and Work: Rapid Evidence Review. Detailing the frameworks for "Learning about AI", "Learning how AI works", and "Learning for life with AI".
View Evidence