NEBB Testing, Adjusting and Balancing Certified Professional (CP) common mistakes
NEBB Testing, Adjusting and Balancing Certified Professional (CP) · Understand the traps and how to avoid them.
Recording the as-found airflow readings before the system has stabilized and treating them as the baseline for the report, rather than waiting for steady-state conditions at each terminal.
Candidates carry over field habits from quick walkthroughs and under exam time pressure move from terminal to terminal too fast; they also forget that duct systems need several minutes to rebalance after each damper adjustment, so early readings drift and later readings contradict them.
What to do instead
Adopt a fixed stabilization protocol for every measurement point: confirm fan is at design rpm and filters are clean, then allow the system to settle before reading. On calculation items, always ask whether the stated readings were taken at steady state; if the stem implies sequential damper changes, recompute downstream totals after each change rather than reusing the first pass.
Summing branch airflows and comparing to fan airflow without accounting for duct leakage, fan heat, or density corrections, then declaring the balance failed or passing it incorrectly.
Candidates treat the continuity equation as a simple arithmetic check and forget that field-measured fan airflow and terminal totals legitimately differ by several percent; they also mix standard-air and actual-air values without converting.
What to do instead
Before judging balance, state the acceptance tolerance and the reference conditions. Convert all readings to a common density basis, apply the leakage allowance stated in the problem, and only then compare totals. Practice problems where the discrepancy is within tolerance and where it is not, so the decision rule becomes explicit rather than intuitive.
Using a pitot-tube traverse average that ignores the velocity profile, for example averaging equally spaced points in a round duct without weighting by annular area or taking too few points in a rectangular duct.
Candidates memorize the log-linear method as a point count but not the geometry behind it, and many have only used rotating-vane or thermal instruments in the field; they also forget that the traverse plane must be in a straight run of adequate length.
What to do instead
Rehearse the log-linear point locations for round ducts (centers of equal-area annuli) and the equal-area grid for rectangular ducts, including minimum point counts for the duct size. For each traverse question, first check whether the measurement plane meets the upstream/downstream straight-duct requirement; if not, the correct answer often involves relocating the plane or applying a correction factor.
Selecting an instrument whose range or resolution is inappropriate for the reading, such as a large-range manometer for a low-pressure drop or a hot-wire anemometer for a highly turbulent grille face, and then reporting the number at full precision.
Candidates focus on whether the instrument type is 'correct' rather than whether it is fit for this magnitude; exam stems often hide the key number (expected reading) in the middle of the description, and candidates skim past it.
What to do instead
For every instrument question, write down the expected reading and the required accuracy first, then compare to the instrument's range and resolution, requiring the reading to sit in the upper portion of the range. Also apply the rule of reporting only to the precision the instrument supports, and know that face velocity at a grille is best obtained by averaging a defined grid of readings or by a flow hood.
Adjusting the balancing dampers at the terminals to fix a problem that originates at the fan or in the main, such as a starved branch caused by a closed fire damper or a backward-running fan.
Candidates default to the terminal damper because it is the most familiar adjustment and gives immediate visible change; they skip the systematic sequence of verifying fan rotation, airflow, and main static pressure before touching branch dampers.
What to do instead
Follow a fixed commissioning sequence in every troubleshooting item: verify fan rotation and speed, belt condition, filter loading, damper positions including fire and smoke dampers, then main static pressure, then branch, then terminal. When a stem describes one branch that cannot be brought up to design despite a fully open terminal damper, look upstream for the restriction rather than prescribing a larger terminal opening.
Setting the proportional balance by opening every terminal fully and then closing the last one, rather than starting from the index terminal or the terminal with the least excess and working back toward the fan.
Candidates confuse 'proportional balancing' with simply trimming everything, and they misidentify which terminal is the index; they also forget that adjusting one branch changes flows in all others, so order matters.
What to do instead
Memorize the proportional method as a defined sequence: identify the index run, set the index terminal to design, then adjust each successive upstream terminal while holding downstream ones fixed, rechecking as you go. Practice with a small network where you must state the adjustment order and predict the direction of change at other terminals after each step.
Reporting fan airflow from nameplate or design documents instead of from measurement, or accepting a fan curve reading without correcting for actual speed and air density.
Candidates treat design values as measured values under time pressure, and they are unsure how fan laws interact with density when temperature or altitude differs from the curve's basis.
What to do instead
Establish the rule that reported airflow must be measured, with the measurement method named (traverse, flow hood, or fan pressure differential). For fan-curve items, always apply the affinity corrections for speed and the density ratio before reading airflow, and state the corrected value. Do a few drill problems where the same fan at a different rpm and altitude gives a very different actual cfm.
Mixing up the sign and reference side of static pressure and velocity pressure readings, for example reporting duct static pressure measured against the wrong reference or subtracting velocity pressure when it should be added.
Candidates memorize instrument hookups visually but not the underlying pressure relationships, and exam stems deliberately describe a gauge connection rather than naming the quantity, so the candidate must infer which pressure is being read.
What to do instead
Anchor on the definitions: static pressure acts normal to the flow, velocity pressure is always positive in the direction of flow, and total pressure equals static plus velocity. For each stem, sketch the duct cross-section, mark where each port of the instrument connects, and label which quantity results. Practice converting between static, velocity, and total at the same point.
Failing to apply temperature and altitude corrections to density when converting measured velocity pressure to velocity or mass flow, and then comparing the result directly to standard-air design values.
Candidates treat the standard density as a constant and do not connect the stem's stated air temperature or elevation to the calculation; they also use volume flow and mass flow interchangeably.
What to do instead
Build a one-line habit for every airflow calculation: note the actual density from the given temperature and pressure, convert velocity pressure to velocity using that density, and only then compare with design (converting design to the same basis or vice versa). Keep clear in mind that volume flow changes with density while mass flow is conserved, which drives many 'why did the cfm change' questions.
Documenting adjustments with a single final set of readings and no record of as-found conditions, adjustment sequence, or instrument identification, so the report cannot support the claimed result.
Candidates view documentation as clerical work after the 'real' balancing and underestimate how heavily the exam tests report content, tolerances, and traceability; they also do not distinguish as-found, as-left, and design values in the narrative.
What to do instead
Use a standard report skeleton in practice: system identification, instrument list with calibration status, as-found readings, adjustments made with sequence, as-left readings, and a statement of compliance against the specified tolerance. For documentation questions, check that all three reading sets appear and that the tolerance is explicitly cited; a report missing as-found data or instrument traceability is the wrong answer even if the final numbers look correct.