BPI QCI common mistakes
BPI QCI · Understand the traps and how to avoid them.
Treating the inspection as a visual walkthrough and skipping instrument measurements (manometer pressure readings, blower-door CFM50, combustion analyzer values) before signing off.
Candidates carry over habits from general home-inspection work, where observation is the primary tool, and underestimate how much of a QC inspection depends on recorded diagnostic data; time pressure during field practice reinforces the shortcut.
What to do instead
Build a fixed measurement checklist per inspection type (pressure pan or room-pressure differentials, duct leakage, worst-case depressurization, combustion safety) and rehearse it until every item is captured before any judgment is written; practice writing the numbers into the report as they are taken.
Confusing the roles of the QC inspector, the installing contractor, and the program representative, and issuing corrective direction or approving work that falls outside the inspector's authority.
The three roles overlap in the field and candidates memorize definitions without mapping them onto realistic scenarios, so they default to 'fixing' problems rather than documenting and referring them.
What to do instead
Study the program's written role definitions and practice classifying sample situations as 'inspect and document', 'contractor must correct', or 'program decision'; state the boundary explicitly in report language rather than giving verbal direction on site.
Applying a single standard or threshold across all programs and jurisdictions instead of checking which version of the standard, which program rule, and which effective date govern the job.
Candidates learn one familiar numeric threshold and treat it as universal, missing that programs adopt different versions of standards and set their own stricter limits.
What to do instead
Before each practice scenario, write down the governing program manual, standard edition, and effective date, then derive the applicable threshold from those sources; drill with deliberately conflicting program rules so version-checking becomes automatic.
Reporting a deficiency without the supporting measurement, location, and reference to the requirement it violates, leaving a note such as 'insulation inadequate' with no R-value, area, or standard cited.
Candidates write reports as memory aids for themselves rather than as defensible records for the contractor, program, and any later audit, and they draft from recollection after leaving the site.
What to do instead
Adopt a fixed finding template (observation, measurement, location, requirement cited, required correction, photo reference) and write each finding on site as it is discovered; review completed reports against the template before submission.
Failing to establish and document a baseline or reference condition (pre-inspection readings, existing damage, homeowner belongings, prior work) before work is verified or attributed.
Inspectors arrive after the work is complete and assume the current state is the only relevant state, so they cannot distinguish new defects from pre-existing ones or defend attribution later.
What to do instead
Use a standard pre-work documentation set (photos, moisture or pressure baselines, signed condition notes) and, when arriving post-work, explicitly record what cannot be verified and why; never attribute a condition to the contractor without evidence.
Misreading or misapplying diagnostic test conditions, such as running a blower door without proper baseline, ignoring stack effect and wind, or comparing leakage results taken under non-comparable conditions.
Candidates memorize target numbers without understanding what the test setup controls, so they do not recognize when a reading is invalid or when two readings cannot be compared.
What to do instead
For each diagnostic test, learn the setup requirements and the common confounders, and practice flagging invalid tests (wrong configuration, insufficient stabilization, weather outside limits) instead of recording a number that will mislead.
Verifying work scope from the contractor's invoice or verbal description rather than from the approved scope of work and the installed condition.
Paperwork is faster to read than to verify in the field, and candidates assume the contractor's summary reflects what the program authorized.
What to do instead
Perform line-by-line scope reconciliation: for each approved measure, confirm quantity, specification, location, and installation quality in the field, and record any deviation, substitution, or omitted measure explicitly.
Using ambiguous or judgmental language in reports ('poor', 'significant', 'should be better') instead of measurable, verifiable statements.
Candidates write for a general audience and worry about sounding harsh, so they soften findings; this also masks uncertainty they have not resolved.
What to do instead
Replace every adjective with a quantity, a location, and a cited requirement; where a judgment is genuinely required, state the criterion used and the measurement that triggered it.
Skipping or superficially completing combustion-safety and worst-case depressurization testing because it is uncomfortable, weather-dependent, or time-consuming.
These tests require specific conditions and equipment setup, and candidates under field time pressure rationalize deferring them or recording a single spillage check as a full test.
What to do instead
Treat combustion safety as non-negotiable: rehearse the full sequence (worst-case setup, draft and spillage measurement, CO readings) under realistic conditions, and document any test that could not be performed with the reason and required follow-up.
Missing program administrative requirements such as photo protocols, sampling and re-inspection rules, data submission formats, or required signatures, so technically correct inspections are rejected.
Candidates focus on technical content and treat paperwork as an afterthought, and program requirements vary enough that assumptions from one program carry over incorrectly to another.
What to do instead
Maintain a per-program administrative checklist (photo set, sampling eligibility, data fields, sign-off sequence) and run it as a final gate before submitting any inspection package; practice with rejected-package examples to see how technical work is lost to administrative gaps.