BPI BA-T common mistakes
BPI BA-T · Understand the traps and how to avoid them.
Treating the stack effect as a fixed rule of thumb ("warm air rises at about X Pa per floor") and applying it without computing pressure from indoor-outdoor temperature difference and building height.
Stack effect is intuitive and candidates memorize a single number from a study guide, then reuse it on items where the temperature difference, neutral pressure level, or building height has been changed to test whether they understand the driving equation.
What to do instead
Practice deriving stack pressure from the density difference and height, and work several items where one variable (height, delta-T, leakage distribution) is changed while others are held constant. State the relationship in words before selecting an answer.
Confusing the three driving forces of air movement (wind, stack, mechanical) and attributing an observed pressure pattern to the wrong one.
All three produce pressure differences across the envelope, and exam items often describe a symptom (e.g., consistent pressurization on the leeward side, or a seasonal reversal) without naming the driver. Candidates pattern-match on a single keyword.
What to do instead
For each scenario, list the signature of each driver (wind: varies with gust and orientation; stack: reverses with season and scales with height and delta-T; mechanical: follows HVAC schedule and fan operation) and eliminate drivers that do not fit all the clues.
Mixing up sensible and latent heat and misapplying the psychrometric chart when estimating loads or interpreting moisture conditions.
Candidates can read a chart in a classroom but freeze when an item requires moving between dry-bulb, wet-bulb, dew point, humidity ratio, and enthalpy in a specific sequence, or when latent load is embedded in a ventilation scenario.
What to do instead
Drill a fixed procedure: locate state point, read dry-bulb and humidity ratio first, then derive dew point and enthalpy. Practice process lines for heating, cooling, humidification, and dehumidification until each direction is automatic.
Skipping the pre-inspection interview and building history review, then walking the site without a hypothesis list.
Field time feels scarce and candidates want to start measuring immediately; the assessment domain rewards a systematic sequence, and items that describe a rushed inspection expect the candidate to identify the missing step.
What to do instead
Use a standard pre-visit checklist (occupant complaints, recent renovations, prior reports, utility data, weather history) and convert it into three to five testable hypotheses before arriving. Practice writing that list for sample scenarios.
Recording measurements without capturing the conditions and metadata that make them interpretable (date, time, weather, indoor-outdoor delta-T, instrument, calibration status, location).
Candidates focus on the number itself and treat context as optional, but the assessment and documentation domains test whether data can be defended later or compared across visits.
What to do instead
Adopt a fixed data-capture template and rehearse it until it is automatic. For every reading, record what, where, when, with what instrument, under what conditions, and the uncertainty.
Selecting a diagnostic test without confirming it answers the question at hand, e.g., running a blower door when the complaint is a localized moisture problem, or using an infrared scan on a sun-loaded wall.
Candidates associate certain tools with certain problems and reach for the familiar instrument; exam items deliberately describe conditions where the obvious tool yields ambiguous results.
What to do instead
For each tool, write down what it measures, what it cannot distinguish, and the conditions required for a valid result. Before choosing a test, state the question in one sentence and check that the test discriminates between the candidate causes.
Misreading or misreporting blower door results, such as confusing CFM50 with natural infiltration, ignoring correction factors, or failing to note baseline conditions.
The numbers look authoritative and candidates treat the raw output as the answer; items test whether the candidate knows what the measurement represents and its limits.
What to do instead
Practice explaining in writing what a blower door result does and does not mean, including the difference between envelope leakage at test pressure and estimated natural leakage, and the effect of wind, temperature, and building preparation.
Interpreting infrared images without accounting for emissivity, reflectivity, thermal mass, and solar or mechanical gains, and presenting a thermal pattern as a confirmed defect.
Thermography produces compelling images and candidates over-claim; items often describe a pattern that has multiple explanations.
What to do instead
For every anomaly, list at least two alternative explanations and the confirmatory test (e.g., moisture meter, smoke pencil, invasive check) before concluding. State confidence level and required conditions in the report.
Writing reports that describe what was done rather than what was found, with no clear separation of observation, interpretation, and recommendation.
Candidates mirror the chronological field notes they took and do not restructure them for the reader; the reporting domain rewards findings-first organization and explicit evidence.
What to do instead
Draft with a fixed structure: summary of findings, evidence for each finding, interpretation with stated confidence, limitations, and prioritized recommendations. Practice converting a page of raw notes into that structure.
Omitting limitations, assumptions, and the scope of work, so the report implies more certainty and coverage than the assessment actually provided.
Candidates worry that caveats weaken the report and cut them for concision; exam items test whether the candidate recognizes that undocumented scope and uncertainty create liability and mislead the client.
What to do instead
Include a standard section covering scope, methods, inaccessible areas, assumptions, and confidence levels, and tie each conclusion to the specific evidence that supports it. Review sample reports for missing scope statements.