Six weeks is long enough to transform exam outcomes — but only if you stop “doing revision” and start running a system. The sprint has three phases: (1) cover the map (breadth), (2) attack weakness (depth), (3) rehearse performance (simulation).
Design principle
High-yield revision is a feedback loop: retrieve → test → analyse errors → schedule the next retrieval. Evidence reviews consistently favour practice testing and distributed practice over passive techniques (Dunlosky et al., 2013).
Assumption: you have limited time and variable shift patterns. So we build around a “Minimum Viable Day” (MVD) and a “Full Day” template. If you hit the MVD consistently, you will progress even on weeks with long shifts.
1
Step 0 — Setup (Day 1, 60–90 minutes)
Choose your primary Q-bank(s). Create three lists: (A) Core topics, (B) Weak topics (from prior mocks), (C) High-risk traps (things you repeatedly miss). Set a daily question target (small but non-negotiable). Decide your mock schedule for Weeks 4–6 now.
2
Weeks 1–3 — Breadth (Knowledge acquisition)
Goal: touch the full blueprint once while building retrieval cues. Daily: 60–120 Qs (or 30–60 if working long shifts), closed-book. For every session, extract 3–5 ‘decision rules’ (thresholds, contraindications, next best step) and schedule them for spaced review. Do not write long notes.
3
Week 1 template (repeat for Weeks 2–3)
Mon–Sat: (1) 10-minute quick recall warm-up (blurt from memory), (2) Q-bank block, (3) error log + spaced cards. Sun: light consolidation + catch-up reviews + rest. If behind, reduce new content but keep retrieval and reviews.
4
Weeks 4–5 — Depth (Weakness targeting)
Goal: turn weaknesses into strengths. Use your error log to rank topics by “marks lost per hour.” Create focused sets (e.g., cardio ECGs, rash differentials, paeds dosing) and re-test until accuracy stabilises. Add 1–2 mixed-topic sets daily to maintain breadth.
5
Week 6 — Simulation (Timed mocks)
Goal: performance under exam constraints. Do 2–4 full timed mocks (depending on the exam), plus short timed blocks on non-mock days. After each mock: spend 2–3 hours on error analysis and targeted re-testing. Don’t chase volume — chase correction.
6
Minimum Viable Day (MVD) — when you’re exhausted
Do 20–30 closed-book questions + 10 minutes of review cards. That’s it. Consistency beats hero days. Never miss twice in a row.
What “good” looks like in the sprint
You can explain your misses in one sentence (not “I was tired”), your error log shrinks week-on-week, and your mock scores stabilise under timed conditions. That’s metacognition turning into marks.
The tempting time-waster
Rewriting notes and making beautiful summaries is often performance, not learning. If it does not force recall or change your future decisions, it is low yield.
SourceDunlosky et al. (2013) — Evidence on effective study techniques
Open Link SourceBjork & Bjork — Desirable difficulties (PDF)
Open Link