Access Official Technical PDF

Share Summary:LinkedInEmail

Emissions data sharing can help agencies and facilities compare reported information across the National Emissions Inventory (NEI), the Toxics Release Inventory (TRI) and state, local and tribal emissions inventories (SLT-EIs). But shared data are useful only when users understand how each program defines facilities, pollutants and reporting obligations. A cross-program analysis of 2014 data found substantial overlap, alongside meaningful differences that affect comparisons and quality assurance (QA).

These findings offer a practical lesson for environmental data managers and reporting-system designers: integration is not simply a matter of transferring values between databases. Reliable workflows need to preserve the context behind each estimate, identify where data may be incomplete and make differences visible to reviewers.

Why emissions data sharing matters

The NEI brings together emissions estimates for criteria air pollutants, hazardous air pollutants and other pollutants. State, local and tribal agencies submit much of its facility-level information, while EPA also uses other sources, including TRI data, to fill some gaps. TRI collects information from qualifying facilities in specified industry sectors that meet employee and chemical-use thresholds. Facilities report to EPA and their respective state or tribe.

The programs therefore serve different reporting purposes and do not cover identical populations. The NEI includes stationary sources beyond TRI’s industry scope and also includes non-stationary sources such as airports and rail yards. TRI, by contrast, is limited by its own facility definitions, covered sectors and reporting thresholds. Some SLT-EIs may include facilities or pollutants not required under TRI.

In the 2014 analysis, the NEI contained approximately 66,000 stationary-source facilities, compared with about 20,000 TRI facilities reporting air emissions. At least 10,238 TRI facilities were matched to the NEI. Among TRI facilities with emissions greater than zero, about 64% were also represented in the NEI. The matched facilities accounted for 97% of TRI-reported emissions for pollutants common to the programs, excluding hydrogen sulfide from that comparison.

These figures show why matching records can be valuable, but they do not mean the two inventories are interchangeable. Differences in coverage and reporting rules shape what each system contains.

Why emissions values do not always match

Comparisons of SLT-reported NEI emissions with TRI values found differences by state, industry and pollutant. Nearly half of the facility-pollutant records compared were within 10%, and the median TRI-to-NEI ratio was close to one for most states. However, TRI values were higher in more cases, and comparable total emissions did not always have the same allocation between stack and fugitive releases.

Several factors can explain a discrepancy:

  • Different reporting thresholds and facility definitions: Requirements may cause a facility or emissions source to appear in one program but not another.
  • Incomplete facility data: The NEI may not use TRI to fill a pollutant value when an SLT has reported some emissions for that pollutant, even if the reported amount does not represent the facility’s full emissions.
  • Different pollutant definitions: Chemical groups may not align exactly across programs. Certain glycol ethers and cyanide compounds are examples where definitions and treatment can differ.
  • Different estimation approaches: TRI and SLT programs may use different emission factors or calculation methods. Programs may also allow different numerical formats, precision or ranges.
  • Different treatment of events: Some SLTs may not report non-routine emissions, such as accidental releases, to the NEI, and are not required to do so.
  • Reporting errors: Data-entry or estimation errors can also contribute to mismatches.

As a result, an apparent disagreement is a prompt for investigation, not automatic evidence that one value is wrong. Reviewers need to understand the source, scope and method behind each record.

Build QA around context, not just comparison

TRI and NEI data can inform each other’s QA, but comparisons should account for program limitations. The analysis found variation in how program offices and EPA regions reviewed data. No surveyed office operated entirely in isolation, yet practices and priorities differed, and staff varied in how they used cross-program comparisons.

Useful steps for improving cross-program QA include:

  • Share guidance explaining appropriate ways to compare NEI and TRI data, including the limits of direct comparisons.
  • Coordinate review schedules so that TRI information is available when states are checking inventory submissions.
  • Improve facility-identifier crosswalks between the NEI’s Emissions Inventory System (EIS) and TRI, including processes to track facility merges and identifier changes.
  • Provide facilities with clearer technical guidance on estimating representative emissions for both programs.
  • Keep emission-factor resources, including WebFIRE and AP-42, current and accessible.

One near-term workflow improvement identified in the project was loading TRI data into EIS earlier in the NEI development cycle. This gives state agencies more opportunity to use available comparison tools during their reviews. Automated procedures to prevent double-counting overlapping pollutants were also developed within the NEI during the project.

Designing a common emissions reporting workflow

A proposed CAER Common Emissions Form (CEF) was intended to let facility reporters collect and quality-check information for SLT-EIs and TRI. Its value depends on supporting each program’s requirements rather than forcing all data into a single, oversimplified structure.

A practical common form would need to account for program-specific thresholds, exemptions and state requirements, then send information in the format each receiving program requires. It should guide reporters through required fields, explain pollutant definitions and provide relevant instructions. Links to previously submitted data could help reporters review and, where appropriate, reuse information.

Crosswalks are also essential. NEI has more detailed emission calculation method codes than TRI has basis-of-estimate codes, while NEI control codes are more detailed than TRI waste-treatment codes. Because these categories do not always map one-to-one, a form should offer the closest applicable options while retaining the distinctions needed by each program. It should also support calculations and guidance beyond simple emission-factor use.

Changes and resubmissions create additional workflow questions. The project’s recommendations focused on the scenario in which reporters use the form to submit to SLT-EIs and TRI; procedures for changing previously submitted information still require consideration.

Practical implications for data managers

Effective emissions data sharing is built on coordinated processes, clear definitions and traceable estimates. Facility matches and comparison tools can help identify potential gaps, but they cannot resolve differences in scope or methodology on their own. Agencies and system designers should preserve program-specific context, maintain identifier crosswalks and give reporters usable guidance.

For operations and environmental reporting teams, the practical priority is to treat cross-program comparisons as a structured QA resource—not as a substitute for understanding reporting rules. With that approach, shared data can support more informed reviews, reduce avoidable inconsistencies and provide a stronger foundation for future common reporting workflows.

Access Official Technical PDF

About The Author