How to Build an IGCSE Revision Timetable That Actually Works
Every failed revision plan dies the same death: an over-ambitious timetable built in a burst of motivation, abandoned by day four, followed by guilt-revision with no structure at all. The fix isn't more discipline — it's a timetable designed around how memory and motivation actually work. Here's how to build one that survives contact with real life, whether you're prepping for mocks, the November series, or May/June 2027.
- Plan blocks, not hours: 25–40 minutes, one subject, ending with retrieval — never "3–6pm: Chemistry".
- Allocate by weakness × exam weight, not by fondness — your weakest heavily-tested topics get the most slots.
- Build in spaced returns: every topic reappears ~2 days, ~1 week and ~1 month after first study.
- Schedule one timed, marked past paper per week from day one — rising to two in the final month.
- Plan at 80% capacity. A timetable with slack survives a bad day; a perfect one dies on it.
Step 1: audit before you allocate (one honest hour)
Rate every topic in every subject red/amber/green — by testing yourself, not by feeling. Then weight by what's actually examined: our data shows exam questions concentrate hard in a few chapters (in Maths 0580, Number + Algebra are ~68% of all questions; Chemistry, Physics and Biology have their own maps). Your priority list is simply: red × high-weight first, green × low-weight last.
Step 2: build the weekly skeleton
| Mon | Tue | Wed | Thu | Fri | Sat | Sun | |
|---|---|---|---|---|---|---|---|
| Block 1 | Maths (red topic) | Chemistry (red) | Maths (red) | Biology (amber) | Chemistry (red) | Timed past paper | — |
| Block 2 | Biology (amber) | English practice | Physics (amber) | Maths (spaced return) | Physics (red) | Mark it + fix list | Flashcard sweep |
| Block 3 | Flashcards 15m | Maths (spaced return) | Flashcards 15m | Chemistry (spaced return) | Flashcards 15m | — | Buffer / catch-up |
The rules encoded in that grid:
- Hardest subject in block 1, when energy is highest — never "warm up" on easy topics.
- Spaced returns are scheduled, not hoped for: Thursday revisits Monday's topic, next week revisits this week's. That's the forgetting-curve schedule doing its work.
- Saturday is sacred: one full paper under time, marked the same day against the scheme, dropped marks becoming next week's red topics. This one habit outperforms everything else on the grid.
- Sunday holds slack. Life happens; the buffer absorbs it. No buffer → one missed day → "the plan is ruined" → collapse.
Step 3: scale it to your runway
| Time left | Blocks/day | Past papers | Focus |
|---|---|---|---|
| 3+ months | 2–3 | 1/week | Full syllabus in spaced cycles, weighted by the data |
| 6–8 weeks (mocks / resit) | 3–4 | 1–2/week | Red × high-weight topics only; perfection is cancelled |
| 2–3 weeks | 4–5 | 3/week | Papers ARE the revision — mark, fix, repeat |
| Final week | — | ~1/day per priority subject | Timed papers + re-testing the exact marks dropped |
FAQ
How do I make an IGCSE revision timetable?
How many hours a day should my timetable have?
When should I start my revision timetable?
Should the timetable include days off?
A revision timetable isn't a contract with your ideal self — it's infrastructure for your ordinary self on an ordinary Tuesday. Blocks not hours, weakness-times-weight, scheduled returns, a weekly marked paper, and slack for real life. Build that grid once and the only remaining job is the one no timetable can do: sit down and start block one.
Put this into practice — free
4,168+ past papers, flashcards and an AI tutor for O Level, AS & A2. No credit card.
Start free →