12.2 Flag and Review Workflow

Flag for Evidence, Not Worry

A flag is a promise to return with sharper focus, not permission to postpone thinking. On the first pass, give every item a real attempt: if you are unsure, pick the best available option, flag it, and move on. That protects the clock while guaranteeing nothing is left blank. Because scored and pretest items are mixed and unmarked, the goal is never to guess what counts; it is to answer everything and spend review time where it can actually raise confidence.

The four-question review gate

Before touching an answer in the review pass, run it through four checks. Naming a concrete reason turns review from gut-feel second-guessing into evidence inspection. If you cannot state a specific trigger, the original answer usually deserves to stand.

There is one well-documented exception to the "do not change answers" caution that is worth internalizing. Research on multiple-choice testing consistently finds that revisions from a clearly wrong answer to a clearly better one are usually correct, and only revisions made on a hunch tend to backfire. So the rule is not "never change"; it is "change only with a named trigger." Build the trigger list into muscle memory: a misread task verb, a date error, a vendor or scoring contradiction, an absolute word you missed, or a more specific category-anchored option you overlooked on the first pass.

Many review gains come from catching planted fact errors. If an option names a delivery vendor other than Prometric, it is wrong, because delivery is through a Prometric test center or Prometric ProProctor remote exam. If an option converts the 125-200 scaled score into a raw "you got X percent of questions right," it is wrong, because the scaled score is statistically equated and not a simple percentage. If an option states a specific current pass-rate percentage, treat it as invented unless the prompt supplies it.

If an option claims v5 beta results appear instantly at exam end, it conflicts with the rule that beta results are delayed until analysis is complete.

Sequencing and self-discipline

Other gains come from sequencing. "What should the team do first?" items usually reward an earlier planning, assessment, rating-system-selection, or documentation step, not a final tactic. If your answer jumps to the last move, reread the task. "Which best explains..." items reward a precise tie between a project choice and its controlling category, not a vague sustainability slogan. If your answer is broad, ask whether a more specific option exists.

Spotting the manufactured distractor

Green Associate items are written so the wrong options are plausible, not silly. The most common distractor families are worth memorizing so you recognize them on sight. The right idea, wrong category option states something true about sustainability but assigns it to the wrong LEED category (for example, attributing a heat-island measure to Water Efficiency instead of Sustainable Sites). The absolute option uses "always," "never," "all," or "only," which rarely survives in a framework full of conditional credits and prerequisites.

The off-by-one number option swaps a real figure for a near miss (170 to pass becomes 175; 15 CE hours becomes 18). The scope creep option describes a real LEED concept that is simply outside the question's stated boundary. When two options look equally right, the correct one is usually the more specific, directly tied to the controlling category, while the trap is broader and slogan-like.

Watch the wording of the task verb with equal care, because reversing it flips the entire answer. "Which is not a benefit..." rewards the single false statement; "Which would the team do first..." rewards the earliest step in the LEED process, often integrative-design planning rather than a construction tactic; "Which best describes..." rewards precision over generality. A single careless read of the verb is the most common avoidable error on this exam.

During timed practice, keep a short review log: items flagged, items changed, changes that turned out correct, and the trigger for each change. If most of your changes are wrong, your review is anxiety-driven, and you should switch fewer answers. If most changes are correct and tied to a named trigger, your system works. The objective is not the fewest flags; it is the most useful flags. Train the first pass too: read the final sentence of each prompt twice, mark version words (v4, v5 beta, final v5, data-collection phase, retake), and notice whether the item is about the exam itself or a project scenario.

A cleaner first pass leaves your review minutes for the genuinely hard decisions.