Burn through your best full papers in the first two weeks of revision, and the simulation phase arrives with nothing genuine left to run on. That’s not a discipline problem. It’s an orchestration problem. Most IB Math AI SL students have plenty of question banks, topic sets, and quiz resources. What they lack is a clear framework for when each resource serves its purpose. A six-week plan that moves from a skills audit in Weeks 1–2, through targeted remediation in Weeks 3–4, to timed full-paper simulation in Weeks 5–6 fixes that. However long you have—three, six, or twelve weeks—full timed papers still belong at the end, with at least two fresh mocks protected for the final stretch.
Here’s the week-by-week cadence that makes it work, including the non-negotiable sequencing gate that determines when you’re actually ready to advance.
Setup and logging (15 minutes, once): create a one-page attempt log—paper or notes app—with fields for date, resource/type (quiz, ladder, timed section, full paper), topic tag, outcome (✓ / partial / ✗), error type (concept / tech / interpretation / time), next action (one drill or one concept revisit), and re-test date. At the same time, mark at least two untouched full papers as Week 6-only fresh-paper reserve.
Review cadence: after each session (2 minutes), log only missed or guessed items and assign exactly one next action plus a re-test date. At the end of each week (about 15 minutes), count repeats by topic tag and error type, update your ranked gap list, and decide whether to advance the phase or repeat the week’s intent. After each full-paper simulation (20–30 minutes), create an error-type breakdown and a brief fix plan before the next run.
Non-negotiable sequencing gate: do not start any full-paper timed mocks until Weeks 1–2 have produced a ranked gap list with confirmed repeats from multiple topic sets on different days. Diagnostic work must clearly come before simulation.
Decision and interpretation rules: treat two or more repeats of the same weakness across days as a real gap to promote. If an error type repeats twice within the same skill, change the tool you’re using—move from mixed sets to a revision ladder, from a ladder to worked examples, or from full papers to shorter timed sections—rather than just increasing volume. When time is the dominant error type, stop adding topics and adjust pacing and triage rules under timed conditions. If fatigue is high in Weeks 5–6, protect simulation quality by swapping one planned full paper for a targeted timed section rather than forcing a low-energy full run.
Week 1 — Skills Audit
Do: short quizzes and topic-filtered question bank sets across statistics and probability, financial mathematics, calculus applications, and modeling.
Output (end of week): a first-pass ranked gap list with initial error tags.
Gate to Week 2: you can name your top five to eight suspected gaps and describe what ‘missing’ each one looks like.
Week 2 — Confirm and Prioritize
Do: re-test the same top five to eight gaps with new items spaced across days, plus a small mixed set to catch surprises.
Output (end of week): a ranked top three to five gaps that each show at least two repeat misses or fragile performances, with an initial resource choice—worked examples versus ladder versus targeted drills—for remediating every one of them.
Gate to Week 3: each of your top three gaps has clear repeat evidence and a named remediation resource.
Week 3 — Targeted Remediation, Pass One
Do: focus on revision-ladder style practice and worked examples only for the ranked gaps, keeping sets short with immediate feedback.
Output (end of week): for each gap, a decision of ‘fixed enough’ or ‘still failing’ based on a fresh re-test.
Gate to Week 4: you have a short list of still-failing topics that will remain your core priorities.
Week 4 — Targeted Remediation, Pass Two
Do: give stubborn gaps a second ladder pass and add timed sections that stress-test pacing and technique without spending full papers.
Output (end of week): a brief mock-readiness list naming your likely time-pressure points and top two recurring error types, plus a chosen first full paper to simulate.
Gate to Week 5: you can state your main time-pressure points, your top recurring error types, and which full paper you’ll sit first.
Week 5 — First Simulations
Do: sit one timed full paper early in the week and a second full paper later on, or, if fatigue is an issue, pair one full paper with a shorter targeted timed section under authentic exam conditions.
Output (end of week): for each simulation, an error-type breakdown in your log and a short fix plan before the next run.
Gate to Week 6: you can identify the dominant error types and pacing issues that appeared across your first simulations.
Week 6 — Final Simulations and Consolidation
Do: run one or two more simulations—either two full papers or one paper plus a focused timed section—using the fresh-paper reserve you protected at the start.
Output (end of week): a concise last-week priorities list that pinpoints the single biggest remaining correction for content, technology process, interpretation habits, and pacing.
Gate to exam week: you have a clear, limited set of last adjustments drawn from that priorities list.
Scaling Rule-Set (for 3–12 Week Plans)
Always keep full-paper simulation in the last two weeks, regardless of how early you start. With eight to twelve weeks, expand Weeks 1–4 by adding extra audit-and-confirm cycles and more passes up your revision ladder rather than pulling full papers forward. With only three to five weeks, run a compressed audit over several days, remediate only your top three gaps, and still reserve at least two untouched full timed simulations for the end instead of spending scarce fresh papers in week one.
Weeks 1–2 — Conducting a Skills Audit Before Touching a Mock Paper
The temptation at Week 1 is to sit a full paper and see where you land. Don’t. A cold mock gives you a score with no real context—you can’t yet tell whether a missed question signals a conceptual gap, a technique slip, or a misread under pressure. The better move is topic-filtered quizzes and question bank sets across statistics and probability, financial mathematics, calculus applications, and modeling.
The goal isn’t high quiz scores. Research in university calculus has shown that spaced retrieval—retesting topics across several short quizzes on different days—can feel harder and produce lower scores than massed practice, yet leads to better long-term retention. That’s the audit method, not a warm-up for the real work. By the end of Week 2, you want a ranked list of repeated gaps with concrete evidence, while every full mock remains unopened for the simulation phase.
For every miss or guess, record: date, resource (quiz/ladder/mock), topic, outcome (✓ / partial / ✗), error type (concept / tech / interpretation / time), next action (one drill or one concept revisit), and re-test date.
After each session, spend two minutes logging only missed or guessed items—don’t log correct questions.
After each timed mock (this rule applies in Weeks 5–6; allow 20–30 minutes per review): tally errors by type, focus on the highest-frequency type for the next 48 hours, and switch resources if the same error type repeats in the same skill. When time management is the dominant error type, do not add new topics—adjust your pacing and triage rules for the next simulation instead.
Weeks 3–4 — Remediating Gaps With Structured Ladder Practice
By Week 3, your ranked gap list should be doing the thinking. That list—not general familiarity with the syllabus, not gut instinct—dictates what you study. Revision Village, a platform built specifically for IB Mathematics AI SL Practice Exams, explicitly separates topic quizzes, a structured revision ladder, and full mock exams, treating full papers as the final stage reached only after quiz and ladder work. Treat that architecture as a design signal rather than a convenience feature. In Weeks 3–4, most of your time belongs inside ladder-style problem sets and worked examples tied directly to the gaps your log keeps flagging.
Match each gap to the right tool so remediation stays precise. When the concept itself feels unclear, work through examples first to rebuild understanding before touching ladder items. When you recognize a topic but keep making execution slips, prioritize ladder questions with immediate checking, then schedule a spaced re-test a few days later. For interpretation mistakes, practice rewriting the prompt in your own words before calculating. In Week 4, test your fixes with short timed sections that mix your target topics—but keep full papers off the table. The simulation phase earns its value precisely because those papers haven’t been seen before.
Weeks 5–6 — Timed Simulation and Structured Post-Mock Review
Weeks 5–6 are for treating past papers as simulations, not as another source of random practice. Plan backwards from your exam date so these weeks contain your most realistic runs—recent papers, exact time limits, the tools you’ll use on the day. Practitioner guidance on IB Math exam strategies reinforces this: full timed papers earn their value when reserved for this late stage, functioning as genuine dress rehearsals rather than early, unfocused runs.
A raw score from a mock tells you how you did. It doesn’t tell you what to do next. After each timed paper, review every missed or guessed question and classify it by topic and error type—concept, technology, interpretation, or time. Add only those items to the same compact log you’ve been using since Week 1 so you can see patterns building across days. The goal is a short, actionable picture of why marks were lost and which weaknesses are still active under pressure.
Use that picture to choose the next intervention, not just the next paper. Conceptual gaps warrant a brief return to topic-level resources, then a re-test after a little spacing. Technology errors call for a focused calculator or software drill followed by a similar question under time. Interpretation failures respond to the practice of translating a question into a single sentence—what is actually being asked—before calculating. If time management is the main problem, change your pacing and triage rules for the next simulation rather than adding new content. If the same error type keeps repeating across mocks, change the kind of practice before you sit another full paper.
Protecting Your Best Materials — Resource Exhaustion and Budget Planning
The risk isn’t running out of practice questions—there are plenty of those. It’s arriving at Weeks 5–6 to find your best simulation materials have already been spent as diagnostic tools, leaving nothing genuinely untouched for the stretch where novelty carries the most weight. Protect at least two unopened full papers from the start of the plan. Earlier in the cycle, use past papers as question sources rather than full runs—pull problems by topic or error type to support remediation. Grinding through papers chronologically builds familiarity with formats and questions in a way that quietly undermines the simulation value later.
For most of the diagnostic and remediation phases, free or lower-cost materials are sufficient: topic quizzes, mixed question banks, and worked solutions. Premium full-length mock packages deliver their highest return once you already know your main gaps and need to practice decisions under real pressure. Save those materials for Weeks 5–6, and what looks like a budgeting decision turns out to be the same sequencing logic applied to resources—protecting what’s most useful until the moment it can actually deliver.
Orchestrated Prep as a Decision Architecture
Students who peak in the exam room aren’t always the ones who practiced most. They’re often the ones who still had something genuinely fresh to simulate with in Week 5.
That sequencing is what keeps topic quizzes, ladder sets, and full papers doing the jobs they were designed for. Your log and ranked gap list tell you when to advance, which weaknesses to prioritize, and how to respond after each attempt. Follow the sequence, and every session ends with a concrete next action.
Your strongest materials stay fresh for the phase where they matter most. When exam week arrives, you’ll know exactly what still needs fixing—not just how many papers you’ve sat.
