A-Level Computer Science Grade Boundaries History

The frustrating thing about grade boundaries is that they look like targets, yet nobody knows the target before the exam. Looking at A-Level computer science grade boundaries history can still be useful, however, provided you treat it as context rather than a prediction.

The short answer is that AQA Computer Science boundaries fell noticeably in $2022$, then rose in each year from $2023$ to $2025$. They have not yet returned fully to their $2019$ level for every grade. This reflects changing papers, student performance and the return to normal grading after pandemic disruption -- not a permanent promise that future boundaries will rise or fall.

This article focuses on AQA specification $7517$, because boundaries cannot be compared directly across different exam boards or specifications. The latest confirmed summer boundaries available at the time of writing are from $2025$.

The grade boundary checklist

Before interpreting the figures, remember:

• a boundary is the minimum total mark needed for a grade;
• AQA Computer Science has a maximum scaled mark of $375$;
• Paper $1$ and Paper $2$ each contribute up to $150$ scaled marks;
• the non-exam assessment contributes up to $75$ marks;
• boundaries are set after scripts have been marked;
• boundaries from different exam boards are not interchangeable;
• past boundaries are useful benchmarks, not forecasts.

You can check the complete figures on the AQA A-Level Computer Science grade boundaries page.

A student worrying about a boundary chart while a teacher recommends past papers

Past A-Level Computer Science grade boundaries

The table shows the confirmed overall AQA boundaries for the main summer examination series. The figures apply to the listed C#, Java, Python and VB.NET routes in each included year.

Summer examinations were cancelled in $2020$ and $2021$, so those years do not provide comparable summer exam boundaries. Teacher-assessed arrangements were used instead. Treating figures from those years as ordinary exam boundaries would create a misleading trend.

What the year-by-year changes reveal

The pre-pandemic benchmark in $2019$

In $2019$, an $A^{\ast }$ required $309$ marks, equivalent to:

$$\frac{309}{375}\times 100=82.4\%$$

An $A$ required $261$ marks, or $69.6\%$. These figures provide a useful pre-pandemic reference, but they do not represent fixed percentages for the qualification.

The lower boundaries of $2022$

Formal summer examinations returned in $2022$, with grading designed as a transition between pandemic-era outcomes and pre-pandemic standards. The $A^{\ast }$ boundary was $278$, which was $31$ marks below the $2019$ figure. The $A$ boundary dropped from $261$ to $223$.

That does not mean the qualification suddenly became easier. A lower boundary can compensate for a more demanding assessment or weaker performance across the cohort. The mark must always be read alongside the particular examination series.

The return towards normal grading in $2023$

Ofqual returned to pre-pandemic grading standards in $2023$, with protection recognising the disruption experienced by that cohort. The AQA $A^{\ast }$ boundary rose to $296$, while the $A$ boundary increased to $237$.

This is the clearest turning point in recent A-Level computer science grade boundary trends. Yet it would be too simple to attribute the entire change to grading policy. Awarding decisions also consider evidence from the actual scripts and statistical information.

Smaller movement in $2024$

The boundaries moved only slightly in $2024$. The $A^{\ast }$ threshold increased by $2$ marks to $298$, while the $A$ threshold also increased by $2$ marks to $239$.

Small changes like these are normal. They help preserve a comparable standard when one paper is marginally more or less demanding than another.

Another rise in $2025$

In $2025$, the $A^{\ast }$ boundary reached $300$, exactly $80\%$ of the available marks. The $A$ boundary rose more sharply to $245$, or approximately $65.3\%$.

Even after that rise, the $A^{\ast }$ boundary remained $9$ marks below its $2019$ level, while the $A$ boundary remained $16$ marks lower. The trend is upward from $2022$, but it is neither perfectly uniform nor a reliable prediction of the next boundary.

Why boundaries change

Grade boundaries exist to keep standards comparable when papers vary in difficulty. Senior examiners review evidence after marking rather than selecting an arbitrary percentage in advance.

Several factors therefore matter:

• the difficulty and accessibility of the papers;
• how students performed across the mark range;
• evidence from examiners and statistical data;
• changes to assessment arrangements;
• the grading standard that must be maintained.

A high boundary does not automatically mean students were unusually clever. A low one does not mean the exam board was generous. Both may simply indicate how demanding that year’s assessment proved to be.

How to use boundary history in revision

Start with a timed paper from the AQA A-Level Computer Science past papers collection. Mark it strictly, then compare your total against several historical boundaries rather than choosing the lowest one.

A sensible approach is to build a margin above your desired grade. If your score sits exactly on one old boundary, normal variation could move you below it in another year. More importantly, identify where the lost marks came from: programming, algorithms, data structures, computer systems, theory or imprecise written explanations.

Use the AQA A-Level Computer Science revision hub to move from diagnosis to focused practice. Students balancing Computer Science with maths can organise their week using the MathsGenie revision planner, while A-Level predicted papers can support maths preparation alongside official past-paper work.

A crystal ball competes with a stack of marked past papers

Common mistakes when analysing boundaries

Treating a past boundary as a prediction

The next boundary cannot be confirmed before marking and awarding are complete. Revising only to reach last year’s threshold leaves no safety margin.

Comparing raw marks from different qualifications

AQA and OCR use different specifications and assessment structures. Even when two courses share a subject name, their totals and boundaries cannot be compared as though they were the same scale.

Using notional paper boundaries as final grades

For a linear A Level, the overall qualification mark determines the final grade. Notional component boundaries are illustrative and do not award separate certificated grades for individual papers.

Ignoring the missing examination years

There were no normal summer A-Level examinations in $2020$ or $2021$. Any graph implying an uninterrupted sequence of comparable exam boundaries is incomplete.

Turn the trend into a revision decision

The history tells a simple story: AQA boundaries dropped in the disrupted assessment period and then climbed between $2022$ and $2025$. But the most useful lesson is not the direction of the line. It is that boundaries move, while secure knowledge travels with you into every paper.

Begin with MathsGenie’s free A-Level Computer Science past papers, mark each attempt carefully and turn every lost mark into a specific revision task. Combine past papers with revision lessons, practice questions and mark schemes. If you are still completing GCSEs before choosing your A Levels, the GCSE maths revision hub and predicted paper resources can help you build the algebraic reasoning and disciplined exam habits that Computer Science will later reward.