Treat your BD+C preparation as training a decision procedure: for any project fact, ask whether it touches a prerequisite, a credit, or a rating-system boundary, then choose a compliance path and check its side effects on other credits. Work scenarios, not flashcards alone, until that procedure runs without prompting.
Why prerequisite-versus-credit thinking changes your answers
Prerequisites are mandatory and unscored; credits are optional and scored. BD+C scenario questions hinge on knowing which is which, because a project that misses a prerequisite fails regardless of how many points it accumulates elsewhere.
Start every practice scenario by sorting the project's actions into three buckets: things that must happen (prerequisites), things that earn optional points (credits), and things that define whether the rating system even applies (requirements at the system level). Trainees who skip this step answer point-chasing questions confidently but wrongly, because they treat a mandatory item as a choice.
Build the sort into a physical habit. When you read a credit reference or study outline, write a one-line trigger for each prerequisite: the condition that, if absent, disqualifies the project. Later, when a scenario mentions energy systems, water fixtures, or ventilation design, you should reflexively check whether the mandatory baseline is addressed before evaluating any scored option on the table.
- Prerequisite: compliance is mandatory; no points are awarded for it.
- Credit: optional; points contribute to the certification level.
- System-level requirements: conditions the project must meet to use the rating system at all.
Matching the rating system to the project: BD+C and its neighbors
BD+C applies to new construction and major renovations. Scenario prompts deliberately blur boundaries with interior-focused and operations-focused rating systems, so practice identifying which system a project description actually calls for before evaluating any credits.
USGBC's credential materials describe the LEED AP with specialty as measuring knowledge of a specific rating system and the certification process, with the Green Associate as a prerequisite. That structure matters for study planning: your specialty exam assumes the general green-building foundation and adds depth in how design-phase projects are rated and documented.
In drills, read each project description twice: once for the scope of work and once for the occupancy and ownership facts. A full new building points toward BD+C; a tenant fit-out scope points toward an interiors-focused system; an existing building seeking ongoing performance improvement points toward an operations-focused system. Misreading the scope makes every later credit question unanswerable, so this identification step deserves deliberate practice, not a glance.
The integrative process: why early decisions dominate scenario answers
BD+C scenario questions test whether you can place a decision at the right project phase. Integrative thinking means assembling the team and analyzing energy, water, and site interdependencies before schematic design hardens the options.
The distinguishing behavior of integrative design is timing. Analysis happens with the whole team present — owner, designers, engineers, and, where relevant, the commissioning authority — so strategies are compared while changing them is still cheap. When a scenario shows a team discovering an energy problem during construction documents, the better answer usually involves moving that analysis earlier, not fixing it later.
Practice by rewriting scenario timelines. Take a project narrative and mark each decision as discovery, analysis, design, or construction phase. Then ask which decisions could have been moved one phase earlier and what that move would have preserved — design options, cost, or credit opportunities. This rewriting exercise builds the instinct the exam asks you to demonstrate: recognizing the phase in which a described action should have occurred.
Worked scenario: a daylighting decision that backfires on energy
A design team maximizes glazing to chase a daylight credit and ignores the energy consequence. The stronger decision runs an early energy model first, then tunes glazing size and orientation so daylight and energy performance improve together.
The scenario: an architect sizes perimeter glazing generously across all facades to support a daylight strategy, and the team treats the energy model as a compliance step to be run at the end. The plausible mistake is committing to glazing area before modeling its effect on heating, cooling, and lighting loads — the daylight gain and the energy penalty are coupled, and late modeling locks in the penalty.
The better decision: run preliminary energy analysis during schematic design, model a few glazing ratios by orientation, and pair the daylight goal with shading and electric-lighting controls so both strategies reinforce each other. This matters because BD+C credits are interdependent — a strategy in one category can quietly erode performance in another. Scenario questions reward candidates who identify the coupling and propose a decision sequence that evaluates both effects before the design is fixed.
Documentation and roles: who does what in the certification workflow
BD+C questions describe project roles — owner, design team, contractor, commissioning authority — and ask which party supplies or verifies which documentation. Learn the role-to-submittal mapping as a workflow, not a list, and check independence requirements.
A second worked scenario: a team assigns the commissioning role to a member of the design firm that also produced the construction documents, and routes equipment submittals through the owner's agent who never reviews them. The plausible mistake is treating commissioning as an external formality and documentation as a single pile of files rather than outputs tied to specific responsible parties.
The better decision, in this training example, is recognizing when independence is required for the commissioning role and mapping each documentation stream — design intent, submittal review, verification results, final reports — to the party that originates it and the party that confirms it. On the exam, role-confusion questions are answerable only if you have practiced tracing a document from origin to submittal, so rehearse that trace narratively: who wrote it, who checked it, who uploaded it, and what it proves.
| Decision type | What it demands | Typical scenario cue | Trained response |
|---|---|---|---|
| Prerequisite check | Confirm a mandatory condition is met | Prompt describes energy systems or water use with no baseline mentioned | Flag the prerequisite before evaluating credits |
| Compliance-path choice | Select among prescriptive or performance options | Project has an unusual feature that a prescriptive path doesn't fit | Weigh which path matches the project's actual design and documentation ability |
| Synergy or trade-off | Detect cross-category effects | One strategy boosts one credit and burdens another | Propose analysis early enough to adjust the design |
| Role assignment | Match task to responsible party | Prompt names multiple team members and a deliverable | Trace the deliverable to its originating and verifying roles |
Credit-path drill: a repeatable exercise with a self-check rubric
Run a weekly drill: pick one credit, write a short project scenario, list its compliance paths, and log which path you would choose and why. Score yourself against a rubric that rewards reasoning, not recall.
The exercise: for any credit you are studying, write a three-sentence project scenario (building type, scope, one constraint). Then answer four questions in writing: which prerequisites does this scenario touch, which compliance paths exist, which path fits the constraint, and which other credits could be affected. Numbered example for calibration — if a scenario fixes a small site with no outdoor area, a path requiring open space is unavailable, so the correct answer is the path that fits the constraint, not the path with the most points.
Score each drill on a 0-3 rubric per question: 0 means no answer, 1 means a recalled fact, 2 means a correct application to the scenario, 3 means a correct application plus an identified side effect on another credit or a rejected alternative. Suggested milestone: reach 2 or higher on every question across five consecutive drills before you treat that credit area as learned. These scores are learning milestones for your own tracking, not predictions of exam performance.
- Write the scenario before looking at the credit's options — this prevents reverse-engineering the answer.
- Always name at least one rejected alternative and the reason it loses.
- Note any cross-category effect; if you cannot find one, say so explicitly rather than inventing one.
A preparation sequence and concrete readiness checks
Sequence your study in three passes: structure first (rating systems, prerequisites, roles), reasoning second (paths, synergies, phases), then timed scenario practice. Confirm readiness with behavior checks, not by rereading notes.
Pass one, roughly the first third of your calendar: map the BD+C rating system's structure and write the prerequisite trigger list described earlier. Pass two: run the credit-path drill across credit categories, adding one worked trade-off scenario per category to your own scenario bank. Pass three: assemble your scenarios into timed sets and answer them cold, then grade with the rubric. Adapt the pacing to your schedule; the order matters more than the dates.
Readiness checks you can actually observe: you can sort any project description into the correct rating system in under a minute; you can list the BD+C prerequisite triggers from memory; you can narrate a documentation trace from origin to submittal for a named credit; and you can explain one synergy and one trade-off you discovered yourself in a drill. If any check fails, return to the matching pass rather than adding more reading. For administrative matters such as registration, exam delivery formats, and credential maintenance rules, rely on the issuer's pages rather than secondhand summaries.
- Check 1: correct rating-system identification from a project description, unaided.
- Check 2: prerequisite triggers recited from memory with a one-line condition each.
- Check 3: a full role-to-documentation trace spoken aloud for two different credits.
- Check 4: five consecutive drill sessions scoring 2+ on every rubric question.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.