How To Evaluate An Oil And Gas Operator Using Public Records

An operator should not be judged by one number.

A permit count can show intent. A reported spud can show that drilling started. Production can show reported scale. County concentration can show where the operator is leaning. Source dates tell you whether the record is fresh enough to act on.

That is why a useful operator review keeps the record types separated. The goal is not to create one generic "activity score." The goal is to understand what the operator is doing, where the evidence comes from, and what follow-up should happen next.

This page is a practical workflow for evaluating an oil and gas operator using public records. It is built for mineral buyers, land teams, service companies, analysts, and data buyers who need a repeatable review path before they ask for current exports, alerts, maps, or API access.

Here is how to evaluate an oil and gas operator using public records such as drilling permits, reported spuds, production data, county activity, operator labels, and source-date checks.

Quick Reference

Start With The Operator Label

The first mistake in operator review is assuming every record under a familiar name belongs in one clean company bucket.

Public records often carry legacy labels, subsidiaries, acquired names, or source-specific operator names. That matters when an account team is comparing Devon and Coterra labels, XTO and Exxon labels, or other parent and subsidiary relationships.

Before you compare anything, answer three questions:

1. What exact operator label appears in the source?
2. Has that label been reviewed into a parent-company grouping, or is it still a source label?
3. Does your workflow need the filed label, the reviewed parent label, or both?

If that step is skipped, the rest of the operator review can look precise while still mixing unlike records.

What Each Record Proves And Does Not Prove

Each record family answers a different question.

This separation is the core rule. A permit-heavy operator can be interesting before production moves. A production-heavy operator can still have little current permit activity. Both can be true at the same time.

The Operator Review Workflow

The simplest useful workflow looks like this:

operator label -> county footprint -> permits -> reported spuds -> production -> source dates -> map/export/API handoff

1. Define The Question First

Do not start with a vague question like "is this operator good?"

Start with the actual use case:

• mineral acquisition screening
• service-company account targeting
• competitor monitoring
• county watchlist review
• internal API or export workflow

The right record order changes with the question. A service company may care more about current permits and reported spuds. A mineral buyer may care more about county concentration and production follow-through. A data team may care most about source dates and row-level export fields.

2. Check State And County Concentration

An operator review should narrow quickly into state and county context.

A Texas permit signal in Reeves or Midland means something different from a permit in a mature legacy county. A New Mexico signal in Lea or Eddy belongs in a different workflow from a San Juan gas-weighted review. County concentration can tell you whether an operator is building, defending, or shifting a position.

This is also where state differences matter. Permit structure, source clocks, production reporting, and field names vary by state. Texas and New Mexico are both core Permian states, but they should not be treated as one source system.

3. Review Permit Activity

Permits are one of the strongest early operator signals because they show where the company is still filing.

Check:

• recent permit count
• permit dates
• county concentration
• whether permits cluster around an existing position
• whether the operator appears in one county or several

The main question is simple: is this operator still putting new paper into the system where you care about it?

No permits in the recent window does not automatically mean the operator is inactive. It can mean the operator is drilling through inventory, shifting counties, pausing, or using a different timing window. But it is still a useful signal.

For the broader permit workflow, see How to track drilling permits by operator.

4. Check Reported Spud Follow-Through

Permits are intent. Reported spuds are stronger field evidence.

After the permit review, ask whether the operator is moving those rows into reported drilling starts. An operator with a large permit queue and little reported-spud follow-through may still be worth tracking, but the account story is different from an operator with both permits and fresh spuds.

This is also where source lag matters. Reported spuds may trail permit filings by days or weeks depending on the state and source family. A weak spud count is not always a weak operator. Sometimes it is only a source-clock issue.

For earlier-activity workflows, see Tracking Active Drilling Rigs Without Expensive GPS Feeds.

5. Review Production As Reported Scale, Not Current Activity

Production should answer a narrower question: what reported operating scale and history does this operator have?

Production is useful for:

• reported scale
• historical trend
• county-level operating footprint
• follow-through from earlier activity

Production is not the right record to use when you need same-week account movement. It is usually lagged and source-specific. That does not make it weak. It makes it better suited for history, scale, and comparison than for immediate field activity.

Use the state-specific guides when the workflow turns into production review:

• Texas oil and gas production data
• New Mexico oil and gas production data

6. Check Concentration Risk And Workflow Fit

Once permits, spuds, and production are on the table, ask whether the operator is concentrated enough to matter to your exact workflow.

Questions that usually change the decision:

• Is activity concentrated in one county or spread across several?
• Is the current signal permit-heavy, spud-heavy, or production-heavy?
• Does the operator appear under one clean label or several reviewed labels?
• Does the workflow need a public check, a saved watchlist, or a current export?

This step is where raw rankings become usable account workflows. A ranked operator list can tell you who is visible. It does not tell you which record created the signal or what should happen next.

For that transition, see Operator activity chase lists.

7. Finish With A Source-Date Check

Every operator review should end with one direct question: are these records current enough for the action I want to take?

The key source-date checks are:

• latest permit issue date
• latest reported spud date
• latest production month
• whether the page is a public sample or current app workflow

This is where many weak operator reviews fail. They compare a current permit table to a lagged production table and treat both as if they answer the same timing question.

For source-clock rules, use Oil and gas data source dates: permits, spuds and production.

Example Operator Review

Here is a simple masked example that shows how the workflow should be read.

An operator shows 18 recent permits in Reeves County, 7 reported spuds in the same review window, production reported through April 2026, and activity filed under two related operator labels.

That record set supports a specific conclusion: this is a permit-plus-spud signal with existing reported scale. It does not support a claim that production is currently accelerating, that every filed permit was drilled, or that both labels should be treated as one parent-company total without review.

This kind of example is enough to screen the operator correctly. The next step depends on the workflow: a county watchlist, a current export, a map review, or an API handoff.

Simple Operator Scorecard

If the workflow needs a quick decision screen, keep the scorecard narrow and record-aware.

This scorecard is a screening aid, not a final rank. It is only useful when the record types stay separated and the source dates stay visible.

The weights can change by use case. A service company may weight permit and spud activity more heavily. A mineral buyer may weight county concentration and production more heavily. A data buyer may weight source clarity more heavily than everything else.

When Public Review Stops Being Enough

Public records are enough for source checks, workflow framing, and early operator screening.

Public records stop being enough when you need:

• current operator rows instead of public samples
• unmasked well or operator detail
• county maps
• repeatable alerts
• reviewed parent-label handling
• exports for internal analysis
• API delivery into another system

That is the boundary between a public insight page and an app workflow. The public page should tell you what to ask for next, not pretend to be the full operating table.

Next Useful Pages

• Operator Intelligence for live operator-focused briefs and recurring account pages.
• State Watchlists for state-level permit, county, operator, and source-date monitoring.
• Coverage for state-by-state permit and production parity before you compare operators across states.
• Methodology for source handling, caveats, and workflow boundaries.
• Oil and gas data API when the operator review needs to move into a recurring integration.
• Request access when the workflow needs current operator rows, maps, exports, alerts, or API access.

Frequently Asked Questions

What is the first record I should check when evaluating an operator?

Start with the operator label and the exact question you need answered. After that, permits are usually the strongest early activity check, while production is better for reported scale and history.

Does a high permit count mean an operator is strong?

Not by itself. A high permit count can show intent and county focus, but it should be checked against reported spuds, later lifecycle records, production history, and source dates.

Should I compare operators across states with one scoring model?

Only if the state-source differences are visible. Permit systems, production clocks, and operator labels vary by state, so the comparison should keep those caveats attached.

Is production the best way to judge current operator activity?

No. Production is better for reported scale and history than for current activity. Current activity usually starts with permits, reported spuds, county movement, and source-date checks.

When should I move from a public page to app access?

Move to app access when the review needs current rows, unmasked detail, repeatable county or operator monitoring, exports, alerts, maps, or API delivery into another system.