A 4-week exam revision timetable that doesn't fall apart

Exams · 7 min read

Revision timetables have a well-earned reputation: you spend two happy hours colour-coding a grid, follow it for a day and a half, fall behind on Wednesday, and abandon the whole thing out of shame by the weekend.

The grid wasn't the problem. The design was. Most revision plans fail for one of three reasons: they schedule hours instead of outcomes, they assume every day goes perfectly, and they treat all topics as equally important. Fix those three and a four-week plan becomes surprisingly hard to break.

The shape of four weeks

Week 1 — map, then make. Before revising anything, list every examinable topic per module and give each an honest rating: fine / shaky / no idea. This takes an afternoon and controls everything after it, because your "no idea" list is where marks live. Spend the rest of the week making your materials — flashcards for recall-heavy topics, formula sheets, summary pages. After this week, making materials is no longer a legal form of revision.

Week 2 — a thin first pass over everything. The instinct is to start with topic one and do it perfectly. Resist it. Perfect-first-topic plans die with six topics untouched. Instead, cover every topic quickly: recall practice, worked examples, cards. Shallow and complete beats deep and partial, because it kills the terror of the unopened chapter and shows you where the real problems are.

Week 3 — past papers and weak spots. Now you earn marks. Past papers under rough exam conditions, then mark them harshly. Every lost mark becomes a task: "redo integration by parts", "learn the three causes cold". Your shaky list from week one, updated by real evidence, is the syllabus now.

Week 4 — review, don't learn. Final week is for running your cards, redoing the problems you got wrong, and sleeping. Learning brand-new material in the last 72 hours is a bad trade against consolidating what's already half-in. If a topic is still "no idea" by now, make a strategic call: can this exam be passed without it? Usually yes.

Schedule outcomes, not hours

"Tuesday 14:00–16:00: Microeconomics" is a fake commitment — you can sit there for two hours and produce nothing. Write tasks instead: "redo 2023 paper Q1–4", "cards for weeks 5–8", "summary sheet for market failure". A day's plan is three to five of those. When they're done, you're done — some days that's 3 p.m., and that's the plan working, not you slacking.

This is exactly the workflow NowOne is built around: exam prep broken into tasks per module, pulled into your Today list each morning, each one run as a focus session. The calendar shows the plan spread over the month; the day only ever shows the next small thing.

Build in the bad days

Here's the design decision that separates plans that survive from plans that don't: schedule only five or six days a week, and leave one slot completely empty. You will lose a day — to a cold, a birthday, a bad night. A plan with slack absorbs it; a perfect plan shatters and takes your morale with it.

Falling behind has one rule: cut scope, never sleep. Drop the lowest-value topic from the plan rather than adding late-night hours — hour seven is worth almost nothing anyway.

Two exams? Interleave them

With multiple exams, alternate days between subjects rather than blocking "all of subject A, then all of B". Coming back to material after a gap feels less fluent, and that slight difficulty is precisely what makes it stick. Block scheduling feels better and works worse.