Med school · daily drill · 5-minute protocol

Daily drill cards in med school, written as a clock, not a feature tour.

Every other guide on this tells you to pick a time, keep it short, and stay consistent. Correct. Also useless on a Tuesday at 9:43 pm when you have one cardiology deck open and no idea what you are supposed to do for the next five minutes.

This page is the literal minute-by-minute version. One deck. Five minutes. Roughly 30 to 60 retrieval attempts. A per-deck progress visual that does not punish you for a missed Wednesday.

Jump to the clock →
M
Matthew Diakonov
6 min read

Direct answer · verified 2026-05-19

What does daily drill cards look like in med school?

Convert each lecture deck to drill cards the day it was given (about 60 seconds of setup), drill 30 to 60 retrieval attempts from that single deck for roughly 5 minutes that night, then let the spaced-repetition scheduler interleave older decks across the rest of the week.

The session is anchored to one specific deck instead of a global queue, and the progress visual is per-deck rather than a single chain. That is what makes missing a Wednesday cost you one paused tree instead of a shattered streak. The per-deck visual is verifiable in this site's open source at src/components/TreeGrowth.tsx, where the STAGES array marks day 1, 3, 7, and 14.

The 5-minute clock, minute by minute

The session is one deck and five minutes. That is the whole thing. The reason it works is density: drill cards generated from your own lecture deck have a much higher exam-relevance hit rate than the same 5 minutes spent on a generic board bank, because the question source matches the test source.

One deck, five minutes

1

Minute 0: open one deck. Just one.

Pick the deck from today's lecture, not a global review queue. The decision of which deck is already made for you, so the session does not start with a planning step. If today had two lectures, do them in order and stop after the first one tonight. The second one gets tomorrow's slot. The point of the per-deck anchor is that you never sit down to drill and immediately face an unbounded list.

2

Minute 1: 6 to 10 MCQs from that deck

Start with multiple-choice, because the recognition-under-distractor format is the closest miniature of the block exam. Aim for roughly 6 to 10 stems in the first minute. Get them wrong is fine; the point of minute 1 is to find the gaps the lecture left, not to look competent.

3

Minute 2 to 3: 4 to 6 free-response or image-occlusion cards

Switch formats. Free-response forces unprompted recall (no answer pool to anchor against), and image-occlusion is the format that actually matters for anatomy, histo, derm photos, and any named visual sign. The same fact retrieved two ways is the whole reason this is faster than re-reading slides.

4

Minute 4: review explanations on what you missed

Do not re-read the slide deck. Use the explain-my-mistake panel that cites the specific slide your wrong answer came from, then move on. The single most common time-sink in med-school drilling is treating the explanation as a re-lecture; it is a diff, not a re-read.

5

Minute 5: the scheduler resurfaces 4 to 8 cards from older decks

The last minute is the interleaving step: the spaced-repetition scheduler pulls a handful of cards from earlier decks in the block, so the session ends with a mixed pool instead of a single-subject one. By the end of week 2 this minute alone is doing most of the work, because today's deck only contributes 4 new cards but the previous 8 decks all have something to resurface.

Why per-deck beats a global queue

The default in most card-drilling apps is one big pile of due cards, mixed across every deck you have ever uploaded. This sounds tidy. In med school it breaks first.

Two reasons. First, the pile grows uncapped. New cards from this week's lectures land on top of the back half of last week's schedule, and a single skipped day in a block week roughly doubles tomorrow's number. A bounded daily target (one deck, today's) stays the same size regardless of how the block is going. Second, when the pile gets long, the user's response is to consolidate into one long Sunday session, and the Sunday session does not happen. The per-deck nightly anchor keeps the unit of failure small: skip a night and one deck slips, not the whole pile.

FeatureOne global queue, one streakOne deck per night, per-deck tree
What you face when you open the appA global queue of every card due today, across every deck. Length grows uncapped during exam blocks.One deck, today's. A bounded session you can finish.
Source of the questionsA generic shared deck or a board question bank, written for an average curriculum.Your professor's actual slide deck, with each answer key linked to a slide number.
What happens on a second pass through the deckIdentical wording. By revisit three you are matching the first few words of the stem.Each stem auto-rephrased on revisit; same testable fact, different patient, different distractor order.
Visible reward for showing upThe cards-due number drops to zero, then refills tomorrow. Nothing carries over.The deck's tree gains height and a leaf. Still on screen tomorrow.
What missing a day costsTomorrow's queue roughly doubles. If you tracked a streak, it is gone.One deck's tree pauses at its current height. The other decks keep growing.
Daily time floor before it falls apartAbout 20 to 40 minutes once a few weeks of cards have accumulated.About 5 minutes per deck; scales by deck count, not total backlog.

The per-deck visual, lined up to the days you actually fall off

A retention habit needs a visible reward for showing up, not just a penalty for skipping. The per-deck tree is the small piece of UI carrying that load on Studyly. You can check this in the open source: the file src/components/TreeGrowth.tsx defines a four-stage STAGES array: day 1 with 0 leaves at 18 percent height, day 3 with 2 leaves at 42 percent, day 7 with 4 leaves at 66 percent, and day 14 with 7 leaves at 92 percent. The checkpoint at day 3 lands at the point a willpower-only routine usually quits (day 2 produced nothing on screen, so day 3 had nothing pulling you back), and day 14 lands at the two-week cliff where most spaced-repetition apps lose their users.

One deck's tree, day 1 to day 14

day 1day 3day 7day 14

Each checkpoint is a day you turned up for that specific deck. Missing a day pauses the tree at its current height; the other decks' trees keep growing. There is no single chain to shatter, which is the failure mode this is built to avoid.

What to do on Wednesday after you skipped Tuesday

Skipping a day in a med-school block is not the problem most guides frame it as. Two failure modes hide under that one phrase, and only one of them is real.

The fake one is a broken streak. Anki's maintainer specifically resists shipping a native streak feature, recorded in GitHub issue #4085, because all-or-nothing chains push people into clock-backdating and one-card sessions just to keep a number alive. A per-deck visual that pauses sidesteps this entirely: nothing breaks, nothing resets, you pick up where the tree paused.

The real failure mode is a backlog. Yesterday's cards stack on top of today's new deck, and if you also try to make up the missed session you turn a 5-minute night into a 15-minute night, which is the pattern that produces the next skipped day. The fix is to absorb the skip, not pay it back.

What to actually do the night after a skip

  • Do not try to make up the missed day. A double session the next night is the pattern that turns a skipped day into a skipped week.
  • Lower today's new-card intake by half until the queue is back inside your 5-minute slot. Backlog compounds faster than the raw card count suggests.
  • Drill today's new deck first, then let the scheduler pull from older decks last. Newest deck has the steepest forgetting curve.
  • Resist the urge to count days. A per-deck visual that pauses is not a chain you can shatter; treating it like one re-introduces the failure mode you avoided.

One more thing: the second pass through a deck has to feel new

A card you have seen three times with the same wording is not a retrieval rep anymore; it is a sentence-shape match. By the third revisit your brain is pattern-matching the first six words of the stem and pulling the answer from short-term memory, which the block exam will not reward because the exam stem is worded differently.

The mitigation is auto-rephrasing on revisit: the same testable fact is presented with a different patient, different phrasing, and a rotated distractor pool. The underlying topic stays pinned so the spaced-repetition scheduler can keep tracking retention, but the surface form changes, so the second and fifth pass through the deck are still real retrievals. If the tool you use does not rephrase between passes, your fifth night with the same deck is closer to rereading slides than to active recall.

Daily drill cards in med school, frequently asked

What does a daily drill cards routine actually look like in med school?

The pattern that holds up across an MS1 block looks like this: convert the day's lecture deck to questions the same evening it was given (about 60 seconds of setup), drill 30 to 60 questions from that single deck for roughly 5 minutes that night, then let a spaced-repetition scheduler interleave the older decks across the rest of the week. The deliberate part is that each session is anchored to one specific deck, not a global queue. A global queue of 'all cards due today' grows scary fast in med school because new cards keep arriving on their own schedule on top of the back-half of last week's lectures. A per-deck nightly anchor keeps the session short and keeps the failure mode local: skip one night and one deck's review slips, not all of them.

MCQ or flashcards for daily drilling?

Both, from the same source, drilled in one mixed pass. A named clinical sign is at least four facets (the maneuver, the condition, the mechanism, the look-alike sibling sign); a flat term-to-definition flashcard tests one of them. A multiple-choice stem tests recognition under distractor pressure, which is closer to what the exam grades. The honest answer is to upload one deck and ask the tool to produce both formats, then alternate them inside a single 5-minute pass: a few MCQs to force recognition under a wrong-answer trap, a few free-response or image-occlusion cards to force unprompted recall. The point is not picking a format religiously; it is making sure each fact gets retrieved more than one way before exam week.

How many questions per night is realistic across an 8-week block?

If you convert each lecture deck the day it is given, a typical 90-slide block lecture yields 60 to 80 generated multiple-choice questions plus 20 to 30 image-occlusion or free-response cards. You will not drill all of them on day one. The viable pace is 30 to 60 retrieval attempts per nightly session, mixing today's new deck with whatever cards the scheduler resurfaces from the last 5 to 10 days. Pushing past 60 attempts per session is where people start consolidating sessions into 'I will do a long block on Sunday', which is the exact pattern that collapses by week 3.

What happens when I skip a day?

Two failure modes, only one of which is real. The fake failure mode is a broken streak: a global counter resets to zero, you feel demoralised, you skip again. Anki's maintainer resists shipping a native streak for exactly this reason, recorded in GitHub issue #4085: an all-or-nothing chain pushes people into clock-backdating and one-card sessions just to keep the number alive. The real failure mode is a backlog: the questions you owed yesterday stack on top of today, plus the new deck from today's lecture. The fix that works is per-deck progress (each deck has its own tree, a missed day pauses one tree at its current height, the rest of your decks keep their progress) and lowering new-card intake for a day or two until the queue is back inside your nightly time budget. Catastrophising a single skipped day is a worse strategy than absorbing it.

When should I do the daily session?

Anchor it to something you already do every day without deciding. For most med students that is one of three slots: between the last lecture and dinner (works only if your block has clean afternoon endings), the 10 minutes after you close the laptop on the day's note-taking, or the last 5 minutes before bed. The specific slot matters less than the anchor: a session decided fresh every day stops happening by week two. The other rule is to do the session BEFORE switching to a longer 'I should also do qbank questions' block. The daily drill is the load-bearing minimum; the longer sessions are optional on top.

Should an MS1 even be drilling daily, or is this an MS2 / dedicated thing?

Daily MS1 drilling is the foundation for surviving MS2 and dedicated, not a substitute for them. The catch is what you drill on. Most MS1 block exams are professor-written from specific slide decks, not Step 1 blueprinted, so the highest-yield daily card during MS1 is one generated from your professor's lecture, not from a board question bank. Save UWorld for dedicated; spend MS1 nightly time on the deck your block exam will actually pull from. The transfer to Step 1 happens because the underlying physiology, pharm, and path do not change between a slide-fact question and a clinical vignette: a retrieval rep on potassium handling is a retrieval rep either way.

How is this different from just using Anki with daily reviews?

Anki the scheduler is fine and you can run this protocol entirely inside Anki if you want. The catch is the authoring step. Hand-making cards from a 90-slide deck runs 60 to 120 minutes for most people; do that for 4 decks in a day and the authoring tax alone is longer than lecture itself. Most people who 'fall off Anki' did not fall off spaced repetition, they fell off the cost of feeding it. The other gap is on the reward side: Anki shows one number (cards due) that resets to zero each session, so showing up leaves no visible mark and skipping doubles tomorrow's queue. A per-deck visual that accumulates with each session, plus auto-rephrasing on revisit so a second pass through the deck is a real retrieval and not a sentence-shape match, are the two pieces missing from a default Anki setup.

Will 5 minutes a night actually be enough in a hard block?

Five minutes a night per deck, drilling cards generated against that specific deck, is enough to keep the retrieval curve flat between the day the lecture was given and the day of the block exam. It is NOT enough as the only thing you do; lecture, notes, and any case-based work still sit on top of it. The reason 5 minutes works is density. Drill cards generated from your own lecture have a much higher exam-relevance hit rate than the same time spent on a generic web bank, because the question source matches the test source. In weeks where the block lands 4 decks on the same day (a cardiology week, for example), 5 minutes becomes 20 minutes split across the 4 trees, not a 4x longer single session.

One deck. Five minutes. Tonight.

Drop the lecture slide deck from today. About 60 seconds later you have roughly 200 questions across four formats (MCQ, free-response, case-style, image-occlusion), and the deck starts its tree. Free tier on app.jungleai.com, no card required.

How did this page land for you?

React to reveal totals

Comments ()

Leave a comment to see what others are saying.

Public and anonymous. No signup.