In the run-up to exams, most of us know roughly where our class is weak. We have a gut sense — “they’re shaky on titrations”, “the essays are thin”. But a gut sense isn’t a plan. It tells you to worry; it doesn’t tell you what to teach on Tuesday. The gap between a vague worry and a targeted reteach is a method — a repeatable procedure you run on the evidence you already have, that ends with a ranked list of the things actually worth fixing in the weeks you have left.

This guide is that method. It’s not about how a student finds their own weak topics, and it’s not another piece on early-warning detection or dashboard data-literacy (those are inputs — I’ll link them where they fit). This is the process itself: how to identify learning gaps before exams at the level of a whole cohort, framed for the part of the year where time is the constraint and every reteach has to earn its place.

Why “gut feel” isn’t a gap analysis method

The problem with intuition is that it’s biased toward the loud and the recent. You remember the student who argued, the topic you taught last week, the question one kid bombed in front of you. You forget the quiet middle of the class and the topic from October that’s silently rotted. A proper gap analysis method corrects for that by forcing you to look at all the evidence, sorted in two ways your memory can’t manage: by topic, and by skill.

It also forces a distinction that matters enormously for exam prep — the difference between a gap the whole class shares and a gap that’s specific to a handful of students. Those need completely different responses, and gut feel blends them into one anxious blur. The five steps below pull them apart.

The five-step method to find learning gaps before exams

Step 1: Gather the evidence — don’t rely on one source

Before you analyse anything, assemble the evidence base. The single most common mistake is leaning on one mock and treating it as the truth. One paper on one bad day is noisy. Pull together, instead:

• the most recent mock or full past paper
• the last two or three pieces of marked classwork or homework
• any topic tests or end-of-unit checks from the term
• low-stakes signals — what they ask in lessons, where hands stop going up

You’re not marking again here; you’re collecting what’s already marked into one view. The point of multiple sources is to separate a real, persistent gap from a one-off wobble. If a weakness shows up in the mock and in homework from a month ago, it’s real. If it only appears once, hold it loosely. (Auto-marked work helps here precisely because it gives you several clean data points without several lost evenings — more on that below.)

Step 2: Read the evidence by topic and by skill

This is the step most teachers skip, and it’s the one that makes the method work. Don’t just ask “which topics did they lose marks on?” Read the same evidence twice, through two different lenses:

• By topic. Map lost marks onto the specification. Where on the syllabus is the bleeding? Electrolysis, quadratic graphs, source evaluation — content-shaped gaps.
• By skill / command word. Now ignore topic and sort the same errors by what the question asked them to do. Are they fine on “state” and “describe” but collapsing on “explain”, “evaluate”, “compare”? Do they lose marks for not addressing the command word, for poor working, for running out of time?

The reason both lenses matter: a topic gap and a skill gap need opposite fixes. A topic gap means reteach the content. A skill gap means the content is fine but they can’t show it under exam conditions — and no amount of reteaching titrations fixes a student who can’t structure a six-mark “explain”. In my experience, the skill-shaped gaps are the most under-diagnosed and the highest-yield to fix late in the year, because they cut across every topic at once. (Tracking weaknesses along both axes over time is its own discipline — see tracking strengths and weaknesses by topic for an IGCSE class.)

Step 3: Separate class-wide gaps from individual gaps

Now sort what you’ve found into two buckets, because they get two different responses:

• Class-wide gaps — where most of the class lost marks on the same thing. These are teaching problems. They belong in front-of-class time: a reteach, a worked-example lesson, a technique clinic for everyone.
• Individual gaps — where a specific student or small group struggles with something the class as a whole handled. These are intervention problems. Whole-class reteaching wastes everyone else’s time; these want targeted support, a different explanation, or a short small-group session.

Getting this split wrong is one of the most expensive mistakes in exam prep. Reteach the whole class something only five students needed and you’ve burned a lesson the other twenty-five didn’t need — time you don’t have in the run-up. Conversely, leave a genuinely class-wide gap to “individual revision” and it never gets fixed. If you’re already getting early signals about which students are slipping, that detection work feeds straight into this bucket — see spotting struggling IGCSE students before the mock.

Step 4: Prioritise by impact and time left

You will always find more gaps than you can fix. This is the step that turns a list into a plan, and it’s the one anxious teachers most often skip — they try to fix everything and fix nothing well. Rank every gap by two factors:

• Impact — how many marks are at stake, and across how many students? A gap that costs eight marks in a topic that appears on every paper outranks a niche one worth two marks that may not come up.
• Time-to-fix — some gaps are quick wins (a command-word habit you can drill in one lesson); others need sustained reteaching you may not have time for.

The sweet spot is high-impact, low-time-to-fix — the gaps that move the most marks for the least teaching. Do those first. Be honest about the high-impact, high-time gaps too: with limited weeks, decide deliberately which you commit to and which you triage out, rather than half-attempting all of them. This is the same prioritisation logic as reading a class performance dashboard and deciding what to act on first — except here you’re applying it to the whole gap list, not a single dataset.

Step 5: Target the fix — then re-check

A gap analysis isn’t finished when you’ve found the gaps; it’s finished when you’ve confirmed they closed. So:

1. Target each prioritised gap with the matching response — class reteach for class-wide, small-group or individual support for the rest.
2. Re-check with a short, focused assessment a week or two later — not another full mock, just a handful of questions on exactly the gap you taught. Did the marks move?

This closing loop is what separates a method from a one-off audit. A re-check that shows the gap is gone frees you to move down the priority list. One that shows it’s still there tells you the fix didn’t work — and finding that out before the exam is the entire point of doing this early. Build these re-checks small and cheap so re-testing isn’t a fresh ordeal each time.

Where the evidence base comes from

The whole method stands or falls on Step 1 — having clean, multi-source evidence to read. If gathering it means hand-marking five sets of work and tallying errors into a spreadsheet, you’ll do it once and never again, which is exactly why most gap analysis stays at gut-feel level. (If you’ve sworn off spreadsheets entirely, the same end can be reached without one — see identifying gaps at A-Level without a spreadsheet.)

A free Tutopiya for Teachers account is built to make Steps 1 and 2 fast: set work that auto-marks to the mark scheme, and the class and per-student analytics surface gaps already sorted by topic and by question type — the two lenses Step 2 needs — so the evidence assembles itself. You still do the thinking that matters: separating class-wide from individual, prioritising, and re-checking. But the grunt work of gathering and sorting, the part that usually kills the habit, stops being grunt work. It’s free to start with one class — though the method is the point, and it works on whatever evidence you already collect.

Putting the method into a calendar

This gap analysis isn’t a one-time event before the final exam — it’s a loop you run after each mock through the run-up. The natural rhythm is: run a mock, apply the five steps, target the top gaps, re-check, repeat with the next mock. That cadence dovetails with a deliberate sequence of mocks across the year — which is its own planning job, covered in how to set IGCSE mock exams term by term. The mock plan generates the evidence; this method turns each round of evidence into a reteach plan.

FAQ

How do I identify learning gaps before exams without just guessing? Run a repeatable method rather than relying on gut feel. Gather evidence from several sources (a recent mock, recent marked work, topic tests), read it twice — once by topic and once by skill or command word — separate gaps the whole class shares from gaps specific to individuals, prioritise by impact and time remaining, then target the top gaps and re-check that they closed. The procedure is what stops you defaulting to the loud, recent worries your memory over-weights.

Why analyse gaps by skill as well as by topic? Because a topic gap and a skill gap need opposite fixes. A topic gap means reteach the content. A skill gap — losing marks on “explain” or “evaluate” questions, ignoring command words, running out of time — means the knowledge is there but they can’t show it under exam conditions, and reteaching content won’t help. Skill-shaped gaps cut across every topic at once, so they’re often the highest-yield thing to fix late in the year.

How is this different from a student finding their own weak topics? A student gap-check is about one learner’s revision priorities. This is a teacher’s cohort method: you’re analysing the whole class to decide what to teach — what goes into front-of-class reteaching versus targeted intervention for a few students — and how to spend limited lesson time before the exam. The separation of class-wide from individual gaps only makes sense from the teacher’s seat.

How many sources of evidence do I really need? At least two or three, so you can tell a persistent gap from a one-off bad day. A weakness that appears in a mock and in homework from a month ago is real and worth teaching; one that shows up once might just be noise. Relying on a single mock is the most common way to mis-target your reteaching.

How do I know my fix actually worked? Re-check. A week or two after teaching to a gap, set a short, focused assessment — just a few questions on exactly that gap, not a whole new mock — and see whether the marks moved. Confirming a gap has closed (or hasn’t) before the real exam is the whole reason for running this method early rather than discovering the problem on results day.

The bottom line

Knowing your class is “weak somewhere” is not a gap analysis. Identifying learning gaps before exams properly means running a method: gather multi-source evidence, read it by topic and by skill, split class-wide gaps from individual ones, rank by impact and time left, then target and re-check. Done as a loop through the run-up, it converts the anxiety of “are they ready?” into a ranked, finite list of fixes you can actually deliver — which is the only version of gap analysis that changes a grade rather than just predicting one.

Surface your class’s gaps by topic and question type — free with one class →

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