LDAR Reconciliation Without Chaos: Turning Leak Logs into Assurance-Ready Proof

Leak Detection and Repair (LDAR) is a structured program used to find, measure, repair and verify leaks from equipment such as valves, flanges, connectors, pumps and compressors. In oil and gas, LDAR is especially important for managing methane emissions from fugitive sources. A strong LDAR program does not only detect leaks; it also creates the evidence needed to prove what was inspected, what was repaired and how emissions were calculated.

LDAR reconciliation is the process of connecting component-level leak evidence to reported methane emissions totals. For GCC oil and gas operators, this means linking component registers, survey logs, repair records, verification readings, calculation assumptions and site-level measurements into one governed evidence chain. OGMP 2.0 Level 5 and the EU Methane Regulation are increasing pressure on operators and exporters to show not only that methane was measured, but how reported totals were built and reconciled. The practical goal is simple: move from scattered leak logs to defensible, traceable proof.

Key takeaways

• LDAR reconciliation connects source-level leak evidence to site-level methane emissions totals.
• The GCC faces dual pressure from domestic environmental requirements and international buyer expectations.
• OGMP 2.0 Level 5 requires reconciliation between source-level inventories and independent site-level measurements.
• The EU Methane Regulation creates import-side requirements that can affect GCC gas and LNG exporters commercially.
• The most common failure is not always missing surveys. It is fragmented evidence that cannot be retrieved when assurance teams ask for it.
• A reconciliation-ready LDAR program needs consistent component IDs, timestamped survey data, repair verification, locked assumptions and a clear evidence trail.

Why LDAR reconciliation has become harder in the GCC

LDAR reconciliation has become harder because methane programs are now expected to support assurance, commercial access and external reporting, not only internal maintenance.

At many large GCC oil and gas facilities, the operational side of LDAR is already mature. Survey schedules exist. Optical Gas Imaging (OGI) cameras are used. Leak tags are assigned. Repair timelines are monitored. Contractor reports are submitted.

The difficulty appears later, when someone asks a different question:

Can the reported methane figure be traced back to the underlying evidence?

That evidence may be spread across field tools, maintenance systems, contractor PDFs, spreadsheets, SharePoint folders and ESG reporting files. Each system may be useful on its own, but assurance requires the chain to connect.

The pressure is rising for three reasons.

First, methane reporting frameworks are becoming more measurement-based. OGMP 2.0 has pushed oil and gas companies toward more granular reporting, with Level 4 focused on source-level measurement and Level 5 focused on reconciling source-level inventories with site-level measurements.

Second, import-side regulation is changing market expectations. The European Commission’s methane emissions guidance states that EU importers must provide information on the origin, route, monitoring, reporting, verification and leak detection and repair measures applied to imported crude oil, natural gas and coal. From 1 January 2027, importers must demonstrate that certain imported fossil fuels were produced under equivalent monitoring, reporting and verification requirements, or at OGMP 2.0 Level 5 plus verification for oil and gas. From 5 August 2028, importers must report methane intensity for relevant imported fuels, with methane intensity limits following from 5 August 2030.

For GCC gas and LNG exporters, this does not mean the EU directly regulates every upstream facility in the Gulf in the same way it regulates EU operators. It does mean buyers, importers and counterparties may increasingly ask for evidence that methane measurement, LDAR and reconciliation practices are credible.

Third, independent top-down data is becoming more available. Aramco has stated that it is using the GHGSat Satellite Constellation to monitor methane emissions from in-Kingdom operations. As satellite, aerial, drone and continuous monitoring technologies become more common, discrepancies between bottom-up LDAR records and site-level observations will be harder to ignore.

The practical implication is clear. Operators need a way to explain the difference between what was measured at component level and what is observed at site level.

What LDAR reconciliation actually means

LDAR reconciliation is the process of connecting source-level leak evidence to a site-level emissions total, then explaining how that total compares with independent site-level measurements.

A strong LDAR reconciliation workflow should connect:

• The component register
• The survey schedule
• The field inspection record
• The leak detection result
• The repair work order
• The post-repair verification
• The emissions calculation
• The assumptions and emission factors used
• The reported site-level methane total
• The comparison with aerial, satellite, drone, continuous monitoring or other top-down data

This matters because different measurement methods do not always measure the same boundary.

A component-level OGI survey may focus on fugitive leaks from valves, flanges, connectors, pumps and compressors. Site-level aerial or satellite measurement may capture a wider picture, including tanks, vents, combustion-related sources, intermittent events or sources outside the LDAR survey boundary.

A discrepancy does not automatically mean the LDAR program failed. It does mean the operator needs a documented explanation.

See our blog on Emission Factors in the GCC: DEFRA vs IEA vs Local Utility Factors for the broader factor-governance question. The same principle applies here: assumptions should be documented, frozen by reporting period and traceable through a change log.

Where the LDAR evidence chain usually breaks

LDAR evidence usually breaks when component registers, survey logs, repair records, verification readings and calculation files use different identifiers or live in separate systems.

Here are the most common breakpoints.

Between the component register and the survey log

A survey is only assurance-ready if it can show which components were inspected, on which date, using which method, by which team.

If the component register lives in one system and the survey record sits in a contractor PDF, the link is often manual. When an assurance provider asks which components were covered in Q3, the answer should not require someone to rebuild the record from scattered files.

A reconciliation-ready workflow needs consistent component IDs across the register, survey record, repair system and emissions calculation.

Between the survey log and the repair record

A detected leak is not the end of the evidence chain. It is the start of the repair and verification trail.

For each detected leak, the operator should be able to show:

• Detection date and time
• Component ID
• Detection method
• Initial reading or estimated emission rate
• First repair attempt date
• Repair completion date
• Repair method
• Post-repair verification reading
• Any reason for delay, deferral or exclusion

Saudi Arabia’s Executive Regulation for Air Quality requires relevant facilities to set up fugitive emissions plans, keep data and annual reports on fugitive emissions management for at least five years, and maintain records such as component tracking results, equipment specifications and OGI leak survey videos.

That turns LDAR evidence into a records-management question, not only an inspection question.

Between the repair record and the emissions calculation

Even when surveys and repairs are well documented, the emissions calculation may still be difficult to defend.

The calculation depends on assumptions such as:

• How long the leak was active before detection
• Whether the emission rate came from direct measurement or an approved estimation method
• Which emission factor was used for the component type
• Whether the same method was used across all sites
• Whether any components were excluded from the inspection scope
• Whether assumptions changed between reporting years

If these assumptions are not locked and documented, year-on-year comparisons become weak. A methane total may look precise, but it will be hard to explain under assurance.

Between source-level totals and site-level measurements

This is the reconciliation gap that OGMP 2.0 Level 5 is designed to address.

A bottom-up LDAR inventory may estimate emissions from identified equipment leaks. A top-down aerial or satellite measurement may suggest a higher total across the site. The gap may be caused by measurement uncertainty, different boundaries, intermittent events, non-LDAR sources or missing source categories.

The reconciliation step should explain:

• Which sources are included in the LDAR inventory
• Which sources are included in the site-level measurement
• Which source categories could explain the gap
• Whether the difference is within expected uncertainty
• Which follow-up actions are required if the gap remains unexplained

Without this step, a measurement difference can look like a data quality failure. With this step, it becomes a documented boundary and methodology discussion.

Between this year’s report and last year’s baseline

LDAR reconciliation also needs time consistency.

If the operator changes emission factors, component counts, survey frequency, site boundaries or leak-duration assumptions between reporting years, those changes need to be documented. Otherwise, the year-on-year methane trend may be misleading.

A reported reduction should reflect real operational improvement, not a silent methodology change.

See our blog on Product Carbon Footprints Without Version-Control Hell: Factors, Audit Trails, and Change Logs for a parallel example of why methodology version control matters for emissions reporting.

What a reconciliation-ready LDAR evidence chain should include

A defensible LDAR reconciliation package is not one document. It is a connected set of records that can be traced from component-level evidence to reported methane totals.

1. A maintained component register

The component register is the foundation of LDAR reconciliation.

It should include:

• Site
• Facility area
• Component ID
• Component type
• Process fluid
• Installation date
• Inspection zone
• Required survey frequency
• Inspection method
• Exclusion status, where relevant
• Reason for exclusion, such as safety, inaccessibility or regulatory classification

The register should also be version-controlled. If a component is added, modified, removed or excluded, the date and reason should be recorded.

A missing or outdated component register creates a weak starting point for every downstream calculation.

2. Timestamped survey records

Survey records should show more than whether a leak was detected.

A useful LDAR survey record should capture:

• Survey date and time
• Technician or contractor name
• Instrument type
• Calibration date
• Weather or operating conditions where relevant
• Components inspected
• Components not inspected and why
• Detection result
• Non-detection result
• Reading or emission estimate, where measured
• Supporting photos, videos or files

This is especially important when OGI videos or contractor deliverables are used as evidence. A video without component tagging, timestamping and survey context is difficult to use in an audit.

3. Repair records with verification evidence

For each detected leak above the applicable threshold, the repair record should show what happened after detection.

At minimum, it should include:

• Leak detection date
• Component ID
• Initial reading or estimated emission rate
• First repair attempt date
• Repair completion date
• Repair method
• Reason for delay, if any
• Post-repair verification date
• Post-repair verification reading
• Closure status

The verification step is often where evidence becomes weak. Marking a leak as repaired is not the same as proving it was fixed.

4. Locked calculation assumptions

LDAR data becomes reportable only when it is converted into an emissions estimate.

That requires clear assumptions, including:

• Measurement method or estimation method
• Emission factor source, where factors are used
• Leak duration assumption
• Treatment of non-detects
• Treatment of delayed repairs
• Treatment of excluded components
• Treatment of missing data
• Reporting period boundary
• Global warming potential values, if methane is converted into carbon dioxide equivalent

These assumptions should be locked by the reporting year and stored in a methodology note. If they change, the change should be logged.

5. A documented reconciliation note

The reconciliation note connects bottom-up LDAR totals with site-level data.

It should answer:

• What does the bottom-up LDAR inventory include?
• What does the top-down site-level measurement include?
• What are the known differences in boundary and timing?
• What is the size of the difference?
• Which sources could explain the difference?
• What remains unexplained?
• What follow-up action is required?

This note does not need to force two measurement methods to produce identical numbers. It needs to show that the operator understands the difference and has a defensible explanation.

6. A retrieval workflow that survives assurance

The strongest LDAR program still fails under assurance if the evidence cannot be retrieved.

A reviewer should be able to search by component ID and see:

• The component record
• The survey history
• The detection event
• The repair work order
• The verification evidence
• The emissions calculation
• The methodology used
• The approval history
• The reporting output where the data was used

If this requires five systems and three people, the evidence chain is fragile.

Example: what one reconciled leak record should show

A single leak record should be able to answer the full story from detection to reporting.

For example:

• Which component leaked: component ID, equipment type, site, process area and inspection zone
• How it was detected: survey date, method, instrument, calibration record and technician
• How large it was: measured rate, concentration reading or approved estimation method
• What happened next: first repair attempt date, repair method and completion date
• Whether it was fixed: post-repair verification result and date
• How it entered the inventory: leak-duration assumption, factor or measurement method, calculated methane emissions and reporting period
• Where the evidence lives: survey file, repair work order, verification record, calculation log and methodology note

This is the level of traceability that turns LDAR from a field activity into assurance-ready proof.

The GCC-specific version of the problem

The LDAR reconciliation challenge is especially important in the GCC because many operators manage large assets, multi-site portfolios, contractor-led inspection programs and export relationships that now face more scrutiny.

Multi-contractor programs create evidence silos

Large facilities may use different contractors, methods or frequencies across different zones.

One contractor may submit OGI survey files. Another may provide Method 21 records. A third may support aerial surveys or continuous monitoring. Each may use a different file structure, field naming convention or component identifier.

Without a central intake process, reconciliation becomes a manual exercise every reporting cycle.

Export exposure raises the evidence bar

For GCC operators selling crude, gas or LNG into EU-linked supply chains, methane evidence may become part of commercial due diligence.

The EU Methane Regulation’s import-side requirements are aimed at EU importers, but those importers will need information from producers, suppliers and counterparties. That means GCC exporters may face increasing requests for methane measurement, reporting, verification, LDAR and reconciliation evidence.

The commercial risk is not only regulatory non-compliance. It is buyer friction, delayed documentation, weaker contract positioning and lower confidence in reported methane performance.

Satellite and aerial data increase transparency

Top-down methane data is becoming more accessible. Aramco’s satellite monitoring program is one regional example of how methane detection is moving beyond facility-level surveys.

This does not replace bottom-up LDAR. It makes bottom-up evidence more important.

When top-down data identifies a methane plume or site-level anomaly, the operator needs enough source-level evidence to investigate and explain it. Without that foundation, the operator is reacting to external data with incomplete internal records.

LDAR reconciliation readiness checklist

Use this as a quick internal audit before an assurance review, buyer request or regulatory submission.

Your LDAR program is reconciliation-ready if:

• The component register is current and version-controlled.
• Each component has a consistent ID across survey, repair, calculation and reporting systems.
• Excluded components are documented with clear reasons.
• Survey records include date, time, technician, instrument, calibration data, method and component coverage.
• Detection and non-detection results are stored in a structured format.
• Detected leaks are linked to repair records by component ID.
• Repair records include first attempt date, completion date, method and post-repair verification.
• Post-repair verification readings are stored and retrievable.
• Emission factors, measurement methods and leak-duration assumptions are documented.
• Assumptions are locked by reporting year.
• Methodology changes are logged and approved.
• Bottom-up source-level totals are compared with available top-down site-level data.
• Differences between bottom-up and top-down results are explained by source category, boundary, timing or uncertainty.
• All evidence can be retrieved by component ID in one workflow.
• The final reported methane total can be traced back to the underlying records.

If several answers are “not yet,” those gaps will likely define the assurance conversation.

Why LDAR reconciliation matters beyond compliance

LDAR reconciliation matters commercially because the same evidence chain used for assurance can reveal repeat leak patterns, ineffective repairs, high-risk equipment types and better maintenance priorities.

A tagged component register with survey history can show which equipment types leak most often and where. Repair verification records can show which fixes worked and which leaks returned. Site-level reconciliation can reveal sources that were missed by the original survey boundary.

This creates operational intelligence.

It can help operators:

• Prioritize maintenance budgets
• Reduce repeat leaks
• Improve contractor accountability
• Identify high-risk equipment types
• Strengthen methane reduction plans
• Support credible site-level targets
• Improve confidence in external reporting

That is why LDAR reconciliation should not be treated as an ESG reporting clean-up exercise. It is part of measurement-informed methane management.

Where Coral fits

Coral does not replace LDAR field surveys, OGI cameras, aerial measurement providers or maintenance systems.

Coral helps operators govern the evidence those systems produce.

For LDAR reconciliation, that means bringing fragmented records into a connected workflow where survey files, repair records, calculation assumptions, emission factors, approvals and reporting outputs can be traced. Coral’s Emissions Management System is designed to centralize operational data, measure Scope 1, Scope 2 and Scope 3 emissions, identify hotspots, support audit-ready methods and produce board- and auditor-ready outputs.

For GCC operators, this is especially important when methane evidence is spread across contractor deliverables, maintenance systems, field tools and reporting spreadsheets. The goal is not to create a larger spreadsheet. The goal is to create a governed evidence chain from component-level activity to reported emissions.

Explore Coral’s Emissions Management System, or book a demo to see how GCC operators can move from scattered leak logs to decision-grade proof.

FAQ

What is LDAR reconciliation?

LDAR reconciliation is the process of connecting source-level leak detection and repair evidence to a reported methane emissions total. It links component surveys, detected leaks, repair records, verification readings, calculation assumptions and site-level data into one evidence chain. The goal is to show how the reported number was built and why it is defensible.

Why does LDAR reconciliation matter in the GCC?

It matters because GCC oil and gas operators often manage large, complex facilities with multiple contractors, systems and reporting obligations. Domestic environmental requirements, investor expectations, OGMP 2.0 participation and EU-linked buyer requirements are all increasing the need for traceable methane evidence. Operators with export exposure may also face more requests from counterparties for methane measurement, reporting, verification and LDAR documentation.

What is OGMP 2.0 Level 5?

OGMP 2.0 Level 5 is the highest level of methane reporting under the Oil and Gas Methane Partnership framework. It requires operators to reconcile source-level methane inventories with independent site-level measurements. In practical terms, this means operators need to compare bottom-up estimates with top-down data and explain material differences.

Does the EU Methane Regulation apply to GCC operators?

The regulation directly applies to EU operators, undertakings and importers, but it can affect GCC operators commercially when their crude oil, natural gas, LNG or coal enters EU-linked supply chains. EU importers must increasingly provide information about methane measurement, reporting, verification and LDAR measures associated with imported fossil fuels. This can create documentation expectations for non-EU producers and exporters.

How should operators handle discrepancies between OGI surveys and satellite or aerial data?

Operators should not assume the two methods will match exactly. OGI surveys usually focus on component-level fugitive leaks, while aerial or satellite measurements may capture broader site-level methane signals. A defensible reconciliation note should explain each method’s boundary, timing, uncertainty and source coverage, then identify which source categories may explain the difference.

What LDAR records should be retained?

Operators should retain the component register, survey records, instrument and calibration data, OGI videos or supporting files, leak detection results, repair timelines, post-repair verification readings, calculation assumptions, emission factors, methodology notes and approval records. Saudi Arabia’s Executive Regulation for Air Quality requires data, records and annual reports on fugitive emissions management to be kept for at least five years, with the possibility of extension for some activities. For operators with EU-linked exposure, longer retention may be prudent because buyer and assurance requests can arise after the reporting year.

Is LDAR reconciliation the same as methane MRV?

No. LDAR is focused on detecting and repairing leaks, usually at component or equipment level. Methane Measurement, Reporting and Verification (MRV) is broader and covers how methane emissions are measured, calculated, documented, verified and reported across relevant sources and boundaries. LDAR evidence is an important input into methane MRV, but it is not the full MRV system by itself.