A revision timetable that survives
The colour-coded hour-by-hour grid is a genre of procrastination. It takes a Sunday to build, breaks on Tuesday, and its main output is guilt.
The short version
- Don't schedule hours. Schedule topics, and let each one take what it takes.
- Prioritise by marks at stake and current weakness, not by which subject you enjoy.
- Plan a week at a time. Anything beyond that is fiction you'll have to rewrite.
- Build in explicit slack — two empty slots a week — so one bad day doesn't invalidate the plan.
- The plan must include revisiting old topics, or spacing never happens.
The standard revision timetable is a grid of the next six weeks, in half-hour blocks, colour-coded by subject. It looks like control. It fails for reasons that are structural rather than motivational, and it's worth being clear about them before building anything else.
It assumes you know how long a topic takes, which you don't until you've done it. It assumes nothing goes wrong for six weeks, which it will. It measures time rather than progress, so sitting in front of a book for the allotted hour counts as success. And because it's a single interlocking structure, one missed afternoon shifts everything — at which point the rational move is to rebuild the whole thing, which is another Sunday gone.
What follows is a plan with the same purpose and much less to break.
Step 1: list the topics, not the subjects
Take the syllabus for each subject and break it into topics of about the size you'd cover in one sitting — an hour or two. Not "Biology" but "enzyme kinetics", "the cardiac cycle", "gas exchange".
You now have a list of perhaps sixty to a hundred items across all subjects. That list is the real object of planning. It's finite, you can tick things off it, and it turns "revise biology" — a task with no end state — into a set of tasks that can actually be completed.
Step 2: score each topic
Two numbers, one to five each, taking about ten seconds per topic.
- Weight — how many marks does this topic put at stake? Look at past papers rather than guessing; frequency across recent years is a decent proxy.
- Weakness — how badly would you do on it right now? Be honest. If you're not sure, that's a 4 by definition.
Multiply. Sort descending. The topics at the top of that list are where your next fortnight goes, and the ones at the bottom get a quick review at some point and nothing more.
Why this is the whole trick
Left to instinct, people revise what they already know, because it feels good, and the subject they like, because it's pleasant. The weight × weakness score is unpleasant precisely because it points at the opposite, which is where the available marks are.
Step 3: plan one week
Look at the actual week ahead — lessons, work, commitments, the things you're not going to cancel — and find the study slots that genuinely exist. Not the ones that would exist if you were a different person.
Then assign topics to slots from the top of your sorted list. One topic per slot. If the slot is ninety minutes and the topic takes sixty, you've gained thirty minutes for review; if it takes two hours, it runs into the slack.
Leave two slots a week empty. Not as rest — as absorption. Something will overrun, something will get cancelled, some topic will turn out to be far worse than you thought. Slack is what converts that from a plan failure into a Wednesday.
Step 4: put review in the plan
The commonest structural flaw in a revision plan is that it's a single pass. Sixty topics, sixty slots, done — and by the time you reach topic sixty, topic four is gone.
Reserve roughly a third of your slots for revisiting things you've already covered, oldest first. It feels like less progress and it is the difference between finishing the syllabus and knowing the syllabus. Why the gaps do the work →
A weekly shape that works:
| Share of slots | What goes in them |
|---|---|
| ~50% | New topics, from the top of the priority list |
| ~25% | Review of topics covered 1–3 weeks ago, mixed up |
| ~15% | Practice questions and past-paper sections |
| ~10% | Slack |
Step 5: end each session with a mark, not a time
A slot is finished when you can produce the material, not when the clock says so. Practically: spend the last ten minutes of every session testing yourself on what you just did, and write one of three things next to the topic — solid, shaky, barely started.
That single word is what feeds next week's plan. Shaky topics come back sooner; solid ones move to a longer cycle. Without it you're planning blind and the priority list goes stale within a fortnight.
The state of every topic, without a spreadsheet. YourSubjects tracks which sections you've read, which cards you've marked learned, and how every practice attempt and paper went — so "what's shaky and what haven't I touched in three weeks?" comes out of the app rather than out of your memory of the last month.
Open the appSessions, breaks and the hours question
There's a lot of confident advice about optimal session lengths. The evidence for any specific number is thin, and the honest summary is: most people can concentrate properly for somewhere between twenty-five and fifty minutes, and you'll find your own figure faster by observation than by adopting someone else's.
Two things are better supported than the exact numbers. Breaks should be actual breaks — a phone break isn't a rest, it's a different demand on the same attention. And total daily hours have a hard ceiling: four to five hours of genuine focused study is a lot, and people reporting ten are mostly reporting time spent near books. Fewer honest hours will beat more dishonest ones.
Sleep is not the thing to trade. Consolidation happens during it, and a late night before a heavy revision day usually costs more than the night gained.
When it goes wrong
It will. The rule that keeps the system alive is: never reschedule backwards. Missed slots do not roll forward as debt. On Sunday you rebuild the week from the current priority list, and whatever you didn't get to simply competes for a slot on its merits like everything else.
This matters more than it sounds. A plan that accumulates debt gets more depressing every week until it's abandoned. A plan you rebuild weekly from where you actually are is never behind — it's just a list in priority order, and you're always working on the most important thing left.
If you take one thing
Throw away the six-week grid. Make a topic list, score each one on weight and weakness, and plan only the next seven days. Then do it again next Sunday, in ten minutes, from wherever you actually are.
Where this comes from
- Cepeda, N. J., Pashler, H., Vul, E., Wixted, J. T., & Rohrer, D. (2006). Distributed practice in verbal recall tasks. Psychological Bulletin, 132(3) — the case for building review into the plan.
- Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the "planning fallacy". Journal of Personality and Social Psychology, 67(3) — why time estimates need slack.
- Gollwitzer, P. M. (1999). Implementation intentions. American Psychologist, 54(7) — why "topic X, Tuesday evening" beats "revise more".
- Walker, M. P., & Stickgold, R. (2006). Sleep, memory and plasticity. Annual Review of Psychology, 57.