LDAR programs under 40 CFR Parts 60 and 63 require monitoring of hundreds — often thousands — of fugitive emission components on a quarterly or monthly basis. The sheer volume of data generated by a working LDAR program is what breaks manual systems: paper logs with handwritten ppm readings, spreadsheets tracking repair deadlines across pump and valve populations, binders full of component histories that no one can search in real time.
Missed surveys and incomplete repair records are among the most common findings in EPA enforcement actions against refineries and chemical facilities. The issue is rarely that inspectors didn’t do the work — it’s that the documentation system couldn’t keep up with the program.
EHSTracks LDAR software puts the entire LDAR program in a mobile app with built-in compliance logic. Component inventories, Method 21 survey workflows, leak detection thresholds, repair deadlines, skip period tracking, and audit-ready reporting all operate within a single system that goes where your inspectors go.
A functioning LDAR program starts with an accurate component inventory. Every pump, valve, connector, pressure-relief device, open-ended line, and agitator subject to your applicable NESHAP or NSPS subpart needs to be tracked — with its location, process unit, component type, service classification (gas service, light liquid, heavy liquid), and monitoring frequency.
EHSTracks LDAR software maintains that inventory in a format that actually supports field operations:
- Track every tagged component with full attribute set: tag ID, component type, process unit, service, applicable regulation subpart (VV, VVa, H, GGG, GGGa, or others), and monitoring frequency
- Configure custom monitoring routes that match your plant layout — inspectors follow a logical path through the unit rather than working from an unsorted component list
- Import existing component databases from spreadsheets or legacy LDAR software — no need to rebuild an inventory you’ve maintained for years
- Flag components removed from service, in non-applicable service, or physically inaccessible — with the documentation required to support those designations during an audit
When your component database is clean and complete, everything else in the LDAR program flows from it correctly.
Method 21 — EPA’s standard portable analyzer method for fugitive emission screening — requires the inspector to bring a calibrated instrument to each component, record the ambient background concentration, take the screening reading at the component interface, and document both values. Done on paper across a 500-component route, that’s 1,000+ data entries per survey period.
EHSTracks puts that workflow on iOS or Android:
- Inspectors open their assigned monitoring route in the app and work component by component — the interface is built for gloved hands and field conditions, not a desktop screen
- Capture instrument readings, background concentrations, and screening values in real time — each reading stamped with the time and the inspector’s credentials
- GPS location verification confirms the inspector was at the component location when the reading was recorded — not estimated from memory back at the office
- Offline mode handles the reality of plants with poor cell coverage: surveys sync automatically when the device is back in range
- Photo documentation for components with condition issues, damaged tags, or access problems that affect survey completion
The result is a complete Method 21 survey record that withstands the scrutiny of an EPA audit — not a reconstructed paper log.
Under 40 CFR Part 63 Subpart VV, a valve in gas service is considered leaking if the screening value exceeds 10,000 ppmv. Subpart VVa tightens that threshold to 500 ppmv for valves. The threshold varies by component type, service classification, and applicable subpart — and applying the wrong threshold to the wrong component is a recordkeeping violation even if the underlying reading is accurate.
EHSTracks applies the correct threshold automatically:
- Define leaking component thresholds by regulation subpart, component type, and service — the system applies the right standard to each component based on its attributes
- When a survey reading exceeds the applicable threshold, the component is automatically flagged as leaking and a corrective action workflow is triggered
- Inspectors see the leak flag in real time during the survey — no waiting until the data is uploaded to identify which components need immediate attention
- Dashboard view shows all currently leaking components, organized by process unit and days since detection
This is the compliance logic that manual LDAR systems leave to human memory — and where enforcement exposure accumulates.
Repair deadlines under LDAR regulations are specific and unforgiving. For most subparts, the first repair attempt must occur within 5 days of detecting a leak. If that attempt fails, the component is tagged as a Difficult-to-Monitor (DTM) or Unsafe-to-Monitor (UTM) component with specific delay-of-repair documentation requirements. Final repair must be completed within 15 days, or within 2 scheduled shutdowns for components that require process unit downtime.
EHSTracks tracks every step:
- When a component is flagged as leaking, the 5-day repair clock starts automatically — no manual calendar entries
- Log the first repair attempt with instrument re-read, inspector sign-off, and outcome (repaired or first-attempt failure)
- If the first attempt fails, the system triggers delay-of-repair documentation and sets the 15-day deadline or shutdown-based deadline
- Log the final repair and re-monitoring read — if the component is re-screened within the survey instrument detection limit, the leak is closed and the record is complete
- Overdue repair alerts flag approaching and missed deadlines to the EHS team before they become violations
The complete repair record — first attempt, delay-of-repair documentation if applicable, final repair, re-monitoring — is attached to the component history and available for audit at any time.
Components that meet no-detectable-emissions (NDE) criteria may qualify for reduced monitoring frequency or skip period status. Under EPA’s Alternative Work Practice (AWP), eligible facilities can use optical gas imaging (OGI) cameras on a modified schedule in lieu of Method 21. Managing skip period eligibility and AWP schedules manually — across a population of hundreds of components — is where documentation errors accumulate.
EHSTracks tracks skip period and AWP status within the component inventory:
- Document skip period eligibility criteria per component, including the NDE verification results that established eligibility
- Track AWP survey schedules — the system maintains the schedule automatically once AWP status is assigned to a component
- Log skip period eligibility reviews (required periodically under most subpart rules) and document any components removed from skip period status
- Maintain the documentation trail that demonstrates eligibility was properly established and maintained throughout the monitoring period
LDAR recordkeeping requirements under 40 CFR Parts 60 and 63 require maintaining component logs, monitoring records, repair records, and skip period documentation for the life of the equipment plus 5 years post-shutdown. Over the life of a refinery or chemical plant, that’s a substantial archive.
EHSTracks generates compliance reports directly from the operational data:
- Component-level monitoring reports by process unit, monitoring period, and regulation subpart — the format EPA asks for during a compliance evaluation
- Leak summary reports showing number of components detected leaking, repair completion rates, and delay-of-repair documentation by period
- Audit-ready export in PDF or CSV — every reading, every repair, every skip period entry, with inspector credentials and timestamps attached
- Full inspection history per component: every Method 21 reading in chronological order, every repair action, every skip period eligibility review
- Reports are formatted to align with the data fields EPA requests during a compliance evaluation of an LDAR program
When an inspector arrives and asks for the LDAR program records for Unit 4 covering the last 12 months, you pull the report in EHSTracks and hand them a complete, properly organized package.
LDAR programs at large industrial facilities have requirements that generic inspection software can’t accommodate. EHSTracks is designed specifically for the scale and complexity of real LDAR programs:
- Scalable from 200 to 20,000+ tagged components — the platform doesn’t degrade with large component populations
- Multi-site and multi-process-unit support — manage LDAR programs across multiple facilities or permit boundaries from one platform
- Configurable to your applicable subparts — whether your facility is subject to Subpart VV, VVa, H, GGG, GGGa, or a state-equivalent rule, the compliance logic is configured to match
- Built by EHS professionals who have run LDAR programs — the workflow reflects how LDAR inspections actually happen in the field, not a theoretical model of compliance
Facilities subject to LDAR requirements under 40 CFR Parts 60 and 63 are typically subject to other environmental regulations that require the same inspection discipline. EHSTracks covers the full environmental compliance stack:
See all EHSTracks products for the complete compliance program suite.
What EPA regulations does EHSTracks LDAR software support?
EHSTracks LDAR software is configurable to the major LDAR regulatory subparts under 40 CFR Part 63 NESHAP and 40 CFR Part 60 NSPS, including Subparts VV, VVa, H, GGG, GGGa, and other NESHAP subparts with LDAR requirements. The platform applies the correct leaking component thresholds, monitoring frequencies, and repair deadline logic for each subpart based on each component’s attributes. State-level rules equivalent to federal LDAR standards can also be accommodated. Contact EHSTracks to confirm support for your facility’s specific applicable subparts before configuration.
Can EHSTracks handle multi-site LDAR programs?
Yes. EHSTracks supports multi-facility LDAR programs from a single platform. Each facility or process unit can have its own component inventory, applicable regulation subpart, monitoring routes, and reporting configuration — while all sites remain accessible to corporate EHS oversight from a centralized dashboard. This is particularly relevant for companies operating refineries, chemical plants, or natural gas processing facilities across multiple permits or permit boundaries, where LDAR programs may run under different subparts at each location.
Does EHSTracks LDAR software work offline in the field?
Yes. EHSTracks is designed for the field conditions common to refineries and chemical plants, where cell coverage in process units and tank farms is often unreliable. Inspectors can complete full Method 21 survey routes in offline mode — all readings, component data, and GPS coordinates are stored locally on the device and sync to the cloud when connectivity is restored. No survey data is lost due to connectivity interruptions, and no readings need to be re-entered manually after returning to an office area.
How does EHSTracks generate LDAR compliance reports?
LDAR compliance reports in EHSTracks are generated directly from the monitoring, repair, and skip period data collected during normal operations — there is no separate data entry step. Reports can be filtered by process unit, monitoring period, regulation subpart, component type, or individual component. The standard output formats include component-level monitoring summaries, leak detection and repair records, and skip period/AWP documentation packages. All reports include inspector credentials, timestamps, and GPS verification for each data point, in a format consistent with EPA compliance evaluation documentation requests.
See how EHSTracks handles your specific LDAR program configuration. Schedule a demo with the EHSTracks team.