Every valve, flange, pump seal, and connector in a facility that handles hydrocarbons or volatile organics is a potential source of small, invisible leaks, and across a large site those countless small leaks add up to a significant loss of product and emissions. An LDAR program, short for leak detection and repair, is the structured process facilities use to find those leaks, fix them, and prove they did both on schedule. This guide explains what an LDAR program is, how its survey-monitor-tag-repair-reverify cycle works, and how the recordkeeping it demands ties into a compliance database.
LDAR Program (Leak Detection and Repair) in one line: An LDAR program, or leak detection and repair program, is a systematic process for finding and fixing fugitive emissions leaks from equipment components such as valves, flanges, pumps, and connectors. It works on a repeating cycle: regulated components are inventoried and monitored on a required frequency, leaking components are tagged, repaired within a set deadline, and then reverified to confirm the leak is fixed. The program is documented in detail to demonstrate that monitoring frequencies and repair deadlines were met.
A fugitive emission is a leak from equipment that is not meant to emit, as opposed to a designed vent or stack. Individually, a weeping valve stem or a slightly loosened flange releases only a small amount of gas or vapor, but a process facility contains thousands upon thousands of such potential leak points, and collectively they can represent one of the largest sources of volatile organic compound and methane emissions on a site. Because each point is small and the leak is usually invisible, the only way to control the total is to check components systematically rather than wait for something to become obvious.
That systematic checking is what an LDAR program provides. Rather than relying on chance discovery, it treats leak control as a managed, repeating engineering process with a defined inventory of components, defined monitoring methods and frequencies, defined thresholds that constitute a leak, and defined deadlines to repair what is found. The program exists both to reduce actual emissions and lost product and to satisfy regulatory requirements that increasingly mandate this kind of structured monitoring for facilities above certain thresholds.
Different component types carry different leak potential and are treated differently within a program. Valves and pump seals, which have moving parts and dynamic sealing surfaces, tend to be monitored more frequently than static connectors like flanges. The applicable regulation, the type of service a component is in, and its past leak history all feed into how often it must be checked. Getting that classification right for every component in the inventory is the foundation the whole program rests on.
The heart of an LDAR program is a repeating cycle applied to the component inventory. It begins with monitoring, in which each regulated component is screened on its required frequency, typically using a portable instrument that samples the air right at the component to detect escaping vapor, or increasingly an optical gas imaging camera. A component whose reading exceeds the defined leak threshold, or that shows a visible plume, is declared leaking. This survey step is what generates the list of problems the rest of the cycle resolves.
When a leak is found, the component is tagged so it is clearly identified in the field and in the records, and a repair clock starts. Regulations generally require a first attempt at repair within a short window and a final repair within a longer deadline, so tracking the date each leak was discovered and the dates of repair attempts is essential. Some components that cannot be fixed without a shutdown may be placed on a delay-of-repair list with its own rules. After a repair, the component is monitored again to reverify that the leak has actually been eliminated, closing the loop for that component.
The cycle then repeats on schedule, and its integrity depends on nothing falling through the cracks: every component monitored at its required frequency, every leak tagged and repaired within its deadline, and every repair reverified. Miss a monitoring round and the frequency requirement is violated; miss a repair deadline and the repair requirement is violated. The discipline of the cycle is what turns a pile of individual components into a defensible, controlled emissions program, and it is also what makes recordkeeping so central.
An LDAR program lives or dies on records, because the regulatory obligation is not only to monitor and repair but to prove it. For every component the program must be able to show when it was last monitored, what the reading was, whether it leaked, when a leak was found, when repair was attempted and completed, and when the repair was reverified. Multiplied across tens of thousands of components on a repeating schedule, that is an enormous body of data that is impractical to manage on paper and error-prone in scattered spreadsheets.
This is where integrating LDAR into a records and monitoring system pays off. A platform such as Merobix, built to gather and trend field and compliance data, can hold the component inventory, capture monitoring results as they are collected, and run the repair clock automatically so that a leak found today surfaces a first-attempt deadline and a final-repair deadline that are tracked to completion. Overdue monitoring or an approaching repair deadline becomes an alert rather than a surprise found during an audit, which is exactly the kind of proactive compliance tracking regulators and operators both want.
Centralizing the data also makes the reporting and audit obligations tractable. Because every monitoring event, tag, repair, and reverification is stored against the component, the system can produce the frequency and deadline evidence an inspector asks for, and it can trend leak rates by component type or area to reveal recurring problems. When leak-survey results, repair-clock tracking, and recordkeeping all sit in one place tied to the physical inventory, an operator can demonstrate at any moment that monitoring frequencies and repair deadlines were met, which is the whole point of running the program.
An LDAR program typically covers equipment components that can leak volatile vapors, including valves, pump and compressor seals, flanges and other connectors, pressure relief devices, and open-ended lines. The exact set depends on the applicable regulation and the type of service the component is in. Components with moving parts, such as valves and pump seals, are usually monitored more frequently than static connectors.
When monitoring finds a leaking component, it is tagged and a repair clock starts from the date of discovery. Regulations generally require a first attempt at repair within a short window and a final repair within a longer deadline, after which the component must be reverified as fixed. Components that cannot be repaired without a shutdown may go on a delay-of-repair list with its own rules. Tracking these dates for every leak is central to demonstrating compliance.
A leak survey is one round of monitoring components for leaks, while an LDAR program is the whole ongoing system of which surveys are a part. The program defines the component inventory, the required monitoring frequencies, the leak thresholds, the tagging and repair deadlines, the reverification, and the recordkeeping. A survey produces a snapshot of leaks; the program ensures those leaks are repaired on time and the entire cycle is documented and repeated.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.