REAC Qualifying Exam common mistakes
REAC Qualifying Exam · Understand the traps and how to avoid them.
Citing a regulation or statute from memory by number and title without confirming that the cited provision actually covers the scenario described in the question, so the answer names a real rule that does not apply.
Candidates study regulation lists as a memorization exercise and pattern-match on keywords (for example, seeing 'waste' or 'discharge' and reaching for the first rule that comes to mind) instead of reading what the question's fact pattern requires and checking whether the cited provision's scope, definitions, and trigger conditions match it.
What to do instead
For every regulatory question, write out three things before choosing: (1) the activity or substance at issue, (2) the jurisdictional trigger in the question (who is doing it, where, and under what authority), and (3) the specific definitional term the provision hinges on. Then verify the citation against that term. Practice by taking five rules you know and writing the exact scope clause of each, then finding a scenario the rule does not reach.
Treating a permit condition, guidance document, or agency policy statement as if it carried the same legal weight as a statute or regulation, and answering that something is 'required' when it is only recommended or is a condition of one facility's permit.
Candidates conflate the hierarchy of authorities because in day-to-day practice permits and guidance drive most decisions, and exam questions often quote permit-style language to test exactly this distinction. The habit of practical compliance thinking overrides the legal hierarchy.
What to do instead
Build a one-page authority ladder and use it on every question: constitution/statute, then regulation, then permit condition, then guidance/policy, then standard practice. For each answer option, label which rung it sits on. If a question asks what is legally required, reject options grounded only in guidance or a single permit unless the question is explicitly about that permit.
Selecting an environmental assessment conclusion (significant impact, no significant impact, categorical exclusion) based only on the size or type of the project rather than on the assessed context and intensity of effects, including cumulative and indirect effects.
Candidates memorize project categories and thresholds and then apply them mechanically. Assessment frameworks are context-sensitive, and the most common trap is an option that sounds decisive but ignores cumulative, indirect, or connected actions that the question deliberately includes.
What to do instead
Before answering any assessment question, list the effects the fact pattern mentions across four axes: direct, indirect, cumulative, and connected actions. Then check whether the proposed conclusion accounts for all four. If an option concludes 'no significant impact' while the facts describe a cumulative effect, that option is wrong regardless of project size.
Confusing the purpose of screening, scoping, and the substantive impact analysis, and answering a question about one stage with the output of another (for example, giving a scoping output when asked what screening determines).
The stages share vocabulary and are taught together, so candidates blur them under time pressure. They also recall the documents produced at each stage but not the decision each stage makes, which is what the exam tests.
What to do instead
Memorize each stage as a decision question: screening asks 'does this require assessment at all and at what level'; scoping asks 'what issues and boundaries will the assessment cover'; impact analysis asks 'what are the effects and their significance'; decision and follow-up ask 'what is approved and how is it monitored'. Drill by writing the stage name next to each verb in a practice question before reading the answer options.
Designing or critiquing a sampling plan without matching the sampling design (random, stratified, systematic, judgment) to the stated objective, and without addressing sample size, replicates, and field blanks as separate requirements.
Candidates default to the design they use most often in their own workplace and evaluate options by familiarity rather than by fit to the stated data quality objective. They also treat quality control samples as an afterthought rather than a design element the question is testing.
What to do instead
For each sampling question, state the objective in one sentence (characterize a mean, detect a hotspot, delineate a boundary, demonstrate compliance) and then select the design that serves it. Separately list the QC samples the plan needs and justify each: field blanks for contamination, duplicates for precision, matrix spikes for recovery, and enough replicates to estimate variance. If an option lacks a QC element the objective requires, it is incomplete.
Reporting a measured concentration without its detection limit and uncertainty context, or comparing a result to a regulatory threshold when the result is below the method detection limit or within the uncertainty band, and declaring a clean pass or fail.
Candidates focus on the numeric result and treat the detection limit as a footnote. Questions frequently plant a result near or below the detection limit to test whether the candidate recognizes that a 'less than' value does not establish compliance or exceedance by itself.
What to do instead
Adopt a rule: never compare a value to a threshold without first checking whether the value is above the detection limit and whether the difference from the threshold exceeds the combined uncertainty. For censored data, state the handling method (substitution, Kaplan-Meier, or maximum likelihood) explicitly. Practice by rewriting three compliance statements to include detection limit, uncertainty, and censoring treatment.
Treating a quality assurance project plan as a document to be filed rather than a set of testable commitments, and failing to identify which data quality indicators (precision, accuracy, representativeness, comparability, completeness, sensitivity) a given question is actually about.
Candidates learn the indicator acronyms as a list and cannot map a described problem back to the right indicator. When a question describes duplicate results diverging, they may answer 'accuracy' because both sound like 'correctness', missing that duplicates test precision.
What to do instead
Build a mapping table from symptom to indicator: duplicates and replicates map to precision; reference materials and spikes map to accuracy (bias); sampling design and location map to representativeness; method and units map to comparability; recovered valid samples over planned samples map to completeness; detection limit and calibration map to sensitivity. Drill by reading a described QA failure and naming the indicator before seeing options.
Confusing data verification (checking that data were collected and transcribed per the plan) with data validation (judging whether data meet the quality objectives and are usable for the decision), and approving data as valid when only verification was performed.
The two terms are used loosely in practice and often collapse into 'checking the data'. Candidates answer based on the everyday meaning of 'valid' rather than the technical stage distinction the exam is drawing.
What to do instead
Memorize the sequence: collection, verification (completeness, transcription, holding times, calibration checks), validation (comparison against data quality objectives, qualification and flagging), then usability determination. When a question asks what step is missing, locate where in the sequence the described activity sits and name the next step. Practice by writing what evidence each stage produces.
Writing or evaluating a report that presents conclusions without traceable links to the underlying data, methods, and limitations, and omitting the uncertainty, detection limits, and data gaps that a reader needs to interpret the findings.
Candidates mirror the summary-style reports they see at work, which are written for managers and compress method detail. Exam questions test whether the candidate knows that a defensible report must let an independent reader reconstruct how each conclusion was reached.
What to do instead
Use a checklist for every reporting question: objective, methods and standards cited, data quality summary, results with uncertainty and detection limits, limitations and data gaps, conclusions tied to specific results, and references. If an answer option states a conclusion with no supporting data trail, mark it deficient even if the conclusion sounds correct.
Failing to recognize and disclose a conflict of interest, or accepting a client's preferred conclusion and back-filling the analysis, when the question describes pressure to reach a predetermined result or a personal or financial stake in the outcome.
Candidates read ethics questions as abstract and look for the most technically sophisticated option, missing that the correct answer is usually the straightforward disclosure or withdrawal step. Workplace norms that treat client preference as service also push candidates toward accommodation.
What to do instead
For any ethics scenario, apply a fixed sequence: identify the stake, disclose it in writing to the appropriate party, recuse or mitigate where the stake could bias the judgment, and document the decision. If an option accommodates the pressure without disclosure, eliminate it. Practice by writing the disclosure statement you would send in three hypothetical scenarios.