The flyover file lands before lunch. Operations recognizes the pad. LDAR already has an open tag on a nearby valve. The methane inventory still uses last year’s factor for that source, because nobody owns the rule for whether this event reopens a value the program already accepted. The measurement exists. The inventory does not yet know it.
Teams run into that gap once campaigns outpace intake. Aerial files, continuous monitors, contractor leak surveys, and satellite detections arrive faster than the program can absorb them. Someone still has to attach the event to an asset, decide whether it changes a reported total, and keep the evidence with the number. Collecting another dataset is the easier part. The work that decides inventory confidence is the handoff from a detection or measurement event into a governed emissions inventory. That is the workflow gap: an emissions event has been observed, and the governed inventory has not yet incorporated it, rejected it, or explained why it does not apply.
This guide is for environmental, EHS, air, GHG, and methane program managers at oil and gas operators, plus the LDAR, inventory, and operations partners who generate the source data. It assumes the reader already runs some detection or measurement. It walks the path from event to inventory update. It is not an LDAR software buyer’s guide, an MRV definition rewrite, an OGMP 2.0 how-to, or a second emissions management software evaluation.
Connecting methane measurements to an emissions inventory means a detection or measurement event can change a governed total. That path needs the right asset, an approved method, an exception if needed, investigation and repair or recheck where required, and a traceable update that reporting and assurance can still reconstruct. A file in a historian, a contractor workbook, or a shared-drive flyover folder is not yet inventory work. It becomes inventory work when someone can tell which asset and operating state it belongs to, whether the previously accepted value should change, and how that decision will be explained later.
Industry groups already use measurement-informed inventory (MII) for a related idea. GTI Energy’s Veritas protocols describe an MII as an inventory informed by direct site-level measurements of the assets in that inventory, rather than emission factors alone. METEC uses similar language for inventories built from site-specific measurements rather than generic assumptions. OGMP 2.0 uses measurement-based reporting, including measurement-informed source inventories at Level 4 and reconciliation of that inventory with independent site-level measurements at Level 5.
Those protocols answer a statistical and methodological question: how measured results and bottom-up source estimates should be combined. The operating problem comes first. Before anyone can reconcile a site-level rate with a source inventory, an event has to find the right asset, survive a method and ownership decision, and either update the governed record or leave a reason it did not. That closed path is what many programs still lack, even after they have paid for more measurement.
On a slide, measurement feeds inventory. On a Tuesday the names, clocks, and owners fail in ordinary places.
The names do not match. Maintenance knows the unit as K-120. The leak tag says COMP-120A. The inventory row is still “Station 12 compressor.” A continuous-monitor spike, a work order, and a calculated emission land on three identities. Someone will reconcile them in a meeting. Until then, the measurement has nowhere to attach.
The clock does not match. The event happens on the 12th. The inventory was frozen on the 8th for a monthly close, or last quarter’s method was already approved for GHGRP. The new observation sits in operations while reporting continues on the accepted value. By the time environmental sees the file, the question is no longer “did this happen?” It is “are we allowed to reopen what we already signed?”
Nobody owns the reopen rule. Operations assumes environmental will decide whether the event changes the total. Environmental assumes the methane lead owns exceptions. The methane lead is waiting on a contractor’s interpretation of the plume. Procedures describe roles. They often do not name who decides when a measurement is a data defect, a repair-only event, or a change to an accepted inventory line.
The method is frozen and the evidence is not. Engineering agrees the factor should move after a study or a series of finds. The new number is in a workbook. The method note, the approval, and the comparison to the prior period stay in last year’s folder or in email. When a reviewer asks why the line moved, the people who changed it have a different assignment.
These are the same class of failures as other industrial compliance workflow bottlenecks: the record is assembled after the work, not while it happens. Methane programs just make the cost obvious, because the measurements keep arriving whether the inventory is ready or not.
Each step has to leave something attached for the next one. If the asset, the decision, or the evidence stays in someone’s head, the inventory never sees the event.
Figure 1: A measurement creates inventory value when the event can change, or explain, a governed total.
Detect or measure. Something is observed: an LDAR find, a continuous-monitor spike, an aerial or satellite detection, or a stack test. Those are measurement events. An engineering estimate can still be an inventory input. It is not the same kind of event, and it should not be labeled as if it were.
Contextualize. Attach the event to the asset identity, timestamp, and operating state the inventory already uses. The leak tag, the work order, the monitor point, and the inventory line can have different names. They still have to resolve to the same governed object: this equipment, this operating state, this source. If the program cannot say which compressor, which mode, and which hour, it cannot yet decide inventory impact.
Decide inventory impact. Not every detection should change a total. An event may be an in-scope inventory change, a repair-only finding, a method or coverage issue, or a data defect. The decision needs an owner and a recorded reason, including when the answer is not to change the governed value.
Two events can land in the same inbox and take different paths. An aerial detection is matched to a pad. Investigation confirms abnormal venting inside the inventory boundary, an approved quantification method is applied, the inventory line is reopened, the prior value stays in history, and the evidence is attached. A satellite detection is matched to a site. Investigation attributes the plume to an adjacent third party, the governed total does not change, and the attribution still stays on the record. Both are closed loops, and only one changes the number.
Investigate or repair as required. When the event implies a leak, an abnormal operating state, or a source the inventory never had, field work has to happen and come back. Repair and recheck are one required step on this path when the finding warrants them. They should not live in a system the inventory never sees.
Update the governed inventory. Change the accepted value, the method, or the activity data, with versioning. Or record that the event was reviewed and left the prior value in place. Either outcome is a closed step. Silence is not.
Retain evidence. Method version, inputs, exception, investigation outcome, and approval stay with the line that reporting will later use. Emissions reporting software can then produce a package without reconstructing inboxes. If the support for the number lives only in someone’s head, the inventory was updated in conversation, not in the record.
Programs that skip from “we measured it” to “the dashboard looks better” are missing the middle of this path. The middle is where inventory confidence is made or lost.
LDAR is one measurement input family, not a separate methane program. A leak tag, a first-attempt date, a repair, and a recheck should attach to the same asset identity the inventory uses, then follow the same impact and evidence rules as other events. If inspection data remains a compliance silo, the inventory will keep using a factor while the field team already knows the component leaked, was repaired, or is still open.
Scheduling, field capture, repair windows, and component-level record-keeping belong in the LDAR software buyer’s guide. The question here is narrower: when a finding matters to methane inventory confidence, can it enter the governed total, or does environmental discover it in a year-end folder?
Treat OGI surveys, handheld screening, and other close-range detection the same way. They are intake shapes. The handoff rules do not change because the camera is on a truck instead of a plane.
Continuous monitors, fenceline systems, aerial flyovers, drones, and satellites produce different files, timescales, and false-positive patterns. They do not get a second inventory process. The same tests apply: Can the observation be tied to an asset and operating state? Does someone own the impact decision? If investigation is required, does the outcome return? If the inventory should move, does the method version move with it?
What changes is intake shape. A continuous spike may need an event window rather than a single survey timestamp. An aerial plume may need spatial attribution before it is safe to assign to a pad or a piece of equipment. A satellite detect may be useful as a trigger and still be the wrong grain for a source-level line. Those are contextualize-and-decide problems. They are not reasons to park the dataset beside the inventory until the next campaign.
The failure mode is buying more coverage and hoping the inventory will catch up. Extra measurements without an absorption path increase the pile of files that never change a governed number.
An emissions inventory is the set of values an organization is prepared to stand behind for a defined period and boundary. Once a line is accepted, changing it is a governance act, not a spreadsheet edit. That is why so many measurements die in a side folder: the program measured after it had already decided what to report.
A new measurement should trigger review of a previously accepted value when three things are true. The event belongs to an asset in the inventory. It arrives under a method the program recognizes, or it is strong enough to challenge that method. And the reopen rule says the prior value is no longer the best governed estimate. The rule can be conservative. It cannot be unspoken.
Review is not the same as replacing a prescribed calculation. Reopening an internal governed estimate does not necessarily mean substituting a measurement for a method a reporting program requires. The event may instead trigger investigation, a correction to activity data, a method review, or a separately governed measurement-informed estimate. A GHGRP or Subpart W total still has to be calculated the way the rule requires. That is not a reason to ignore the measurement in the internal record.
When the inventory should not change, write that down too. An illustrative close might read: reviewed, attributed to a third-party event outside the boundary. Another might record that the observation was below the method’s detection limit and did not change the source estimate. Those are examples of a closed path, not generic regulatory guidance. Reviewers can test a recorded decision. They cannot test an undocumented choice to ignore the file.
Method versions have to travel with the number. If this year’s factor, activity data, or measurement-informed estimate differs from last year’s, the record should show what changed, who approved it, and whether prior periods were restated or left as filed. Subpart W and other GHGRP outputs are one place that discipline is tested.
Nearby programs use measurement and inventory language. They depend on this handoff rather than replacing it.
OGMP 2.0 is UNEP’s voluntary, measurement-based methane reporting framework. Level 4 is a measurement-informed source inventory. Level 5 is reconciliation of that Level 4 inventory with independent site-level measurements, not site-level measurement alone. For those levels, Gold Standard clocks, and reconciliation practice, use the OGMP guide. The operating need underneath them is still the same: events that can be attributed, reviewed, and absorbed before anyone averages a site-level rate.
MRV is the broader process for turning operational and emissions data into reported information that can be traced, reviewed, and verified. The methane event-to-inventory path is one demanding sequence inside that process.
EPA GHGRP and Subpart W specify what U.S. petroleum and natural gas facilities calculate, keep, and submit. A measurement campaign does not replace the method the rule requires. The rule is not a reason to ignore measurements the internal record should have reviewed.
Emissions management software is the broader program platform: collection, calculation, reporting, forecasting, investigation, and response. When the buying job is the platform, use that guide. When the failure is that measurements never become inventory truth, the sequence above is the diagnostic.
Before buying another methane measurement technology, test whether the current workflow can do these six things. Many programs already measure more than they can absorb. These tests are operational. They are not a software scorecard, and repair linkage matters only as one step inside inventory reopen.
Software can make that queue visible and keep the evidence attached. The organization still has to name owners, freeze rules, and reopen rules. Connecting field, measurement, and inventory work is the job. Replacing every existing system is not.
Connecting methane measurements to an emissions inventory means a detection or measurement event can change a governed total, with the asset, method, exception, and evidence still attached. A measurement sitting in a historian or contractor file has not entered the inventory yet.
They usually fail at the handoff: mismatched IDs, a missing operating state, a frozen inventory, an unowned reopen rule, or evidence left in email. The campaign produced data. The governed total never saw it.
A measurement-informed inventory is an emissions inventory informed by measurements of the assets in that inventory, rather than emission factors alone. GTI Energy’s Veritas protocols and METEC use that language for site-level measurement and reconciliation; OGMP 2.0 uses related language at Level 4 and Level 5. None of that works if the event cannot change, or explain, a governed value.
LDAR is one measurement input family. A leak tag, repair, and recheck should attach to the same asset identity the inventory uses, then follow the same reopen and evidence rules as other measurement events. Buying and running the inspection program is a separate evaluation; see the LDAR software buyer’s guide for that depth.
OGMP 2.0 is a voluntary measurement-based methane reporting framework, and MRV is the process that makes reported values reconstructable. Both depend on the methane event-to-inventory handoff. Neither is a substitute for it.
Trigger review when the event belongs to an inventory asset and a reopen rule says the prior value may no longer be the best governed estimate. That is not the same as replacing a calculation method a reporting program requires, and not every detection should change the total.
A closed loop means detect or measure, attach asset and operating state, decide inventory impact, investigate or repair when required, update the governed inventory, and keep the evidence with the number. Field work and the reported total then tell the same story without reconstructing inboxes.
On that same Tuesday path, Validere can match a flyover event to the relevant asset, put it beside existing LDAR and operating context, route investigation or response, and carry the decision into the governed inventory with the evidence attached. It can work alongside existing LDAR, operations, measurement, and reporting systems rather than requiring those systems to be replaced.
See how Validere supports emissions measurement and response, including how measurement events feed Air & GHG emissions software. For OGMP-oriented voluntary emissions reporting, that same handoff still has to hold.
If you want to see that path on your asset list, a flyover file, and an open LDAR tag, book a walkthrough.