Oklahoma Pooling Order Docket Research 2026: Building a Reviewable Record

Oklahoma Pooling Order Docket Research 2026: Research question

What does an Oklahoma Corporation Commission pooling docket actually allow a land team to verify, and what does it leave for the title file, the operating agreement, or the authorized reviewer? Pooling research often begins with a search for an order number and ends with a saved PDF. That is a start, but it is not a reviewable record. A docket can contain an application, a notice, exhibits, a recommended order, an exception, a final order, and later amendments. Each item may describe the same tract differently or carry a different date. The research question is how to preserve that chain without turning one document into a conclusion that the whole chain cannot support.

This study describes a documentary method for Oklahoma pooling order research. It does not interpret a specific order, determine the rights of any interest owner, or offer a legal opinion. The method is designed for an administrative land research role that organizes public records for review by an authorized professional.

Scope and method

The review used the twelve public sources listed at the end of this article, checked on November 2, 2026. The method was source-bound and descriptive. For each docket observation, the file retained the case number, the order or application number, the applicant, the respondent or affected parties where shown, the tract identifiers, the exhibit references, the date on the document, the retrieval date, and the direct locator.

The study did not estimate how many Oklahoma pooling dockets exist, how complete any public index is, or how often orders are amended. It also did not assume that a document found under one search path is the only version of that document. Public systems can display current indexes, historical images, or both. The review records what the tested path returned rather than treating the path as a complete inventory.

Start with the case identity, not the order number

An order number is useful, but it is not always the best entry point. Begin with the case identity: the commission case number, the applicant, the county, the section, township, and range, and the general subject of the application. Then record the order number or numbers associated with the case. This order helps when a case has multiple orders, a corrected order, or an exhibit that was filed separately from the order text.

If the public index shows a case style but not a complete document set, record the case style exactly as displayed. Do not shorten a party name or normalize a tract description in the identity field. A later reviewer may need to search by the original text. Keep a separate normalized field for internal matching, and label it as a research aid rather than a source value.

Distinguish the application from the order

An application states what the applicant asked the commission to do. An order states what the commission decided. The two documents can use different tract lists, different exhibits, and different legal descriptions. A research file that saves only the order may miss the scope of the request, the notice list, or an exhibit that explains how the applicant assembled the tract.

Record the application date, the hearing date if shown, the order date, and the date the document was retrieved. If a recommended order or a proposed order appears in the file, label it as a distinct document type. Do not treat a recommended order as a final order unless the source itself shows that it became final. That distinction is basic, but it is easy to lose when files are combined into a single PDF.

Track order versions and corrections

Pooling dockets can produce more than one order version. A corrected order, an amended order, or a subsequent order may change a tract description, a party, or an exhibit. The research file should have a version field and a relationship field. The version field identifies the document as original, corrected, amended, or subsequent. The relationship field explains which earlier document it affects.

Do not overwrite an earlier version in the file. Keep each version with its own date and locator, then add a comparison note. The note should identify what changed and whether the change is visible in the public record. If the change is not visible, say so. A reviewer who needs to know which version controls must make that determination from the record and the applicable rules, not from a research assumption.

Capture tract descriptions verbatim

Tract descriptions are the heart of many pooling reviews. Capture the description exactly as it appears in the application, the exhibit, and the order. Include the section, township, range, acreage, and any lot or tract identifiers shown. If the document refers to an attached exhibit, record the exhibit identifier and whether the exhibit is present in the retrieved file.

A common error is to replace a legal description with a centroid or a map label. That substitution may help a GIS view, but it loses the language that the docket actually used. Keep the source description and add a separate geometry or map reference only when the project has an approved method for doing so. The two fields should never be confused.

Compare the docket tract list with the unit exhibit

A pooling order may rely on an exhibit that lists tracts, owners, or both. The order text may summarize the exhibit rather than reproduce it. If the exhibit is available, compare the tract list in the exhibit with the list in the order. Record whether the lists match, whether one is a subset of the other, or whether the comparison cannot be completed because an exhibit is missing.

This comparison is not a substitute for a title examination. It is a check on the internal consistency of the docket packet. A mismatch may be a drafting difference, a later correction, or a missing page. The research file should describe the mismatch and the next document needed, not guess which list is correct.

Record notice and party information carefully

A docket may include a notice list, a certificate of service, or a party schedule. These records can help a reviewer understand who was identified in the proceeding. They do not necessarily prove that every owner received notice, that the list is complete, or that a party's interest is correctly stated. Record the document type and the date, and avoid converting a mailing list into an ownership conclusion.

If the public record includes addresses or contact details, collect only what the review requires and follow the project's privacy policy. A land research file should not become an uncontrolled copy of personal information. Point to the controlled source when the detail is needed for an authorized purpose.

Keep the legal framework separate from the file facts

Oklahoma's pooling framework is grounded in statute and in the commission's conservation rules. The public sources listed below include the Oklahoma statutes and the relevant administrative code chapter. Those sources provide context for why a docket exists and what kind of record the commission maintains. They do not answer a specific title question, and a research note should not quote a rule as if it resolved a fact in the file.

Use a separate field for the legal or regulatory question. For example, a reviewer may need to know whether a particular order affects a tract, whether a later order supersedes an earlier exhibit, or whether a party's interest is pooled. Those are questions for the authorized reviewer. The research file can supply the documents and the chronology. It should not supply a legal conclusion that the sources do not contain.

Build a chronology that shows gaps

A chronology is more useful than a folder list. Put the application, notice, exhibits, orders, and amendments in date order. Add a column for the document type and a column for the open question. Where a date is missing, mark it as missing rather than inferring it from the neighboring document. Where a document is referenced but not retrieved, add a row for the missing item.

The chronology should distinguish filing dates from decision dates and retrieval dates. A document filed in March may describe a hearing held in April and an order issued in May. A single "date" field hides that sequence. The chronology makes the sequence visible and helps a reviewer see where the record is incomplete.

Use status labels that do not overclaim

A workable status model for docket research is: located, retrieved, indexed, compared, question routed, and closed. "Indexed" means the key fields and locators are recorded. "Compared" means the tract and party fields have been checked against the related documents in the packet. "Question routed" means a specific issue has been sent to the authorized reviewer with the supporting locators.

Avoid labels such as "valid," "approved," or "clear" unless the project defines them narrowly and the authorized reviewer owns the decision. A docket packet can be complete for research purposes and still leave the legal question open. The status should describe the research step, not the merits.

Design the handoff around the open question

A good handoff starts with the question the reviewer must answer. Then it lists the documents that bear on the question, the exact fields, and the conflicts. Attach only what policy allows, and point to the controlled file for the full packet. If the packet includes a summary, label it as a summary and keep the verbatim fields in an appendix or linked table.

The reviewer should not have to reconstruct the search. Include the case number, the search path, the retrieval date, and the list of documents reviewed. If a search returned no result for an expected document, include that fact and the query used. A clean handoff is not one that hides uncertainty; it is one that makes uncertainty easy to examine.

Quality sampling for docket files

Sample completed dockets across document types and reviewers. Check whether the application and order are both present, whether the tract descriptions were captured verbatim, whether the exhibit references resolve, and whether the chronology distinguishes filing and decision dates. Also check whether the same tract mismatch was routed to the same role in different files.

Record the sample date, the docket numbers reviewed, the defects, and the correction. If reviewers consistently miss exhibits, change the intake checklist or the retrieval order. If the public system often returns incomplete images, add a verification step before the file is marked indexed. The sample should improve the process, not just produce a score.

Limits of the evidence

The public sources used here describe the commission's oil and gas programs, public data paths, forms, and the statutory and regulatory framework. They do not prove that a particular docket packet is complete, that a notice was effective, that a tract description is correct, or that an order has a particular legal effect. They also do not establish ownership, leasehold title, unit participation, or royalty entitlement.

A pooling docket research file is valuable because it preserves the chain of public documents and the questions that remain. It is not a title opinion and should not be presented as one. The authorized land professional, attorney, or client representative must decide what the record means for the project.

Data sources and methodology

This study evaluates Oklahoma pooling order docket research through the public sources listed below. Each observation retains its publisher, case or document identifier, original date label, direct locator, and access date. Comparisons are documentary and descriptive. The study does not estimate missing records, infer legal effect, or extend a source beyond its stated coverage.

Frequently asked questions

Is a pooling order the same as a lease?

No. A pooling order is a commission document. A lease is a contract between parties. They can affect the same tract, but they are different records and should be kept in separate source categories.

Can a public docket search confirm all interest owners?

It can show the parties and notices that appear in the public record. It does not by itself establish complete ownership or the correctness of an ownership schedule. Those questions require the underlying title and conveyance records.

What is the most important field in the research file?

The direct locator for each document, paired with the date and document type. Without a locator, a later reviewer cannot reproduce the search or verify the quoted description.

If your team needs help organizing Oklahoma regulatory dockets for review, Book a free consultation.

Sources

• Oklahoma Corporation Commission, Oil and Gas - Oklahoma oil and gas division programs and resources; accessed November 2, 2026.
• Oklahoma Corporation Commission, Oil and Gas Data - Public oil and gas data entry points; accessed November 2, 2026.
• Oklahoma Corporation Commission, OGCD Forms - Oil and Gas Conservation Division forms; accessed November 2, 2026.
• Oklahoma Corporation Commission, Database Search and Imaged Documents - Public search paths for commission records and images; accessed November 2, 2026.
• Oklahoma Corporation Commission, Well Status Definition - Commission explanation of well status terms; accessed November 2, 2026.
• Oklahoma Corporation Commission, OGIMS - Oil and gas information management system overview; accessed November 2, 2026.
• Oklahoma Corporation Commission, County Table - County-level oil and gas reference table; accessed November 2, 2026.
• Oklahoma Corporation Commission, GIS Data and Maps - Mapping and spatial data resources; accessed November 2, 2026.
• Oklahoma Corporation Commission, Annual Reports - Division annual reports and program context; accessed November 2, 2026.
• Oklahoma Corporation Commission, Oil and Gas Optional Procedure - Administrative procedure context for oil and gas cases; accessed November 2, 2026.
• Oklahoma Administrative Code, Title 165, Chapter 10 - Oklahoma oil and gas conservation rules; accessed November 2, 2026.
• Oklahoma Statutes, Title 52 - Oklahoma statutes concerning oil and gas; accessed November 2, 2026.