Build a Weekly Exam Sprint from One Lecture
The default weekly study plan is a calendar with "review lecture 4" written on Sunday — a vague intention that becomes a reread when the day arrives. It looks like organization and it produces the same result as cramming: one massed session, passive review, no spacing, no retrieval. The calendar is scheduled; the learning isn't.
A sprint is different: it's a structure, not a date. Day 0, convert the lecture into 8 stems — the generation work, done once. Days 1, 3, 7, re-attempt the misses — three spaced retrievals, each one a test. One transfer stem on day 3 — the far-transfer check. The lecture gets processed once and retrieved three times; the reread calendar processes it once and retrieves it never.
One lecture can feed a week — not because the lecture is big, but because the spacing makes it stick. Convert once, test three times, and the material is still there on day 7. That's a sprint.
Why the Sunday reread fails
Saving all the week's review for Sunday night is the anti-sprint — it takes the week's material and compresses it into one massed session, which is exactly what spacing exists to prevent. You read the week's lectures back-to-back, feel like you've covered them, and retrieve almost nothing: the exposure is dense, the retention is thin, and the "review" was really just a re-exposure.
The sprint works because it separates the two jobs. Day 0 is generation — convert the lecture into stems, the one-time processing work. Days 1/3/7 are retrieval — spaced attempts that consolidate what day 0 built. The reread calendar merges them into one session that does neither: no deep processing (it's a skim), no spaced retrieval (it's all at once). Spacing the re-tests is the spacing effect; the day-0 generation is the testing effect — and the Sunday blob has neither.
The sprint workflow
Day 0: convert, don't review. Friday's lecture becomes 8 stems — the questions the lecture's content can produce, written once. This is the generation step: you're not reviewing the slides, you're mining them for the exam items they contain. Ten to fifteen minutes, once.
Day 1: first re-test. Attempt the stems closed-book — the day-0 questions come back, and the misses get flagged. Not a review session; a test session. The retrieval is the consolidation; the misses are where the next attempts focus.
Day 3: second re-test plus a transfer. Re-attempt the misses, plus one transfer stem — the mechanism in a new story. The day-3 gap is where the spacing does its work; the transfer is where you check the concept survives a different surface.
Day 7: timed mixed set. One final run, timed, with an older lecture's stems mixed in — the exam's interleaved structure. Not just this lecture anymore; this lecture among the others, which is how the test will present it.
Misses keep their dates. A stem you missed on day 3 gets re-attempted on day 7; a stem that's still missing gets flagged for the next week. The spacing isn't rigid — it's the gap between attempts that matters, and the miss determines when the next one lands.
A 40-minute session on the clock
The weak plan is the calendar entry — "review Sunday, practice if time" — which is a reread with a vague aspiration attached. The strong plan names the stems (6 compute/interpret, 2 transfers), the dates (day 0, 3, 7), and the structure (mixed with older material on day 7). That's the sprint: specific, scheduled, and built on retrieval instead of re-exposure.
Why the spacing is the mechanism
The sprint's power isn't the stems — it's when you attempt them. Day 0 generation builds the initial encoding; the day-1, 3, 7 retrievals are what consolidate it into something that lasts. Each spaced attempt is a re-encoding: the memory gets pulled up, used, and re-stored, which is the mechanism that makes it durable. Compress the attempts into one session and you lose the re-encoding — the memory gets one shot, not three.
This is why "review lecture 4" on a calendar isn't a plan. It doesn't say what you'll do (retrieve what?), when (how many times?), or with what spacing (which gaps?). The sprint answers all three: 8 stems, three dated attempts, gaps that force the re-encoding. The calendar is a hope; the sprint is a structure.
If you don't want to run the calendar by hand, this is literally what a LearnX Exam Sprint does: upload the lecture deck and the Agent generates the day-0 stems, schedules the 1/3/7 re-tests, and keeps resurfacing your misses until they hold.
Ready to study smarter?
Turn your materials into targeted practice questions with explanations and exam-level difficulty.
- Exam sprint generator to prioritize what matters.
- Dynamic question generation from your materials.
- Explanations that fix gaps fast (not just answers).