What this is
What is a stack test record?
What is a stack test record?
A stack test record is the formal record of a calibrated emissions measurement at a stack, carried out by an accredited contractor against a prescribed method and compared to the permit's limit for each determinand. It happens periodically, to a defined method, rather than continuously.
How does a stack test differ from the air emissions log?
The air emissions log is the site's own ongoing reading, taken as often as the permit requires. A stack test is a periodic, accredited campaign, usually annual, that validates the log's readings and satisfies a permit condition the log alone cannot.
Who carries out a stack test?
An accredited testing contractor, working to a recognised method standard, under conditions the site must set up correctly: representative process load, abatement fully operating, and compliant sampling ports.
Scope
When is a stack test record required?
The record is for the periodic, accredited measurement campaign itself. Routine monitoring between tests belongs in the air emissions log, and the two should reference each other rather than duplicate.
Use this template when
- A permit-required periodic stack test is due, and needs its conditions, contractor and results recorded
- A stack test is being run for commissioning, after a process modification, or to investigate a suspected exceedance
- Test conditions, representative load, abatement status and sampling port compliance need to be confirmed before results are accepted
- Results need to be checked against each determinand's permit limit and flagged where marginal
- An exceedance needs to be linked to the permit register, the compliance log and a corrective action
Do not use it for
- Air Emissions Log, the routine, ongoing reading taken to the permit's monitoring schedule, not the periodic accredited test.
- Refrigerant Leak Record, which tracks refrigerant loss from cooling and freezing systems, not stack emissions.
- Greenhouse Gas Inventory, which totals emissions across scopes 1, 2 and 3 for reporting rather than measuring one stack against its limit.
- Permit Condition Compliance Log, which evaluates the permit as a whole rather than recording one test's results.
- Anything outside KnowEnviro, which belongs in the workspace that owns that process.
Compliance mapping
Which EPA Method testing requirements does this satisfy?
Stack testing is prescribed in more procedural detail than routine logging: the method, the load condition and the accreditation are usually named in the permit itself, with the surrounding management-system expectation set by ISO 14001.
| Clause | Requirement | Where it lands |
|---|---|---|
| EPA Reference Methods (40 CFR Part 60, Appendix A) | Prescribed sampling and analysis methods for each determinand, stated on the record | Test provider |
| Clean Air Act Title V (40 CFR Part 70) | Permit-specified test frequency, method and representative operating conditions | Test conditions |
| ISO 14001:2015 cl.9.1.1 | Monitoring and measurement of significant aspects, carried out under representative conditions | Test conditions |
| 40 CFR 70.6(a)(3) | Prompt reporting of a deviation identified through periodic testing | Outcome |
| ISO 14001:2015 cl.9.1.2 | Evaluation of compliance with the permit's emission limits, on a planned basis | Results |
| ISO 14001:2015 cl.10.2 | Corrective action following a nonconformity, including an exceedance found by test | Outcome |
| ISO/IEC 17025 | Accreditation basis for the testing contractor's competence and method validity | Test provider |
What it does not cover
- Air Emissions Log, the routine reading taken between tests, not the periodic accredited campaign.
- Permit Condition Compliance Log, which evaluates the whole permit's conditions, not one test's results.
- Greenhouse Gas Inventory, a scope 1/2/3 total for reporting, not a determinand-level test result.
- The testing contractor's own accreditation audit, assessed by the accreditation body, not recorded here beyond citing the scheme.
- Permit renewal or variation, a regulatory application, not a test result.
Global
Stack Test Record requirements by country
Stack testing is prescribed in more detail than routine logging almost everywhere it is required: the method, frequency and conditions are usually named in the permit, with accreditation expectations set nationally.
Clean Air Act; EPA Reference Methods (40 CFR Part 60, Appendix A); Title V permits
Permits typically name the method, the minimum representative load and the test frequency, with deviation reporting on a short statutory clock.
A test conducted outside the permit's stated conditions is not evidence of compliance even if the result is accurate.
Provincial environmental permits; CCME and provincial reference methods
Test method, frequency and reporting format are set permit-by-permit, provincially, often referencing similar methods to the US.
The applicable method and load condition should come from the specific provincial permit rather than a generic template.
ISO 14001:2015; ISO/IEC 17025
Monitoring under representative conditions and evaluation of compliance are management-system requirements, alongside accreditation of the testing body.
Certification audits examine whether test conditions were representative and the result was evaluated against the obligation, not only whether a report exists.
How to complete it
How to complete a stack test record, step by step
Most stack test records are completed once the report arrives. The parts that make the record defensible are set before the test runs, not after.
Process load against the permit's minimum, abatement fully operating, and normal fuel or feed all need confirming as the test starts, because a compliant result run under non-representative conditions is a wasted test that still has to be repeated.
An accredited contractor using an unstated or non-standard method has not necessarily produced a defensible result. Recording the method standard alongside the accreditation is what lets the result be compared to the permit limit with confidence.
A result close to a limit within the stated uncertainty could be a pass or a fail depending how the uncertainty is applied. Flagging results above roughly ninety percent of limit as marginal, rather than a clean pass, keeps the margin visible before it becomes an exceedance.
Where a determinand exceeds its limit, the notification deadline usually runs in days from the result, not from when the report was reviewed internally. Treat it as a distinct action from receiving and filing the report.
What auditors find
Most common stack test record findings
Stack test findings rarely concern the measurement itself, which an accredited contractor is competent to take. They concern the conditions the test was run under and what happened after the result came back.
| Finding | Clause | What fixes it |
|---|---|---|
| Test run below the permit's minimum process load, with the result accepted as representative. | Clean Air Act Title V (40 CFR Part 70) | Confirm load against the stated minimum before the test starts; reschedule if it cannot be met. |
| Contractor accreditation or method standard not stated on the record. | ISO/IEC 17025 | Require accreditation scheme and method standard as a condition of accepting the result. |
| Abatement equipment not confirmed fully operating during the test. | ISO 14001:2015 cl.9.1.1 | Record abatement status as a test condition, not an assumption from normal operation. |
| Marginal result filed as a clean pass with no flag or follow-up. | ISO 14001:2015 cl.9.1.2 | Flag results above a stated margin below the limit and schedule an earlier check. |
| Exceedance not reported to the regulator within the permit's own deadline. | 40 CFR 70.6(a)(3) | Tie the notification deadline to the result date, not to internal report review. |
| Corrective action and retest requirement raised with no owner or verification. | ISO 14001:2015 cl.10.2 | Assign the CAPA and retest date when the exceedance is confirmed, and verify before closing. |
Case in point
Case in point: the compliant test run under the wrong conditions
A dairy processor's dryer stack was due its annual test. The contractor arrived on schedule, but the site was running a short batch at reduced throughput, and the test proceeded at roughly forty percent of the permit's stated minimum load. Every determinand came back comfortably within limit, and the report was filed as a pass.
Eight months later a regulator inspection queried the load condition after checking the production log against the test date. The test was found invalid, and a retest was required at the site's cost, run during a full shift. The second result showed particulates at eighty-five percent of limit, a figure the first test, at partial load, could never have produced. The fix was not a better test; it was checking the load condition before the contractor was booked, not after the report came back.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
6 sections
- Reference
- ENV-023
- Archetype
- Record
- Record ID
- STK2-2026-000
- Scoring
- Result against limit
- Direction
- High is bad
- Singleton
- No
- Basis
- EPA Method testing
- Links
- Links Asset, Vendor, Permit
- Tags
- Environment, Air
- Sections
- 6
- Fields
- 50
- Follow up fields
- 4
- Repeating sections
- 1
- Links out
- 6
Header
11 fieldsRecord ID*
Auto sequence. Format STK-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Emission Point Reference*
Test Reason*
Permit required periodic test, commissioning, after modification, or investigation.
Test Due Date*
Test provider
5 fieldsTesting Contractor*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Contractor Accredited*
- Yes3 pts
- No0 pts
Accreditation Scheme
Method Standard Used
Test conditions
7 fieldsTest At Representative Load
A stack test at fifty percent load proves nothing about normal operation. Permits usually specify a minimum load, and testing below it invalidates the result.
Process Load Percent*
Minimum Load Required
Representative Operation*
- Yes3 pts
- Partly1 pt
- No0 pts
Abatement Fully Operating*
- Yes3 pts
- Partly1 pt
- No0 pts
Fuel Or Feed Normal*
- Yes3 pts
- No0 pts
Test Ports Compliant*
- Yes3 pts
- Marginal1 pt
- No0 pts
Results
Repeats8 fieldsDeterminand*
Particulates, nitrogen oxides, sulphur dioxide, carbon monoxide, volatile organics, ammonia or odour units.
Result*
Units*
Permit Limit*
Percent Of Limit*
Within Limit*
- Yes3 pts
- Marginal1 pt
- No0 pts
Measurement Uncertainty Stated
- Yes3 pts
- No0 pts
Result Marginal
A result at ninety percent of limit will eventually exceed. Treat it as a finding now.
- No3 pts
- Yes, above 90 percent of limit0 pts
Related records
1 fieldEmissions Log ID
The log period this stack test covers.
Links to ENV-022 Log ID
Outcome
18 fieldsAll Determinands Compliant*
- Yes3 pts
- No0 pts
Report Received*
- Yes3 pts
- Awaited1 pt
- No0 pts
Report Submitted To Regulator*
- Yes3 pts
- Not required3 pts
- No0 pts
Submitted Within Deadline*
- Yes3 pts
- Late0 pts
Retest Required*
Next Test Due*
Permit Condition Affected*
Discharge consent, emissions permit, waste licence or abstraction licence.
- No3 pts
- Yes0 pts
Permit Register ID
Links to ENV-039 Register ID
Breach Of Permit Condition*
- No3 pts
- Yes0 pts
Compliance Log ID
Links to ENV-040 Log ID
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Environmental Lead*
Signature*
Site Manager*
Second Signature*
ENV-023 · record IDs look like STK2-2026-000 · Links Asset, Vendor, Permit
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The test itself is run by an accredited contractor. What slips on the site's side is the load condition nobody checked beforehand, the marginal result nobody flagged, and the reporting deadline that ran out while the report sat unread.
Holds the stack test record against the permit register and the emission point, and tracks the next test due date against the permit's schedule.
Confirms abatement equipment status against its maintenance record before a test is accepted as run under representative conditions.
Tracks the testing contractor's accreditation status, so a test cannot be booked with a contractor whose accreditation has lapsed.
Watches for a marginal result, a load below the stated minimum, or an unreported exceedance, and raises it against the permit's own reporting clock.
This template lives in KnowEnviro — environment and energy. Aspects, permits, waste, emissions, spills and sustainability reporting.
Meet KnowEnviro→Glossary
Stack Test Record definitions and key terms
- Determinand
- The specific pollutant or parameter a stack test measures, such as particulates, nitrogen oxides or sulphur dioxide, each assessed against its own limit.
- Representative operation
- Running the process at or above the permit's stated minimum load during the test, so the result reflects normal operation rather than a favourable moment.
- Measurement uncertainty
- The stated range around a result within which the true value is expected to lie, which matters most when a result sits close to the limit.
- Reference method
- The prescribed sampling and analysis procedure for a determinand, used so results from different tests and sites are comparable and defensible.
- Test port compliance
- Whether the sampling location on the stack meets the geometric requirements the reference method assumes, without which a result may not be valid.
FAQ
Frequently asked questions about stack test record
What is the difference between a stack test and the air emissions log?+
The stack test is a periodic, accredited campaign, usually annual, run to a prescribed method under specified conditions. The air emissions log is the site's own routine, ongoing reading, taken far more frequently, and the two should reference each other rather than replace one another.
Why does the process load matter for a stack test?+
Emissions from most combustion and process sources scale with load, so a test run below the permit's stated minimum understates what the source emits at normal operation. An under-load result is not evidence of compliance even if accurately measured.
Does the contractor need to be accredited?+
Yes, to a recognised scheme, with the method standard stated alongside the accreditation. An unaccredited result or one using an unstated method is difficult to defend if challenged.
What counts as a marginal result?+
A result close enough to the permit limit, commonly cited as above roughly ninety percent of it, that normal variation could tip it into an exceedance next time. Filing it as a clean pass without a flag loses the warning it is giving.
How quickly must an exceedance be reported?+
Permit conditions typically require reporting within days of the result, not at the next scheduled review. The clock runs from the test result itself, so delay in internal review of the report can create a second breach.
What happens after an exceedance is confirmed?+
A corrective action is raised, a retest usually scheduled, and the permit register and compliance log updated to reflect the breach. The retest, not just the corrective action, closes the finding.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Environmental Management
Legal and Other Requirements Register
Lists every law, regulation, permit and commitment that applies to your operation
Compliance Evaluation Record
Records the periodic evaluation of whether you actually comply with each obligation
Waste Stream Register
Lists every waste stream produced on site, with its classification, container and disposal route
Waste Transfer Record
Records waste leaving site, including type, quantity, carrier and destination
Hazardous Waste Record
Records generation, storage and disposal of hazardous waste
Waste Area Inspection
Checks waste storage areas for correct segregation, labelling, containment and housekeeping
More in Emissions
Air Emissions Log
Records emissions from permitted sources, including operating hours and control equipment status
Refrigerant Leak Record
Records refrigerant loss from cooling and freezing systems
Greenhouse Gas Inventory
Records emissions across scope 1, 2 and where available scope 3
Emissions Permit Compliance Review
Checks that every condition of an air permit is being met
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- EPA Reference Methods, 40 CFR Part 60, Appendix A
- Clean Air Act; Title V operating permits, 40 CFR Part 70
- 40 CFR 70.6(a)(3), permit deviation reporting condition
- ISO 14001:2015, clauses 9.1.1, 9.1.2 and 10.2; ISO/IEC 17025 accreditation
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.