Get the data

Free. You will be asked to confirm an email address before the files are built — that is the only gate, and it is there so we can tell you when a large export is ready.

Preview the first 100 rows

What this is

ODA037K. The Commission's docket: 223,000 cases with the full procedural calendar — filed, noticed, heard, decided, ordered, closed, reopened — plus the examiners, the witness and transcript counts, whether the case was protested, and whether it was granted or denied.

Two child files hang off it: the parties named in each docket and the subject lines describing what it was about. EZRRC publishes both separately.

This is where Rule 37 exceptions, allowable disputes, operator enforcement and rulemaking actually happen.

What you can do with it

Find every case an operator has been party to, measure how long the Commission takes from filing to decision, and count contested versus uncontested outcomes.

Follow a rulemaking from proposal to completion, and find the docket that set a field's rules.

Gotchas

The original layout stores every date as four separate two-digit fields — century, year, month, day. Upstream reassembles them into real dates, which is why the warehouse columns look nothing like the manual.

The docket number alone is not unique: a suffix and a division qualify it.

Many date columns are empty because that procedural step never happened. An empty decision date usually means the case is still open.

Record layout

57 columns. Byte positions are 1-based and come from the RRC record layout, so you can check our decoding against the original file yourself.

og_docket_master 48 columns

# Column Type Bytes RRC name Meaning Lookup
1 record_type text The two-byte record type from the original hierarchical file. Constant within a table; kept so a row can be traced back to its line in the source.
2 docket_number key join text The docket number. Join the name and subject tables on this. e.g. 79865
3 suffix text Docket suffix, e.g. R37 for a Rule 37 spacing exception, A37 for an amendment. e.g. R37
4 div text Division the docket sits with.
5 filed_date date Date the application was filed.
6 notice_date date Date notice was issued.
7 hearing_date date Date of the hearing.
8 decision_date date Date the proposal for decision was issued.
9 close_date date Date the application was closed.
10 order_date date Date the order was signed.
11 con_mfrh_date date Date of the consolidated motion for rehearing.
12 conference_date date Date of the conference.
13 admin_closed_date date Date the docket was administratively closed.
14 transcript_date date Date the transcript was produced.
15 pre_hearing_date date Date of the pre-hearing conference.
16 exceptions_date date Date exceptions were filed.
17 rep_pro_date date Date of the reply to the proposal for decision.
18 oral_argument_date date Date of oral argument.
19 motions_date date Date motions were filed.
20 rep_mot_date date Date of the reply to motions.
21 interim_order_date date Date an interim order was issued.
22 expiration_date date Date the order expires.
23 appl_letter_date date Date of the applicant letter.
24 reopen_hearing_date date Date the hearing was reopened.
25 hearing_closed_date date Date the hearing record closed.
26 rehearing_hours integer 202-204 Hours of rehearing time.
27 h2_type text Hydrogen sulphide classification, where the docket involves one.
28 reporter integer 227-229 Court reporter identifier.
29 lease_no1 join integer 230-235 Primary lease number the docket concerns.
30 lease_name1 text Primary lease name the docket concerns.
31 rulemakings_proposed integer 268-270 Count of rulemakings proposed.
32 rulemakings_completed integer 271-273 Count of rulemakings completed.
33 well1 text Primary well the docket concerns.
34 county join integer 318-320 County code the docket concerns.
35 mfrh_granted text Whether a motion for rehearing was granted.
36 exam2 integer 322-324 Secondary examiner identifier.
37 exam1 integer 325-327 Primary examiner identifier.
38 protested text Whether the application was protested.
39 active_inactive text Whether the docket is active.
40 granted_denied text Whether the application was granted or denied.
41 witnesses integer 334-336 Number of witnesses.
42 transcript_pages integer 337-340 Number of transcript pages.
43 hearing_hours integer 341-343 Hours of hearing time.
44 old_new_docket text Whether the docket predates the current numbering system.
45 referral_status_flag integer 345-347 Referral status.
46 hb1407_law_date date HB1407 law date.
47 hb1407_compliant_date date Date HB1407 compliance was reached.
48 ingested_at timestamptz When the upstream pipeline last wrote this row. Not an RRC field — it is EZRRC's provenance stamp, and it is what the freshness badge is measured against.

og_docket_name 4 columns

# Column Type Bytes RRC name Meaning Lookup
1 docket_number key join text The docket these parties belong to. Join to the docket master on it.
2 name text A party to the docket — applicant, operator, protestant or representative. One docket has several.
3 row_no key integer Sequence number of this row within its parent record. Part of the key.
4 ingested_at timestamptz When the upstream pipeline last wrote this row. Not an RRC field — it is EZRRC's provenance stamp, and it is what the freshness badge is measured against.

og_docket_subject 5 columns

# Column Type Bytes RRC name Meaning Lookup
1 docket_number key join text The docket this subject text belongs to. Join to the docket master on it.
2 line_no key text Line number within the docket's subject text. Order by it to rebuild the paragraph.
3 subject_text text One 50-character line of the docket's subject description.
4 subject_flags text Two bytes of subject flags.
5 ingested_at timestamptz When the upstream pipeline last wrote this row. Not an RRC field — it is EZRRC's provenance stamp, and it is what the freshness badge is measured against.

What this joins to

The Railroad Commission never states these keys anywhere in the files. They are the reason the data is hard to use, so here they are with the exact columns on both sides.

Oil and Gas Docket joins to Oil and Gas Docket Parties on Docket number — one row here matches many rows there.

was brought by and against

The organizations and people named in the case, one row each.

oil-and-gas-docket.docket_number = oil-and-gas-docket-parties.docket_number

Oil and Gas Docket joins to Oil and Gas Docket Subjects on Docket number — one row here matches many rows there.

was about

The subject text of the case, line-wrapped across several rows. The master record says when things happened; this says what happened.

oil-and-gas-docket.docket_number = oil-and-gas-docket-subjects.docket_number

Oil and Gas Docket joins to High Cost Gas on Docket number — one row here matches many rows there.

was granted in docket

The docket that granted the certification. The two files write the number differently — the certification file zero-pads to six digits and the docket file does not pad at all — so this join needs the leading zeros stripped first and is recorded here as documentation of the link rather than as a lookup that will match as-is.

high-cost-gas.docket_number = oil-and-gas-docket.docket_number

Where this comes from

Published by
Texas Railroad Commission — the original page
Original format
Fixed-width Columns are byte ranges with no separators, described only in a scanned record layout.
Update cadence
Updated once a month (Monthly. Available by the 27th.)
RRC download link
GoAnywhere MFT
Record layout manual
Our table
texas.og_docket_master

EZRRC is an independent mirror of public-domain data published by the Texas Railroad Commission. It is not affiliated with or endorsed by the RRC. For any legal or regulatory purpose, verify against the official RRC release.