Protocol
Start the hard block with retrieval before notes
Find the hole before you fill it.
When it fits
- A demanding study session begins by reopening all notes, slides and AI summaries, making the material feel familiar before you test what is available from memory.
When to avoid it
- For genuinely new material, build enough initial understanding before demanding retrieval that the learner has never encoded.
Why it matters
Open a difficult block with a short closed-source attempt: answer a few questions, outline the concept, or solve the first step. Then use notes only to repair what failed. End with another fresh retrieval or application item so the block measures change rather than exposure.
Steps
- Attempt from memory.
- Mark the specific miss.
- Open only the source needed for that miss.
- Repair the model or rule.
- Attempt a fresh item without the source.
An example
Before reviewing partner-function notes, write the logic you remember, check the missing condition, then solve a different customer scenario.
Check your result
The notes answer a diagnosed question rather than being the first activity by default.
Keep this limit in mind
- For genuinely new material, build enough initial understanding before demanding retrieval that the learner has never encoded.
Connected ideas
Useful withInterleave confusable cases, not unrelated workstreams
Evidence and sources
Supports
Successive relearning combines successful retrieval with relearning on later sessions rather than treating one correct recall as permanent mastery.
The studied key-term tasks do not map directly onto every applied skill.
Relearning attenuates the benefits and costs of spacing · Abstract