Introduction
Study & Recall
Spacing the reviews is easy. Making each review actually prove something is the bit that matters.
You’ve probably heard the advice a hundred times by now.
“Use spaced repetition. It’s scientifically proven. Review on Day 1, Day 3, Day 7…”
So you dutifully put reminders in your calendar, open your notes on each of those days, read them again — and three weeks later you still can’t explain the topic without the page in front of you.
Here’s the thing: spaced repetition works. But not because of the calendar. The spacing only becomes useful when each review forces you to retrieve the material from memory — instead of simply rereading the same notes on a schedule.
That distinction is the whole article, really. But let’s make it practical, especially if you’re working through an online course, a professional qualification, a technical cert or anything else you actually need to remember and use — not just recognise.
What spaced repetition actually is
The basic idea is simple.
Instead of studying a topic five times in one weekend and then never touching it again, you spread your reviews out over increasing intervals.
You review it soon after learning it.
Then a few days later.
Then a week later.
Then a couple of weeks after that.
Each successful review lets you wait a bit longer before the next one. The material slowly moves from “I just learned this” to “this is just something I know.”
That’s it. No magic. No complicated system required. Spacing beats cramming mainly because it keeps checking in on the material just as it’s starting to fade — instead of letting it quietly evaporate while you move on to the next module.
The mistake: scheduling rereading instead of recall
This is where most spaced repetition quietly goes wrong.
A typical attempt looks like this: you finish a course lesson, add “review Chapter 4” to your calendar for Tuesday, and when Tuesday arrives you open the chapter and read it again.
Job done, apparently.
But if the notes are open during the whole review, you’re checking recognition, not proving recall. The material looks familiar, so it feels learned — and that familiar feeling is exactly the trap we covered in why rereading feels like learning but often isn’t .
Recognising the material when it’s in front of you is not the same as being able to:
If every “spaced review” is just a scheduled reread, all you’ve built is a rereading calendar. Useful reviews start with the material closed.
How to do spaced repetition step by step
Here’s the whole thing as a practical loop.
Step 1: Learn a reasonably focused topic
Not “the entire module”. One topic. One lesson. One concept you could describe in a sentence or two.
Step 2: Close the material
No notes open. No video playing. No course page on the second monitor.
Step 3: Retrieve from memory
Answer a few questions, do a brain dump on paper, explain the topic aloud, or attempt a practice task — whatever fits the material.
Step 4: Check against the source
Now open the material and compare. What did you get right? What was wrong or missing?
Step 5: Mark the gaps
The interesting part isn’t the score. It’s the specific bits you couldn’t produce. Write them down.
Step 6: Fix only the weak bits
Go back into the material for the gaps — not the whole lesson from the top. Then close it and try those bits again.
Step 7: Schedule another retrieval attempt
Put the next review a sensible distance away, then repeat the same loop. As the topic gets easier to recall, stretch the gaps out.
Notice what the calendar’s job is here: it decides when you come back. The recall decides what happens when you do.
A simple spaced repetition schedule
You need something to start with, so here’s a practical pattern:
That’s the D1 / D3 / D7 / D14 / D30 pattern, and it’s a decent starting structure. It is not a universal law handed down on stone tablets.
Harder material — the stuff you half-missed on Day 3 — probably needs to come back sooner. Material you recalled cleanly and confidently can be pushed further apart. The schedule should bend around what your retrieval attempts tell you, not the other way round.
What should you actually do at each review?
You’ve got options. Pick the one that matches what you eventually need to do with the knowledge.
If the end goal is passing an assessment, written questions and mini answers make sense. If the end goal is doing the thing — configuring the thing, writing the code, running the process — then at least some of your reviews should be practice tasks, not just question cards.
Retrieval should look like the thing you’re training for. Otherwise you’re getting very good at something adjacent to what you need.
Spaced repetition for knowledge you need to apply, not just remember
A lot of spaced repetition advice assumes you’re memorising vocabulary or facts. Fine if that’s your situation.
But if you’re learning coding, cyber security, business processes, networking, accounting, or any technical skill, recalling definitions is only half the job. You need to apply the material too.
So build application into the reviews:
A Day 7 review that asks “explain the concept” is good. A Day 7 review that asks “here’s a scenario — what would you do and why?” is better, if doing is the point.
How active recall and spaced repetition fit together
People often talk about these as if they’re rival techniques. They’re not.
Active recall is what you do during a review — pulling the information out of your head instead of letting the notes hand it to you. Spaced repetition is when you come back — spreading those retrieval attempts over increasing intervals.
One is the engine, the other is the timetable. We’ve got a separate piece on practical active recall study methods if you want more ways to run the retrieval part.
Don’t review everything equally
Here’s a way to waste a lot of well-organised time:
Give every topic the same review schedule, regardless of whether you can already recall it perfectly or can’t recall it at all.
If something comes back cleanly on Day 3 — full explanation, correct example, no hesitation — it doesn’t need the same attention as the topic you half-remembered and had to check.
Weak material returns sooner. Strong material gets more space.
That’s the same thinking behind the Fail First approach : test first, find the gaps, spend your effort where the evidence says it’s needed — instead of spreading it evenly over stuff you already know.
A worked example
Say you’re studying for an IT certification and you’ve just finished the lesson on network segmentation.
First study: You work through the lesson, take notes, and before you call it done, you close everything and explain the idea back to yourself. That’s your baseline.
Day 1: Brain dump on paper. VLANs — solid. Why segmentation improves security — mostly there. The difference between two specific approaches — fuzzy. You note the gap, restudy just that bit, and try it again.
Day 3: Three questions, no notes. The fuzzy bit from Day 1 is now fine, but you’ve mixed up two terms. Gap noted, gap fixed.
Day 7: Application. “A small company wants to separate guest Wi-Fi from internal systems — what would you suggest and why?” You write a mini answer, then check it against the material.
Day 14: Quick retest. Five minutes. Mostly clean.
Day 30: Confirmation. If it still comes back cleanly, it’s earned a long break.
And if you miss something along the way? You don’t restart the whole schedule. You study that gap, shorten the next interval for that topic, and carry on.
What if you miss a scheduled review?
Nothing dramatic happens.
Do the review when you next can. Test from memory first — especially if it’s been a while, because the extra gap just made the retrieval more honest. Check, fix the gaps, schedule the next one.
What you should not do is let overdue reviews pile up into a guilt backlog of 47 topics you’re now “behind” on. This isn’t a streak app. Nobody’s keeping score. If the backlog gets silly, pick the topics that matter most and quietly let the rest go back to normal study.
How long should a spaced review take?
Shorter than you think, if the topic is focused.
A good review tests the topic, reveals the gaps and fixes them. It is not a replay of the entire original lesson. If your Day 14 review takes as long as learning the topic in the first place, the review has swollen into rereading-with-extra-steps.
Ten focused minutes of retrieval and gap-fixing beats an hour of rewatching the same video. Again.
The short version: how to do spaced repetition properly
If you remember nothing else:
Learn a focused topic → wait → recall it without looking → check → fix the gaps → schedule the next retrieval → increase the gap as recall improves.
That’s how to do spaced repetition so it actually changes what you know. The spacing decides when you return. The retrieval decides whether returning was worth it. Without the second half, you’ve just built a very organised rereading habit.
Keep learning
• Rereading vs Active Recall → Why familiar notes can fool you into thinking you know more than you can recall.
• 7 Active Recall Study Methods → Practical ways to run the retrieval part of each review.
• How to Use the Feynman Technique → Explain a topic from memory, expose the gaps and check them — with a worked DNS example.
• Why The Stack Works → See how active recall, Fail First and retesting fit together.
• More study guides → Browse practical guides to study methods, recall and finding knowledge gaps.
Let the scheduler handle the dates
Study & Recall includes a Spaced Repetition Review Scheduler that logs a topic and gives you D1, D3, D7, D14 and D30 review dates. It doesn’t pretend to learn your memory or do the recall for you — it schedules the reviews. The recall–check–fix loop is still yours to run.