Study the SITES AP material by mapping each concept to its lifecycle phase and its role in the rating system. Prerequisites, credits, site assessment records, construction-stage actions, operations commitments, and building-scope overlap each behave differently, and scenarios make those differences concrete.
Prerequisites versus credits: why the distinction changes every scoring decision
Prerequisites are mandatory requirements a SITES project must satisfy to certify, while credits are optional actions that earn points toward a certification level. Confusing the two changes how you evaluate any project scenario, so this distinction is the first thing to drill.
When you read a prerequisite, expect a pass/fail logic: the project either meets it or it cannot proceed, and there is no partial achievement to weigh. A credit, by contrast, involves choices among actions of varying ambition, so a scenario may ask which credit path fits a site's constraints. Practice reading each item with two questions: is achievement binary, and is it tied to a performance threshold?
This distinction matters when a scenario describes a constrained site. If an action is a prerequisite, the correct response is to find a way to satisfy it, not to trade it against a preferred credit. If it is a credit, the correct response may be to select among alternatives or accept fewer points. Write the label prerequisite or credit beside every concept in your notes until the classification is automatic.
- Prerequisite thinking: mandatory, binary, no points, no substitution
- Credit thinking: optional, scored, often offers multiple compliance paths
- Scenario habit: name the requirement, name its role, then decide the action
Ecosystem services as the framework's organizing logic
SITES organizes its guidance around ecosystem services: benefits such as stormwater regulation, habitat support, climate mitigation, resource conservation, and human health that landscapes provide. Anchoring every concept to the service it protects helps you predict why a requirement exists.
The rating system's public description emphasizes enhancing biodiversity, mitigating climate change, conserving resources, improving public health, and protecting ecosystems. Treat those outcomes as the spine of your study. For each domain you review, such as soils, vegetation, water, or site materials, ask which ecosystem service the domain protects and how site decisions strengthen or weaken that service over time.
A useful trace exercise: pick a familiar landscape feature, for instance a grove of preserved mature trees, and name the services it supports, including shade, habitat, and stormwater interception. Then consider what happens to each service if the soil beneath the trees is compacted during construction. This trace shows how a single design decision cascades across several service areas, which is exactly the kind of reasoning scenario items reward.
- Service domains to anchor: soil function, vegetation and habitat, water, materials and resources, human health and wellbeing
- Trace practice: feature to services to the decision that protects or degrades them
Early site assessment records versus later design documentation
Early assessment captures existing conditions, such as soils, vegetation, hydrology, and site context, before design choices are made. Design documentation records intended interventions. These record types differ in timing, author, and content, and mixing them up is a core conceptual difficulty.
Assessment answers the question of what exists on the site now: which areas hold healthy soil, which vegetation is worth protecting, how water moves, and what the surrounding context contributes. Because the rating system addresses the full arc from planning through management, assessment is the evidence base that justifies later choices. When a scenario hands you a site description, practice mentally filing each stated condition as an assessment finding.
Design documentation, in contrast, answers what the team intends to do. A labeled comparison exercise works well here: take six short statements about a hypothetical park, mark each as describing an existing condition or an intended intervention, and note what evidence supports each. Expected observation: existing-condition statements reference surveys, mapping, or observation, while intervention statements reference plans, specifications, and drawings. Repeating this until the two record types feel distinct is a realistic milestone for your notes.
Construction-stage actions: a worked scenario on who does what, and when
Some SITES-relevant actions occur or can only be verified during construction, such as protecting soils and existing vegetation from unnecessary disturbance. Recognizing which decisions belong to the construction phase keeps roles, records, and responsibilities straight.
Scenario: a landscape architect prepares drawings for a campus courtyard and includes a sheet noting that existing trees shall be protected. During construction, the grading subcontractor stages heavy equipment inside the tree protection area, compacting the root zone. The mistake here is treating a construction-stage protection measure as satisfied by drawing it. A drawing records intent; the protective outcome depends on site practices and verification while work is underway.
The better decision embeds the requirement where the construction phase actually operates: clear specifications, a defined protection area, and on-site observation to confirm the measure is maintained as work progresses. Why it matters: the ecosystem services those trees provide, including shade, habitat, and stormwater interception, depend on the soil and root conditions surviving construction, not on the existence of a drawing. When you study any protection-oriented concept, ask what must be true during construction, not only what appears in the document set.
Where SITES ends and LEED begins on a mixed project
SITES addresses the land: planning, design, construction, and management of outdoor spaces, with or without buildings. LEED centers on buildings. The published LEED v5 and SITES v2 synergies crosswalk identifies overlap topics, but the two scopes remain distinct.
Imagine a corporate campus where the architecture team pursues LEED for the new office building while the landscape team pursues SITES for the grounds. Topics such as water use, heat reduction, and responsible materials touch both scopes, which is precisely why the crosswalk exists. When studying, sort each topic by scope: does the decision primarily concern the building and its systems, or the land and its ecological and hydrological function?
Scenario: a project manager proposes counting the building's low-flow plumbing fixtures toward the landscape's water efforts. The mistake is letting scope overlap blur into scope substitution; plumbing fixtures are a building-system decision even though both frameworks care about water. The better response identifies which landscape-scale actions, such as plant selection and irrigation approach, belong to the site scope. This sorting habit converts an confusing overlap into two clear decision tracks, and it is the reasoning to rehearse with crosswalk topics in your notes.
One-time design choices versus ongoing operations commitments: a second scenario
Design decisions are made once before construction; operations and management decisions repeat across a site's life. Separating a one-time intervention from a continuing commitment is the second scenario skill to practice.
Scenario: a design team specifies drought-tolerant planting and an efficient irrigation layout for a civic plaza, and the project narrative declares water conservation achieved. The mistake is treating a design-phase choice as a permanent outcome. Plant performance and water savings depend on how the site is managed afterward: monitoring, adjusting schedules to weather and plant establishment, and repairing the system when components fail.
The better decision pairs the design choice with an operations commitment: a management approach that revisits irrigation performance as the landscape matures. Why it matters: the ecosystem services the design intended, including reduced water demand, persist only if management sustains the conditions that provide them. When you study any performance-oriented concept, ask both when the decision is first made and what ongoing behavior keeps it true over the site's life.
Phase-mapping exercise, readiness checks, and an adaptable study sequence
Run a phase-mapping drill: list site features and actions, then assign each to assessment, design, construction, or operations, and label it prerequisite or credit. Score yourself with a short rubric, then repeat with harder scenarios until placement is fast and accurate.
Exercise: write ten short statements about a hypothetical riverfront park, mixing existing conditions, design intentions, construction practices, and maintenance commitments. For each statement, record three judgments: phase, record type, and prerequisite or credit. Expected observations on a first pass: maintenance and construction statements are the ones most often misplaced, and prerequisite labels get attached to ambitious-sounding actions that are actually credits. Repeat the drill weekly, adding statements that deliberately blur phases, such as a soil protection measure that spans design specification and construction practice.
Readiness self-check: you can state the rating system's scope in one sentence covering planning through management of landscapes with or without buildings; you can classify any concept as prerequisite or credit without hesitation; you can trace a credit back to the ecosystem service it supports; and you can place any scenario event in the correct phase with its correct record type. A suggested sequence: weeks one and two, framework logic, prerequisites and credits, and ecosystem services; weeks three and four, phase mapping across domains such as soils, vegetation, water, materials, and human health; week five, the two scenario types above plus crosswalk overlap topics; final stretch, timed statement-sorting drills and a full rubric-scored mapping set. Treat any self-assigned score as a learning milestone, not a prediction of exam results. One short note on administration: registration and scheduling details belong to the credential issuer at gbci.org rather than to study materials.
| Lifecycle phase | What it captures | Typical record type | Practice focus |
|---|---|---|---|
| Pre-design assessment | Existing soils, vegetation, hydrology, and site context | Surveys, mapping, condition reports | Label statements as existing conditions |
| Design | Intended interventions and performance targets | Plans, drawings, specifications | Sort one-time choices from ongoing commitments |
| Construction | Protection measures and practices verified while work proceeds | Specifications and construction-stage verification | Ask what must be true on site, not on paper |
| Operations and management | Recurring actions that sustain performance over the site's life | Management approaches and monitoring records | Identify the ongoing behavior behind each outcome |
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.