Compliance Testing Versus Engineering Estimate

A boiler is operating at a steady load, fuel records are complete, and published emission factors appear to provide a reasonable answer. Then a permit condition requires a source test, an NPRI threshold is approached, or a regulator asks how an annual emissions value was derived. At that point, the distinction between compliance testing versus engineering estimate becomes operationally significant. These approaches can support the same environmental program, but they do not carry the same level of direct evidence, uncertainty, or regulatory acceptance.

For industrial facilities, the right question is rarely whether testing or estimating is universally better. The decision is which method is appropriate for the contaminant, source, reporting obligation, permit condition, and consequence of being wrong.

Compliance Testing Versus Engineering Estimate: The Core Difference

Compliance testing produces emissions data by directly measuring a source under defined operating conditions. A qualified field team collects stack gas samples or monitors flue gas using specified methods, documents process operation, completes quality assurance activities, and reports results in the units required by the applicable regulation or approval. Depending on the program, this may involve EPA reference methods, continuous emission monitoring requirements, or source-specific provincial protocols.

An engineering estimate calculates emissions from indirect information. Common inputs include fuel consumption, production throughput, operating hours, material balances, equipment specifications, vendor data, mass transfer assumptions, published emission factors, or prior test results. The estimate is only as credible as the input data and the assumptions used to convert those inputs into an emissions rate or annual total.

Direct measurement is not automatically required for every source or every regulatory filing. Conversely, an estimate is not a substitute where an approval, test protocol, or enforcement requirement calls for representative source testing. The two methods serve different purposes and often work best together.

When Compliance Testing Is the Appropriate Basis

Compliance testing is generally necessary when a facility must demonstrate that a specific stack, engine, heater, kiln, or process source meets an enforceable emissions limit. It provides a defensible record of what was measured at the source during a documented operating period.

A typical compliance test program establishes the applicable methods, target parameters, sampling locations, minimum run duration, required process load, calibration requirements, and reporting format before mobilization. Field documentation matters as much as the final concentration. Regulators and facility teams need to understand whether the unit was operating representatively, whether sampling conditions met method criteria, and whether the analytical results passed quality control checks.

This is particularly relevant for pollutants such as nitrogen oxides, sulfur dioxide, carbon monoxide, particulate matter, volatile organic compounds, hydrogen chloride, metals, dioxins and furans, or greenhouse gas-related parameters where the source configuration and operating conditions can materially affect results. A generic factor may not reflect a facility's actual fuel quality, combustion efficiency, control equipment performance, or process chemistry.

Compliance testing also becomes the stronger basis when emissions data will support high-consequence decisions. Examples include demonstrating compliance with a permit limit, responding to a regulator request, validating the performance of a scrubber or selective catalytic reduction system, establishing a source-specific emission factor, or resolving a discrepancy in reported emissions. In these cases, the cost of uncertain data can exceed the cost of a properly designed test.

Testing Measures a Point in Time - With Important Conditions

A source test is a high-quality measurement of a source under the conditions tested. It is not automatically a complete picture of annual performance. A boiler tested at high load on one fuel blend may produce different results at low load, during startup, after maintenance, or when fuel composition changes.

That limitation does not reduce the value of testing. It reinforces the need for careful test planning. The facility should identify the operating scenario the result must represent, coordinate plant load and process conditions, confirm control equipment status, and retain the operating records that explain the measured result. Representative testing is a joint effort between the test team and plant operations.

Where Engineering Estimates Add Value

Engineering estimates are essential to practical emissions management. Facilities cannot conduct source testing on every vent, tank, intermittent process, and maintenance activity each year. Estimates allow environmental teams to build complete inventories, screen sources for potential reporting thresholds, forecast permit impacts, and prioritize testing budgets.

For example, fuel use and an appropriate factor may provide a reasonable annual estimate for a small combustion source where no stack-specific limit applies. A material balance may be more meaningful than a stack test for determining solvent losses from a batch operation. Equipment specifications and operating hours can support planning estimates for a new source before it is installed or commissioned.

Estimates are also useful between compliance test events. A validated stack test can establish a source-specific emission rate, which can then be applied to operating data to develop an annual inventory. This approach is often more representative than relying on a broad published factor, provided the facility assesses whether process conditions have remained comparable.

The critical discipline is to document the estimation methodology. A defensible engineering estimate identifies the data source, factor or equation used, units, assumptions, control efficiency basis, time period, calculation steps, and known limitations. If an estimate relies on a manufacturer guarantee or a generic reference value, that should be stated clearly rather than presented as measured plant performance.

The Main Trade-Off: Certainty, Coverage, and Cost

The decision usually comes down to three competing needs: measurement certainty, inventory coverage, and available resources. Compliance testing offers direct evidence and a stronger basis for source-specific decisions, but it requires planning, access, safe sampling locations, representative operating conditions, and a greater project cost. Engineering estimates are faster and can cover many sources, but their uncertainty can be substantial when actual operations differ from the assumptions.

A low-risk source with stable operating data may be appropriately managed through an estimate. A source near a regulatory threshold, subject to a stack limit, or connected to a control device should receive greater scrutiny. The same source may move from one category to the other as production increases, fuel changes, new equipment is installed, or reporting requirements evolve.

Environmental managers should also consider the purpose of the number. An estimate suitable for an internal emissions reduction forecast may not be suitable for proving compliance with an approval condition. A value accepted for preliminary permitting may need to be replaced by test data after commissioning. Treating all emissions numbers as equally reliable creates avoidable compliance risk.

Building a Defensible Emissions Program

The most effective programs use a tiered data strategy rather than choosing one method for every need. Direct testing should be directed to the sources and pollutants where measured data are required or where uncertainty has meaningful regulatory, operational, or financial consequences. Engineering calculations should support broader inventory coverage and help identify where testing will provide the greatest return.

A practical program begins by listing each emission source, applicable limits, reporting obligations, pollutants of concern, existing data, and the date and quality of the latest information. From there, each source can be assigned an appropriate basis: current source test data, continuous monitoring data, source-specific factor, mass balance, published factor, or another documented calculation method.

The program should also define triggers for reassessment. These may include a fuel change, production expansion, control equipment modification, recurring deviation, a change in permit conditions, an approaching NPRI reporting threshold, or a result that conflicts with expected performance. Waiting until a report is due to evaluate data quality often leaves too little time for field work or corrective action.

Do Not Use Old Test Data Without Checking Representativeness

Historical stack test results can be valuable, but only if they remain relevant. Before applying an older result to current operations, confirm the source design, fuel or raw material characteristics, production rate, operating range, burner configuration, and pollution controls have not changed in a way that could affect emissions.

The same review applies to prior engineering estimates. A calculation based on annual operating hours from several years ago may understate emissions after a capacity increase. A control efficiency assumption may no longer be valid after maintenance issues or process changes. Data management is not administrative overhead - it is part of maintaining a credible compliance position.

Questions to Resolve Before Selecting a Method

Before relying on either approach, facility teams should establish what the result must prove. Is the objective to demonstrate compliance with a source limit, prepare an annual inventory, support an air permit application, determine whether a reporting threshold applies, verify control equipment performance, or plan a capital project?

They should then assess the source's variability and risk. A stable, well-characterized source may support an estimate. A complex combustion process, variable feedstock, or tightly controlled emissions limit often justifies measurement. Finally, review the governing requirement. Permit language, applicable regulations, and reporting guidance may specify the accepted method or define when testing is mandatory.

Air Research Group can help facilities translate those requirements into field testing, calculation, and reporting plans that match the intended use of the data. The objective is not to test every source unnecessarily or to estimate where direct evidence is required. It is to establish emissions data that are technically sound, traceable, and fit for the decision in front of the facility.

When the consequences of uncertainty are high, the most useful next step is to identify exactly what is known, what is assumed, and what must be measured. That discipline turns emissions data from a reporting task into a reliable basis for compliance and plant decision-making.