How to make an A-Level revision timetable you'll actually follow
Build your timetable from topics, not subjects: list every topic across your subjects, rate each red/amber/green for confidence, then schedule the reds first in 45–60 minute blocks working backwards from your exam dates. Include spaced-repetition slots (revisit each topic after a few days), leave two buffer days a week, and plan no more than four focused hours a day — a timetable you can follow beats a perfect one you abandon by Tuesday.
Most revision timetables fail in the same way: they are beautiful, colour-coded, and abandoned by Wednesday. The problem is not discipline — it is design. A timetable that schedules 'maths' for three hours is not a plan; it is a wish. Here is how to build one that survives real life.
Step one: list topics, not subjects
Open your specification — every board publishes it free — and write down every topic you will be examined on, for every subject. Then rate each red, amber or green for confidence. This list is the timetable's raw material. 'Revise chemistry' is not actionable; 'revise electrode potentials (red)' is. The traffic-light list also tells you what the timetable should prioritise — the reds, not the subjects you happen to like.
Step two: work backwards from the exams
Write your exam dates down first — they are fixed. Then schedule backwards: the topic for the earliest exam gets revised first, the hardest reds get the most slots, and the final week before each exam is for past papers and the error log, not new content. Most timetables are built forwards ('what shall I do this week?'); the working ones are built backwards ('what must be done by June?').
Step three: the week structure
| Day | Session 1 | Session 2 | Notes |
|---|---|---|---|
| Monday | Red topic — 45 min questions | Different subject — 45 min | Never two blocks of the same subject |
| Tuesday | Spaced repeat of last week's red — 30 min | New amber topic — 45 min | The repeat is what makes it stick |
| Wednesday | Red topic — 45 min | Timed paper section — 45 min | One timed block midweek |
| Thursday | Spaced repeat — 30 min | Amber topic — 45 min | Lighter day is deliberate |
| Friday | Off or light review — 30 min | — | One evening off is not optional |
| Saturday | Timed paper or long section — 90 min | Marking + error log — 45 min | The log is where the learning is |
| Sunday | Buffer / catch-up | Plan next week — 20 min | The buffer absorbs the week's slips |
The rules that make it survive
- 45–60 minute blocks, real breaks between — retention collapses after an hour of continuous work.
- Never more than four focused hours a day — a fifth hour produces almost nothing and costs tomorrow.
- Two buffer slots a week minimum — a timetable with no slack fails at the first bad day and is never restarted.
- Schedule the hardest topic when you are freshest — for most people that is first, not last.
- Review and replan weekly — twenty minutes every Sunday, moving the reds that did not get done rather than pretending they did.
What goes in each block
A block is not 'revise integration'. It is 'do twelve integration-by-parts questions, mark them, log the errors'. Every entry should name the output — the questions done, the essay planned, the checklist ticked — because an entry with no output is how an afternoon becomes three hours of rereading. If a block's output cannot be stated in one line, it is not specific enough.
Mistakes that kill timetables
- Scheduling subjects instead of topics — 'maths' is not a plan.
- No spaced repetition — learning a topic once and never revisiting it.
- No buffer — the first missed day breaks the whole plan.
- Too many hours — an eight-hour day you abandon is worse than a four-hour day you keep.
- Front-loading favourite subjects — the reds go first, always.
- A timetable that takes a day to design — a simpler plan you start today beats a perfect one you make instead of revising.
The checklist
- Every topic is listed and rated red/amber/green.
- Exam dates are in first, and revision is scheduled backwards from them.
- Blocks are 45–60 minutes and each names its output.
- Every red topic has at least two slots — learn, then revisit.
- Two buffer days a week are built in.
- A weekly twenty-minute replan is scheduled, not optional.
A timetable gets you to the desk; it cannot make the hour count. The block's real work — the questions, the stuck points, the explanations that finally land — is where Lumi fits: bring it the topic you scheduled, and it turns the block into a session that produces something.
What to take from this
- Plan topics, not subjects — 'Tuesday: maths' is not a plan; 'Tuesday: integration by parts' is.
- Work backwards from exam dates, scheduling weakest topics first.
- 45–60 minute blocks with real breaks beat long sessions.
- Build in spaced repetition — revisit topics days later, not just once.
- Two buffer days a week: a timetable with no slack collapses at the first bad day.
Questions people also ask
During term, two focused hours a night; in holidays, four to five with real breaks. Beyond that, retention per hour falls off sharply — a timetable that demands more is a timetable you will abandon.
Mix them — interleaving subjects and topics improves retention, and two blocks of different subjects beat one long block of one. The exception is a timed paper or mock, which needs a longer single block.
For the exam season, work backwards from the first exam — typically starting the structured plan around Easter for summer exams. A rolling weekly plan works year-round; the formal timetable matters most in the final term.
That is what the buffer days are for. If you are behind every week, the plan is too ambitious — cut the hours, not the sleep, and replan rather than abandon it.