Revision that works with the brain, not against it
Re-reading feels like revision and performs like almost nothing. Spaced retrieval, testing yourself at stretching intervals, is the method the evidence backs, and it is simple enough to start today.
Method guide, written July 2026. Exam patterns and dates belong to official notifications and change on their own schedule; verify specifics there before building plans on them.
The forgetting curve is the enemy, retrieval is the weapon
Memory decays on a curve: steep in the first days, flattening later, and every re-encounter with material slows the next decay. But the encounters are not equal: passively re-reading a chapter barely registers, because recognition (that looks familiar) mimics recall (I can produce it) while sharing none of its strength. Retrieval, forcing the answer out of your head before checking, is the encounter that rebuilds the memory, and testing at the moment you are about to forget rebuilds it strongest. That timing trick is the whole method.
The method in one paragraph
After learning something, test yourself on it soon, within a day or two. If you retrieve it, wait longer before the next test; if you fail, repair it and test again sooner. Repeat, letting the intervals stretch: days become weeks become months for material you keep knowing, while shaky material cycles back quickly. Run across a syllabus, this produces the outcome every aspirant wants and cramming never delivers: month-one material still retrievable on exam day, at a total time cost far below one panicked re-learning.
Running the system
-
1
Make material retrievable
Turn each chapter's essentials into testable units: questions, cards, or representative problems. One fact per unit; anything with 'and' in the answer becomes two.
-
2
Test soon after learning
First retrieval within a day or two of finishing a topic, closed-book. This single early pass intercepts the steepest part of the forgetting curve at trivial cost.
-
3
Grade honestly, space accordingly
Knew it: next test waits longer. Hesitated or failed: repair and retest sooner. Honesty in the grading is the system's only hard requirement.
-
4
Keep the daily queue sacred
Ten to twenty minutes daily, attached to an existing routine. The queue's power compounds through unbroken days and collapses through skipped weeks.
-
5
Let tests audit the system
Periodic mixed tests across old material verify the spacing is working and flag chapters whose intervals stretched too fast. The system corrects itself if you feed it results.
A worked example
Two aspirants finish the same chapter on 1 September. The crammer re-reads it on 20 February and meets a stranger: effectively relearning, at final-phase prices. The spacer tested herself on 3 September (rocky, repaired), 8 September (better), 20 September, mid-October inside a mixed drill, and December's mock: five encounters totalling under two hours, and her February revision of that chapter took twenty minutes of confirmation. Multiply the difference across forty chapters and it stops being a study tip and becomes the exam result.
Figures are illustrative, for mechanism only. Verify current rates and your own structure before relying on any number.
Why this method feels wrong and works anyway
Spaced retrieval is desirably difficult: the struggle to recall is the mechanism, so effective revision feels harder and less smooth than re-reading, and progress is less visible session to session. Aspirants abandon it for exactly this reason, drifting back to the fluent comfort of highlighted pages. Expect the discomfort, and judge the method by mock recall, where its advantage is unmistakable, not by how mastery feels mid-session.
A note on scale and honesty
The system's two failure modes are both human: decks bloated with trivia that dilute the minutes, and self-grading that drifts generous. The fixes are editorial ruthlessness (only card what the exam actually pays for) and treating a hesitation as a miss. Software cannot supply either honesty. That is why the method's floor is human even when its ceiling is automated. One practical marker of a healthy system: your due-queue feels boring. Cards you keep meeting mean intervals are too short or grading too generous; a queue of near-misses caught just in time is the method running as designed.
How PrepWise applies this
PrepWise runs this entire method as infrastructure: cards generate from finished chapters, the scheduler works out what is due, revision cycles apply the same spacing at chapter scale, and mixed tests audit retention automatically. You supply the grading and the daily minutes. The bookkeeping, the part that kills hand-run systems, disappears.
Go deeper: Flashcards · Revision system · Practice tests
Written by Databus Technology Solutions, the makers of PrepWise. We are not affiliated with any examination body; exam patterns, dates and rules live in official notifications and change on their own schedule. PeopleDeck applies statutory rates and generates upload-ready files; it never files returns on your behalf, and positions on contested questions belong with your consultant.
Frequently asked questions
How is this different from just revising regularly?
Two differences: retrieval instead of re-reading (the test is the revision), and adaptive spacing instead of fixed cycles (strong memories earn longer gaps, weak ones shorter). Regular passive revision is better than nothing; spaced retrieval is better than regular passive revision by a wide, well-measured margin.
What interval schedule should I use?
Any reasonable stretching pattern works to start: one day, three days, a week, two weeks, a month, adjusting by performance. The precise numbers matter less than two properties: intervals grow on success and shrink on failure. Software exists because tracking this across hundreds of items by hand is the part humans abandon.
Does it work for problem-based subjects like physics and maths?
Yes, with problems as the retrieval unit: re-solving a representative problem cold is the test, not re-reading its solution. Concept-level cards (when does this theorem apply?) pair well with periodic cold re-solving of the chapter's hardest examples.
Is cramming ever the right choice?
In the final days, a light pass over your weakest, highest-yield material has value, precisely because the retrieval interval is short. As a strategy it is a trap: crammed material decays in days. That is why the mock two weeks after cramming feels like amnesia.
How do I fit spacing around new learning?
Interleave from the start: each day carries mostly new work plus a short due-for-review queue. The queue stays small if you keep it daily; skipping a week turns it into a wall, which is the point where most hand-run systems die.
Can I run this with paper flashcards and a notebook?
Yes, the Leitner box method has run it on paper for decades, and for a few hundred items it works. Past that scale, the bookkeeping becomes its own job, which is exactly the part software removes so the minutes go to retrieval instead of admin.
When should I start spacing, relative to the exam?
The day you start preparing: the method's advantage compounds with runway, and material learned this week is cheapest to secure this week. Starting late still helps, but the aspirant who begins spacing in month one is playing a different exam by the final phase.
Forgetting is optional.
Applied on every payslip, files generated for upload — per employee, per month.
Start free