2.6 Documentation Mindset and Process Scenario Reasoning
Key Takeaways
- The exam is closed-book, so official references are for study and verification before the appointment, not lookup during the exam.
- Process scenarios should be sorted by actor, version, source type, and workflow stage before selecting an answer.
- Scored and unscored questions are mixed randomly, so every process item should be treated as potentially scored.
- A strong documentation mindset rejects unsupported pass rates, raw score percentages, vendor substitutions, and invented exact counts.
Think like a careful document reviewer
A documentation mindset does not mean the Green Associate exam is open-book. The source brief is clear that the exam is not open-book. Instead, documentation mindset means studying official sources before the appointment, internalizing the key structures, and answering from those structures during the two-hour delivery window. It also means reading prompts the way a careful reviewer reads a submittal: identify the actor, version, workflow stage, and controlling source before deciding what the answer choice is really claiming.
For this chapter, the actor might be an exam candidate, a credential holder, or a project team. The version might be v4, v5 beta, or final v5. The workflow stage might be registration, purchasing, test delivery, result reporting, project certification guidance, rating-system selection, or maintenance. The controlling source might be the candidate handbook, the credential page, the registration policy, Guide to Certification: Commercial, LEED rating systems, addenda, or LEED Rating System Selection Guidance. Sorting these variables reduces the chance of choosing a true statement that answers the wrong issue.
| Scenario clue | Question to ask |
|---|---|
| Candidate fee | Which official fee category applies? |
| Remote exam | Is Prometric ProProctor the delivery frame? |
| v5 beta result | Is beta result delay the controlling fact? |
| Rating-system selection | Which official selection or rating-system reference applies? |
| Project certification workflow | Does Guide to Certification: Commercial control the study frame? |
| Maintenance | Is the 15 CE hours within 2 years requirement relevant? |
Documentation mindset also includes rejecting unsupported claims. The source brief tells writers not to invent published pass-rate claims, not to translate the scaled passing score into a raw percentage, not to promise passing or score gains, not to claim exact scored and unscored counts beyond what the handbook states, and not to use another testing-vendor name in place of Prometric. These guardrails are not only writing rules; they are answer-choice filters. If an option depends on a forbidden claim, it is likely not the best answer in a source-based practice item.
Because scored and unscored questions are mixed randomly and the exact current unscored count is not publicly stated, every process scenario deserves attention. A candidate cannot decide that a process question is experimental and skip it. The stronger approach is to answer all items, flag uncertain ones, and review if time remains. Timed practice should reproduce the closed-book setting and the one-correct-answer format.
Use this reasoning sequence on process items:
- Name the topic: delivery, scoring, eligibility, domain structure, certification workflow, rating-system selection, or maintenance.
- Name the version or phase: v4, v5 beta data collection, v5 beta testing-only, or final v5.
- Identify whether the prompt is about the candidate exam or project certification.
- Eliminate claims that use the wrong vendor, wrong date, wrong result timing, or unsupported number.
- Choose the answer that stays closest to the official source brief.
This method is intentionally conservative. It does not promise a passing result and does not inflate the source brief into facts it does not contain. Instead, it gives the candidate a repeatable way to handle process questions under exam conditions. That is the heart of LEED Process study: use official references while learning, preserve version control, and answer the question that was actually asked.
What does documentation mindset mean for this closed-book exam?
Which answer-choice claim should be rejected under the source brief guardrails?
A process scenario asks about a v5 beta candidate's result timing. What should control the answer?