11.6 Scenario Drills and Review Debriefs

Make Every Miss Diagnostic

Scenario practice only pays off if review is specific. "I missed this because I forgot LEED" teaches nothing. A better debrief names the failure mode. Did you choose the wrong domain anchor? Did you answer a different question from the one asked? Did you confuse v4 and v5 beta timing? Did you accept a green-sounding distractor that invented a pass rate or promised a result? Did you miss a logistics fact, such as Prometric delivery or the cap of three attempts in any 12-month period?

Build Drills Around the Real Format

Mirror the actual exam: 100 multiple-choice items, one correct answer each, a 2-hour testing window, and a total appointment of about 2 hours 20 minutes. A drill can be smaller than the full exam, but it should still be timed. If every item is untimed and reviewed immediately, you will not build the pacing and decision-from-memory judgment the closed-book appointment demands. A practical cadence: 25 items in 30 minutes, then a structured debrief.

The Debrief Table

Name the Miss Type

The miss-type column matters most. Four recurring types each need a different fix:

• Content gap — you did not know the fact or domain. Fix: restudy that domain's core concepts.
• Reading error — you knew the material but missed the task. Fix: slow down on the final sentence and the decision verb.
• Version-confusion error — you mixed v4, v5 beta, and final v5 facts. Fix: keep a one-page transition table and quiz the dates.
• Unsupported-fact error — you accepted a claim the official source does not support, such as an invented pass rate. Fix: reread the logistics facts and rewrite them in exact wording.

Review the Distractors, Not Just the Key

For each cross-category item, write one short reason every wrong option failed: wrong vendor, wrong timing, wrong domain, premature action, unsupported promise, or too vague. This is more valuable than rereading the correct explanation because it trains your eye to recognize how plausible wrong answers are built. Over a week, you will start predicting the trap before you read the key.

Keep Practice Original and Weekly

Do not copy official examples into your notes. Build new items that exercise the same moves — one item tests beta result expectations, another tests v4/v5 date boundaries, another tests whether a project prompt is really asking for process sequence. Original practice keeps you from memorizing one wording pattern and missing the skill underneath.

At the end of each week, tally your misses by category and let the count drive your next sessions:

• Many unsupported-fact errors → reread the logistics and scoring facts; rewrite them in exact wording.
• Many task-reading errors → drill slowing down on the last sentence of each prompt.
• Many domain-anchor errors → drill the official domain lists until you can label any scenario in seconds.
• Many version-confusion errors → re-quiz the v4/v5 transition dates and the beta-vs-final result rule.

This converts final review from random rereading into targeted maintenance, and it is exactly the disciplined, fact-anchored reasoning the cross-category items reward.

A One-Week Drill Schedule

A simple structure prevents review from drifting into rereading. Spread drills across the week so each day pairs a timed set with a focused debrief:

• Day 1–2: mixed cross-category sets of 25 items in 30 minutes; debrief by domain anchor.
• Day 3: logistics-only set (dates, scoring, retakes, delivery); debrief by unsupported-fact errors.
• Day 4: synergy and tradeoff sets; debrief by whether you chased a secondary clue or overreached.
• Day 5: a full 100-item timed simulation under appointment conditions; no pausing, no lookups.
• Day 6: rework only your missed items, writing the correct reasoning from scratch.
• Day 7: tally misses by category and choose next week's focus.

Why the Tally Beats Re-Reading

The weekly tally is the engine of improvement because it turns a pile of misses into a ranked to-do list. If unsupported-fact errors dominate, your fix is concrete: rewrite the logistics and scoring facts in exact wording and quiz them daily. If domain-anchor errors dominate, drill the official domain lists until labeling is instant. If version-confusion errors dominate, re-quiz the v4/v5 dates and the beta-versus-final result rule until you never mix them. Reading explanations feels productive but rarely changes behavior; counting failure modes and attacking the largest one does.

That measurable loop — drill, debrief, tally, target — is what carries cross-category skill from practice into the real 2-hour appointment.