Stepora Blog · UWorld
How to Review UWorld Questions: The 5-Bucket Method That Turns Misses Into Tomorrow's Drills
You finished the block. Now comes the part that actually moves your score — and the part most students skip or rush. Reviewing a UWorld block is not re-reading explanations until your eyes glaze over. It is a structured pass with one job: for every question you missed, name exactly why you missed it, and turn that reason into something you will do tomorrow.
Review every 40-question block the same day you do it: about 1.5–2.5 hours of review on top of the hour the block took. For each miss, assign exactly one of five buckets — knowledge gap, misread, reasoning error, second-guess, or timing — and let the biggest bucket set tomorrow's drills. Review the questions you got right too, but fast: one line on why each right answer was right. Never carry review debt into the next day.
First, budget the review — or it will not happen
A timed 40-question block takes roughly an hour to sit through, and 1.5–2.5 hours to review properly. That makes one honest block a 2.5–3.5-hour commitment, not a one-hour task. Most review failures are really scheduling failures: a student plans four blocks a day, finishes the doing, and discovers at midnight that the reviewing never fit.
So the first rule of reviewing is set before you open the first question: never schedule more blocks than you can fully review the same day. In dedicated, that usually means 2–3 blocks (80–120 questions) with full review. A reviewed 40 beats two skimmed 40s every time — in the Deng et al. Step 2 CK data, every ~445 additional practice questions tracked with about one more point, but only because those questions were studied, not merely completed.
The 5-bucket error log
Open your block, explanations on, and go question by question. For every miss, write one line in a running log — the question's topic, and exactly one bucket:
| Bucket | What it looks like | The fix it points to |
|---|---|---|
| 1. Knowledge gap | You never learned the fact the question tested | Learn it properly — one focused pass on that topic, then a drill set on it tomorrow |
| 2. Misread | You answered a different question — missed the "except", the patient's age, the time course | A reading protocol: read the actual question first, mark the decisive detail, then read the stem |
| 3. Reasoning error | You knew the facts but picked the wrong mechanism or next step | Deeper review: write the one-sentence rule the question tested, in your own words |
| 4. Second-guess | Your first instinct was right; you changed it | A confidence rule: change an answer only on new evidence, never on mood |
| 5. Timing | You rushed the last ten questions, or never reached them | Pacing practice: timed blocks with checkpoints, so the clock becomes a reflex |
One bucket per miss, no hedging. A miss tagged "kind of a knowledge gap, kind of a misread" is a miss you have not diagnosed, and an undiagnosed miss gets the wrong fix. If you genuinely cannot tell, default to knowledge gap and check the explanation again — the explanation usually tells you which it was.
The review pass, step by step
- Work in the order you answered, not in score order. Reviewing in the order you sat the block keeps the reasoning fresh — you remember what you were thinking, which is the whole point of diagnosing a misread or a second-guess.
- Start with the misses, then skim the rights. Misses get the full treatment: explanation, one-sentence rule, bucket tag, log line. Questions you got right get a fast pass — one line on why the right answer was right, and a check that you got it right for the right reason. A lucky guess is a miss wearing a costume; log it as one.
- Write the rule, don't just read it. For every miss, write one sentence: the rule the question tested, in your own words. Ten written rules at the end of a review session beat ten read explanations — reading feels like learning, writing proves it.
- Close the loop in the log. End the session by counting the buckets. Whichever bucket holds the most misses owns tomorrow's drill time — that is the entire point of the log. A review session that ends without a plan for tomorrow was a reading session, not a review session.
Turning misses into tomorrow's drills
This is where the 5-bucket log earns its keep. Your biggest bucket is not a statistic — it is tomorrow's first task:
- Knowledge gaps clustered in one system: tomorrow starts with a targeted re-learn on that system, then a drill set drawn from your incorrects on it. Not "study more" — study that.
- Misreads or second-guesses leading: tomorrow's block is done with the strict reading protocol — question first, decisive detail marked, answer changed only on new evidence. The drill is the method, not the content.
- Reasoning errors leading: tomorrow's review goes deeper, not longer — every miss becomes a written rule, and the rules get re-read before the next block.
- Timing leading: tomorrow's block is a pacing drill with checkpoints, and the last ten questions get the same calm as the first ten.
Over a week, the bucket counts tell you what no single percentage can: whether your prep has a content problem, a reading problem, a confidence problem, or a pacing problem. And when a plateau arrives — two NBME forms returning the same score — the same buckets are the diagnosis.
What not to do
Don't carry review debt. Done questions piling up unreviewed is the single most common way a prep quietly stalls: the question count rises while the NBME trend stays flat. If debt has already built up, stop doing new blocks until it is cleared — review debt is paid by doing less, not by working longer.
Don't review only your strengths. It feels productive to re-read explanations for topics you already know. It is the review equivalent of re-doing questions you already got right — comfortable, and useless. Your log decides the drills; your feelings do not.
Don't let the review eat the NBME chain. Reviews are daily work; NBMEs are the decision-grade assessment. Keep the cadence — current online forms 28–34 at $62 each, 7–14 days apart, last full form at least 7 days before the exam, Free 120 3–7 days out — and let the NBMEs, not your block percentages, decide the exam date. Two recent forms at about 69–70% correct (EPC) is the green light.
Done right, a review session is the most honest hour in your prep: it tells you, in writing, exactly what is still broken and exactly what tomorrow fixes first. Fit it into a full day with the Step 1 study schedule, or let the schedule maker build the review time into your day automatically — and if your block percentages are confusing you, here is what they actually mean.
Turn this schedule into a plan that runs itself
Stepora takes your exam date, your hours and your resources, then runs every day for you — one mission at a time, with NBME tracking and automatic replanning when life happens.
Build my plan — $1.99/monthFrequently asked questions
How long should it take to review a 40-question UWorld block?
About 1.5–2.5 hours of review on top of the roughly one hour the timed block took — so 2.5–3.5 hours for one honest block. That is why you should never schedule more blocks than you can fully review the same day: review debt is the most common way a prep quietly stalls.
Should I review the questions I got right?
Yes, but fast. Skim each right answer and confirm you got it right for the right reason — a lucky guess is a miss wearing a costume, and it belongs in your error log. Misses get the full treatment: explanation, a one-sentence rule in your own words, and a bucket tag.
What is the 5-bucket error log?
A way to diagnose every miss with exactly one cause: knowledge gap, misread, reasoning error, second-guess, or timing. Count the buckets at the end of each review session, and let the biggest bucket set tomorrow's drills. Over a week, the counts tell you whether your prep has a content problem, a reading problem, a confidence problem, or a pacing problem.
What should I do if my misses are mostly misreads and second-guesses?
Treat it as a method problem, not a knowledge problem — more volume will not fix it. Do timed blocks with a strict protocol: read the actual question first, mark the decisive detail, decide once, and change an answer only on new evidence, never on mood.
Keep planning
Reviewing is one block inside a full plan — these guides cover the rest: