You can usually tell which of your IGCSE students is struggling. What’s much harder to hold in your head is the other dimension: which topics your whole class is weak on, and whether a given weakness belongs to three students or to twenty-five. That second picture is the one that decides what you reteach, what you can move past, and where your limited revision time should go — and it’s almost impossible to assemble from a paper mark book or a gut feeling.

This guide is about building that picture deliberately: how to track strengths and weaknesses by topic across an entire IGCSE class, so you can see at a glance where the cohort is solid and where it’s collapsing. It’s written for the individual teacher mapping their own class, not a school running a data department. The core idea is a topic map — think of it as a matrix or heatmap — and the skill is learning to read it in both directions.

Why a class average hides your real problems

A column of overall percentages tells you who’s doing well and who isn’t. It tells you almost nothing about what to teach next. A student sitting on 62% might be rock-solid on six topics and in freefall on two — and the next student on 62% might have the exact opposite profile. The average flattens both into the same dull number, and the specific, fixable gaps disappear into it.

Topic-by-topic IGCSE tracking does the opposite. Instead of one number per student, you hold one number per student per topic. That’s the difference between knowing “the class is averaging a 5” and knowing “the class is fine on stoichiometry but two-thirds of them can’t balance redox equations.” Only the second statement tells you what to do on Monday. The whole point of tracking class strengths and weaknesses by topic is to convert vague unease into a specific teaching decision.

The topic map: a matrix, not a list

Picture a grid. Down the side, one row per student. Across the top, one column per topic or sub-topic on the IGCSE specification you’re teaching. Each cell holds how that student has performed on that topic across your recent checks — a percentage, a colour, a simple strong/shaky/weak band. That grid is your topic map, and it’s the single most useful artefact for planning the back half of a course.

The map doesn’t come from one big test. It’s built up from repeated, narrow checks over time — each one tagged to the topic it covers — so that cells fill in gradually and a pattern emerges. A single quiz gives you one column. Six weeks of short topical quizzes give you a readable heatmap. This is why short, single-subtopic checks are so valuable: each one cleanly populates a column without muddying the others. (Building those is its own craft — see creating topical IGCSE tests one subtopic at a time.)

Two things make a topic map trustworthy:

• Consistent tagging. Every question has to be attributed to a topic and, ideally, a sub-topic, or the columns blur together. “Organic chemistry” is too coarse to act on; “naming alkanes” and “addition reactions of alkenes” are columns you can actually reteach.
• Enough data points per cell. One question on a topic is a coin flip. Three or four questions across a couple of checks turn a cell from a guess into a signal. Sparse cells are the most common reason a map lies to you.

Reading the map: rows versus columns

A topic map is only useful if you read it in both directions, because each direction answers a different question.

Reading down a column — is this a class-wide weakness?

Scan a single topic column down every student. If most of the class is red on the same topic, you are not looking at a set of individual problems — you’re looking at your teaching of that topic, or at genuinely hard material the cohort hasn’t absorbed yet. Either way, the fix is collective: reteach it to everyone. A column that’s mostly weak is the clearest signal a topic map gives you, and it’s the one that saves the most time, because reteaching once to the whole class is far more efficient than twenty-five individual conversations.

This is the insight you can’t get from rows alone. Looking student by student, a topic that everyone is shaky on just looks like everyone having an off day. It’s only when you turn the grid sideways and read the column that the pattern resolves into “this is a whole-class gap.”

Reading across a row — is this an individual weakness?

Now scan one student across all topics. A student who is green almost everywhere but red on two specific columns has a targeted, individual gap — and that’s an intervention aimed at them, not a reteach for the room. Setting practice for the whole class on a topic only three students struggle with wastes everyone else’s time and bores the secure ones.

So the same map answers two questions with one read:

• Mostly-red column → reteach to everyone (class-wide weakness, collective fix).
• Isolated red cells in otherwise-green rows → targeted intervention (individual weakness, individual fix).

Telling these two apart is the entire payoff. Acting on individual gaps with whole-class reteaching wastes your strongest students; acting on class-wide gaps with individual tutoring wastes you. The map keeps you from doing either.

Turning the map into a plan

Once you can read it, the topic map drives three concrete decisions.

1. Reteaching priorities. Rank your reddest columns. The topic that’s weak across the most students, and carries the most marks on the paper, goes first. A heatmap makes this triage almost automatic — the worst columns are literally the most coloured-in. (For how to prioritise when several signals compete for attention, see reading a class performance dashboard and what to act on first.)

2. Curriculum emphasis next time round. A topic your class collapses on year after year is telling you something about where it sits in your scheme of work — too rushed, too early, or taught before a prerequisite was secure. The map is a record you can carry into next year’s planning, not just this term’s revision.

3. Targeted assignments for the isolated gaps. For the individual red cells, set practice aimed precisely at that topic and pitched at that student’s level, instead of generic “revise more.” (Assigning past-paper questions by topic and difficulty covers how to target it without building everything by hand.)

This map also complements early detection rather than replacing it. Spotting which students are slipping before the mock is a different read of your data — the row-and-trend view — covered in spotting struggling IGCSE students before the mock. The topic map adds the column view: not just who’s at risk, but on what, across everyone at once.

The honest caveats

A topic map is a powerful planning tool, but it’s only as good as what feeds it.

• Garbage tagging, garbage map. If questions aren’t accurately attributed to topics, the columns are meaningless. Get the tagging right before you trust the colours.
• Watch the data density. A column built on one question per student isn’t a class-wide weakness — it’s a small sample. Wait for a few checks to accumulate before you reteach a whole unit on the strength of one quiz.
• A weak column isn’t always a teaching failure. Sometimes a topic is genuinely hard and the cohort needs a second pass — that’s normal, not an indictment. The map tells you where to spend time, not why the gap exists; the why is still yours to judge.
• Don’t reteach to the average and bore the secure students. Even on a mostly-red column, the green students don’t need the full reteach. Use the map to differentiate, not to flatten everyone into the same lesson.

How this looks in practice

Maintaining a topic map by hand is the hard part — re-tagging every question, filling every cell, re-colouring it after each check. That’s where it usually falls apart, not in the reading.

Tutopiya’s platform for teachers builds the map for you: past-paper work is auto-marked and tagged by topic and sub-topic, so every check you set populates the grid automatically. You get a class view (the columns — where the whole cohort is strong or weak) and a per-student view (the rows — each student’s individual profile) from the same data, updated as work comes in. The mostly-red columns surface the class-wide weaknesses to reteach; the isolated red cells flag the individual gaps to target. It’s free to start with one class, which is enough to build a real topic map for a single cohort and see whether the heatmap view changes how you plan.

FAQ

How do I track strengths and weaknesses by topic across a whole IGCSE class? Build a topic map — a grid with one row per student and one column per topic — and fill it from short, repeated checks that are each tagged to the topic they cover. Read it in two directions: down a column to see class-wide weaknesses, across a row to see an individual student’s gaps. The map only works if questions are accurately tagged by topic and each cell has a few data points behind it, not just one question.

How do I tell a class-wide weakness from an individual one? Read the topic column. If most students are weak on the same topic, it’s a class-wide gap — reteach it to everyone. If a topic is red for only a handful of students who are otherwise fine, it’s an individual gap — set targeted practice for those students instead. The same map answers both questions depending on whether you read columns or rows.

Why isn’t a class average enough for topic-by-topic IGCSE tracking? An average gives one number per student and hides the shape underneath it. Two students on the same overall mark can have opposite topic profiles — strong where the other is weak. Only a per-topic breakdown tells you what to reteach, because it shows which specific topics are dragging marks down across the cohort.

How many checks do I need before the topic map is reliable? Enough that each topic column has more than one or two questions behind it — usually a few short topical checks over several weeks. A column built on a single question is a small sample, not a signal. The map gets more trustworthy as cells fill in, which is why frequent narrow checks beat one big test for this purpose.

Does building a topic map mean more marking? Only if you mark by hand. The map is just a by-product of checks you’d set anyway, provided they auto-mark and tag each question by topic. When that happens, every quiz you run populates the grid automatically and the class strengths and weaknesses view maintains itself.

The bottom line

Knowing who’s struggling is half the picture; knowing what the whole class is weak on is the half that decides your teaching. Build a topic map from repeated, well-tagged checks, then read it both ways — columns for the class-wide gaps you reteach to everyone, rows for the individual gaps you target one student at a time. Do that, and revision stops being a scramble and becomes a list of the right topics in the right order.

Build a topic-by-topic map for one class, free →

Ready to Excel in Your Studies?

Get personalised help from Tutopiya's expert tutors. Whether it's IGCSE, IB, A-Levels, or any other curriculum — we match you with the perfect tutor and your first session is free.

Book Your Free Trial