Study Planning
How to Make an A-Level Revision Timetable That Actually Works
Quick answer
Every January and every April, the same ritual. Students spend an entire evening colour-coding a beautiful revision timetable, follow it for four days, miss one session, and abandon the whole thing by the weekend. I want to be upfront: I'm really guilty of this one. When I was at your stage I spent hours building the perfect timetable, then realised those hours could have gone on actually learning. The problem is almost never discipline. Most timetables are designed to look reassuring, not to work with how memory actually behaves. Here's how to build one that survives contact with real life.
Key takeaways
- ✓Plan topics, not subjects. "Chemistry: electrode potentials" gets revised. "Chemistry, 2 hours" gets wasted.
- ✓Schedule each topic several times at spaced intervals (day 1 learn, day 2 recall, day 3 or 4 review, day 7 test), not once.
- ✓Weight your time toward weak topics: roughly 60% weak, 25% medium, 15% maintaining strengths.
- ✓Fill only 70 to 80% of your available time. Slack is what stops one bad day collapsing the week.
- ✓Rebuild the plan every Sunday based on what your testing revealed, not what the old plan assumed.
Why your last timetable failed
Do a post-mortem on any abandoned revision timetable and you'll usually find the same three design flaws:
- Subject-level blocks. "Biology, 4 to 6pm" lets you spend two hours on the photosynthesis notes you already like, while genetic drift, the topic actually costing you marks, never comes up. The unit of revision has to be the topic.
- One-and-done scheduling. Most timetables march through the specification once, front to back. But memory decays on a curve. What you revise this Monday is mostly gone in a fortnight unless it comes back. A plan that never revisits anything is a plan for forgetting things in a tidy order.
- Zero slack. The classic timetable fills every waking hour and assumes no bad days, no overruns, no life. The first missed block creates a backlog, the backlog creates guilt, and the guilt kills the plan. Fragile schedules don't fail occasionally. They fail every time.
Building one that works: the five steps
Step 1: Audit at topic level (about an hour, once)
Print the specification for each subject and rate every topic: confident, shaky, or no idea. Use your mock results and marked homework to keep yourself honest. Feelings lie, marks don't. This list, not the calendar, is the real revision plan. The timetable is just the delivery mechanism. And notice what's happening here: you're diagnosing before you treat. I'm a doctor. I can't give you a medication until I know what's wrong. Same principle.
Step 2: Count your real hours
Map your actual week. School, travel, clubs, work, meals, and rest you won't give up. What's left is your theoretical capacity. Take roughly 80% of it. For how much total time each stage of A-levels needs, see how many hours a day you should revise.
Step 3: Weight by weakness
Spread your hours roughly 60/25/15 across weak, medium and strong topics. This feels wrong. Everyone gravitates to the topics they enjoy, and the topics you enjoy are the ones you already know. But grade improvements live almost entirely in the shaky column. Those are marks you're currently losing that you're fully capable of winning.
Step 4: Schedule each topic on a spaced cycle
This is the step that separates a working timetable from wallpaper. Each weak topic should appear in your week several times, in different modes:
- Day 1, deep work: learn or relearn the topic properly. Notes, videos, worked examples.
- Day 2, active recall: blurt it or do questions from memory, and mark the gaps.
- Day 3 or 4, light review: a short pass over the gaps, 15 to 20 minutes.
- Day 7, test: past paper questions on the topic, timed where possible.
And mix your subjects across the day rather than binging one. Avoid three same-subject blocks in a row. It feels less tidy, but it works better, because mixing forces your brain to keep re-selecting the right method. Which is exactly what an exam paper does to you.
Step 5: The Sunday rebuild (20 minutes)
Each week, look at what your testing revealed. Topics that came back clean get demoted to maintenance. Topics that fell apart get promoted to deep work. Then rebuild next week's grid. A timetable is a living document. The version that matters is always next week's.
Or let the tool do steps 2 to 5 for you
What a working week actually looks like
Take a Year 13 student with Biology, Chemistry and Maths, revising around school in the spring term. A realistic week looks like this. One deep-work block on a weak topic most weekdays, 45 to 60 minutes. A next-day recall slot for whatever yesterday's deep work covered, 20 to 30 minutes. Light reviews stacked onto two evenings. One longer weekend session built around past paper questions. Total: 8 to 10 hours, every subject touched several times, no heroics. And two evenings completely free, so the plan bends instead of breaking.
Free: get a revision timetable built for you
Answer a few questions about your subjects and weak topics, and our free revision tracker builds you a personalised weekly plan using spaced repetition, the same method covered in this article.
Build My Free TimetableThe bottom line
A revision timetable has one job. It makes sure the right topic, in the right mode, comes back at the right moment, without you having to renegotiate it with yourself every evening. Build it at topic level, space the repetitions, bias it toward what you can't yet do, and leave room for being human. Do that and the timetable stops being a January decoration and becomes the quiet machine behind your grades.
Want expert help, not just advice?
A-Level Accelerators runs live online classes in Biology, Chemistry, Maths and Physics, taught by subject specialists and led by Dr Waleed Ahmad, a doctor and former top-performing A-level student. Small groups, real exam technique, first session risk-free.
See Our A-Level CoursesFrequently asked questions
Why do most revision timetables fail?
Three reasons. They plan by subject instead of by topic, so your weak areas hide inside vague blocks like "Chemistry, 2 hours". They schedule each topic once instead of at spaced intervals, so the content fades. And they assume a perfect week, so the first missed session collapses the whole plan. A working timetable is topic-level, spaced, and built with slack.
How far in advance should I make my revision timetable?
Plan one week at a time inside a rough long-term map. You need the long view to know how many topics have to be covered before your exams, but planning weekly lets the timetable respond to what you actually got done and which topics came back weak when you tested them.
Should every subject get equal time in my timetable?
No. Weight your time toward your weakest subjects, and within each subject, your weakest topics. Marks come from fixing what you can't do, not from polishing what you can. A good rule of thumb is roughly 60% of your time on weak topics, 25% on medium ones, and 15% keeping your strengths warm.
How do I stick to a revision timetable?
Make it survivable rather than impressive. Schedule at most 70 to 80% of your available time so overruns and bad days have somewhere to go. Put your hardest subject in your best hours. Include proper rest. And review the plan every Sunday. A timetable you follow at 80% beats a perfect one you abandon by Wednesday.
What is the best free revision timetable maker for A-levels?
Our free Revision Tracker at alevelaccelerators.com/revision-tracker builds a personalised weekly A-level timetable around your subjects, your topic-by-topic confidence ratings and your fixed commitments, with spaced repetition and active recall sessions placed automatically. Unlike generic timetable apps, it schedules topics, not just subjects.

Written by Dr Waleed Ahmad, MBBS
Waleed is a UK doctor and former top-performing A-level student. He founded A-Level Accelerators and has worked with over 1,000 A-level students on revision systems, exam technique and grade improvement. Everything on this blog comes from methods he used himself and teaches students every week.
Questions? Get in touch →