Alberta Stack Sampling Code (ASSC) Explained

A stack test can produce technically valid numbers and still fail to support a compliance decision if the work was not planned, performed, and documented to the Alberta Stack Sampling Code (ASSC). For Alberta industrial facilities, the code establishes the framework for obtaining emissions data that regulators can evaluate with confidence.

The ASSC is not simply a field technician’s sampling checklist. It affects how a facility defines the test objective, selects operating conditions, prepares access, confirms methods, manages quality assurance, and reports results. Treating it as a last-minute field requirement creates avoidable risk when testing is tied to an approval condition, emissions limit, permit application, complaint response, or annual reporting obligation.

What the Alberta Stack Sampling Code governs

The Alberta Stack Sampling Code sets expectations for source testing conducted to demonstrate compliance or characterize emissions from industrial sources. Its purpose is to promote representative, repeatable, and defensible measurement. That means the testing program must account for both the emission source and the process that produces the emissions.

A compliant program generally considers the sampling location, traverse points, flow conditions, test duration, production rate, fuel or feed characteristics, analyzer performance, laboratory procedures, and the applicable reference methods. The required approach depends on the contaminant and source. Particulate matter, nitrogen oxides, sulfur dioxide, carbon monoxide, volatile organics, acid gases, metals, and greenhouse gases do not necessarily share the same sampling or analytical requirements.

The code should also be read alongside the facility’s specific regulatory instruments. An approval, registration, environmental protection order, or site-specific request may prescribe pollutants, testing frequency, operating limits, averaging periods, notification requirements, or reporting deadlines beyond the general code framework.

A representative test begins before the crew arrives

The highest-value compliance work occurs before field mobilization. A test plan should establish what question the data must answer: Is the facility demonstrating a concentration limit, a mass emission rate, destruction efficiency, control-device performance, or baseline emissions for engineering purposes?

That question drives the test design. For example, a test intended to demonstrate a maximum allowable emission rate must capture a representative operating condition and sufficient process data to calculate the rate correctly. Testing during an unusually low-load period may not demonstrate compliance at normal or maximum production. Conversely, forcing an abnormal operating condition solely for the test can make the results unrepresentative.

Facilities should confirm the following well in advance of the scheduled date:

• The applicable approval conditions, pollutants, limits, units, and averaging periods

• Source operating scenarios and the production data needed during each run

• Safe, compliant access to test ports, platforms, power, lighting, and fall-protection anchor points

• Sampling port configuration and whether the location supports the required traverse and method

• Control equipment operating parameters, such as pressure drop, reagent flow, temperatures, or baghouse conditions

• Required notifications, test plan submissions, and report delivery dates

These items are operational controls, not administrative details. Missing process records, restricted port access, or an improperly located sampling plane can compromise an otherwise well-executed test.

Field execution: methods, calibration, and quality control

ASSC-aligned testing relies on recognized sampling and analytical methods, commonly including applicable EPA reference methods and approved alternatives where appropriate. Method selection must match the source conditions, target compounds, concentration range, moisture level, gas composition, and reporting requirement.

Calibration and quality assurance are central to defensible results. Instruments require documented pre-test checks, calibration gases and procedures appropriate to the measurement range, drift assessments where required, leak checks, sample recovery controls, and complete field records. When laboratory analysis is involved, chain of custody, sample preservation, recovery calculations, and laboratory quality-control results also matter.

A result should never be viewed in isolation from its supporting records. Regulators and facility teams may need to understand whether the process was stable, whether the test train operated within method criteria, whether the sampling was isokinetic when required, and whether any deviations occurred. A documented deviation does not automatically invalidate a test, but an unexplained deviation can materially weaken its use for compliance.

Common compliance issues under the ASSC

The most frequent problems are usually preventable. Testing may be scheduled before the process is at a representative load. A stack may lack adequate ports or safe platform access. Continuous operating data may not be recorded at the intervals needed to support the runs. Or a facility may assume that a previous test method remains suitable after a process, fuel, control system, or stack configuration change.

Another concern is unit consistency. Emission limits may be expressed on a dry basis, at reference oxygen, at standard conditions, per unit of production, or as a mass rate. The report must apply the correct corrections and conversions, supported by measured data. A concentration that appears acceptable before oxygen correction or moisture adjustment may not satisfy the actual approval limit.

Reporting that supports regulatory decisions

A strong source-test report gives the regulator and facility a traceable path from the approved requirement to the final reported value. It identifies the source and control equipment, describes operating conditions, specifies methods, presents calibration and quality-control data, documents deviations, and shows calculations clearly enough for technical review.

For facility managers, the report should also identify practical implications. If results are close to a limit, the next step may be increased monitoring, control-equipment maintenance, operational adjustments, or testing under a more demanding production scenario. If results exceed a limit, prompt technical review is needed to distinguish a process issue from a measurement, unit-conversion, or operating-condition issue.

The Alberta Stack Sampling Code is most effective when it is integrated into routine compliance planning rather than treated as a one-day testing event. Early coordination between operations, EHS personnel, engineering teams, and qualified source-testing professionals produces safer field work, more representative data, and reporting that can withstand regulatory scrutiny.