A CBSE student has one board exam cycle to plan around. An IB, IGCSE, or A-Level student is usually juggling Internal Assessments, an Extended Essay, or coursework deadlines at the same time — and generic "start in Grade 11" advice ignores all of it.
Slot SAT prep into the wrong window and it either competes with the highest-stakes academic work of the year, or gets quietly abandoned the moment a coursework deadline wins. The fix isn't more hours — it's sequencing prep around each curriculum's actual load pattern, not a generic calendar that assumes every international curriculum works the same way.
Three different curricula, three different squeeze points. Here's the realistic window for each.
The Diploma's second year is where everything lands at once — Internal Assessments across up to six subjects, the Extended Essay, Theory of Knowledge, and the run-up to May finals. Grade 11, before IA deadlines start stacking, is the realistic window. IB Math AA/AI students usually bring a solid foundation that transfers well — the gap is rarely knowledge, it's the shift from IB's depth-over-fewer-problems rhythm to the SAT's speed-over-many-shorter-problems rhythm.
IGCSE exams typically wrap by May or June. The six-to-ten weeks right after results — before the next two-year program's coursework begins — is often the most genuinely open stretch a student sees for the next two years. No IAs, no coursework, no board exam pressure. It closes fast once term starts, so it's worth protecting deliberately rather than assuming "there'll be time during A-Levels or IB."
A-Level's defining feature is depth over breadth — most students take three subjects, occasionally four. A student doing Physics, Chemistry, and Further Maths has likely had less recent, less broad exposure to some SAT Math domains than a student from a curriculum with compulsory general math through the final year. Not a competence issue — a recency-and-breadth gap, straightforward to close if diagnosed early. Calendar-wise, the squeeze mirrors IB: Lower Sixth (Year 12) is the realistic window, before Upper Sixth fills up.
| Curriculum | Highest-Load Period | Realistic SAT Window | Key Risk If Ignored |
|---|---|---|---|
| IB Diploma | Grade 12 (IAs, EE, ToK, May finals) | Grade 11 | Prep collides with IA season and gets dropped |
| IGCSE | Final exam term | 6–10 weeks post-results | Assuming "time during A-Levels/IB" — that window is smaller than it looks |
| A-Level | Upper Sixth (Year 13) | Lower Sixth (Year 12) | Narrow subject combinations leave undiagnosed content gaps |
The General Principle
The same total number of prep hours produces very different results depending on when in the curriculum calendar they land. Prep that overlaps with IA deadlines, mock boards, or coursework crunch periods gets rushed or dropped — not from lack of discipline, but because the calendar genuinely has no room that month.
Grade 11, before Internal Assessment deadlines start stacking. Grade 12 is where IAs across every subject, the Extended Essay, Theory of Knowledge, and May finals all land at once — there's very little genuine slack left for SAT prep by then.
The six-to-ten weeks right after IGCSE results, before the next two-year program's coursework begins. It's often the most genuinely open stretch a student sees for the next two years, and it closes fast once term starts.
Lower Sixth (Year 12), for the same reason as IB — the final year fills up fast with coursework and exam preparation, leaving little room for SAT prep to compete for attention.
Yes. A-Level students with narrow, depth-focused subject combinations sometimes have less recent, less broad exposure to specific SAT Math domains than students from broader-curriculum backgrounds. It isn't a competence gap — it's recency and breadth — and it's straightforward to close once identified early.
Strongly recommended. Planning a schedule around an assumption like "5 months until applications means 5 months of usable prep time" is where most derailed prep plans start. A diagnostic mock gives you real data on where your child actually stands before committing to a timeline.
Run a free diagnostic mock first, then build the schedule around real data — not a guess about how much time is actually open.