Running an In-House Compliance Reporting Program

Running an in-house compliance reporting program means the operator stays accountable for the reporting boundary, the accepted fuel value, the calculation method the rule allows, and the submission. A workbook, a consultant, or software can carry the yea

The same fuel records can support both a federal greenhouse gas report and a state air emissions inventory. What changes from one report to the other is which equipment is included, how the fuel is allocated, and which calculation method each program requires. Consider a gas processing facility that already has both reporting obligations. Its engines and a heater draw from one fuel meter.

What does an in-house compliance reporting program actually own?

The program owns six decisions, and they have to work next year, when the fuel changes and someone else prepares the file. If nobody inside the company can rerun the file and explain the accepted fuel value, the operator cannot stand behind the submission. Before the reporting year closes, the team should be able to answer these without rebuilding the file from scratch.

• Which reports are in scope, and what does each one include?
• Who is accountable for the submission, and who may accept a fuel value for that report?
• Which activity data meets each requirement?
• Which calculation method applies, and which inputs produced the submitted result?
• How is a gap or a rejected value handled so the filing deadline is still met?
• What stays with the submission so the year can be reconstructed, including a later correction?

Those answers can live in a workbook, in a platform, or across both. The scope here is air and GHG reporting. Permits, inspections, and LDAR sit in the facility's broader environmental compliance work. A limit or a repair matters to this program when it changes what gets reported.

Applicability and methods change. What the file needs is which requirement applied to the year being filed.

Which obligations apply, and what belongs in each report?

Each report specifies its own contents. The federal report covers the greenhouse gases and the reporting boundary in the applicable rule, using the calculation method that rule permits. The state inventory covers the pollutants and emissions sources on its own list. If that inventory also includes greenhouse gases, that result follows the state requirement and is kept apart from the federal total.

Write the period down for each report. A calendar year is common. A revision or a permit condition can use a different window, so check the fuel year against the inventory year before treating them as the same twelve months.

In this example, the facility files a greenhouse gas report to EPA and an air emissions inventory to the state. The greenhouse gas report goes to EPA under 40 CFR Part 98, through EPA's electronic greenhouse gas reporting tool. The EPA GHGRP reporting guide is the orientation for that federal filing. The state inventory goes to the state or local air agency that requires it. EPA's National Emissions Inventory is compiled later from what state, local, and tribal agencies submit.

One fuel meter serves the engines and the heater. The federal reporting boundary takes that fuel as activity for the facility's combustion equipment. The state inventory lists the engines and the heater as separate emissions sources, so the same fuel is allocated between those lines. The program records both reporting boundaries before anyone accepts a fuel value.

Who is accountable for the filing and the underlying information?

Operations owns the meter and the historian. Production accounting may hold another fuel figure, built from allocations rather than from the meter. The environmental lead may coordinate the reporting process, while the designated certifying official is responsible for the certification the applicable program requires. A technical reviewer checks that the calculation method is one the report is allowed to use. For the federal submission, EPA expects the certifying official to stand behind the report.

Name who may accept the fuel value for each report. For the federal calculation, that is the person who may accept the facility fuel volume. For the state inventory, that is the person who may accept the allocation between the engines and the heater, and the inputs to that inventory's calculation. One person can hold both roles. The person who accepted the March fuel value is often not the one who certifies the federal submission. The team should know which, before anyone is asked to sign.

A consultant can prepare the workbook. The operator is still accountable for the filing, which means someone on staff can say which fuel value was accepted for each report.

When nobody will pick up the next step, the break is in the handoff. Those patterns are described in 9 workflow bottlenecks that create industrial compliance risk.

How does the team establish a defensible reported value?

A fuel value is acceptable for a report when it covers the reporting year, uses the units the calculation method expects, and includes the equipment inside that report's reporting boundary. The reviewer writes down why this input was the one used. For the federal report, the accepted fuel value is the one that satisfies that report's calculation method, or a documented combination that does.

The historian can export one volume for the engines and the heater together. Production accounting can offer another volume for the same months. Both can be internally consistent and still fail that check. One may include a month outside the reporting year. The other may be a rate where the calculation method expects a volume, or it may leave out equipment inside the reporting boundary.

The state inventory uses the same underlying fuel records, subject to its own reporting requirements. In this example, the team allocates the fuel between the engines and the heater and records the basis for that allocation.

The historian export still has to pass the same check. What has to be true of the tag, the units, and the gaps is covered in SCADA data for emissions reporting in oil and gas.

The calculation record sits beside the fuel record. The program keeps the calculation method the applicable rule requires and the inputs that produced the submitted result. The state inventory requires its own calculation record, even when it uses the same underlying fuel data. Both records can be valid for that fuel.

If an activity-data source fails the check, the team records why its value was rejected, which value replaced it, and who accepted the replacement. A production-accounting figure that includes fuel outside the reporting period is set aside for that report. Any state allocation built from the rejected figure is rebuilt from the accepted fuel value.

What happens when a reporting input or result cannot be accepted?

The historian shows an unchanged fuel reading for nine days in March, even though the equipment was operating. The team cannot treat that flat reading as actual consumption.

Each report's rules determine how a gap like that may be handled. The team uses only the handling the applicable rule allows, and records the value, the basis, and the person who applied it.

If the team cannot yet show that the fuel value meets the requirement, they escalate to the person accountable for that submission. The filing deadline still stands.

The initial report is prepared and submitted on time, using that allowed handling and any explanation the submission itself requires. If a later revision is needed, the team uses the correction process that program provides. A correction follows the original filing. It does not replace it. After a GHGRP report is filed, EPA may require an explanation or a revised submission, which is why the basis needs to be in the file before the deadline.

The state inventory can have its own due date and its own rule for the gap. The state question is handled on that date. The federal report is still filed on its own.

What must remain with the submitted report?

After the report is submitted, someone who was not in the review has to rebuild the year from the file. An agency question is answered from that record. If EPA or the state agency later requires a correction, the correction is filed against the original reporting year, so the basis has to still be there.

For each submission, keep the reporting boundary, the accepted fuel value and why it was accepted, any allocation and its basis, and the calculation method and inputs that produced the reported result. Keep the value used for the gap and the basis for it.

What a verifier expects to see with a reported value is covered in emissions assurance and verification in oil and gas.

How can the same activity support more than one reporting obligation?

Each report starts from the accepted fuel value and then follows its own requirement.

The federal calculation applies its calculation method to the fuel inside the federal reporting boundary. The result is the greenhouse gas total that method produces.

The state inventory uses the allocation between the engines and the heater, then applies its own calculation method. The result is that inventory's emissions estimate for the pollutants on its list.

Both results can be right. They can cover different pollutants, use different reporting boundaries, or assign the fuel differently before either calculation runs. The reviewer checks whether each result used the accepted fuel value as its own requirement specifies: the right equipment, the right allocation, the right calculation method, and the right period.

Two workbook mistakes look similar on a screen. Someone starts a second fuel total that cannot be tied to the accepted fuel value. Or someone edits the fuel in one file so that report's result resembles the other. The edit can misstate emissions, because the activity was changed to force an agreement the two requirements do not ask for.

A later customer or voluntary request can ask for another total from the same fuel. That request needs its own reporting boundary, gases, and calculation method. Voluntary emissions reporting is the commercial home when the request is a voluntary disclosure.

When is the existing reporting process enough?

The workbook is enough when someone can reproduce the reported values from it in the next cycle. It has to hold the reporting boundary for each report, the accepted fuel value and why it was accepted, the calculation method and inputs, and the basis for any gap. A facility in this example, with a reviewer who already records the reporting boundary, the accepted fuel value, and the allocation, can keep the workbook. That record sits next to the annual total.

Software becomes the relevant conversation when those records no longer last from review to certification, or when a second report is built from a fuel total nobody can tie to the accepted fuel value. When spreadsheets stop working for emissions management covers that threshold.

Where can software support the program?

A reporting platform can store the reporting boundary, the accepted fuel value and its basis, the calculation method and inputs, and a second output from the same fuel. The operator still needs to establish that the activity data and calculation meet each report's requirements. Teams choosing a platform for that path can use the emissions reporting software guide.

How Validere fits

Validere keeps an emissions calculation traceable to its operational source and the methodology behind it, and it can sit beside the systems operations already runs. That is a fit when the same activity has to support more than one air and GHG report.

The operator remains responsible for applying each program's requirements and for the value that gets filed. See how Validere supports regulatory air and GHG reporting.

Frequently asked questions

What is an in-house compliance reporting program?

It is how an operator keeps air and GHG reporting decisions usable every year: which reports apply, what each reporting boundary includes, which fuel value meets each requirement, which calculation method and inputs produced the submitted result, and how gaps are handled without missing the filing. Workbooks, consultants, and software can support the work. Accountability for the submission stays with the operator.

Who is accountable for an in-house compliance reporting program?

The person who must file the report and stand behind it is accountable for the submission. Someone else may own the meter, accept the fuel value, or check the calculation method. Name those roles before the year closes. A consultant who builds the file leaves the obligation with the operator.

What should be decided before a reporting cycle starts?

Which reports are in scope, which equipment and period each reporting boundary covers, who may accept a fuel value, and which calculation method applies. Also decide how an unusable interval will be handled under the applicable rule, and what will be kept with the submission so the next cycle can reproduce the reported values.

Why can the same facility activity produce different emissions totals for different reporting programs?

Each program sets its own reporting boundary and calculation method. A state inventory that lists emissions sources separately may allocate the same fuel across those lines before it calculates. Both results can be correct. They are different measures, so agreement between the totals is not the test. The failure is a second fuel value nobody can tie to the accepted one, or an edit made so the results look consistent.

Can a compliance reporting program still run in spreadsheets?

Yes, when a small group can still explain the reporting boundary, the accepted fuel value, the calculation method and inputs, and the basis for any gap a year later. The file is in trouble when the next reviewer cannot reproduce the reported values from it. When spreadsheets stop working for emissions management covers that threshold.