Capture blueprints
Turn one public outline slice into blueprints. Do not open a second chapter.
Accounting / CPA path — a weekly ladder of sessions. Treat the week as a budget for blueprints, not a festival of new items.
Scores here are relative ranks inside this atlas, not lab grades or official cut scores.
Week
Due before new
Finish due blueprints, then add a capped set from the same slice.
Repair blueprints
Rewrite every blueprints that failed twice. It was usually two facts glued together.
Mix blueprints
Let due blueprints from different chapters sit in one queue. Do not re-sort into textbook order.
Audit public outline
Check ten mature blueprints against public outline. Retire anything the outline dropped.
Light new
Halve new blueprints and spend the rest on due reviews plus one closed-book dump.
Sessions
- Due-only sprint — Twenty minutes of due blueprints, no browsing.
- New-item clinic — Thirty minutes to turn one public outline subsection into blueprints.
- Repair surgery — Fifteen minutes: split, add a cue, or move the item off infinite grind.
- Closed-book dump — From memory, list this week's high-yield names, then only flip blueprints for misses.
- Freeze rehearsal — Run a day with zero new blueprints to feel the true review load before an exam week.
Ladder
- Novice — You can produce a first set of blueprints from one public outline page in a single sitting.
- Stable — Due blueprints stays inside a weekday time box and repairs happen within a week.
- Fluent — You can explain why today's blueprints is due using the method, not "the app said so".
- Exam-ready — New blueprints is frozen before a sitting and the remaining work is almost all retrieval.
Educational atlas — not an official syllabus, medical advice, or leaked item bank. Accounting / CPA path: Keep the public outline in view and treat this page as method, not a leaked key.
ScienceMethodDrillsFast passPitfallsToolsStoriesLocale playbook