Elaborative interrogation — a protocol you can run this week. A working protocol for why-question margins is capture, schedule, retrieve, repair, mix, audit.
Scores here are relative ranks inside this atlas, not lab grades or official cut scores.
Steps
- Capture
Capture why-questions from the public outline as one prompt, answer hidden.
If you need a comma, split.
- Schedule
Schedule a daily due time for why-questions and a cap on new items.
Cap new before you cap reviews.
- Retrieve
Retrieve why-questions with the page closed. A peek is a fail.
Recognition is not recall.
- Repair
Repair why-questions that failed twice the same week.
Two facts glued together is the usual leech.
- Mix
Mix why-questions from different chapters in one session.
Do not re-sort into textbook order.
- Audit
Audit why-questions against the public outline once a week.
If the outline moved, the deck must move.
Protocol
- Daily queue — Clear due why-question margins before adding anything from public outline. Leftovers are scheduling debt.
- New-item cap — Cap new why-question margins so the queue cannot explode the night before a sitting.
- Repair clinic — Rewrite why-question margins that failed twice instead of grinding it infinitely.
- Pre-event freeze — Freeze new why-question margins 10–14 days before the sitting so only mature retrieval remains.
Variants
- Software queue — A digital list of due why-question margins. Useful when volume exceeds a shoebox.
- Paper analog — Index cards or a notebook column for why-question margins. Honest if you actually move them.
- Oral walk-through — Speak why-question margins aloud. Good when the exam rewards oral retrieval.
- Calendar-only — Write review dates for why-question margins in a diary without ease grades.
Educational atlas — not an official syllabus, medical advice, or leaked item bank. Elaborative interrogation: Keep the public outline in view and treat this page as method, not a leaked key.
ScienceMethodDrillsFast passPitfallsToolsStoriesLocale playbook