Every spring, petroleum and natural gas facilities above the reporting threshold have to hand the EPA a full accounting of the prior year's greenhouse-gas emissions, and the mechanism for doing that is a Subpart W report filed through the agency's e-GGRT system. The report is not a single number; it is a set of emission figures calculated for each source category on the site, from wells and tanks to pneumatic devices, compressors, and flares. Those figures come out of the Subpart W emission equations, and every equation is hungry for operational data the facility already generates during the year: throughput volumes, vented gas, flared gas, run times, and equipment counts. This guide walks through the annual filing workflow, how that field data feeds the calculations, how the finished numbers enter e-GGRT by web form or XML upload, and why continuous measurement replaces the frantic spreadsheet reconstruction most operators still do at year-end.
e-GGRT Subpart W reporting in one line: Filing a Subpart W report in e-GGRT means calculating each source category's greenhouse-gas emissions for the prior calendar year using the subpart's equations, then submitting those numbers through the EPA's e-GGRT portal either by typing them into web forms or by uploading a single XML file, and certifying the report by the March 31 deadline. The calculations draw on throughput, vent, flare, and equipment-count data captured during the year, so the quality of that field data determines whether the filing is a straightforward export or a months-long reconstruction.
The Subpart W report is built one source category at a time, and each category has its own equation or emission-factor method that turns operational data into a mass of methane and carbon dioxide. A flare's emissions depend on the volume of gas routed to it, the composition of that gas, and the destruction efficiency assumed for the flare. A storage tank's flashing and working losses depend on throughput and, where applicable, measured or modeled flash-gas volumes. Pneumatic controllers are counted by type and multiplied by activity and emission factors. In every case the equation is only as trustworthy as the volumes and counts fed into it, which is why the report is fundamentally a data-assembly exercise rather than a modeling one.
The volumes those equations want are precisely the ones a well-instrumented site is already measuring. Sales and allocation metering give throughput. A metered flare header gives the gas volume sent to flare rather than an after-the-fact estimate. Continuous gas analysis or periodic sampling gives the composition that converts a raw volume into a methane and carbon-dioxide mass. Vent volumes from blowdowns, dehydrator still vents, and tank vapors are the hardest to pin down and are where estimates most often creep in. When those quantities are captured as they happen, the annual calculation becomes an aggregation of real records; when they are not, the operator ends up back-calculating them from monthly production and a stack of assumptions.
The distinction matters because Subpart W numbers are increasingly scrutinized and increasingly consequential, so a defensible report is one whose inputs trace back to measurement rather than to a spreadsheet built in March. An operator who can point to metered flare volumes, logged blowdown events, and documented equipment counts has a report that survives review. An operator who reconstructs those inputs from memory and averages has a report that is technically compliant but fragile, and every fragile input is a place where the total can be challenged or restated later.
Once the numbers are calculated, e-GGRT accepts them two ways, and the right choice depends on the size and complexity of the facility. The web-form path has the reporter open each applicable Subpart W section in the browser and type the calculated values into the fields the tool presents. It is workable for a small facility with few source categories, and it keeps the reporter close to the tool's own inline checks, but it is slow and error-prone for a large site with many wells, tanks, and compressors because every value is a manual keystroke.
The XML upload path lets the reporter build the entire report as a structured file that conforms to the EPA's reporting schema and load it into e-GGRT in one action. For a facility with many source categories, or for an operator filing for many facilities, this is the practical route, because the report can be generated from the underlying data rather than transcribed. The trade-off is that the XML has to match the schema exactly, so the value of the approach depends entirely on having the source data organized well enough that a file can be produced from it without manual patching. That is where an operator with clean, structured field records pulls ahead: the report is closer to an export than a construction.
Whichever path is used, the wall on the calendar is the same. Subpart W reports for a calendar year are due by March 31 of the following year, and the report must be certified by the facility's designated representative before submission counts. Because certification is a legal statement, the representative has to be registered and authorized in e-GGRT well before the deadline, and the data has to be final. Operators who leave both the data assembly and the account setup to March discover that a single missing registration or one unreconciled vent volume can stall a submission at the worst possible moment.
The habit Subpart W filing tends to breed is a year-end reconstruction: sometime after the calendar closes, a small team pulls production reports, flare estimates, maintenance logs, and equipment lists together and rebuilds twelve months of activity into the numbers the equations need. This is slow, it is stressful, and it is where most of the uncertainty in a Subpart W report is born, because volumes that were never measured in real time have to be inferred late, and events that were never logged have to be remembered. The report ends up as accurate as the reconstruction, not as accurate as the operation.
Continuous monitoring turns that reconstruction into an aggregation. When a cloud SCADA platform such as Merobix trends flare header flow, records blowdown and venting events with timestamps, tracks tank throughput, and holds the equipment inventory that feeds the pneumatic and component counts, the raw material of the Subpart W report accumulates through the year rather than being assembled at its end. Instead of estimating how much gas went to flare, the operator reads the metered total. Instead of remembering how many blowdowns occurred, the operator reads the event log. The March filing becomes a matter of summing records that already exist.
The financial and audit stakes make this more than a convenience. Subpart W numbers now feed downstream obligations and are examined by verifiers and, increasingly, by anyone assessing a facility's methane performance, so a report grounded in continuous measurement is both easier to file and easier to defend. When a reviewer questions a flared volume, the operator produces the metered trend. When a total is challenged, the inputs trace to logged data rather than to a spreadsheet nobody can reproduce. The same measurement discipline that makes the filing faster also makes it defensible, which is the real reason continuous field data belongs at the center of the Subpart W workflow.
The Subpart W report for a calendar year is due by March 31 of the following year, filed through the EPA's e-GGRT system. The report must be certified by the facility's designated representative before it counts as submitted, so that person has to be registered and authorized in e-GGRT ahead of the deadline. Because certification is a legal statement, the data also has to be final before submission, not still being reconciled.
Web-form entry works for a small facility with few source categories, since the reporter types calculated values directly into the tool. XML upload is the practical choice for a large site or a multi-facility operator, because the whole report is built as one structured file and loaded in a single step rather than transcribed field by field. The XML has to match the EPA schema exactly, so its value depends on having source data organized well enough to generate the file cleanly.
Each source category's equation draws on operational data such as throughput volumes, gas routed to flare, vented volumes from blowdowns and dehydrators, gas composition, equipment counts, and run times. Metering the flare header and logging venting events as they happen make those inputs traceable to measurement rather than to year-end estimates. The completeness and quality of that captured data determine whether the annual filing is a straightforward aggregation or a labor-intensive reconstruction.
Primary references from the standards bodies and regulators that define this topic:
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.