NABCEP PVSI common mistakes
NABCEP PVSI · Understand the traps and how to avoid them.
Citing only the NEC article number when asked which code or ordinance governs a field condition, without naming the edition, the local amendment, or the AHJ requirement that actually controls.
Candidates memorize article numbers from a single edition and assume one national code answers every question; the PVSI exam deliberately tests jurisdiction-specific adoption, permitting, and inspection authority, so a bare citation leaves the answer incomplete.
What to do instead
For every code question, state the hierarchy explicitly: adopted NEC edition, any local amendment, and the AHJ's inspection or permitting role. Build a one-page reference listing the current NEC edition and the typical local overlay (fire setback, structural permit, utility interconnection) and rehearse answers in that order.
Treating fire setbacks, rapid shutdown, and labeling as interchangeable requirements and applying whichever one the candidate remembers first.
These three come from different code sections and different editions, and candidates conflate them because they all appear in rooftop PV discussions; the exam separates them to test precise scoping.
What to do instead
Make a comparison table with columns for what triggers the requirement, who enforces it, and which edition introduced or changed it. Practice classifying a scenario into exactly one bucket before writing the answer.
Listing only the major components (modules, inverter, racking) when asked to identify all system components, omitting disconnects, overcurrent protection, grounding and bonding hardware, rapid shutdown devices, and monitoring or communications equipment.
Candidates think in terms of the energy-conversion path and forget balance-of-system items that do not appear in a simple single-line drawing; exam items often ask for a complete enumeration.
What to do instead
Walk the system in a fixed physical order: source, DC conductor path, DC OCPD and disconnect, conversion, AC path, AC OCPD and disconnect, point of interconnection, grounding and bonding, rapid shutdown, labeling, and monitoring. Use that checklist on every component-identification item.
Misidentifying the point of interconnection or the service equipment rating when the question describes a supply-side versus load-side connection.
Supply-side and load-side taps have different OCPD and busbar implications, and candidates skim the scenario without extracting which connection type is described.
What to do instead
Before answering, underline the connection type, the busbar rating, the main breaker rating, and the PV OCPD rating in the prompt, then apply the appropriate calculation for that connection type. Practice both connection types side by side until the distinction is automatic.
Answering safety and operation questions from general electrical intuition rather than from the specific shock, arc-flash, and rapid-shutdown hazard controls the code and standard require.
Experienced candidates rely on field habits and skip the documented control hierarchy, so they miss items about labeling, lockout, verification of de-energization, and conductor identification.
What to do instead
Frame every safety answer as hazard, control, verification, and documentation. Name the specific control (for example, verifying absence of voltage at the inverter DC terminals after rapid shutdown initiation) instead of a general statement about being safe.
Describing a commissioning or operational test without stating pass criteria, instrument, or the condition under which the test is invalid.
Candidates describe what they would do but not how they would judge the result, and exam items about system operation ask for measurable acceptance criteria.
What to do instead
For each test, write the instrument, the measurement point, the expected value or range, and the environmental conditions that invalidate the reading. Rehearse insulation resistance, open-circuit voltage, operating current, and rapid shutdown initiation in that four-part format.
Reading a plan set only for the array layout and ignoring the title block, revision history, general notes, and structural or electrical sheets that change the answer.
Candidates jump to the drawing that looks relevant and miss that the revision cloud, general note, or structural sheet overrides the detail they are reading.
What to do instead
Adopt a fixed reading order for every plan question: title block and revision, general notes, single-line diagram, structural sheet, then the detail in question. State which document controls when two appear to conflict.
Failing to convert between drawing scale, roof dimensions, and module dimensions when checking whether a described layout is feasible.
Candidates accept the stated count without checking it against the available area, setbacks, and access pathways, so they miss items where the layout violates a physical or code constraint.
What to do instead
Practice a repeatable area check: usable roof area minus setbacks and access paths, divided by module footprint including clamp and rail allowance, compared with the stated count. Show the arithmetic in the answer.
Writing inspection findings as opinions or general observations instead of observable conditions with location, code reference, and severity.
Candidates describe what they saw but not where, which requirement applies, or how serious it is, and reporting items are scored on structure as much as content.
What to do instead
Use a fixed finding format: location, observed condition, applicable requirement, risk or severity, and required corrective action. Practice converting a vague note into that five-part statement until it is habitual.
Skipping the verification step in an inspection answer, so the response describes what should exist but not how the inspector confirms it was installed and functions.
Candidates treat inspection as visual only and forget that many items require measurement, function testing, or documentation review before the finding can be closed.
What to do instead
For each inspection item, add the verification method: visual, measurement with a named instrument, functional test, or document review. Close every finding with the evidence that would allow it to be cleared.