Guide · pre-clinical workflow
Retain med school lecture volume: the math nobody runs before MS1.
Pre-clinical retention is not a study-technique problem in week 1. It is an arithmetic problem from about week 3 on. Every general guide on this tells you to do active recall, space your reviews, and not rewatch lectures. All true, all useless if the per-deck cost of doing those things is higher than your daily budget. The fix is to drop that per-deck cost.
Direct answer · verified May 17, 2026
To retain med school lecture volume, convert each lecture deck to practice questions the day it is given, drill it in a 10 to 15 minute pass that night, and let a spaced-repetition scheduler resurface the questions you missed across the block. Studyly turns a 90-slide deck into about 200 questions in roughly 60 seconds, which collapses the authoring step that breaks most DIY-Anki workflows by week 3.
Run the arithmetic before you pick a method
A representative US pre-clinical week:
- 4 to 6 hours of lecture per day, typically split into 2 to 4 slide decks.
- 10 to 20 decks per week, each one 50 to 120 slides.
- 80 to 160 decks per 8-week block, all examinable, mostly cumulative.
If a single deck of cards takes you 60 to 120 minutes to author by hand, the bookkeeping is brutal. Two decks a day is 2 to 4 hours of authoring before you have done one review. Four decks a day is a whole second school day. Across a block that is 80 to 320 hours of card-writing, which is structurally impossible to spend in addition to attending lecture and sleeping.
That is the part most retention advice never names. Active recall does not fail in MS1. The authoring tax in front of active recall fails, and what looks like a discipline problem in week 5 is a queueing problem from week 1.
Recognition feels like retention. It is not.
Watching a lecture at 2x and rewatching it is the most common survival reflex when the queue gets ahead of you, and it is the worst use of the same hour. The testing-effect literature, going back to Roediger and Karpicke 2006 and replicated many times since, puts retrieval practice at roughly two to three times the retention of equal-time rereading or rewatching, measured a week to a month out.
An hour of rewatching a 60-minute lecture finishes one deck and trains recognition. An hour of answering 60 to 100 questions on that lecture finishes the deck, trains recall, and produces a review queue that survives the next block. Same hour, very different week-three outcome.
The workflow that survives a 16-week pre-clinical course
Four steps, repeated per deck, repeated per day. The trick is the per-deck cost: if step 1 is cheap, the whole loop runs. If step 1 is expensive, the loop dies on a busy Thursday.
1. Upload the deck the day it is given
Same-day matters more than session length. A 90-slide deck uploaded today and drilled for 10 minutes beats the same deck saved for a Sunday catch-up that does not happen. Studyly converts a deck in about 60 seconds, so this step is a 10-second commit, not a 90-minute commit.
2. Run a 10 to 15 minute pass that night
One deck, mixed format: multiple-choice, free-response, case-style. Get through 40 to 60 questions, mark what you miss. The pass is short on purpose. The aim is not mastery of today's deck, it is a single retrieval rep before sleep so the scheduler has something to space.
3. Let the scheduler interleave decks across the block
Once 5 to 10 decks are in, daily review stops being a single-deck thing and starts looking like a 15 to 30 minute mixed block: a question from yesterday's pharm deck, then one from last week's path, then one from today's. That interleaving is what an end-of-block exam already does to you, except it happens in the question instead of in your head.
4. Use the tree per deck as the volume gauge
Each deck grows its own tree as you drill it, and by exam-day morning the screen looks like a forest, one tree per deck of the block. That is the only visualization in your workflow that maps directly to the volume problem. A deck with a stunted tree is a deck you skipped, and the gauge is honest in a way a self-reported schedule is not.
Hand-rolled Anki versus a per-deck generator, line by line
Anki itself is not the problem. The DIY authoring pipeline in front of it is. Here is what changes when the per-deck cost goes from an hour to a minute, and what stays the same.
| Feature | Hand-rolled Anki workflow | Per-deck AI generator workflow |
|---|---|---|
| Authoring time per 90-slide deck | 60 to 120 minutes by hand in Anki | About 60 seconds to generate 200 questions |
| Source of the questions | A generic shared deck or a web question bank | Your professor's actual slide deck |
| Format coverage from one upload | One format, usually basic cloze | MCQ, free-response, case-style, image-occlusion |
| On revisit | Identical wording, lazy pattern-match wins | Auto-rephrased prompt, rotated distractors |
| Volume gauge | A heatmap of reviews, decoupled from lectures | One tree per deck, one forest per block |
| Anki export | Native, you already live there | .apkg export with image-occlusion masks intact |
If you already have a stable Anki habit that survives your block schedule, do not break it. The argument here is for the more common case: someone who tried Anki, fell behind on cards by week 4, and is now studying by rewatching lectures.
The anchor: questions come from your professor's actual deck
This is the part you can verify on one upload. Drop a single 90 to 120 slide lecture deck into Studyly. In about 60 seconds it returns roughly 200 questions across four formats, multiple-choice, free-response, case-style, and image-occlusion, all generated against that exact deck. Not a generic web question bank, not a shared community deck someone else made for a different professor. The wording, emphasis, and edge cases mirror what your block test will pull from, because they came from the same source the test will.
On revisit Studyly auto-rephrases the prompt and rotates the distractors, which removes the lazy first-three-words pattern-match that quietly kills retention in week 2. Each deck also grows its own tree as you drill it. By exam-day morning the screen reads as a forest, one tree per deck, and a stunted tree is the only honest signal that a lecture is under-rehearsed.
A wrongly-keyed question is worse than no question
Any tool that writes questions for you, ChatGPT included, will produce confident, plausible answers with no quality check. For retention at volume that is a tax: a wrong key gets repped just as often as a right one, and a misnamed pathway carries to the block test. Question quality matters more in MS1 than in most other study contexts, because the same flashcard gets seen 6 to 10 times across a block.
“Studyly's question quality on a held-out three-document eval, scored on factual correctness, clarity, distractor quality, and question-type coverage. Unattle scored 78.0, Gauntlet 68.0, and Turbolearn 57.8 on the same eval.”
Internal eval run by Jungle, the company behind Studyly. Per-criterion methodology is at studyly.io/quality.
Read that as the company's own measurement on a consistent rubric, not an independent audit. Factual correctness is scored first on purpose: for a pre-clinical retention workflow it is the criterion that decides whether the next 8 weeks of review queue is an asset or a slow-burning liability.
Convert today's deck before you forget the lecture
Drop the deck from today's first lecture. Watch it convert in about 60 seconds, then run a 10-minute mixed pass before bed. That single rep is what the rest of the block compounds on.
Free tier on app.jungleai.com, no credit card. Powered by Jungle, used by 1M+ students.
Frequently asked
How many hours of lecture does a typical pre-clinical med school week actually push?
Most US MD pre-clinical schedules run 4 to 6 hours of recorded or in-person lecture per day, plus 2 to 4 hours of small group, lab, or clinical skills. Over a 5-day week that is roughly 20 to 30 hours of lecture content, frequently broken into 12 to 20 slide decks. Across a typical 8-week pre-clinical block that compounds to 80 to 160 decks of material, all examinable. The volume, not the difficulty of any single concept, is what causes retention to collapse around week 3.
Why does Anki alone stop working partway through MS1 for a lot of people?
Anki the scheduler is fine. Anki the workflow breaks when you also have to author the cards. Making your own cards from one 90-slide deck takes most people 60 to 120 minutes. If your day has 4 decks in it, that is a 4 to 8 hour authoring tax on top of lecture, before you have done a single review. People do not abandon Anki because spaced repetition is wrong, they abandon it because the cost of feeding it grew past their daily budget. The fix is to remove the authoring step, not to swap the scheduler.
Is watching lectures at 2x speed and re-watching them a real retention strategy?
Watching is recognition, not recall. Recognition feels like learning because the material is familiar on a second pass, but the format an exam scores is producing the answer without the prompt in front of you. A meta-review of testing-effect studies put the recall advantage roughly two to three times higher than rereading or rewatching at equal time. Rewatching a 60-minute lecture costs an hour of your day and trains the wrong skill. The same hour spent answering 60 to 100 questions on that lecture trains the skill the exam actually grades.
How do you keep up when an exam block dumps 30+ decks in 8 weeks?
The pattern that survives the volume is: convert each deck the day it is given, drill it in a 5 to 15 minute pass that night, then let a spaced-repetition scheduler resurface the questions you missed in the days after. The bottleneck is the conversion step. If it takes 10 seconds per deck to start a generation, 30 decks across the block costs you 5 minutes of setup total. If it takes you an hour per deck to make cards by hand, the same 30 decks cost 30 hours, and that is the deficit most people accumulate without realizing.
What is the difference between memorizing 200 questions per deck and actually retaining the lecture?
If the 200 questions came from a generic web question bank, you are memorizing 200 questions, the structure is brittle, and the exam will key from your professor's wording. If the 200 questions came from your professor's actual slide deck, the questions follow the same emphasis, vocabulary, and edge cases your block test will pull from. Studyly generates against the deck you uploaded, not against an outside bank. On a held-out eval scored across factual correctness, clarity, distractor quality, and question-type coverage, that workflow scored 81.3 versus Turbolearn 57.8, Gauntlet 68.0, and Unattle 78.0.
Does this work for systems blocks where lectures from 4 different professors land in the same week?
Yes, that is the case where the per-deck workflow helps the most. A renal-cardio week with one deck from physiology, one from pharm, one from path, and one from the case discussion is exactly the load where authoring cards by hand falls behind first. One upload per deck, each one its own tree, the spaced-repetition scheduler interleaves them automatically. By the end of the week the four decks have produced roughly 800 questions you can shuffle into a single mixed block, which is closer to how the exam will mix them than studying each subject in isolation.
Related reading
- The hidden time cost of hand-rolled Anki decks the per-deck authoring tax that breaks MS1 workflows.
- Cram for an exam with practice questions the same drill argument applied to the week before a block test.
- The forgetting curve and spaced retesting why interleaved reviews across the whole block matter more than any one session.
Comments (••)
Leave a comment to see what others are saying.Public and anonymous. No signup.