LEED AP ND common mistakes
LEED AP ND · Understand the traps and how to avoid them.
Memorizing the credit point values as a flat list without tracking which rating system version and which credit category each value belongs to, then applying an old point total to a scenario question.
LEED ND has been revised across versions (v3/2009 and v4/v4.1), and point allocations and credit structure shifted between them. Candidates who studied a single summary sheet conflate versions and cannot answer questions that hinge on a specific credit's requirements rather than its point value.
What to do instead
Build a one-page matrix per version you are tested on, with columns for category, credit code (e.g., SLL, NPD, GIB), intent, requirements, and points. When you review a practice scenario, first identify the version implied by the terminology used, then recall the credit from that matrix rather than from memory of a point total.
Treating the LEED ND process as a single certification event and missing the staged review structure (pre-review of prerequisites, then certification review), so questions about when a project can submit or what happens if a prerequisite fails are answered incorrectly.
The ND rating system uses a multi-stage review in which certain prerequisites are verified early and the full certification review comes later. Candidates who only know the credit content skip the administrative process and guess at sequencing.
What to do instead
Write a timeline diagram from project registration through pre-review, preliminary review, final review, and appeal. Annotate which prerequisites must clear early, what documentation accompanies each stage, and what happens to a project that fails a prerequisite at pre-review. Rehearse the sequence until you can state it without notes.
Confusing Smart Location and Linkage prerequisites with credits: assuming a transit proximity or bicycle network measure is optional when it is actually a prerequisite, or vice versa.
SLL contains both prerequisites and credits that address similar topics (transit, bicycle networks, housing and jobs proximity), and the distinction is easy to blur when studying by topic rather than by credit type.
What to do instead
Re-sort every SLL item into a two-column table: prerequisite versus credit. For each prerequisite, write the exact threshold and the documentation needed to demonstrate it. For each credit, note the point tiers and the incremental threshold that earns the next point.
Applying a single transit proximity distance to every scenario instead of recognizing that the qualifying distance depends on the transit type (e.g., rail versus bus, or frequent versus infrequent service).
Candidates memorize one number and reuse it, but the rating system distinguishes transit service quality and mode when setting walkable distances. Scenario questions deliberately vary the transit type to test this.
What to do instead
Create a table mapping transit mode and service frequency to the qualifying distance and the number of qualifying trips or rides required. Practice with scenarios that change one variable at a time so the threshold shift becomes automatic.
Treating Neighborhood Pattern and Design credits as design preferences rather than measurable requirements, so answers about walkable streets, compact development, or mixed-use rely on intuition instead of the stated metric.
NPD credits are quantitative: they specify metrics such as floor area ratio, intersection density, dwelling units per acre, or a proportion of building frontage meeting certain conditions. Candidates who read the intent but skip the metric cannot evaluate whether a described project complies.
What to do instead
For each NPD credit, write the intent in one sentence and then the exact metric, threshold, and calculation method beneath it. Work through at least two numeric examples per credit (one passing, one failing) so you can compute compliance from a scenario description.
Ignoring the distinction between what counts toward a density or diversity calculation and what is excluded, such as which building types, uses, or areas are eligible in a mixed-use or compact development calculation.
The credit language defines eligible uses and measurement boundaries, and candidates who skim assume all floor area or all dwelling units count. Scenario questions often include an excluded use to test whether you apply the boundary.
What to do instead
Annotate each NPD calculation credit with an explicit inclusion/exclusion list: eligible use categories, whether existing versus proposed development counts, and how the measurement area is bounded. When practicing, highlight the excluded item in each scenario before computing.
Treating Green Infrastructure and Buildings credits as generic sustainability measures and missing the ND-specific framing, such as the emphasis on infrastructure serving the neighborhood rather than individual building certification alone.
Candidates with a background in LEED Building Design and Construction carry assumptions about building-level credits into ND. GIB addresses neighborhood-scale infrastructure, district energy, and stormwater at the neighborhood level, and the requirements reflect that scope.
What to do instead
For each GIB credit, write a sentence beginning 'At the neighborhood scale, this credit requires...' to force the shift in scope. Note where a building-level certification or standard is referenced as a compliance path versus where neighborhood-wide performance is required.
Answering stormwater and heat island questions with a remembered percentage or threshold without checking whether the credit is asking about a performance standard, a prescriptive measure, or a percentage reduction relative to a baseline.
GIB credits mix prescriptive options (specific materials or strategies) with performance options (a percent reduction against a baseline). Candidates recall one number and apply it to the wrong compliance path.
What to do instead
Build a table with columns for credit, compliance path (prescriptive or performance), the metric, and the threshold for each path. Practice identifying from the question wording which path is being tested before selecting a number.
Skipping documentation requirements and answering only on technical merit, so questions about what evidence demonstrates compliance, who prepares it, or how a credit is verified are missed.
The documentation domain is perceived as administrative and low-value, so candidates under-study it. But exam questions test whether you know the submittal, calculation, or verification method that proves a credit is achieved.
What to do instead
For every credit you study, add a documentation line: what submittal or calculation proves it, what map or boundary drawing is needed, and what common documentation error causes a denial. Review this column as often as the requirements column.
Drawing the project boundary inconsistently across credits, using a larger boundary for one credit and a smaller one for another without recognizing that boundary definition affects eligibility and calculations.
ND credits are evaluated within a defined project boundary, and some credits allow or require analysis of a surrounding area. Candidates who do not fix the boundary in their mental model misjudge which parcels or populations count in a scenario.
What to do instead
Before answering any scenario, state the project boundary and any permitted surrounding-area analysis out loud or in notes. Then check each credit's requirement for whether it uses the project boundary, a walkable radius, or a larger study area, and keep those definitions separate.