Weekly review

The weekly review: the hour that stops a term quietly collapsing

Nobody notices the week their term goes wrong. There is no moment of collapse — there is a missed processing session in week 4, a module quietly untouched since week 6, and a growing sense in week 9 that you are behind on everything without knowing by how much. A weekly review is the mechanism that makes drift visible while it costs an hour to fix instead of a fortnight. It is the least glamorous habit in this whole subject and the one that most reliably separates students who finish the term intact from students who don't.

9 min readSystems

What a weekly review is for

Not for studying. This is the distinction that makes it work: the hour produces no revision, no notes and no cards, and if you let it turn into a study session it stops doing its actual job. Its job is measurement and triage — finding out where you are, deciding what gets abandoned, and resetting the coming week.

Because it produces nothing visible, it's the first thing dropped when you're busy — which is precisely when it's most valuable. Protecting it requires treating it as maintenance rather than as optional planning.

The checklist

  1. 1

    Empty the capture inbox (15 minutes)

    Every photo, recording, slide deck and scribbled note from the week gets processed or explicitly deferred. Badly processed beats unprocessed — a two-line summary of a lecture you can't face is worth far more than an untouched deck you'll never return to.

  2. 2

    Check the review queue's trajectory (2 minutes)

    Not today's count — the trend. A queue growing week on week means you're adding cards faster than you're reviewing, and the fix is deleting cards, not studying harder. Left alone this is the single most common reason people abandon spaced repetition.

  3. 3

    Score each module out of five, honestly (5 minutes)

    One number per module: how confident are you that you could sit an exam on what's been covered? The number matters less than the trend across weeks, and the module that quietly slips from 3 to 2 to 1 is the one you'd otherwise notice in week 10.

  4. 4

    Look at the calendar four weeks ahead, not one (5 minutes)

    Deadlines cluster. Looking one week ahead means you discover the three-assignments week when you're in it. Four weeks of lead time is what lets you start something early, which is the only real defence against a bad cluster.

  5. 5

    Pick one thing to abandon (5 minutes)

    Explicitly. A reading you won't do, a module you'll do the minimum in, a society commitment. Unabandoned obligations don't disappear — they persist as background guilt and cost you evenings without ever being worked on.

  6. 6

    Choose three priorities for next week (5 minutes)

    Three. Not a task list — three outcomes that would make the week a success. Everything else is optional, and having decided that in advance is what stops the urgent from eating the important on Wednesday.

  7. 7

    Do one repair (20 minutes)

    One hour on the lowest-scoring module, or the backlog item that's been rolling for three weeks. One. The instinct is to fix everything, which is why most people fix nothing.

Why the trend matters more than the number

SignalWhat it meansAction
Review queue growing three weeks runningToo many cards, not too little disciplineDelete a third of the newest cards. This is normal maintenance.
One module scored 2 or below twiceIt has stopped being touched, whatever you intendedNext week's repair hour goes here, no negotiation.
Capture inbox never emptiesProcessing slot isn't happeningMove the slot or shrink it. A 40-minute slot that happens beats 90 that doesn't.
All modules at 4, nothing to abandonEither it's week 2, or you're not being honestCheck against an actual past paper rather than a feeling.
Same repair item three weeks runningIt's too big to be a repair itemBreak it into pieces or abandon it deliberately.

When to do it

Friday afternoon or Sunday evening, and the choice matters more than it sounds. Friday means you finish the week knowing what next week holds and can actually rest — the review closes the loop. Sunday evening means the plan is fresh but you've spent the weekend carrying an unresolved sense of being behind.

Whichever you pick, anchor it to an event rather than a clock time: after your last Friday class, before Sunday dinner. Time-anchored habits break the first week your timetable changes, which is the standard result in habit formation.

The failure modes

  • It becomes a study session. You start processing a lecture, get absorbed, and never reach the triage. Timebox each checklist item.
  • It becomes planning theatre. A beautiful colour-coded plan for a week that doesn't happen. Three priorities, written in a sentence each, is the whole output.
  • It only happens when things are going well. The weeks you skip it are the weeks it would have caught something. Do a ten-minute version rather than none.
  • Nothing is ever abandoned. A review that only adds is an inventory, not a triage, and the list grows until the whole system feels hopeless.
  • The scores are optimistic. Confidence is not calibrated — check one module against a real past paper every few weeks to recalibrate.

The version that survives a bad week

When the week has gone badly, the full hour feels impossible and skipping it is exactly wrong. Do the ten-minute version: empty the inbox as far as you can, score the modules, pick three priorities, choose one thing to abandon. Skip the repair.

That's enough to stop a bad week becoming a bad month, which is the entire function. A system's value is measured in what it does when you're not on top of things — see how to build a study system for where this hour fits in the larger structure.

Common questions

What is a weekly review for students?

A short structured hour that measures where you are rather than producing study: emptying your capture inbox, scoring each module, looking four weeks ahead, deciding what to abandon, and choosing three priorities. Its value is catching drift while fixing it still costs an hour.

How long should a weekly review take?

About an hour, of which twenty minutes is a single repair task. There's a ten-minute version for bad weeks — inbox, scores, priorities, one abandonment — and doing that beats skipping, because the weeks you're tempted to skip are the weeks it would have caught something.

When is the best time to do a weekly review?

Friday afternoon or Sunday evening. Friday lets you close the loop and actually rest over the weekend; Sunday keeps the plan fresh but means carrying the unresolved week through two days off. Anchor it to an event rather than a clock time so it survives a timetable change.

What should I actually do in a weekly review?

Process everything you captured, check whether your review queue is growing, score each module out of five, scan four weeks of calendar, abandon one thing explicitly, pick three priorities, and spend twenty minutes repairing the worst module. Resist turning any of it into studying.

Why do I fall behind without noticing?

Because falling behind has no event attached to it — no single moment where something breaks. A module simply stops being touched and nothing signals it until an exam is close. Scoring each module weekly makes the drift a number you can see rather than a feeling you can dismiss.

Is a weekly review worth it if I'm already organised?

Being organised is what makes it cheap, not what makes it unnecessary. The parts that still pay for themselves are the four-week calendar scan, which catches deadline clusters early enough to act on, and the explicit abandonment, which organised students are usually worst at.

Try it on your own material

Upload your notes, slides or lecture recordings and get a tutor that answers only from them — and says so when they don't cover it.

$12/month, or $8/month billed yearly · cancel in two clicks