A percentage score across a whole paper hides more than it reveals. Here's how to break it down into something you can actually act on.
25 August 2026 · 5 min read
A mock exam that comes back as "62%" tells you very little about what to revise next. GCSE maths spans several genuinely distinct strands — number, algebra, ratio and proportion, geometry, probability, statistics — and a single overall score blends performance across all of them into one number that hides exactly the information that would actually help.
The single most useful thing to do with a completed past paper or mock is to go back through it question by question and tag each one by topic strand, not just right or wrong. A pattern usually emerges quickly: strong on number and ratio, consistently weaker on geometry, patchy on algebra. That's a genuinely actionable picture. An overall percentage never was.
Within a weak topic, it's worth asking whether the issue is not knowing the method at all, or knowing it but making errors applying it — these need different responses. A student who's never secured the rules for simplifying surds needs to learn the method; a student who knows the rules but makes sign errors under time pressure needs targeted practice and careful checking habits, not a fresh explanation of content they already understand.
A single mock can be misleading — a topic that happened to come up in an unfamiliar way, or a bad day, can look like a weakness that isn't really there. Checking whether the same strand shows up as weak across two or three separate assessments is a far more reliable signal than reacting to one result in isolation, similar to distinguishing a genuine gap from a one-off slip at any other stage of school, covered in how adaptive learning identifies maths gaps.
Under exam time pressure, students often skip a question they don't recognise rather than attempt it and get it wrong — which means a topic can look "not that bad" on a mock purely because it barely got attempted, not because it was handled well. It's worth checking blank or minimally-attempted questions separately from ones that were genuinely tried and got wrong, since they usually point to different problems.
Once weak strands are identified specifically, revision time can go directly towards them, rather than working through the whole specification in order regardless of what's already secure — the same principle covered in why doing hundreds of GCSE maths questions isn't always the best revision strategy.
Grasp Maths tracks performance by topic strand automatically, across every paper and practice session, so the picture of what's genuinely weak builds up over time rather than needing to be reconstructed by hand after every mock.
Try a free Grasp Maths practice session and get a strand-by-strand picture, not just a percentage.