WellOPS · Field Data Capture · Oilfield daily log

Oilfield daily log software that is faster than the grease book.

The pumper’s daily log is the oldest record in the field: tank gauges, production readings, runtime and downtime, per well, per shift. Oilfield daily log software replaces the paper logbook only if it is faster than the paper logbook. This page covers what the log holds, how Field Data Capture keeps it at the well instead of in the truck at shift end, and how the same entry reaches production accounting and the next morning’s plan without being retyped.

See Your Wells Ranked View a Sample 6 AM Plan

For pumpers, lease operators, field superintendents and production accountants

In plain terms

What is an oilfield daily log, and what does daily log software do?

An oilfield daily log is the record a lease operator or pumper keeps of each well’s production readings, tank gauges, runtime and downtime for a shift, well by well. Oilfield daily log software keeps that same log on a phone or tablet at each site instead of in a paper logbook and an end-of-day spreadsheet, so each reading is entered once, at the well, and rolls up into the daily production report and the production accounting system without being retyped. The log is also the field record behind statutory production reporting: in Texas, operators file Form PR monthly for all crude oil, casinghead gas, gas well gas and condensate produced, on or before the last day of the month following the month covered.

Source

Railroad Commission of Texas, Form PR Instructions, Monthly Production Report (Statewide Rules 27, 54 and 58(b)), filing required and when to file

What a daily log holds

Five entries, per well, per shift

A pumper daily report, a lease operator daily log, a gauge sheet and a grease book are four names for one record. Here is what it holds and how each line is captured in the app.

The daily log, line by line

EntryWhat it recordsHow it is captured

Tank gauges

The level in each tank at the visit, the gauge sheet line for that well and that shift.One-tap entry with a default from the previous reading; range check against the well’s own history on the device; reconciles against SCADA where a sensor exists.

One-tap entry with a default from the previous reading; range check against the well’s own history on the device; reconciles against SCADA where a sensor exists.

Production readings and well tests

Meter reads and structured well tests, per well.Structured entries that reconcile against SCADA automatically; a disagreement surfaces the same day as a work item.

Structured entries that reconcile against SCADA automatically; a disagreement surfaces the same day as a work item.

Runtime

How long the well ran in the period, and what it did against its expected rate.One-tap entries, with the well’s current rate shown against its own history on the site screen.

One-tap entries, with the well’s current rate shown against its own history on the site screen.

Downtime notes

When the well was down and why, in the pumper’s own words.Voice-to-text, which handles oil and gas vocabulary, with a photo for what a number cannot carry.

Voice-to-text, which handles oil and gas vocabulary, with a photo for what a number cannot carry.

Inspections and JSAs

The facility inspection, hazard observation or JSA done at the same site, on the same visit.The same app the pumper already has open, with photo evidence and signature capture where sign-off is required.

The same app the pumper already has open, with photo evidence and signature capture where sign-off is required.

What it replaces

How the app replaces the end-of-day spreadsheet

Paper grease books and hand-logged tank gauges are re-keyed at end of shift or never, and the errors compound until nobody trusts the data. Excel forms emailed from the field break the attachment chain, lose version control and have no offline support. The daily log in the app removes the second step entirely: there is no end of day entry, because the entry already happened at the well.

01
Entered once, at the well
The reading goes into the device while the pumper is standing at the tank, against the site it belongs to. There is no grease book to copy from later and no spreadsheet session in the truck at shift end. The module calls this zero re-keying, by design.
02
Checked at the moment of entry
Range checks against that well’s own history, required fields that cannot be skipped and unit guards all run on the device, offline. A transposed tank level is caught while the person who took it can still look at the tank, not at month-end as an allocation argument.
03
Rolled up, not retyped
The log rolls up automatically into the daily report the foreman actually reads, and the readings sync through DataHub into the production accounting system of record. The same entry feeds accounting, engineering and the ranked work plan: captured once, synced once, one data pipeline.

The design bar is speed. The grease book only disappears when the app is faster than the grease book, which is why the template leads with one-tap entries that default to yesterday's reading, voice-to-text for the note the pumper would otherwise scrawl, and gloves-on usability. A field team member can record readings and notes with their hands full, and the device carries the day without a signal: the mechanism for that is on the offline field data capture page.

The site screen the log is kept against. Synthetic demo data.

Where the log is kept

Against the well, not in a notebook.

The daily log is not a separate form the pumper fills in at the end of the route. It is recorded against the site screen: the same screen that says why the visit is on the plan, what the well is doing against its own history, priced per day, and what work is waiting there. A gauge entered here already knows which well it belongs to, which shift it belongs to, and what the well read last time, so the three ways a paper log goes wrong (the wrong well, the wrong day, a transposed number) are closed at the moment of entry rather than found at close.

The context goes with it. Photos of leaks, voice notes on equipment condition and a GPS stamp on every reading stay attached to the well, so a pattern across a dozen visits is something you can search for rather than something you have to remember.

Rendered from the synthetic field fixture · synthetic demo data · no customer screen

Where the log goes

One entry feeds production accounting and the 6 AM plan.

When the device returns to coverage, the log syncs through DataHub into the production accounting system of record by direct API integration, and the gauges reconcile against SCADA where sensors exist. Fields map to the production accounting schema, so the reading lands without re-entry, and a manual gauge that disagrees with the sensor surfaces the same shift as a work item instead of at month-end as an allocation argument. Taking manual gauge entry out of the month-end close is what removes the re-keying step from it entirely.

The same entry feeds the other direction. The ranked plan in Work Engine is only as good as the field data underneath it: a downtime note, a well test or a gauge recorded today is in the data the next morning's plan is built from. Captured once, synced once, one data pipeline into accounting, engineering and the ranked work plan.

The log is also the field record behind statutory reporting. In Texas, operators file Form PR monthly for all crude oil, casinghead gas, gas well gas and condensate produced, due on or before the last day of the month following the month covered (Railroad Commission of Texas, Form PR Instructions). How that report is assembled from production accounting is on the Texas RRC Form PR page; the daily log's job is to make sure the volume it draws on was entered once, at the well, and checked when it was.

Where this is running

The daily log at deployment scale.

5,000+

Wells in live deployments, where the daily log is kept on the crew device at the site.

Measured across 5,000+ wells in live deployments

15%

Free cash flow uplift on the same crew, from the ranked plan the clean field data feeds.

Deployment figure, top 25 private producer

Re-keying at shift end. The reading is entered once at the well and rolls up without anyone typing it again.

By design, capability statement

The module's other figures carry their own provenance on the module page. Nothing on this page is a new number.

Frequently asked

Oilfield daily log software, in the words people search for

What is oilfield daily log software?

Oilfield daily log software is the mobile replacement for the pumper’s paper logbook and end-of-day spreadsheet. It captures the per-well gauge sheets, production readings, runtime and downtime notes for each shift on a phone or tablet at the site, checks each entry as it is made, and rolls the log up into the daily production report and the production accounting system without anyone retyping it. In Field Data Capture the daily log is a standard template: one-tap entries with defaults from the previous reading, voice-to-text for notes, and automatic rollup into the daily report the foreman reads.

Is there a pumper daily report app that works offline?

Yes. Field Data Capture is offline-first by design, because most wellsites have no cellular service. The day’s sites, the daily log form and each well’s prior readings are cached on the device while it still has service, the pumper records the shift’s readings at each site with no connection, and the device syncs to the systems of record when it comes back in range. The mechanism, step by step, is on the offline field data capture page.

What does a lease operator daily log include?

Per well and per shift: the tank gauges, the production readings and well tests, the runtime, and the downtime notes that say when the well was down and why. In practice the same visit also produces the inspection, hazard observation or JSA for that site, so the daily log software has to capture those in the same app rather than a second one. Each entry carries a GPS and time stamp, and a photo or voice note can be attached where a number cannot carry what the pumper saw.

Can it replace our oilfield daily log?

Yes. The daily log workflow (per-well gauge sheets, production readings, runtime, downtime notes) is a standard template in Field Data Capture: one-tap entries with defaults from the previous reading, voice-to-text for notes, and automatic rollup into the daily report the foreman actually reads. The grease book only disappears when the app is faster than the grease book, which is the design bar.

How does the daily log reach production accounting?

Through DataHub, by direct API integration into the production accounting system of record (Enertia, Quorum, W Energy or Oildex). Fields map to the production accounting schema, gauges reconcile against SCADA where sensors exist, and the elimination of manual gauge entry takes the re-keying step out of month-end close entirely. The same reading also feeds the ranked daily work plan in Work Engine, which is only as good as the field data underneath it.

Does the daily log still have to be retyped for the monthly production report?

The volumes in the daily log land in production accounting through DataHub, and statutory production reporting draws on production accounting. In Texas, operators file Form PR monthly for all crude oil, casinghead gas, gas well gas and condensate produced, on or before the last day of the month following the month covered (Railroad Commission of Texas, Form PR Instructions). How the Form PR itself is assembled and reconciled is described on the Texas RRC Form PR reporting page; the daily log’s job is to get the reading into the system of record once, correctly, with a GPS and time stamp attached.

Can the daily log form be changed without a developer?

Yes. Admins build and version daily logs, tank gauges, well tests and inspection forms in a drag-and-drop editor, without code. Changes push to crews on the next app sync, with no app store rebuild cycle.

Are your best people working on your most valuable work today?

See your own gauge sheet in the app.

Bring your gauge sheet, your well test form and one inspection checklist. We build them in the editor with you and put them on a crew device in the first week, validated against each well's own history.

See Your Wells Ranked View a Sample 6 AM Plan

Continue the cluster