UST testing, compliance and cleaning

UST testing, with the whole site in view.

Plan the visit, connect the forms to the right equipment and give the office a clear path to the report. Stratum keeps the testing job tied to the customer, site and history behind it.

From the site to the report

One job. The context behind every record.

Before the visit

Plan from the site record.

Bring the customer, equipment and configured scope into the job. Give the crew its assigned work and forms, with site history close at hand.

At the site

Record work against the right equipment.

Keep the tank, line, detector, probe or sensor connected to its form rows. Answers and supporting information stay with the work they describe.

Back in the office

Review the return in context.

See which record needs a correction and which equipment it concerns. Review the revised return before preparing the configured report packet.

A test result, a review decision and a finished report are separate parts of the job. Stratum keeps their meaning distinct.

Follow the complete Annual visit

Equipment, scope and forms

A tank is part of a connected system.

The record should reflect the relationships your crew sees on site.

Tanks connect to lines and probes. Leak detectors belong with their lines. Probes and sensors connect to the ATG. Our fictional Annual visit uses four distinct form types for three tanks and their connected equipment.

  • RP C-7

    Equipment context
    ATG and tank/probe records
    What it documents
    Automatic tank gauge operation inspection
  • RP C-8

    Equipment context
    Sensor location and its ATG connection
    What it documents
    Liquid sensor functionality testing
  • RP C-9

    Equipment context
    Leak detector and corresponding line
    What it documents
    Line leak detector performance
  • Line Tightness Form

    Equipment context
    The lines included in the assigned work
    What it documents
    A separate line tightness record

This is a sample configured scope. It is not an exhaustive annual compliance checklist or a statement that every form applies to every site. Exact form editions, methods and outputs need confirmation.

When a record needs a correction.

A sensor form comes back with an unclear location. The reviewer returns that record for clarification while the crew confirms which sump it belongs to.

Follow the review example
RP C-8 · Sensor #2Needs correction
Equipment location
Sump location awaiting clarification
Reviewer’s question
Identify which sump Sensor #2 belongs to before the report is prepared.
WO-104 final report
Not prepared
Illustrative review example. Clarifying a record does not change the test result or complete repair work.

Keep the cleaning visit with the tank record.

Review how your crew identifies the tank, records the work and hands supporting documents to the office.

Specialized cleaning requirements need a fit check against Stratum’s current site, job and form configuration. These are the records to review together:

Equipment and visit
The tank, site and work requested.
Work record
Observations, completed work and supporting documents.
Customer handoff
The report and any required disposal or service documentation.

Qualified crews remain responsible for the methods and safety procedures.

Ready for the next visit.

Retain the work that happened, alongside the requirements that come next.

Retained reports give the next crew context. Configured requirements identify upcoming work; the schedule records the visit your team actually books.

Authorized customers see the reports published to them. Internal source documents and working records are a separate part of the operation.

Check your starting scope.

Start with a normal job, a form and the report you deliver. Confirm the supported configuration and the work needed to set it up.

Stratum is software used by the company carrying out the work. Your team retains responsibility for testing, technical decisions and the records it delivers.

Questions from UST teams.

Can we use our own forms and reports?

Bring a representative form and finished report. We’ll compare the fields, equipment relationships and output with Stratum’s supported configuration, then make the setup work clear. A form name alone does not establish support for every edition or jurisdiction.

How do state and customer requirements fit?

Your team defines the requirements that apply to the work. Scopes, asset conditions, forms and output configuration need to reflect those decisions. Federal references are a starting point; applicable state and customer requirements still need review.

What about tank cleaning work?

Start with the equipment, the cleaning record and the report your customer needs. We’ll review that workflow against the current site, job and form capabilities. This page does not promise a complete cleaning package or replace the technical and safety procedures used by qualified crews.

Does an approved record mean the equipment passed?

No. The field result records what happened in the test. Office review checks the submitted record. A complete, reviewed record can document a failed test and work that still needs attention.

Bring your next UST workflow into focus.

Federal UST source guide

Different work. Different record requirements.

UST work combines inspection, testing, monitoring, and record requirements. One calendar interval or retention period is not enough.

Confirm the rules and equipment that apply with your implementing agency. The federal examples below are an informational source guide. Stratum’s workflow and coverage are separate from these regulatory requirements.

Start with 40 CFR Part 280 and the EPA directory of state UST programs. State programs can be broader or more stringent than the federal baseline.

Cathodic protection testing

Qualified testing within six months of installation and at least every three years, or another reasonable implementing-agency timeframe. Keep results of the last two tests.

Impressed-current protection

Check operation every 60 days. Keep the last three inspections. This is separate from the cathodic protection test.

Spill equipment and applicable sumps

Spill prevention equipment and containment sumps used for piping interstitial monitoring generally require liquid-tightness testing at least every three years. The rule provides an alternative for double-walled equipment with both walls' integrity periodically monitored at no less than walkthrough frequency. If that monitoring stops, test within 30 days. Testing records: three years; alternative-monitoring documentation: while that equipment is periodically monitored.

Overfill prevention

Inspect at least every three years for appropriate activation level and operation under the specified criteria. Keep inspection records three years.

Thirty-day walkthrough

Check spill prevention and release-detection equipment at least every 30 days under the listed approach. Spill equipment at a system receiving deliveries less frequently than every 30 days may instead be checked before each delivery. Comparable code-of-practice or agency-developed inspection alternatives also exist. Keep walkthrough records one year, including checked areas, condition, corrections, and applicable delivery evidence.

Annual walkthrough

Check containment sumps and handheld release-detection equipment annually under the listed approach. This is distinct from three-year testing of sumps used for piping interstitial monitoring. Walkthrough records: one year.

Release-detection equipment operation

At least annually test proper operation of applicable electronic/mechanical components using manufacturer, recognized code, or agency criteria. Relevant components include controllers, sensors, alarms, and line leak detectors. Keep these operation-test records three years.

Petroleum tank monitoring

Generally at least every 30 days. Tanks installed after April 11, 2016 use the interstitial-monitoring provision; older tanks have method options and specifically limited inventory/tightness or small-tank gauging exceptions. Do not label all tanks as requiring annual tightness testing.

Petroleum piping monitoring

For piping installed on/before April 11, 2016: pressurized lines require an automatic line leak detector plus annual tightness testing or monthly monitoring; suction lines require three-year tightness testing or monthly monitoring, with a qualifying safe-suction exception. Later-installed/replaced piping generally uses interstitial monitoring every 30 days, with a detector additionally required for pressurized lines and the specified suction exception retained. Method requirements and applicability matter.

Release-detection evidence

Routine sampling/testing/monitoring results generally at least one year or another reasonable agency timeframe; annual equipment-operation tests three years; tank tightness results under 280.43(c) until the next test. Performance documentation generally five years from installation. Method-specific assessment and maintenance documentation has separate rules. Do not collapse these into a universal three-year rule.

Operator training

Training content and evaluation depend on Class A, B, or C responsibilities. Newly designated A/B operators must meet training requirements within 30 days of assuming duties; C operators before assuming duties. Federal rules do not impose a blanket recurring annual refresher on every operator.

Retraining and operator records

A/B retraining generally within 30 days after an agency finding of noncompliance, with the annual-refresher and agency-waiver exceptions in the rule. Keep designated-operator lists and qualifying training/retraining evidence for as long as operators are designated.

Record availability

Section 280.34 identifies reporting/record categories and availability obligations; it does not replace their individual retention requirements with one period. Records generally remain at the UST site for immediate inspection or a readily available alternate location for provision on request.

Sources reviewed October 7, 2026. The linked official pages showed source currency dates ranging from September 18 to October 5, 2026 at review. Use the current official text and applicable agency requirements for decisions.