Written for operators of record filing in 2+ states who are tired of rebuilding their monthly workflow from scratch. Not written for non-op partners, service companies, or midstream. If you’ve ever spent the last 3 days of the month hunting stock-change numbers across four spreadsheets, keep reading.
Every upstream oil and gas producer in the United States files monthly or periodic production reports with one or more state regulators and, for federal leases, with ONRR. The forms are different in every state. The deadlines are different. The data fields are different. The portals are different. What stays constant is the underlying obligation: operators of record must report volumes (oil, gas, water, disposal, injection) on a schedule the regulator sets, and penalties for late or incorrect filings are real.
This guide is a map. It covers the 12 jurisdictions that matter most for independent onshore producers: Texas, Oklahoma, North Dakota, California, New Mexico, Louisiana, Colorado, Pennsylvania, West Virginia, Wyoming, Kansas, and federal ONRR. For each one it names the form, the cadence, the portal, and the common filing mistakes. Each state has its own deep-dive page linked below.
Before we get into any of that, the admission nobody in this category leads with: software only handles the easy 60% of regulatory production reporting. It captures volumes, maintains allocation factors, and exports to the format each state wants. It does not replace the judgment calls, does not sign the attestation, does not pay the fees, and does not argue with a regulator when something goes sideways. Every vendor leaves that part out because admitting it up front doesn’t sell licenses. We’re starting there because it’s the part that determines whether the software actually saves you time or just rearranges the same work.
What Regulatory Production Reporting Actually Requires
Every state wants the same core information, structured differently.
- Operator identity. Operator number, lease or well identifier, reporting period.
- Volumes. Oil produced, gas produced (often split by sales, vented, flared, fuel), water produced (often split by disposal method), injection volumes, disposal volumes.
- Status codes. Which wells were active, shut-in, plugged, or temporarily abandoned during the period.
- Dispositions. Where the oil and gas went: tank to pipeline, sales, stock change, lease use.
- Attestation. A signature from a responsible party certifying that the data is true.
Every state takes those five buckets and wraps them in its own schema. Texas wants form PR with well API numbers and lease numbers. Oklahoma wants Form 300R with a specific worksheet structure. North Dakota wants Form 5 monthly. California wants the CalGEM (formerly DOGGR) OG filing. The underlying data is the same. The packaging is what changes.
Software helps with two parts of this job: capturing the raw data correctly (pumper-gauged volumes, run tickets, allocation splits) and formatting it for the specific form the state wants. The actual filing (uploading to the portal, signing the attestation, paying any fees) stays with the operator of record. No software replaces the operator’s signature on the regulator’s form.
For the upstream production capture that feeds these filings, see oil and gas production software. For the allocation math that produces per-well volumes when you have commingled tanks, see oil and gas production allocation software.
The 12 Jurisdictions That Matter
Texas: RRC Form PR
The Texas Railroad Commission Form PR (Monthly Production Report) is filed monthly for every lease producing oil or gas in Texas. It runs through the RRC Online System. Operators report per-well volumes, dispositions, and stock changes. Due around the last day of the month following the production month. Late filings trigger a reminder, then penalties if the pattern continues.
For the full filing walkthrough including portal access, common errors, and the specific data fields RRC requires, see Texas RRC PR form.
Oklahoma: OCC Form 300R
The Oklahoma Corporation Commission Form 300R (Monthly Production Report) is filed monthly. Oklahoma uses a slightly different lease and well numbering structure than Texas and the reporting workbook has its own quirks. See Oklahoma OCC Form 300R for the detailed walkthrough.
North Dakota: NDIC Form 5
The North Dakota Industrial Commission Department of Mineral Resources collects Form 5 monthly. Williston Basin operators deal with NDIC along with federal ONRR for wells on the reservation. See North Dakota NDIC Form 5 for the full state-specific guide.
California: CalGEM (formerly DOGGR)
California’s Geologic Energy Management Division (CalGEM, which replaced DOGGR in 2020) handles upstream regulation. Production reporting in California has unique requirements around steam injection reporting for heavy oil fields and stringent idle well rules. See California DOGGR reporting for the current CalGEM-era requirements.
New Mexico: OCD Form C-115
The New Mexico Oil Conservation Division Form C-115 is the monthly operator’s report. Permian-side operators often run Texas and New Mexico leases in parallel and have to file both forms every month with overlapping but non-identical data. See New Mexico OCD Form C-115.
Louisiana: SONRIS DM-1R
Louisiana’s Department of Natural Resources runs the SONRIS system. DM-1R is the monthly production reporting form. See Louisiana SONRIS DM-1R.
Colorado: COGCC (now ECMC) Form 7
Colorado’s Oil and Gas Conservation Commission was renamed the Energy and Carbon Management Commission (ECMC) in 2024. Form 7 is the monthly production report. ECMC has strict environmental reporting rules layered on top of production, particularly around venting and flaring. See Colorado COGCC Form 7.
Pennsylvania: DEP Production Reporting
Pennsylvania’s Department of Environmental Protection collects production reports semi-annually rather than monthly, which trips up operators used to the monthly cadence in other states. Marcellus and Utica operators file on the DEP’s schedule. See Pennsylvania DEP production reporting.
West Virginia: WR-39
West Virginia’s Department of Environmental Protection Office of Oil and Gas collects the WR-39 monthly production report. Appalachian operators filing in West Virginia alongside Pennsylvania and Ohio run into a three-state filing cadence that varies by state. See West Virginia WR-39.
Wyoming: Form 2
The Wyoming Oil and Gas Conservation Commission collects Form 2 (Monthly Oil and Gas Production Report). Wyoming operators frequently run both state and federal reporting in parallel because much of the production is on BLM or tribal land. See Wyoming Form 2.
Kansas: KCC OGOR
The Kansas Corporation Commission collects the Oil and Gas Operator Report (OGOR) monthly. Kansas has a large tail of low-volume wells and its reporting workflow reflects that. See Kansas OGOR.
Federal: ONRR (Office of Natural Resources Revenue)
ONRR is the federal counterpart for production on BLM, offshore, and tribal lands. Wyoming, Utah, New Mexico, Louisiana offshore, and many other jurisdictions involve federal leases where ONRR filings run parallel to state filings. See ONRR federal reporting for the federal-lease workflow.
The Common Filing Mistakes (Every State)
State forms differ but the failure patterns are universal. These come up across every regulator.
1. Per-well allocation errors on commingled leases. If five wells sell into a single tank battery, the state wants to see per-well volumes, not lease totals. Operators who use a fixed allocation factor from two years ago get flagged when the state runs a back-check against severance tax receipts. Keep allocation factors current and document how they are calculated.
2. Status code mismatches. A well that went shut-in on March 14 but is still coded as active on the March filing creates a discrepancy that auditors find easily. Update status codes in the same cadence as the field observations that trigger them.
3. Disposition coding. Gas vented versus gas flared versus gas used for fuel have different regulatory treatment in almost every state. Miscoding them is one of the fastest ways to draw an environmental complaint, particularly in Colorado, California, New Mexico, and Wyoming where venting and flaring rules are actively enforced.
4. Late filings on PA and other non-monthly states. Operators used to the monthly cadence in Texas and Oklahoma miss the Pennsylvania semi-annual cadence because it does not trigger a monthly habit. Same pattern happens with federal ONRR on some filings. Track cadence per jurisdiction, not per operator.
5. Stock change errors. The volume in tanks at month-end is part of the reconciliation. Operators who report lifted volumes without stock-adjusting produce reports that the regulator’s back-check will flag within a quarter.
6. Signature and attestation failures. Some states (Texas and Oklahoma among them) have strict requirements about who can sign the operator attestation. An office manager signing a form the state expects to be signed by the operator of record is a procedural violation even if the data is correct.
How Production Software Helps (and Where It Stops)
A modern production tool captures field data, maintains allocation factors, applies correct BS&W and temperature corrections, and exports the data in the format the state wants. What it does not do: file the form for you, pay the fees, or replace the operator-of-record signature.
Here is the honest break:
Software handles:
- Daily and monthly production capture (per-well volumes, dispositions, statuses)
- Allocation math for commingled tanks
- BS&W and temperature corrections
- State-specific export formats (CSV, XML, or direct portal submission formats)
- Historical filings archive (you should keep copies indefinitely; many operators do not, and live to regret it)
Operator handles:
- Portal login and submission
- Attestation signature
- Fee payment
- Any regulator correspondence that follows
- Amendments when errors surface
If a vendor tells you their software “automatically files” state reports, ask what that means precisely. In some cases it means the software uploads data through a state API and the operator still has to log in and sign. In other cases the vendor has a service where they submit on behalf of operators with power of attorney. Know which one you are buying.
Who This Guide Is Not For
Service companies. Your reporting obligations are different (SWD operators report disposal, completion companies report fluids and chemicals). This guide covers upstream production reporting by operators of record.
Pure non-op partners. You do not file production reports. The operator of record does. Your job is to read the operator’s statements and reconcile them against your interest.
Midstream and gathering companies. Your reporting obligations run through different systems (pipeline tariffs, FERC, gathering agreements). Not covered here.
Operators filing only in states not covered. Mississippi, Alabama, Ohio, Michigan, Alaska, and other oil and gas states have their own forms. The principles in this guide apply but the specific forms and portals differ. Contact the state regulator directly for those jurisdictions.
The Workflow a Well-Run Operator Actually Uses
For operators running in two to four states, the monthly filing workflow that works is a consistent sequence.
Day 1 to 3 after month close: pumpers finalize field data for the prior month. Any pending run tickets, tank strappings, or stock adjustments get closed out.
Day 4 to 6: office reviews allocation for commingled leases, runs BS&W and temperature corrections, and produces internal exception reports for any volumes that look off.
Day 7 to 10: generate state-specific exports from the production software, review the pre-filing reports, and walk through any exceptions with the field team before filing.
Day 11 to 15: file in each state on its schedule. Texas PR and Oklahoma 300R typically go first because of the late-month deadline pattern. Pennsylvania and other semi-annual filings slot in on their own cadence.
Day 16+: archive filings, update the master filing log, and close the month.
Operators who try to run this workflow off pumper paper and an office spreadsheet can do it, but only at small scale and only with one very disciplined person driving the process. Past roughly 30 wells or across more than two states, the workflow breaks without purpose-built software supporting it.
Frequently Asked Questions
Does production software actually file my state reports?
It prepares the data and exports it in the format the state accepts. Most operators still log into the state portal, review the submission, and sign. A few vendors offer a filing service where they submit on behalf of the operator. Ask explicitly which one the vendor provides before assuming.
What happens if I miss a filing deadline?
Each state has its own penalty structure. Texas sends a reminder, then escalates. Oklahoma has a progressive penalty schedule. California can refer persistent non-filers for enforcement. The common thread: first-time misses are forgiven if corrected promptly; repeat patterns get attention. Chronic non-filing can jeopardize operator certification.
Do I need different software for each state?
No. Most modern production tools cover the major producing states. What changes is the export format and the specific data fields required per state. A tool that only supports Texas and Oklahoma is limited. A tool that covers the 12 jurisdictions in this guide plus ONRR is sufficient for most independents.
How long should I keep filed reports?
Indefinitely. Many regulators have look-back periods of 3 to 7 years for audits. Tax authorities have their own look-back windows. Partners have claims that can surface years later. Storage is cheap. Regret is not.
What about amended filings?
Every state allows amendments. The process varies: Texas has a specific amendment workflow through the RRC portal, Oklahoma handles it through 300R amendments, and so on. File the amendment as soon as the error is identified. Regulators are generally forgiving of errors that are self-corrected; they are much less forgiving of errors discovered by the regulator.
The Short Answer
State production reporting is a recurring tax on operator attention. The best operators treat it as a monthly drill, built around a clean production capture and allocation workflow. The worst treat it as a fire drill at the end of every month, which is expensive in both staff time and penalty risk.
GreaseBook captures the data, maintains allocation factors, and exports to the 12 jurisdictions covered in this guide plus federal ONRR. It does not replace the operator’s role in the filing itself, but it eliminates the data-wrangling step that takes most of the month-end time. For state-specific details, follow the links above to each state’s deep dive.
Two minutes. No sales call, no pushy follow-up.
If GreaseBook lands and the fit turns out wrong inside year one, the 200% money-back guarantee refunds you twice the contract price. That is how confident we are in the pumper-adoption bar. If the data capture doesn’t collapse the filing-prep half of your month, you are owed your money back plus 100%.
P.S. This page is not for a non-op partner or a compliance firm filing on behalf of an operator. No hard feelings. If you are still deciding, the quiz gives you a straight answer in the time it takes to refill your coffee.