Study for the REM credential by practicing a two-step decision habit: first classify what a finding is (an observation needing more information, a confirmed issue needing control, or a non-issue), then apply the logic that matches that classification. Assessment findings call for further investigation and documentation; confirmed issues call for controls, corrective action, and verification. Work scenarios out loud, state your reasoning, and check yourself against a rubric rather than only checking whether your final answer was right.
Two different questions hide inside one scenario: what do I know vs. what do I do
REM-style scenarios test whether you can separate assessment decisions (gathering and interpreting information) from management decisions (controlling a confirmed problem). Train the split deliberately instead of jumping straight to a fix.
Assessment logic answers questions like: what information is missing, what evidence already exists, what does this observation suggest, and what investigation step comes next? The correct answer here is usually an information-gathering action paired with documentation, even when the finding looks alarming. If you catch yourself proposing a control before you can state what the finding actually is, you have skipped the assessment layer.
Management logic takes over only when the problem is characterized: a hazard is confirmed, its extent or severity is known well enough to act, and the question becomes which control, corrective action, or operational change is appropriate and how you will verify it worked. Practicing the split means reading each scenario twice: once asking what you would need to know, once asking what you would do with knowledge in hand.
- Assessment decisions: recognize, investigate, sample, interpret, document.
- Management decisions: select controls, assign responsibility, correct, verify, record.
- The checkpoint question: can I describe the finding in one sentence before acting on it?
Classifying findings: recognized condition, characterized issue, or non-issue
Most scenario mistakes begin with mislabeling an observation. Sort every finding into three categories before deciding anything: needs further assessment, confirmed and needs control, or adequately explained with no action needed.
A recognized condition is an observation that suggests a possible environmental problem but does not yet establish one: stained soil, an unexplained odor, drums without labels, a historical record of on-site chemical use. The defining feature is uncertainty. The correct response is documentation and a recommended next assessment step, not a remediation decision. Compare this with a characterized issue, where investigation has established the nature and extent of the problem, and management responses become the right subject.
The third category, an adequately explained observation, also matters. Not every stain is a release and not every old record is a current hazard; a finding supported by evidence showing no problem should be documented and closed, not escalated. Practice all three categories together, and build your own practice sets so they include findings whose correct handling is 'recommend further assessment' and findings whose correct handling is 'document the explanation.' The classification, not the wording of the answers, is what tells you which is which.
| Finding type | Defining feature | Correct next step | Common wrong move |
|---|---|---|---|
| Recognized condition | Observation suggests a possible problem; extent unknown | Document and recommend further assessment | Selecting a cleanup or control immediately |
| Characterized issue | Investigation has established nature and extent | Choose and verify a control or corrective action | Ordering more assessment that adds no new information |
| Adequately explained observation | Evidence shows no problem exists | Document the rationale and close the finding | Escalating a closed item or ignoring the documentation step |
Worked scenario 1: the stained soil near the former storage area
A site walkthrough reveals stained soil beside a pad once used for drum storage. The defensible response is to record the recognized environmental condition and recommend further subsurface assessment, not to select a remedy.
The plausible mistake here is jumping to action: choosing an excavation or a treatment method because staining suggests contamination. That answer sounds decisive, but it puts a management response ahead of the assessment that should precede it. At that point you do not know whether the staining reflects a past release, a harmless residue, or something unrelated. A remedy selected before characterization may address the wrong area, miss the actual pathway, and create a written record implying a conclusion the evidence does not support.
The better decision has two parts. First, document the observation precisely: location, visual characteristics, surrounding features, and the historical connection to drum storage. Second, recommend the appropriate assessment step, such as subsurface investigation to characterize soil in that area, with the finding logged as requiring further evaluation. Why it matters: the sequencing protects the quality of every later decision. Characterization data determines whether a control or cleanup is even warranted and, if so, where and how extensive. An answer that documents first and assesses second demonstrates exactly this ordering.
Management applied practice: selecting controls in the right order
Once an issue is characterized, management questions ask which control fits best. Compare candidate controls rather than naming the first one that comes to mind, and be ready to explain why one ranks above another.
For hazards affecting people, compare controls using the hierarchy: elimination or substitution first, then engineering controls, then administrative measures, then personal protective equipment. The hierarchy exists because controls higher up remove or reduce the hazard itself, while lower-tier controls depend on individual behavior and equipment condition. A scenario answer that reaches for protective equipment when a substitution is available inverts that logic, even if the equipment choice is itself reasonable.
For environmental issues, compare controls on parallel criteria: does the control address the source, the pathway, or only the symptoms; is it durable or does it require constant attention; can its effectiveness be verified; and what does it cost in resources and disruption. Practice articulating the comparison out loud. An answer that says 'I would prefer substitution over PPE here because it removes exposure rather than shielding it' demonstrates applied reasoning, which is the skill the management portion of preparation is meant to build.
- Rank candidate controls: source removal beats pathway control beats symptom management.
- Ask whether effectiveness can be verified after implementation.
- Ask who maintains the control and whether that creates a new dependency.
Worked scenario 2: the corrective action request from an internal audit
An audit flags repeated late inspections. The tempting fix is to redo the missed inspections, but the defensible management response is root cause analysis, a corrective action addressing the cause, and verification that it worked.
The plausible mistake is treating the audit finding as a to-do item: complete the overdue inspections, mark the finding closed, move on. That response fixes the visible symptom while leaving the cause untouched, so the same finding reappears at the next audit. It also skips a professional obligation: a corrective action request asks why the failure happened, not just what to clean up. Closing a finding without addressing its cause undermines the documentation trail that the finding itself created.
The better decision follows a sequence: investigate the root cause (perhaps inspection scheduling was never assigned to a named person, or the procedure conflicts with actual shift patterns), implement a corrective action aimed at that cause, and then verify effectiveness over a defined period before closing. Compare the two answers directly: 'redo the inspections' addresses one instance; 'reassign ownership of the schedule and verify three consecutive on-time inspection cycles' addresses the pattern. The second answer is longer precisely because it demonstrates the applied management reasoning that corrective action logic exists to produce.
Documentation, ethics, and what makes a written decision defensible
REM-level practice ties decisions to records: what was observed, what was concluded, what was recommended, and who was told. Train yourself to write the one-paragraph record for every scenario answer, not just name the action.
A defensible record answers four questions: what did I observe, what do I conclude from it, what action do I recommend or have taken, and who needs to know. Notice that this structure works for all three finding categories from earlier; the difference is the content, not the format. Documentation is also where professional standards become practical: recording findings accurately even when they are unwelcome, distinguishing observation from interpretation, and not letting schedule or cost pressure compress an assessment step the record shows was needed.
Practice by writing the record as part of every scenario you work. For the stained soil scenario, your paragraph states the observation, the historical basis for concern, the recommended assessment step, and the recipient of the recommendation. If your paragraph would leave a reader unable to reconstruct why you acted as you did, the record is not yet defensible. This habit also sharpens scenario answers generally: stating the documentation step explicitly is almost always stronger than leaving it implied, because the reader can see the decision trail rather than having to assume one.
A self-check exercise, a rubric, and a preparation sequence you can adapt
Use short paper scenarios and sort every finding before answering. Track your reasoning, not just your answers, against a rubric. Build your sequence from classification practice through full scenario write-ups.
Exercise: write five short scenarios, each containing two or three observations (for example, unlabeled containers, a functioning treatment unit, an outdated permit reference). For each observation, classify it as recognized condition, characterized issue, or adequately explained observation, then state the next step and write the one-paragraph record. Score yourself with this rubric: classification correct (1 point), next step matches the classification (1 point), record states observation, conclusion, action, and recipient (1 point) — 3 points possible per observation, so each scenario is worth 6 to 9 points depending on the number of observations. A reasonable learning milestone before moving on is a perfect score on every observation in at least four of your five scenarios, with no single observation falling below 2 of 3 points; treat this as a progress marker, not a prediction of exam results.
Adaptable sequence: weeks one and two, build concept vocabulary and practice classification only. Weeks three and four, add control-selection comparisons for characterized issues, writing the reasoning aloud. Weeks five and six, work full scenarios end to end, including documentation and verification steps, and re-run any scenario you misclassified to see whether the classification or the downstream logic failed. In the final stretch, mix everything together under time pressure and use the readiness checks below. Adjust the pacing to the time you actually have; the order matters more than the calendar.
- Readiness check 1: you can classify any scenario observation into one of the three finding categories and justify it in one sentence.
- Readiness check 2: for a characterized issue, you can compare two candidate controls and state why one ranks higher.
- Readiness check 3: your written records consistently contain observation, conclusion, action, and recipient.
- Readiness check 4: when you get an answer wrong, you can tell whether the classification, the control choice, or the documentation failed.
- For administrative details about the credential itself, consult the issuing body directly rather than relying on secondhand summaries.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.