Skip to content
Editorial title card for Saltwater Disposal Well File Index
Tools WorkflowsPublished6 min readReviewed October 22, 2026

Saltwater Disposal Well File Index

A practical saltwater disposal well file index for land and operations teams that need traceable permits, land agreements, and well records.

Table of Contents

A saltwater disposal well file is easy to accumulate and hard to use. The permit, the surface agreement, the injection reports, the inspection notes, and the plugging correspondence arrive from different people and land in different folders. When a regulator, an auditor, or a purchaser asks a simple question, the team cannot tell which document is current.

This guide describes a file index for saltwater disposal wells. It is an administrative control. It does not interpret a permit, determine ownership, approve an injection, or replace review by engineering, environmental, legal, or regulatory specialists.

Saltwater Disposal Well File Index: what it covers

The index should cover the land rights, the regulatory authorization, the well construction and operation records, and the closure record. Those are different evidence chains, even when they refer to the same well.

A useful index has sections for:

  • Well identity: name, API number or state identifier, location, operator, and status.
  • Land rights: surface use agreement, lease, easement, access, and payment obligations.
  • Regulatory: injection or disposal permit, conditions, amendments, renewals, and correspondence.
  • Construction: drilling, completion, casing, cement, and mechanical integrity test records.
  • Operations: injection volumes, pressures, monitoring, inspections, and incident reports.
  • Closure: plugging plan, plugging report, site restoration, and final inspection.

The index should show the document title, date, version, source, storage location, and the person who verified it. A folder named "permits" is not an index.

Separate the land right from the permit

The surface agreement and the injection permit answer different questions. The agreement establishes the right to use the surface and may include payment, restoration, and indemnity terms. The permit authorizes the injection activity and imposes conditions. A file that has one without the other is incomplete for most operational decisions.

Record the grantor, grantee, tract, term, payment terms, and renewal or termination dates for the land right. Record the permit number, effective date, expiration date, authorized formation, volume limits, pressure limits, and special conditions for the regulatory authorization.

Link the two records by well identifier and tract. If the permit names a different operator or entity than the agreement, flag it. A name change or assignment may explain the difference, but the file should show the connecting document.

Index the operational evidence

Injection and disposal wells generate recurring records: monthly or annual reports, monitoring results, mechanical integrity tests, inspections, and incident reports. The index should link each record to the well, the permit, and the reporting period.

Use a simple table for the reporting chain:

Record Frequency Index field Common gap
Injection volume report Monthly or annual Period and volume Missing month
Pressure monitoring Permit-defined Reading and date No units recorded
Mechanical integrity test Permit-defined Test date and result Report not linked
Inspection Agency-defined Date and findings Corrective action open
Incident report As required Date and status No closure evidence

The table should reflect the actual permit conditions, not a generic list. If the permit requires a specific test or report, the index should use that name and frequency.

Track amendments and conditions

Permits change. An amendment may add a formation, change a volume limit, or impose a new monitoring requirement. The index should show the current permit version and the history of amendments. Do not replace the original with the amendment; keep both and mark which conditions are current.

Conditions deserve their own row. A condition may require a test by a date, a notice to a surface owner, or a report to the agency. Track the condition, the due date, the evidence, and the owner. A permit with an open condition is not fully implemented.

Plan for closure

A disposal well file is not complete without a closure path. Record the plugging plan, the approved plugging procedure, the plugging report, the site restoration evidence, and the final inspection. If the well is still active, the index should show the expected review date for the plugging plan and any financial assurance.

Access and retention matter after closure. Keep the file available for the period required by the client and the regulator. Record who can access it and when the retention review is due.

Measure index quality

Track the percentage of wells with a complete index, the number of missing permit conditions, the age of open corrective actions, the percentage of reports linked to a period, and the time to retrieve a requested document. Test retrieval with a real question, such as "show the current permit and the last mechanical integrity test."

A complete index is not the same as a compliant operation. The index shows where evidence is missing; the responsible specialists decide what it means.

A practical launch sequence

Start with one well or one field. Build the index sections and run a retrieval test. Note which documents are missing or duplicated. Use those gaps to set the minimum index for the next well.

Publish the naming convention and the document request process. Train the field and office contacts. Review open conditions and missing reports monthly. The EPA Underground Injection Control program page provides general context on injection well regulation, not a state-specific permit rule.

For teams that need help maintaining the index and the document requests, a defined title research support service can support the land-right side. The client keeps engineering, environmental, and regulatory decisions. The land file closing certificate checklist is a useful model for the final closeout review.

Frequently asked questions

Is the permit enough to prove the land right?

No. The permit authorizes the activity; the surface agreement or lease establishes the land right. Keep both.

Should superseded permits be removed?

No. Keep the history and mark the current version. Superseded conditions may still matter for past operations.

Who decides whether a well can be plugged?

The authorized engineering, environmental, and regulatory reviewers, following the applicable rules and the client's procedure.

Ready to Scale Your Landman Business?

Discuss a defined remote support scope for title research, lease administration, GIS coordination, or document work.

Quick Answers

How quickly can a remote landman professional start?▾
Timing depends on access, workflow definition, task complexity, and your review process. Confirm a written start plan during the free consultation.
How do I request a scoped quote?▾
Book a free consultation to review your task volume, access, review time, and required tools. Any quote is tied to that defined scope.
Are remote professionals a good fit for sensitive land data?▾
Sensitive work needs least privilege access, documented procedures, appropriate agreements, and client review. The required controls should be confirmed before access is granted.
What if I need to scale up or down?▾
Capacity changes depend on the written service agreement. Discuss expected workload changes before work begins so scope and review coverage remain clear.