12.5 Mock Exam Review and Error Log

Mock Exam Review and Error Log

A mock exam is both a rehearsal and a diagnostic. The CFA Level I exam runs two 135-minute sessions of 90 questions each, with an approved BA II Plus or HP 12C and no notes - your mocks should mirror that pressure exactly, including the optional short break between sessions. The score matters, but the review matters more, because the review is what tells you what to change before the real sitting.

Preserve the evidence first

For every item, before you read a long explanation, record: session, topic, question number, the answer you chose, the correct answer, time spent, your confidence (high/medium/low), and whether the miss was conceptual or procedural. Capture this while you still remember why the wrong answer felt reasonable - that memory is the most valuable and most perishable data you have.

Classify every error

Also log lucky correct answers. A guessed correct item hides the same weakness as a wrong one. Mark every low-confidence answer even when the score gave you credit - the goal is readiness, not a flattering score.

Review in two passes

First pass: fix every missed item without opening any book, solving from memory using only the stem, formula sheet, and your notes. Second pass: use the curriculum, examples, or summary pages to repair the underlying weakness. A good prevention rule is short and usable under pressure. Weak: "review bonds." Strong: "for semiannual bonds, double the years and halve the annual coupon and yield." Weak: "read carefully." Strong: "circle the qualifier word before reading the choices."

Act on thresholds, not vibes

If wrong denominators show up in FSA, Economics, and Portfolio Management at once, that is one reading-and-labeling problem, not three separate content gaps - fix the labeling habit. Do not pour all review time into the hardest questions. Level I passing performance is built by collecting many standard points, so repeated misses on high-frequency basics - ethics duties, TVM setup, ratio definitions, bond price-yield direction, diversification logic - deserve top priority.

Timing and conversion

Treat timing review as fact, not feeling: note every item over two minutes and why. Build a skip rule - if no setup is clear after about one minute, mark it, enter a provisional answer (never blank, since wrong answers carry no penalty), and return later. After review, assemble a mini-set of 10-20 items matching your weaknesses, mixing old misses with fresh items so recognition does not inflate the result. Retest the same rule a few days later; retention is proven by delayed success, not same-day familiarity.

Common trap: finishing a mock and only reading the answer key. Mock review is complete only when it changes the next study plan - each miss must produce a repair task, a prevention rule, or a deliberate decision to accept residual risk. Without that conversion, the mock is a score report, not a training tool.

Reading the score by domain, not in aggregate

A single percentage hides everything useful. CFA Institute reports performance by topic band on the real result, so practice the same lens on mocks: compute your accuracy in each of the ten topics separately, then weight the gaps by the published topic weight. A 50% score in Ethics (15-20% of the exam) is far more urgent than a 50% score in Derivatives (5-8%), because the ethics points are both more numerous and historically pivotal for borderline candidates. Spend repair hours where weight times error is largest, not where the topic feels hardest.

Track the trajectory across mocks, too. The meaningful signal is whether the same error types are shrinking, not whether the headline score is rising - a score can climb on lucky guesses while the underlying reading-error rate is unchanged. If your reading errors fall from eight to three across three mocks while your calculator errors hold steady, you have proof the reading drills are working and the keystroke fluency needs attention next.

Sequencing the final weeks

A practical schedule: take a full timed mock, spend one to two days on the two-pass review and error log, run targeted repair drills for two to three days, then take the next mock to confirm the repairs held. Repeat this loop two or three times in the final month. Leave the last few days for light review of your prevention rules and formula sheet rather than new material, because cramming new concepts late tends to displace retrievable knowledge you already own.

The aim of the entire cycle is a stable, repeatable process - calm pacing, clean keystrokes, accurate reading, and disciplined ethics judgment - that holds up under the real two-session, 180-question format.