InterNACHI CPI common mistakes
InterNACHI CPI · Understand the traps and how to avoid them.
Reporting a system or component as 'inspected and functioning' when it was not operated - e.g., listing the A/C as serviceable without running it - instead of using the Standards of Practice language that describes what was visually observed and disclaiming what was not tested.
Candidates study the SOP as background reading rather than as a reporting template, so they answer questions from an intuitive 'looks fine' mindset instead of the SOP's limited-scope, visual-observation framing.
What to do instead
Memorize the SOP's core verbs: inspect, observe, describe, report, and disclaim. For every practice item, write the report line in SOP language first, then check whether the answer choice matches that scope (visual, non-invasive, not technically exhaustive).
Treating the inspection as a technically exhaustive evaluation - e.g., selecting answers that require dismantling equipment, calculating loads, or predicting remaining service life - rather than recognizing the inspection is visual and non-invasive.
Real-world trade knowledge pulls candidates toward the 'most thorough' answer, but the exam tests the SOP's defined scope, not maximum diligence.
What to do instead
When two answers both seem defensible, pick the one that stays within visual, non-invasive observation and expressly disclaims prediction of future performance or life expectancy.
Failing to identify the correct reporting threshold for a defect - flagging cosmetic or normal-wear conditions as defects, or omitting safety hazards - instead of distinguishing 'defect,' 'hazard,' and 'normal maintenance item.'
Without a consistent internal definition, candidates default to personal preference about what 'looks bad,' producing inconsistent answers on borderline conditions.
What to do instead
Adopt a fixed triage: (1) safety hazard, (2) defect affecting function or integrity, (3) maintenance/deferred item, (4) cosmetic. Classify each practice condition into one bucket before reading the answer choices.
Answering structural questions by naming a specific cause (e.g., 'settlement') when the observable evidence only supports describing the symptom (e.g., 'diagonal cracking at the corner of the opening'), instead of reporting what is visible and recommending further evaluation.
Candidates want to demonstrate diagnostic knowledge, so they jump from observation to causation, which exceeds the inspector's role and the SOP.
What to do instead
Practice the observe-describe-recommend pattern: state the observation, describe location and characteristics, and recommend evaluation by a qualified specialist rather than naming a cause.
Mixing up the inspector's role with that of a code official - citing code sections as the basis for calling something a defect - instead of evaluating against the SOP and general performance expectations.
Code knowledge feels authoritative and candidates over-rely on it, but a home inspection is not a code-compliance inspection and the exam tests that distinction.
What to do instead
Before selecting a code-based answer, ask whether the SOP requires code citation (it generally does not). Prefer answers framed as performance, safety, or SOP-defined deficiency.
Ignoring the effect of the inspection agreement and scope limitations - answering as if every property gets the same full inspection - instead of recognizing that scope, exclusions, and client-agreed limitations change what is reported.
Candidates memorize component lists but not the contractual and scope framework that governs how those components are reported.
What to do instead
Study the agreement/scope material alongside the SOP. For scenario questions, first identify what was in scope and accessible, then choose the answer consistent with that scope.
Describing a safety concern without stating the recommended action - e.g., noting a missing GFCI protection but not recommending correction by a qualified person - instead of pairing every material defect with a clear recommendation.
Candidates focus on detection and treat the recommendation as implied, but the exam scores the reporting behavior, not just the observation.
What to do instead
Use a two-part answer habit: observation plus recommendation. If an answer choice reports a hazard but stops short of a recommendation, treat it as incomplete.
Confusing 'accessible' with 'inspected' - assuming concealed or obstructed components were evaluated - instead of explicitly noting limitations and inaccessible areas in the report.
In practice inspectors glance at blocked areas and move on; the exam tests whether the candidate documents the limitation rather than silently omitting it.
What to do instead
For any scenario involving stored goods, finishes, or obstructions, select the answer that discloses the limitation and its effect on the inspection, not the one that assumes the component was fine.
Applying generic construction assumptions to every house - e.g., assuming a standard wall assembly, foundation type, or heating system - instead of describing the specific system and its observable condition on the property being inspected.
Candidates rely on familiar patterns from their own region or training house and answer from habit rather than from the evidence presented in the question.
What to do instead
Re-read the scenario for the stated system type, age, and materials before answering, and reject any choice that describes a system not established by the facts given.
Spending disproportionate time on a single difficult item and rushing the remainder, or changing correct first answers on review without a concrete reason, instead of pacing and applying a consistent decision rule.
Exam anxiety plus unfamiliar SOP phrasing causes second-guessing; candidates lack a defined tie-breaker, so they oscillate between answers.
What to do instead
Set a per-question time budget, flag and move on from unknowns, and use one pre-committed tie-breaker on review: choose the answer most consistent with SOP scope and safety-first reporting, and change an answer only when a specific fact justifies it.