How to Make an O-Level Revision Timetable That Survives the Term

The short version: start from your exam dates and work backwards. Block time by task ("bonding — past-paper questions + self-mark"), not by clock ("4–5pm Chemistry"). Put foundational topics in the first third, exam technique in the middle, and full timed papers in the last one to two weeks. Then rebuild the plan every fortnight against what actually happened. A rough plan you follow beats a colour-coded one you abandon in week two.

Why most revision timetables fail

The classic failure is the hour-by-hour grid: a spreadsheet coloured by subject, every waking hour assigned, built once in a burst of motivation. It breaks the first time a lesson runs over or you have a bad day, and once one block slips the whole grid feels wrong, so you stop looking at it.

Three things make a timetable last: it has slack in it, it's tied to your real exam dates rather than a generic "study more" goal, and it gets rebuilt on a schedule instead of being treated as a one-time document. The steps below build one that way.

Step 1 — List every paper and its exact date

Write out each subject you're sitting and the date and time of every paper. This is the backbone: your deadlines set your priorities. The paper that is soonest, or the subject where you're weakest, gets the first and biggest blocks. Everything else fits around that.

Check your dates against your school's confirmed timetable, not last year's. Sittings move.

Step 2 — Count the hours you actually have

Be honest about a normal week. Subtract school, travel, sleep, meals, and the time you'll realistically lose to everything else. For most school students, six to twelve focused revision hours a week is a sustainable target outside the final push — more than that for a few weeks is possible, but a plan built on fourteen-hour weekends is a plan built to fail.

Whatever number you land on, plan for about 80% of it. The spare 20% absorbs the days that go wrong without breaking the plan.

Step 3 — Turn each syllabus into a tagged topic list

For every subject, list its topics straight from the official syllabus — one line each. Then tag each topic with your honest confidence: secure, shaky, or not started. "Secure" should mean you can answer a past-paper question on it unaided, not that you've read the chapter.

This list is what you schedule against. Shaky and not-started topics in high-weight areas are where your hours should go first.

Step 4 — Work backwards from the exams

Split the weeks between now and your first paper into three rough phases:

• First third — build. Cover the not-started topics and shore up the shaky ones. This is content work: notes, worked examples, understanding.
• Middle third — apply. Shift to past-paper questions by topic, learning how each topic is actually asked and marked. Keep circling back to weak spots.
• Last one to two weeks — full papers. Whole past papers under timed conditions, self-marked against the mark scheme. No new content unless a paper exposes a gap.

If you have several subjects with staggered dates, run this three-phase shape per subject, anchored to that subject's paper. See how to use past papers for O-Levels for what to do in that final phase.

Step 5 — Block by task, not by clock

Instead of "Monday 4–5pm: Physics", write the actual job: "Physics — forces: 6 mark-scheme questions from 2023 papers, self-mark". A task block tells you what "done" looks like, survives being moved to a different time, and stops you filling an hour with passive re-reading because the slot said "Physics" and nothing more.

Aim for two to four task blocks a day on a school day, more at weekends. Each block should be one subject and one clear output.

Step 6 — Rebuild it every two weeks

Put a recurring 15-minute slot in your calendar — Sunday evening works well. In it you:

1. Update your topic tags: what moved from shaky to secure, what's still stuck.
2. Look at any past-paper scores you've logged and note the weakest area.
3. Redraw the next two weeks of task blocks against that, keeping the three-phase shape.

The plan is never "wrong" because you rewrite it before it can drift. This is the step people skip, and it's the one that makes the difference.

A worked example — one subject, six weeks out

Multiply that across your subjects, offset by their exam dates, and you have a plan. It will change — that's expected. The fortnightly rebuild keeps it current.

This covers building the timetable itself; for why cramming undermines it and a simpler weekly shape to start from, see why cramming doesn't work for O-Levels.

Common mistakes to avoid

• Scheduling by hours, not tasks. An hour "on Biology" quietly becomes an hour of highlighting.
• No slack. A plan at 100% capacity is a plan that breaks on the first bad day.
• Leaving past papers until the last week. They're the revision, not the final check — start topic-level past-paper work in the middle phase.
• Equal time to every subject. Weight by weakness and by exam proximity, not fairness.
• Building it once. Without the fortnightly rebuild, any timetable is out of date within two weeks.

Doing this in Apex. Apex, our O-Level study app, is built to run this method. Its study planner takes a subject and an exam date and drafts the week-by-week, three-phase plan for you, with an examiner note per week. The per-subject syllabus checklist is your tagged topic list, and the past-paper score log gives you the weakest-area figure you need for each fortnightly rebuild.

See how Apex's planner and tracker work →