Automating Production Reporting: A Practical Guide for Small Operators

Every month, the same routine: pull data from SCADA, cross-reference with tank gauges, calculate volumes, reconcile with sales tickets, generate state reports, update investors. For a small operator running 30-50 wells, this process can eat 40-60 hours every month.

That's essentially a full-time position just for production reporting. And for most small operators, it's being done by someone who should be doing something more valuable—a production engineer, an operations manager, or the owner themselves.

The enterprise solution is obvious: buy a production accounting system like Quorum, Enertia, or OGsys. But these platforms cost $30,000-100,000+ per year and require dedicated staff to manage. For a small operator, the math doesn't work.

Here's the good news: you can automate 60-80% of production reporting without enterprise software. It takes some upfront work, but the ongoing time savings are substantial. This guide shows you how.

What We're Actually Trying to Solve

Before we dive into solutions, let's be specific about the problem. Monthly production reporting typically involves:

The pain points are concentrated in steps 1-3: getting the data, making sure it reconciles, and doing the math. Once you have clean, reconciled numbers, the rest is relatively straightforward.

Step 1: Standardize Your Data Sources

Automation requires consistent inputs. The first step is getting your data sources standardized.

SCADA Data

If you have SCADA on your wells (and in 2026, you should on any well that justifies it economically), you already have continuous production data. The question is how to extract it.

Most SCADA providers offer data export functionality. Check with your vendor about:

• Scheduled exports: Can the system automatically export daily/weekly data to a file or FTP server?
• API access: Some providers offer REST APIs for direct data pulls (more useful if you have technical staff)
• Report templates: Can you configure standard export formats that match your accounting needs?

The goal: get your SCADA data flowing automatically to a central location in a consistent format. This eliminates manual data entry for daily production volumes.

Tank Gauges and Manual Readings

For wells without continuous measurement, you're relying on tank gauges. The old way: pumper writes it in a notebook, someone enters it in Excel at end of month.

The better way: mobile data collection. Give your pumpers tablets or smartphones with a simple form to enter gauge readings. The data goes directly to a cloud spreadsheet or database. No transcription, no delay.

Tools that work for this:

• Google Forms + Sheets: Free, simple, and most pumpers can figure it out
• Microsoft Forms + Excel: Same idea, Office 365 ecosystem
• Fieldbook apps: More oilfield-specific, but may cost $50-200/month

Sales Tickets and Run Statements

Sales data typically comes from your purchaser: run tickets for oil, statements from your gas gatherer. The format varies by purchaser, but most send some form of electronic statement.

The automation opportunity: set up a dedicated email inbox for sales statements, then use basic extraction to pull the numbers into your system. This can be as simple as a macro that parses a PDF, or as sophisticated as a document processing tool.

Step 2: Build a Central Data Model

Once your data sources are standardized, you need somewhere to bring it all together. For small operators, this doesn't need to be a database—a well-structured spreadsheet works fine.

The Production Master Spreadsheet

Create a monthly production workbook with the following structure:

• Tab 1 - Well Master: Static data (well name, API, lease name, working interest, net revenue interest, purchaser)
• Tab 2 - SCADA Import: Raw daily production from SCADA exports
• Tab 3 - Manual Gauges: Tank gauge readings from mobile collection
• Tab 4 - Sales Data: Volumes and values from purchaser statements
• Tab 5 - Reconciliation: Formulas that compare produced vs. sold, flag variances
• Tab 6 - Allocated Production: Net volumes by working interest owner
• Tab 7 - State Reports: Formatted output for regulatory filing

The key is building formulas that do the heavy lifting. Once the raw data is imported, the spreadsheet should automatically calculate daily production, monthly totals, variance flags, and allocated volumes.

Google Sheets vs. Excel

Both work. Google Sheets has the advantage of being cloud-native—your pumpers' mobile forms can write directly to it, and you can access it from anywhere. Excel is more powerful for complex calculations and has better formatting for printed reports.

Our recommendation: use Google Sheets for data collection and daily monitoring, then export to Excel monthly for the heavy reconciliation and final reporting.

Step 3: Automate the Reconciliation

Reconciling produced volumes against sales volumes is where people lose the most time. Every variance needs to be investigated and explained.

The automation approach: flag variances automatically, but only require human attention for material differences.

Build conditional formatting into your reconciliation tab that highlights variances by severity. For green wells, the spreadsheet can auto-populate an explanation ("within tolerance"). For yellow and red, you'll need to investigate—but now you're focusing attention where it matters.

Common variance causes that you can pre-program explanations for:

• Timing differences: Production measured daily, sales tickets cover different periods
• Stock changes: Oil in tanks at month-end vs. previous month
• Metering differences: SCADA vs. custody transfer meter reads differently
• Gas flaring/venting: Produced but not sold (should be tracked separately)

Step 4: Automate Regulatory Reports

State regulatory reports follow fixed formats. Once you have clean, reconciled production data, generating the reports should be mechanical.

Texas (RRC Form P-1)

The P-1 requires monthly production by lease, including oil, gas, and casinghead gas volumes. The RRC accepts electronic filing through their P-1 XML submission system.

Automation approach: build a report tab in your spreadsheet that formats data per the P-1 schema. If you're technical, write a script that generates the XML file directly. If not, third-party services like WolfePak offer P-1 generation as a standalone service (~$5-10/well/month).

New Mexico (Form C-115)

New Mexico's C-115 is similar in concept. The OCD accepts electronic submissions, and the format is straightforward. The same spreadsheet approach works.

Other States

Colorado (Form 7), North Dakota (Form 4), and other states have similar requirements. The principle is the same: standardized data in → formatted report out.

Step 5: Automate Internal Reporting

Once regulatory reporting is handled, internal reporting is actually easier—you're not constrained by external formats.

Management Dashboards

Most operators want a simple dashboard showing:

• Total production (current month, prior month, YTD)
• Production by well or lease (with trend)
• Revenue and expenses
• Key operational metrics (uptime, LOE, etc.)

Google Sheets and Excel both have decent charting capabilities. Google Looker Studio (free) can create more polished dashboards from Sheets data. Microsoft Power BI does the same for Excel.

The key: once your production master spreadsheet is updated, the dashboard should refresh automatically. No re-creating charts every month.

Investor Reports

If you have outside investors, they want consistent, professional-looking reports. Create a template once (in Word or Google Docs), then populate it from your production data.

Mail merge functionality can pull numbers directly from your spreadsheet into the report template. Update the data, regenerate the report—done.

The Time Savings Math

Let's quantify what this automation is worth.

That's 32 hours/month saved. At a fully-loaded cost of $75/hour for the person doing this work, you're saving $2,400/month or nearly $29,000/year. More importantly, you're freeing up that person to work on things that actually grow the business.

Implementation Roadmap

You don't have to do this all at once. Here's a phased approach:

When to Graduate to Real Software

The spreadsheet approach works well up to about 75-100 wells. Beyond that, the complexity starts to overwhelm manual processes, and the risk of errors increases.

Signs you've outgrown spreadsheets:

• Multiple people editing the same workbook (version control nightmares)
• Complex working interest structures that are hard to track
• Audit findings related to documentation
• Time spent maintaining the system exceeds time saved

At that point, production accounting software makes sense. The good news: by then, you'll have clean data processes and understand exactly what you need from the software. You'll make a better buying decision than if you'd started there.

The Bottom Line

Production reporting shouldn't consume 40+ hours every month. With some upfront investment in process design, you can automate the repetitive parts and focus human attention on exceptions and decisions.

The approach outlined here isn't fancy. It's spreadsheets, forms, and some basic automation. But it works, and it's within reach for any operator willing to invest a few weeks of effort.

Start with one workflow—data collection is usually the easiest win. Build from there. Every hour you automate away is an hour you get back for running the business.