You can work through every unit in DP1 and still arrive in DP2 with genuine gaps in your IB Math preparation—because schools don’t all teach the course in the same order, at the same depth, or on the same schedule. These aren’t effort failures. They’re sequencing artifacts, and they tend to stay invisible until you run a structured check against the official syllabus and the assessment objective verbs that actually appear in exam questions. The diagnostic workflow is straightforward: map your school’s delivery pattern, self-audit topic clusters, verify each “secure” label with AO-based mini-tasks, then drive a two-week past-paper sprint on the gaps that are actually blocking marks.
Three delivery patterns account for most of those gaps. One runs SL content in Year 1 and defers HL extensions to Year 2. Another compresses large topic clusters into short blocks. A third lets the assessment calendar set the agenda, pushing proof and advanced calculus to “later.” A practitioner-oriented syllabus breakdown for IB Math Analysis and Approaches HL flags several HL strands as worth auditing early for exactly this reason: proof (including induction), complex numbers, advanced calculus and optimization, differential equations, and extended probability/statistics are the strands most structurally prone to being deferred or compressed.
A school-published IA calendar for one recent IB cohort illustrates the underlying pressure concretely: it shows clustered Math AA/AI checkpoints, a Year 2 final IA due date, and an external assessments window all falling within the same period. In a calendar structured this way, late HL topics can easily get crowded out—not through neglect, but because the year’s obligations naturally compete for the same window. If your own school’s calendar looks anything like it, treat “we’ll cover it later” as a trigger to audit coverage now with the syllabus, AO language, and past-paper questions, rather than assuming the timing will work itself out.
Conduct a Topic-Cluster Self-Audit
A topic-cluster self-audit converts the full IB Math syllabus from a vague instruction to “revise everything” into a working gap map. For each small, testable cluster, you determine whether it’s securely covered, partially addressed, or effectively absent. The output is a list of clusters tagged with clear next actions—ready to drive your remediation sprint.
1. Define a tight topic cluster
Pick a slice of the syllabus small enough to test with one or two short AO-style tasks, but big enough that it shows up in past papers (for example, differentiation with tangent/normal lines, normal-distribution calculations, complex-number operations, or the structure of a proof by induction).
2. Pass 1 – Materials-based coverage check
Search your notes, slides, and course platform for evidence that this cluster was explicitly taught. Look for at least a taught explanation plus some practice or an assessed task. If you cannot find any concrete trace, mark the cluster Absent without arguing from memory.
3. Pass 2 – AO-style cold performance check
Write one mini-task using assessment-objective verbs such as apply, solve, justify, or construct, matching the way the cluster appears in the official guide. Attempt it cold, with no notes, under a 10–15 minute cap, then judge your work.
4. Classify status using one rule-set
Securely covered means you have teaching/practice evidence and your cold mini-task is clean. Partially addressed means the materials exist but your cold attempt is only partial or relies heavily on prompts. Absent means you either have no material evidence or you were effectively stuck on the mini-task and would need full re-teaching.
5. Attach only three allowed next actions
For Absent, plan a rapid primer followed immediately by IB-style questions. For Partially addressed, plan consolidation drills tied directly to what went wrong in the cold attempt. For Secure, plan only light mixed-topic practice to keep the skill warm.
6. Lock the results into a tracker
Record each cluster, the evidence you found, your cold-task outcome, its status, and the chosen next action in a simple tracker. Do not upgrade a topic from Absent or Partially addressed until you can repeat the AO-aligned mini-task cleanly.
The cold AO mini-task is the real gatekeeper for each label, and that’s the point. Exam performance depends on what you can deploy under time pressure without notes—not on whether you remember a chapter existing. The gap between those two things is precisely what mock exams expose, usually at the worst possible moment. Treat any cluster that cannot survive an honest cold attempt as not yet secure, regardless of how formally it was taught, and run this audit early in DP2—so the gaps you find still leave you time to close them before past papers turn your study plan into triage.
Verify Exam-Readiness Using AO Language
Recognizing a method and being able to apply it are not the same skill—and the official IB assessment objectives encode that distinction precisely. The course guide’s AO verbs—demonstrate understanding, apply, solve, construct, justify—define the actual standard you’ll be marked against. If you can identify a method in your notes but can’t execute what the verb requires, that topic isn’t secure. It’s just familiar.
For every topic cluster in your audit, pair its content description from the syllabus with one or two relevant AO verbs, then use that pair to write a mini-task. The target is deployment: can you select and execute the right method under mild time pressure, explain or justify your reasoning when required, and handle the standard variations that show up in past-paper questions? Those three demands, taken together, tell you whether a cluster is genuinely exam-ready.
Take proof by induction. A secure label should require a complete AO-aligned write-up: a clearly verified base case, a correctly stated inductive hypothesis, algebra that transforms the n to n + 1 step without major errors, and an explicit concluding sentence that closes the argument. When you can do that cleanly, without substantial scaffolding, that cluster is exam-ready.
Tailor Your Remediation by Gap Category
Once each topic cluster is labeled, the three status categories translate into three distinct remediation problems. Absent clusters are true never-taught areas—no explanation, no practice, no trace in your materials. Partially addressed clusters have been taught but not drilled to AO standard. And then there’s a third failure mode that often still registers as Partially addressed in a cold mini-task: skills that work when prompted in isolation but collapse when embedded in a mixed or unfamiliar question structure—covered, technically, but not yet integrated.
Turn your gap map into an order of operations rather than an undifferentiated to-do list. First, fix Absent clusters that appear frequently in past-paper probes, because being unable to start these question types blocks marks immediately. Next, target Partially addressed skills where the same errors keep recurring; they tend to improve quickly and pay off across multiple papers. Then prioritize integration gaps, where you can execute a method when told but can’t recognize when it applies; mixed-topic practice here unlocks more marks than additional content intake. One rule overrides all three: if your IA deadlines and exams cluster into the same term, pull forward any HL-only or deepened strands—proof techniques, complex numbers, advanced calculus and optimization, differential equations, extended probability/statistics—so they don’t arrive unaddressed in your most deadline-heavy weeks.
For Absent topics, use a rapid-primer sequence rather than trying to rebuild an entire unit from scratch. Start with concise definitions, work through a small number of well-chosen worked examples that mirror the official syllabus, and move as quickly as possible into short sets of exam-style questions. As soon as you can meaningfully attempt standard problems, shift focus from exposition to practice.
Partially addressed areas benefit from consolidation routines tuned to the exact failure modes your cold AO tasks revealed. A 2026 teaching blog on common IB Math mistakes reports that many students have technically encountered formula booklet use, calculator functions like regression and normal distribution, and basic calculus—yet still lose marks on booklet navigation, keying in distributions, and derivatives and tangent lines. Those errors reflect the partially addressed pattern: the material was visited but not drilled to the point where it holds under assessment conditions. That profile makes each of them a good candidate for short, focused consolidation work: timed booklet lookups, calculator reps on the same function until it’s automatic, and deliberate practice on the specific calculus slips that keep recurring.
Covered but not integrated strands require a different kind of work: practice in recognizing when a method applies, not just executing it when told. Mixed-topic sets and past-paper questions that cut across multiple methods train this recognition step far more effectively than single-topic drills. Peer accountability helps keep these sessions consistent, and targeted Q&A is most useful when it focuses on specific bottlenecks that haven’t shifted after your own attempts. Revision Village—which provides exam-focused resources across 14 IB subjects at SL and HL and dedicated IGCSE Mathematics courses—can support this stage too, provided you treat its resources as tools to close clearly labeled gaps rather than an invitation to restart from scratch.
Launch a Two-Week, Past-Paper–Driven Sprint
A two-week remediation sprint works best when it’s anchored to real IB-style questions from the start. Use recent official past papers as coverage probes: scan for questions linked to your flagged clusters and classify each as can attempt, cannot attempt, or attemptable with one missing tool. From there, follow a simple two-phase pattern. Week 1 focuses on single-topic probes—identify and patch the smallest missing concept or procedure with a rapid primer plus a short drill set. Week 2 shifts to mixed-topic, timed sets that deliberately combine recently repaired skills with already secure ones, testing both integration and speed.
- Log each study block with five fields: Gap ID, the specific tool you are working on today (concept, procedure, notation, calculator function, or booklet use), whether you attempted at least one probe question cold, your result (stuck, partial, or clean), and one-sentence next micro-step.
- Every third day, spend 10 minutes sorting all tracked gaps into three piles: (A) now attemptable, (B) still blocked by one clearly named missing tool, or (C) still blocked by multiple missing tools.
- Use a clear exit rule: you are done with a gap when you can attempt relevant questions in mixed sets, under realistic time pressure, at least twice without repeating the same error type.
Give high-priority gaps daily 1–2 hour blocks during the sprint, but only upgrade a status when AO-aligned performance actually changes—not just because you reviewed notes. If a gap stays in the “multiple missing tools” category after two focused cycles, that’s your signal to escalate: get targeted help on the prerequisite ideas blocking that specific area. Meanwhile, keep narrowing and reordering the remaining gaps that are already moving—don’t let one stuck cluster stall the rest of the sprint.
Make Coverage Differences Manageable
Coverage gaps in IB Math are a school-sequencing problem—but they only stay unmanageable if you don’t surface them until mocks. A structured diagnostic workflow converts that institutional variable into something you can actually control: map your school’s delivery pattern, audit topic clusters against the official syllabus, verify each with AO-aligned tasks, and structural gaps stop being surprises and start being a prioritized list with a clear order of work.
Run the self-audit now. Write honest AO-style mini-tasks for each cluster, then drive a focused two-week sprint from the gaps that genuinely block questions. How your school sequences the course isn’t something you chose. What you do with that information is.
