Study NEBB TAB by building decision chains, not flashcard stacks: for each technique (fan laws, proportional balancing, traverse procedures, system effect, instrument selection), practice choosing the method that fits the stated system conditions and explaining why the alternatives fail in that context. Use the two scenarios and rubric below as weekly checkpoints.
Fan Laws: Why a 10% Fan Speed Change Is Not a 10% Flow Change
Fan laws state that airflow varies directly with fan speed, pressure varies with speed squared, and power varies with speed cubed. Use them to predict the fan speed change needed to close a design-to-actual airflow gap before touching dampers.
Work the relationship both directions. If measured supply airflow is 8,000 CFM against a design of 9,600 CFM, the speed ratio needed is 9,600/8,000 = 1.20, so fan speed must rise 20%. But pressure rises by 1.20 squared, about 1.44 times, and power by nearly 1.73 times. This is the trap: a candidate who computes a 20% speed increase and then worries that 'static pressure only has 20% headroom' has misapplied the law — the system curve dictates where the fan actually lands, and system effect can shift that point.
Compare this with damper-based adjustment. Closing a main damper reduces flow but wastes energy and pushes the fan toward surge on some fan types, while slowing the fan moves along the system curve more cleanly. In a scenario where a variable frequency drive exists, the fan law method is usually the better decision; on a constant-speed fan with a wide-open discharge damper, you have fewer options and must work within the fixed speed. State which equipment exists before selecting a method — that conditional judgment is the core of the balancing decision.
Practice numerically: write three systems with measured flow 15% below design, one with a VFD, one with a sheave change option, one with neither. For each, choose the adjustment path and compute the expected new fan pressure and power. Expected observation: the sheave-change and VFD answers differ in cost and precision, and the neither case forces damper work with an energy penalty you should be able to articulate.
- Flow ratio = speed ratio; pressure ratio = speed squared; power ratio = speed cubed
- Always compute all three before proposing a speed change, not just flow
- Damper throttling and fan speed changes are not interchangeable — each has a different operating point consequence
- Check whether the fan has adequate pressure and power margin for the calculated new operating point
Proportional Balancing: Why You Balance Branches Before Chasing the Total
Proportional balancing sets branch and terminal dampers to bring each outlet's ratio of actual-to-design flow into alignment, then adjusts the fan to hit the total. Balance outlets proportionally first; correcting the total at the fan last preserves branch balance.
The logic rests on how a duct network behaves: after a fixed set of damper positions is established, changing fan capacity scales flow in every branch roughly proportionally, so branch-to-branch ratios stay nearly stable while the total moves. A plausible mistake in a scenario: a technician measures a building 20% low overall, opens the fan to full speed, and finds some terminals now blow above design and others still below — because individual dampers had been set while the fan was at the wrong capacity, embedding wrong ratios. The better decision is to first proportion each terminal relative to the lowest-performing outlets, then bring the total up and re-verify sample outlets.
Contrast two sequencing approaches to make the difference concrete. In 'proportional method,' you start at the least-balanced index terminal, set others relative to it, then adjust total flow at the fan. In a 'straightforward' approach of tuning each terminal to design independently, every fan adjustment invalidates prior terminal settings, forcing repeated loops. On paper the second looks simpler; on a real system with many terminals it converges slowly or never. When a scenario offers both, identify the system state — if the total is far off design, proportional sequencing is the defensible choice.
Note where proportional balancing has limits: systems with highly interactive branches, very short runs, or terminals already near balance may need only minimal trimming, and heavy-damper-use cases may create excessive noise. Recognizing when a full proportional procedure is unnecessary is as much a decision as executing it.
- Damper ratios survive fan capacity changes; absolute setpoints do not
- Establish relative branch balance first, correct total at the fan second
- Re-check sample outlets after the total-flow adjustment to confirm ratios held
- Excessive damper throttling raises noise and system resistance — flag it in the report
Duct Traverses: Reading a Pitot Survey When the Profile Is Not Uniform
A duct traverse measures velocity at a grid of points using a pitot tube and manometer, then averages. Treat a wide spread between readings as a diagnostic finding about the location, not just noise to average away.
Trace a realistic scenario: a traverse taken one duct diameter downstream of an elbow yields readings ranging from roughly 800 to 2,400 feet per minute across the grid. The tempting mistake is to average and report the number. The better decision is to recognize that an eddying, separated flow region invalidates the average, relocate the traverse to a straight section several duct diameters from fittings per standard traverse practice, and document why the first location was rejected. Report both locations and the reasoning; a defensible report shows the judgment, not just a final figure.
Distinguish the two quantities you compute from a traverse. Velocity pressure converts to point velocity through the square-root relation, and total flow is the average velocity multiplied by duct area — not the sum of point flows. A common error is multiplying each point velocity by the full area, inflating the result. Also check whether the duct is round or rectangular, because the grid layout and point counts differ, and whether the duct size on drawings matches field measurement; field-verified dimensions are what your calculation must use. These distinctions are easy to overlook when readings look plausible, so practice naming them explicitly in your calculations.
- Wide point-to-point spread signals disturbed flow — move the traverse, do not just average
- Average velocity times field-measured area gives flow; do not multiply per-point velocities by total area
- Round and rectangular ducts use different traverse grid layouts
- Record rejected traverse locations and reasons in the report
System Effect: Why the Nameplate Rating Lies in Real Installations
System effect is the pressure penalty created when poor fan inlet or outlet conditions — elbows close to the fan, obstructions, restricted inlets — distort airflow into or out of the fan, lowering delivered performance below laboratory ratings.
Worked scenario: a supply fan rated for 10,000 CFM at 3 inches of water gauge is measured delivering only 8,500 CFM with the outlet damper fully open, and static pressure across the system checks out lower than expected. The tempting conclusion is that the fan is undersized and a replacement is needed. The better decision is to inspect the inlet and outlet ductwork first: a hard elbow at the fan inlet creates a non-uniform velocity profile into the wheel, a classic system effect condition. Add duct straightening, an inlet condition correction, or a turning-vane retrofit, and the same fan may deliver close to rating — a far cheaper fix than replacement.
Connect this to your balancing sequence. System effect means the fan's actual operating point sits off its lab curve, so fan law predictions calibrated from nameplate data will mislead. The corrective reading habit is to build the fan curve estimate from field measurements taken at the unit after correcting known installation defects, not from the submittal sheet. When a scenario presents 'design said X, field shows Y,' your first diagnostic branch should separate equipment problems from installation-induced system effect before recommending any change of hardware.
- Look for fittings, obstructions, or restricted inlets near the fan before blaming the fan
- System effect shifts the real operating point below lab-rated performance
- Correct installation-induced losses first; re-measure before recommending equipment replacement
- Calibrate fan law predictions from field data, not nameplate curves alone
Instrument Selection: Matching the Tool to Velocity Range and Access
Choose instruments by velocity range, duct access, and accuracy needs: pitot tubes for duct traverses, rotating-vane or thermal anemometers for outlets, and flow hoods for terminals. Using a tool outside its range makes the reading quietly wrong.
Compare the options in a decision table. A pitot tube with an inclined manometer or micromanometer is the reference tool for in-duct traverses but reads poorly at low velocities because the velocity pressure signal becomes tiny. A rotating-vane anemometer is convenient for grilles and large openings but is sensitive to turbulence and insertion angle. A capture hood gives a quick total at diffusers but adds resistance that can alter the very flow you measure on some terminal types. A thermal anemometer resolves low velocities well but is fragile and requires stable conditions.
Scenario drill: a return grille in a low-velocity plenum reads essentially zero on a pitot traverse. The plausible mistake is to record zero flow and move on. The better decision is to recognize the instrument-velocity mismatch, re-measure with a thermal anemometer or vane anemometer suited to the range, and cross-check against the fan's measured total minus supply side. Why it matters: reporting zero flow on a branch that actually carries hundreds of CFM corrupts the balance picture for the whole system. Also note calibration status — an out-of-tolerance instrument invalidates every downstream decision, which is why professional TAB practice requires documented instrument calibration.
- Wide instrument range mismatch produces plausible-looking but wrong readings — verify the tool suits the velocity before recording
- Cross-check hood or anemometer readings against system totals where possible
- Documented calibration status is a condition of defensible readings, not paperwork
| Instrument | Best use | Weakness | Decision cue |
|---|---|---|---|
| Pitot tube + manometer | In-duct traverses, reference-grade readings | Poor low-velocity resolution | Straight duct, moderate-to-high velocity |
| Rotating-vane anemometer | Outlets, large openings, walk-in checks | Turbulence and angle sensitivity | Accessible grilles, mid-range velocities |
| Thermal anemometer | Low-velocity and tight-clearance readings | Fragile, probe handling matters | Plenum or low-velocity return path |
| Capture flow hood | Fast terminal totals at diffusers | Added resistance can change flow | Many similar terminals needing quick totals |
Reports and Documentation: Recording What You Did, Not Just What You Found
TAB documentation must show design values, measured values, instrument identity and calibration, damper and speed settings, and deviations with explanations. A reader should be able to reproduce or re-verify your work from the report alone.
Audit a draft report for the omissions that make it indefensible. If it lists final CFM per terminal but not the damper positions that produced them, a future technician cannot restore the balance after a filter change or tenant fit-out. If it shows flows without instrument identification, no one can judge the accuracy. If a terminal sits far off design with no comment, the reader cannot tell whether it was intentional — perhaps the diffuser was oversized — or missed. Each omission converts a measurement into an untraceable claim.
Build the habit of pairing every deviation with a stated reason and a disposition: corrected, accepted with justification, or flagged for the design team. Compare two report styles on a scenario where one return branch reads 25% below design because of an inaccessible duct obstruction: the weak report lists the number; the strong report notes the obstruction, the attempted corrections, the acceptance rationale or escalation, and the damper settings left in place. Practice by taking any completed balance sheet and rewriting the three weakest lines until they contain setting, value, and disposition — that rewrite exercise trains the judgment the exam scenarios probe.
- Include design value, actual value, instrument used, and its calibration status
- Record final damper positions and fan settings so the balance is reproducible
- Pair every off-design result with a cause and a disposition: fixed, accepted, or escalated
- Field-verify duct and equipment sizes before computing; drawings drift from reality
Readiness Check: A Two-Week Practice Sequence and Scoring Rubric
Spend week one drilling methods — fan laws, proportional sequencing, traverse calculations — on paper systems. Spend week two on integrated scenarios where methods conflict, then score yourself against a rubric rather than a feeling of readiness.
Suggested sequence, adaptable to your available hours. Days 1–2: compute fan law predictions across ten varied cases and write one sentence per case on which adjustment path the equipment supports. Days 3–4: run proportional balancing on paper systems of six to twenty terminals, timing yourself and re-verifying sample ratios after total-flow changes. Days 5–7: perform traverse calculations, including one deliberately bad traverse location, and practice rejecting and relocating it. Week two: rotate through mixed scenarios — system effect, instrument mismatch, reporting gaps — and for each, write the decision and the reason the alternative fails.
Self-check rubric with three milestones. Level 1 — fluency: you compute fan law ratios and traverse flows correctly without notes. Level 2 — judgment: given a scenario, you name the correct method and the specific reason the tempting alternative fails, in two sentences or fewer. Level 3 — integration: in a full scenario you chain measurement, condition verification, adjustment, and documentation without an unexplained gap. Treat these as learning milestones, not predictions of exam results. As a final readiness test, re-attempt the two scenarios in this guide from scratch after one week and confirm you reach the better decision without rereading the answer. For administrative details about the NEBB TAB credential itself — eligibility, scheduling, versions of the standards — consult nebb.org directly rather than relying on summarized pages.
- Week 1: fan law drills, proportional sequencing on paper systems, traverse calculations
- Week 2: integrated scenarios where methods conflict, each answered with a rejection rationale
- Milestone 1: error-free calculations; Milestone 2: two-sentence method justifications; Milestone 3: full unbroken decision chains
- Re-attempt this guide's scenarios a week later without the answers visible
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.