Every producing lease closes its day with the same ritual: someone tallies what each well made, what left in a truck, what sat in a tank, and what went wrong. That tally is the daily production report, sometimes called the morning report because it is what management reads first thing. It is a specific artifact - a per-well, per-day sheet - and it is the raw material that feeds allocation, accounting, and field decisions. This guide describes what the report contains, how it is assembled from field data, and how SCADA telemetry can populate it before a pumper ever opens a spreadsheet.
Daily Production Report in one line: A daily production report is the end-of-gas-day summary of what a lease produced: per-well oil, gas, and water volumes, run tickets for fluids that left the location, downtime and deferment codes, tank levels, and operator comments. It is the standard field artifact that rolls up into monthly accounting and allocation, and it can be filled in manually by a pumper or auto-populated from SCADA field telemetry.
A daily production report is organized well by well for a single gas day, the twenty-four-hour accounting window most operators run from a fixed hour each morning. For each well it captures the estimated or measured oil, gas, and water volumes; the results of any well test taken that day; and the status of the well - flowing, pumping, shut in, or down. Alongside the per-well lines sit the location totals: tank gauges or level readings, run tickets recording every barrel that a truck hauled away, water disposal volumes, and gas sales meter readings. A comments field carries the human detail that numbers alone cannot - a stuck pump, a paraffin cut, a lease road washed out by rain.
Traditionally the person who builds this report is the lease pumper or lease operator, who drives the route, gauges the tanks, records the meters, and writes down what each well did. On a manual route the report is literally the pumper's field ticket transcribed into a form and sent in. That makes it only as timely and accurate as the visit: a well that goes down the hour after the pumper leaves shows a full day of production it never made until the next day's gauge corrects it. The report is the boundary where field reality is converted into a number the office can use, which is exactly why its accuracy matters so much downstream.
There are two ways the numbers on a daily production report get there. The first is manual entry, where a person reads gauges and meters in the field and keys the values into a form. The second is SCADA auto-population, where field telemetry - tank level transmitters, meter run computers, flow computers, and RTUs at the wellsite - already streams the day's readings to a central system, and the report is generated by rolling up those streams at the gas-day boundary. In an auto-populated report the oil volume comes from level-change math on the tank transmitter, the gas volume from the electronic flow measurement device, and the water from the disposal meter, all without a pumper transcribing anything.
In practice most operations run a blend. Telemetry fills in the values that instruments measure cleanly and continuously - meter volumes, tank levels, run statuses - while the pumper still supplies the judgment calls and the context: whether a test is representative, why a well is down, what action was taken. The value of auto-population is not that it removes the pumper but that it removes the transcription step and its errors, and it makes the report available at the gas-day close rather than after a route is driven. A well that trips offline at 2 a.m. is already reflected as down in an auto-populated report; on a manual route that fact might not surface until the next visit.
The daily production report sits directly downstream of a SCADA system, which is the layer that already collects the telemetry the report needs. A cloud SCADA platform such as Merobix polls the wellsite continuously - tank levels, meter counts, tubing and casing pressures, run status - and holds that history, so producing the day's report becomes a query against data that already exists rather than a fresh data-collection effort. Because the platform knows the gas-day boundary, it can draw the exact twenty-four-hour slice and compute per-well volumes, downtime, and totals consistently every day.
This changes the report from a document someone builds into a document the system publishes. The pumper's role shifts from reading and transcribing to reviewing and annotating - confirming the auto-computed volumes, entering the reason a well was down, flagging a bad test. Because the telemetry is in the cloud, the same report is visible to the field, the office, and management at once, and a supervisor watching a live dashboard already sees the day forming before it is formally closed. The report remains the artifact accounting and allocation depend on; SCADA simply makes it faster, more accurate, and continuous rather than a once-a-day snapshot taken whenever the route happened to run.
The daily production report is the field artifact - a per-well, per-day record of volumes, run tickets, downtime, and comments produced at the gas-day close. Production accounting is the downstream office process that takes those daily numbers, applies allocation and pricing, reconciles them against sales and run tickets, and closes the month. The daily report is the raw input; accounting is what turns it into revenue and regulatory volumes.
Because it is typically the first thing management reads at the start of the workday - a summary of what the field did in the previous gas day. The gas day usually closes early in the morning, so by the time office staff arrive, the prior day's production, downtime, and any problems are ready to review. The name reflects when it is consumed, not when the production happened.
Yes. When a SCADA system already collects tank levels, meter volumes, and well status as continuous telemetry, the report can be auto-populated by rolling up that data at the gas-day boundary, with the pumper reviewing and adding context rather than keying in every number. This removes transcription errors and makes the report available at the gas-day close instead of after a route is driven.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.