Store
The Spaced Repetition System
0%
Module 01 / 04

Why timing
beats repeating

Most students review material once, maybe twice, then move on — and a week later most of it is gone. Spaced repetition doesn't add more review time. It times each review to land right before you'd otherwise forget, so each one costs less and sticks longer.

The forgetting curve

In the 1880s, Hermann Ebbinghaus measured how quickly he forgot lists of nonsense syllables and found that forgetting follows a predictable curve: steep at first, then flattening out. Most of what you forget, you forget within the first day or two — after that, the rate of loss slows down considerably.

The implication is easy to miss: a review that happens too early is mostly wasted, because you still remember almost everything and the review feels pointless. A review that happens too late requires relearning from scratch, which is expensive and demoralising. There's a narrow window in between where the review actually does work.

Research signalEbbinghaus, 1885 · replicated >200 times

Retention after a single exposure, with no review: ~100% immediately, ~58% after 20 minutes, ~44% after 1 hour, ~26% after 31 days.

Each successful retrieval at the right moment resets the curve and makes it flatten further next time — which is why the gaps between reviews can grow over time without losing the memory.

The useful window

The useful window sits right at the edge of forgetting — where recall is effortful but still possible. That effort is the point: a review that requires real work to retrieve strengthens the memory far more than a review where the answer is still sitting in working memory.

This is also why a spacing system and active recall are usually discussed together: spacing tells you when to review, and active recall tells you how — by retrieving the information yourself rather than re-reading it. Spacing without retrieval is just a re-reading schedule; retrieval without spacing is cramming with extra structure.

If active recall is new to you: The Active Recall Playbook covers the retrieval side of this system in depth — five methods, ranked, with a session template. The two products are designed to be run together: recall generates the signal of what you don't know, spacing schedules the follow-up.

Try it yourself

Drag the slider below to pick a day since you first learned something, and watch where it lands on the forgetting curve.

Forgetting Curve Explorer — drag to pick a review day
Day 0 Day 5 Day 10 100% 50% 0%
Too early. ~100% retained — you still remember almost everything, so a review now feels easy and barely strengthens the memory.
Module self-check 1 question
According to the forgetting curve, when is a review most valuable?
A Immediately after first learning it, while it's freshest
B Right at the edge of forgetting, when recall is effortful but still possible
C Only after it's been fully forgotten, to force a fresh start
D On a fixed daily schedule, regardless of how well you know it
Module 02 / 04

Building
a deck that works

A spacing system is only as good as the items inside it. Badly written items make every review slower and less useful — well-written items make the whole system run on autopilot. This module covers what makes an item good, and the schedule that decides when each one comes back.

What makes a good item

A good item is atomic — it tests one fact or one idea, not three. "Explain the causes of World War I" is an essay prompt, not a review item; it can't be answered cold in a few seconds and can't be marked clearly right or wrong. "Name one long-term cause of World War I" is atomic.

A good item is also phrased as retrieval, not recognition. If the cue contains most of the answer, you're not retrieving anything — you're filling in a blank you can already see. And it should be unambiguous: if you could reasonably give three different correct answers to the same cue, the item is testing your guess at what the card-maker meant, not your knowledge.

Good vs. bad itemSame fact, two cards

Bad: "The forgetting curve, discovered by Ebb—" → tests nothing, the answer is in the cue. Also: "Describe spaced repetition" → too broad, no single correct answer, can't be marked cold.

Good: "Who ran the original forgetting-curve experiments?" → Ebbinghaus. One fact, one answer, no leakage. "What happens to a Leitner card when you get it wrong?" → it goes back to Box 1. Atomic, unambiguous, retrieval-based.

The Leitner system

The classic low-tech implementation of spaced repetition is the Leitner system: physical flashcards sorted into boxes numbered 1 through 5. Every card starts in Box 1, which is reviewed daily. A correct answer moves the card to the next box up, which is reviewed less often. A wrong answer sends it straight back to Box 1, no matter which box it was in. Digital flashcard apps automate this with the same underlying logic — a shoebox and index cards work identically.

If you'd rather think in calendar days than boxes, the same idea maps to an expanding schedule. Each successful recall roughly doubles the gap before the next review; a failed recall resets the item back to Day 1.

When
What happens
Day 1
First review — shortly after initial learning, while the material is still fresh.
Day 3
Second review — the gap doubles. A successful recall here means the memory is starting to hold.
Day 7
Third review — recall should feel effortful but possible. That's the useful edge of forgetting.
Day 16
Fourth review — items that reach this point are well on their way to long-term memory.
Day 35
Fifth review — a final check to confirm the item has "stuck." From here, reviews can be much rarer.

Try it yourself

Six cards, all starting in Box 1. Reveal each one, decide honestly whether you had it, and watch where it lands.

Leitner Box SimulatorCard 1 of 6
Box 1
Daily
6
Box 2
Every 3 days
0
Box 3
Weekly
0
Box 4
Every 2 weeks
0
Box 5
Monthly
0
Currently in Box 1
Three mistakes that wreck a deck before it starts: writing items that are really mini-essays in disguise (split them into atomic facts); writing two-sided cards where the front contains the back's answer (recognition, not recall); and adding too many new items in one sitting — a deck that grows faster than you can review it guarantees a backlog within a week.
Module self-check 1 question
In the Leitner system, what happens when you get a card wrong?
A It stays in the same box and is reviewed again the next day
B It moves up one box, since a wrong answer means it needs more frequent review
C It goes back to Box 1, regardless of which box it was in
D It's removed from the deck so it doesn't slow down review sessions
Module 03 / 04

Running
the review session

A well-built deck can still be wasted by a badly run session. The mechanics of how you review — the order, the honesty of each attempt, what you do with a missed day — determine whether the schedule actually does its job.

The session itself

A review session should take 15–30 minutes, not hours. If it's taking longer, you're either adding new items faster than you can absorb them, or your items aren't atomic enough. Go through the items that are due — in any order — and for each one, try to produce the answer before you look. A guess counts as an attempt; flipping the card immediately does not.

This single rule — answer first, check second — is the difference between a spacing system and an expensive way to re-read your notes. If you read the question and immediately flip to the answer "to refresh your memory," you're not retrieving anything.

Worked exampleA real review session

18 items are due today. For each one: read the cue, say the answer out loud or write it down, then flip. 12 come back correct on the first try — those get promoted to their next interval. 4 are partially right or slow — those are marked for a same-session re-run at the end. 2 are blank — those reset to Day 1.

After the first pass, the 4 "shaky" items get re-run once more. Total time: about 20 minutes for 18 items, most of it on the 6 that needed extra attention.

Try it yourself

Eight items from a mixed deck. For each one, commit to an answer in your head, reveal it, then mark it honestly — that's pass one. Anything you weren't sure about comes back for a second pass.

Review Session Simulator
0
Promoted
0
Re-run
0
Reset

What goes wrong

Reviewing everything every day. This collapses the system back into cramming — if every item is due constantly, there's no spacing happening. Trust the schedule and let items graduate to longer intervals.
Flipping the card before genuinely trying to recall. Force a real attempt, even a wrong one, before checking — that's the entire mechanism.
Treating a missed day as a failure of the system. Life happens. The schedule adapts — items you missed simply come up as due, slightly later than planned. The system degrades gracefully; abandoning it entirely because you missed a day does not.
Module self-check 1 question
You missed two days of reviews. What should you do?
A Reset every item back to Box 1 and start over
B Just resume — the overdue items will be waiting, slightly later than planned
C Skip the overdue items entirely and only review items due today
D Abandon the deck — once the schedule slips, it's no longer useful
Module 04 / 04

Overload
& exam compression

Every spacing system eventually meets two pressures: a review queue that's grown faster than you can clear it, and an exam date that arrives before the long intervals have finished playing out. Both have a fix — and neither fix is "do more."

When the backlog grows

A growing backlog almost always means new items were added faster than the daily review queue could absorb them. The fix isn't to power through a 90-minute session — it's to stop adding new items until the backlog shrinks back to a normal size, then resume at a slower pace.

When you do sit down to clear a backlog, work through overdue items first, oldest first. These are the items most likely to have decayed the most — and clearing them restores the schedule's integrity faster than working through today's items and leaving the backlog for "later."

Try it yourself

Set how many new items you add per day against how many you can actually review, and watch what happens to your queue over two weeks.

Backlog Simulator — two weeks at this pace
New items added per day 15
Reviews you can do per day 12
D1D2D3D4D5D6D7D8D9D10D11D12D13D14
Days until your exam 10

Compressing under exam pressure

In the final week before an exam, the long-interval logic that makes spacing efficient stops being the priority — you need maximum retention right now, not the most efficient use of review time over the next two months. This is the one situation where the normal rules bend. The schedule below highlights which phase matches the slider you just set.

When
What to do
7+ days out
Run the system normally. Keep adding new items at your usual pace.
5–6 days out
Stop adding new items. Every session from here is review-only, so the queue can shrink instead of grow.
2–4 days out
Prioritise low-box items — the ones the system has flagged as least stable. These are your highest-yield reviews per minute spent.
Day before
One pass through the items you've gotten wrong most often, paired with active recall — explain or write out the answer, don't just flip the card.
Compression is a short-term loan, not a new normal. Prioritising low-box items in exam week means high-box items go briefly unreviewed — that's fine for a week, but if it becomes the permanent pattern, those "stable" items will start decaying too. After the exam, return to the normal schedule and let the backlog catch up gradually.
Final self-check 1 question
Your review queue has grown out of control. What's the first thing to do?
A Run one very long session to clear everything at once
B Stop adding new items, and work through the overdue backlog oldest-first
C Delete the overdue items and start fresh with only new material
D Keep adding new items, but review newest-first instead of oldest-first