CSLD, explained without the jargon

What is CSLD?

Continuous statistical leak detection (CSLD) is a term used for systems that evaluate automatic tank gauge (ATG) measurements statistically over time. Rather than requiring an operator to take the tank out of normal service for every test, the system looks for suitable periods in the inventory data and produces a result when its method has enough valid information. The ATG, probe, software, configuration, and operating conditions all affect that process.

EPA describes continuous in-tank leak detection as an internal release-detection method and explains that some systems gather data during quiet intervals while a tank remains in service. CSLD terminology, status labels, and reports vary by manufacturer. Operators should use the evaluation and instructions for the specific equipment instead of assuming every product analyzes data or reports results in the same way.

Regulatory acceptance also depends on the method, equipment approval, tank system, and implementing agency. A feature named CSLD in a gauge or dashboard is not, by its name alone, evidence that the location has satisfied a release-detection requirement. Confirm the accepted method and required record with the agency that implements the UST rules for the location. This guide is an operational explanation, not legal advice.

What data does a statistical test need?

A statistical method needs measurements that meet the conditions defined by the evaluated system. Depending on the equipment, it may analyze product level, volume, temperature, time, and whether the tank was sufficiently quiet. The method decides which periods qualify; an operator should not manually select a convenient interval and present it as the equipment’s completed regulatory result.

Data quality begins at the tank. Probe condition, tank chart or configuration, product identification, clock settings, and communication continuity can affect the record that reaches a reporting system. Normal operations such as dispensing and deliveries may also interrupt otherwise useful periods. Good connectivity helps preserve received data, but it cannot repair an incorrect gauge configuration or create measurements that the ATG never produced.

Keep equipment service and configuration changes with the results they could affect. If a probe, tank mapping, or ATG setting changes, the reviewer should be able to tell when the change occurred and who verified the system afterward. That context prevents a later reader from treating unlike periods as if nothing changed.

Why can a result remain "pending"?

A statistical test needs usable measurement periods. Deliveries, dispensing activity, product-level conditions, temperature behavior, equipment status, communication gaps, or other activity may prevent the system from collecting enough qualifying data. The exact reasons and labels are equipment-specific, so consult the ATG report and manufacturer instructions rather than diagnosing from the word pending alone.

A pending result is not the same as a passing result. It usually means the method has not produced its completed outcome for the period being reviewed. It also is not automatically proof of a leak. Treat pending as an open evidence item: preserve the status, investigate the available context, and follow the escalation process defined for the location.

Repeated pending results deserve a cause-focused review. Simply waiting can leave the organization without the expected record, while manually relabeling the result hides the problem. Determine whether normal operations, equipment condition, configuration, or missing data is preventing completion, and involve the qualified service or compliance owner when the cause is not clear.

• Check the original ATG or approved report for status details and equipment messages.
• Review whether the tank has accumulated the qualifying data its method requires.
• Review recent deliveries, dispensing activity, alarms, and communication gaps.
• Do not relabel an incomplete or inconclusive result as a pass.
• Follow the ATG manufacturer’s instructions and the location’s approved escalation process.

How should common result labels be interpreted?

Read the result in the context of the specific equipment documentation. Labels such as pass, fail, pending, incomplete, or inconclusive may not have identical definitions across systems. A completed passing result means the evaluated method reached its passing outcome for that test; it is not a promise that a release can never exist or that every other UST obligation is satisfied.

A failed or abnormal result requires the response defined by applicable instructions and rules. An incomplete result means the expected determination was not produced. A communication gap only describes data transport unless the source equipment reports something more. Keeping these ideas separate helps operators avoid turning a network symptom into a regulatory conclusion.

When a dashboard summarizes a source result, retain access to the original record. The summary should not omit the test period, tank identity, method, or status qualifier that changes how the result is understood.

What should a CSLD record show?

Keep the original result produced by the approved equipment or reporting system. A useful record identifies the location, tank, product where relevant, test period, result, method or equipment, and any qualifier shown by the source. If the result needed follow-up, connect the service notes, investigation, additional testing, and final disposition without altering the original.

Use consistent tank identifiers across the ATG, TankActive, service records, and regulatory file. A result that cannot be matched confidently to a regulated tank is difficult to defend during a review. If a mapping is corrected, document what changed and preserve enough history to explain records created before the correction.

The implementing agency controls the required format and retention. Some inspectors may expect the original ATG output or an approved report rather than a custom summary. Confirm those expectations before replacing an established recordkeeping process.

• Location and tank identity that match the regulated system.
• Test period, source equipment or method, and the unmodified result.
• Any status qualifier, equipment message, or data limitation shown by the source.
• Reviewer, review date, and linked follow-up for open or abnormal items.
• Export or source record in the format required by the implementing agency.

How should operators respond to an abnormal result?

1. 1Preserve the original failed, missing, pending, or inconclusive result and mark it as an open item requiring review.
2. 2Check current ATG alarms, equipment messages, recent deliveries, dispensing activity, service work, and communication status.
3. 3Confirm that the result belongs to the intended location and tank and that no recent configuration change explains the discrepancy.
4. 4Contact the qualified service or compliance owner identified by the organization instead of improvising a test or status.
5. 5Follow the applicable investigation and reporting requirements if the information indicates a suspected release.
6. 6Document every follow-up action, supporting result, owner, and final disposition while retaining the original evidence.

How should teams prepare for a records review?

Before an internal or agency review, compare the expected CSLD evidence with the results actually on file for every applicable tank. Separate completed results from pending, failed, inconclusive, or missing items. For each exception, make the follow-up visible rather than burying it in an unrelated service ticket.

Ask a person who did not build the file to retrieve a tank’s result and explain the record chain. They should be able to identify the source, test period, status, reviewer, and resolution. If that takes personal knowledge or access to one employee’s inbox, improve the file before it is needed.

Do not create a passing narrative around incomplete evidence. A clear open item with documented ownership is more accurate than a summary that conceals uncertainty. The implementing agency or qualified adviser should resolve questions about whether the available evidence meets a regulatory requirement.

How can TankActive support CSLD review?

Where supported by the connected ATG and account configuration, TankActive can make received test and compliance records easier for authorized users to review across locations. It can help organize source information and reduce the effort required to find exceptions, but the connected ATG remains the source of the supported result.

TankActive does not approve a release-detection method, perform a regulatory determination, certify a location, or turn a pending, incomplete, inconclusive, or failed test into a passing result. A missing dashboard record should prompt a source and connection review, not an assumption that the test passed or failed.

Use the platform as one part of a controlled process: verify mappings, review received results, assign exceptions, retain required source evidence, and follow the implementing agency’s rules. That keeps the convenience of centralized visibility separate from the regulatory judgment the software does not make.