InterNACHI Well common mistakes
InterNACHI Well · Understand the traps and how to avoid them.
Treating the WELL v2 Air features as a single ventilation checklist and answering questions about filtration, source control, and monitoring as if they were the same requirement, instead of separating what each Air feature (ventilation design, air quality monitoring, construction pollution management, source separation) actually demands.
Candidates study Air as one block and memorize a few numbers (e.g., ventilation rates, PM thresholds) without mapping each number to its specific feature, so scenario questions that ask which feature a given measure satisfies collapse into guesswork.
What to do instead
Build a one-page matrix with each Air feature in one column and its verification method (performance test, document review, letter of assurance) in the next. For each feature, write the single most distinctive requirement and how compliance is demonstrated. Rehearse by reading a scenario and naming the feature and evidence type before answering.
Confusing WELL feature parts and preconditions with optimizations, and answering as if all features are optional or all are mandatory.
WELL v2 structures each feature into parts, and some parts are preconditions required for certification while others are optimizations that earn points. Candidates who skim the standard treat every requirement as equally weighted and misjudge which items gate certification.
What to do instead
For each domain, list preconditions separately from optimizations and note the point values. Practice identifying, in a short scenario, whether the described action satisfies a precondition or earns an optimization point. Anchor the rule: preconditions must all be met; optimizations accumulate toward the point threshold.
Answering water questions by naming a treatment technology (carbon filter, reverse osmosis, UV) without linking it to the specific contaminant class, the WELL threshold, and the required testing evidence.
Candidates memorize technology names and assume any filtration satisfies any water feature, missing that WELL distinguishes turbidity, dissolved metals, disinfection byproducts, and microbial concerns, each with its own limit and verification approach.
What to do instead
Create a table pairing each contaminant group with the effective treatment, the numeric limit, and the test method or report that verifies it. When practicing, always state contaminant, limit, treatment, and evidence together; if any of the four is missing, the answer is incomplete.
Treating thermal comfort as only air temperature and ignoring the other factors WELL expects to be addressed, such as humidity, air speed, radiant temperature, clothing, and occupant feedback mechanisms.
Everyday experience reduces comfort to thermostat setpoint, so candidates pick the temperature-only answer and overlook requirements for surveys, monitoring, or individual control.
What to do instead
Memorize the comfort factor list and, for each, the WELL-relevant control or documentation (e.g., humidity range, draft control, occupant survey). Practice scenario questions by listing which comfort factors are uncontrolled in the scenario and which feature part addresses them.
Confusing daylight access requirements with electric lighting quality requirements, and separately ignoring circadian and glare considerations when answering light questions.
Candidates group all light features together and answer with whichever metric they remember (lux, illuminance, daylight factor) without checking whether the question concerns daylight availability, electric light quality, glare control, or circadian lighting design.
What to do instead
Split light into four buckets: daylight access, electric light quality, glare control, and circadian support. For each bucket, record the key metric, the typical threshold, and the verification method (simulation, measurement, or documentation). Answer by naming the bucket first, then the metric.
Treating nourishment and movement features as policy statements only, and failing to identify the physical design and operational evidence WELL requires, such as food environment criteria, stair access, or activity-promotion signage.
These features read like HR policies, so candidates assume a written policy alone satisfies them and miss the built-environment and operational components that must be documented or observed.
What to do instead
For each nourishment and movement feature, write two columns: design/operational action and evidence required. Practice by reading a building description and identifying which physical provisions (e.g., healthy food placement, stair visibility, exercise space) are present or missing.
Treating mind and community features as soft or unverifiable and guessing at answers instead of learning the specific mechanisms, such as occupant surveys, mental health support resources, inclusive design, and emergency preparedness plans.
Candidates deprioritize these domains because they seem subjective, so they never learn the concrete requirements and evidence types, and then answer from intuition.
What to do instead
Build a short list of each mind and community feature with its concrete deliverable (survey instrument and response rate, policy document, design provision, emergency plan) and who verifies it. Practice by matching a described building program to the feature it satisfies.
Answering materials questions with a general preference for 'low VOC' instead of distinguishing VOC content limits, emissions testing results, and hazard avoidance requirements, and confusing which document proves which.
VOC content and VOC emissions are related but verified differently, and hazard avoidance covers additional chemical concerns. Candidates who blur them pick plausible but wrong evidence types.
What to do instead
Make a three-row table: VOC content (limit and product category), emissions testing (test method and reporting), and hazard avoidance (restricted substance list and disclosure). For each, note the document a project submits. Practice by choosing the correct evidence for a stated product scenario.
Describing a verification method without naming who performs it, when it occurs, and what record results, so answers about performance testing, commissioning, or spot checks lack the specifics the exam expects.
Candidates learn that a feature is 'verified' but not the verification pathway, so they cannot distinguish performance testing from document review or letter of assurance in scenario questions.
What to do instead
For each feature, record verification type, responsible party, timing, and output record. Drill by taking a feature and writing the full verification pathway from memory, then checking it against your notes.
Treating documentation and reporting as an afterthought and failing to connect each claimed feature to the specific submission artifact, such as a narrative, annotated drawing, test report, or signed letter, and the point it supports.
Candidates focus on the technical requirement and assume documentation is generic paperwork, so questions about what to submit or how to report performance are answered vaguely.
What to do instead
Create a documentation map: feature, part, claimed point, required artifact, responsible party. Practice by writing the submission package for a hypothetical project feature and checking that each claim has a matching artifact and no artifact is claimed without a feature.