Every barrel of oil brought to surface comes with water, and often a great deal more water than oil. A produced water disposition report is the accounting that says where all of that water went. It starts from the volume generated across a lease or facility and then follows each barrel to its fate: injected into a disposal well, recycled for completions, hauled offsite by truck, or transferred to another party. Regulators have grown steadily more interested in this accounting because produced water is both a liability and, increasingly, a reused resource, and the report is how an operator proves the water it created is fully and legitimately accounted for.
Produced water disposition report in one line: A produced water disposition report accounts for the volume of produced water generated over a period and documents its disposition, meaning where each barrel ended up: injected into a disposal or enhanced-recovery well, recycled or reused, hauled offsite, or transferred to another operator. Its purpose is to show that a water balance closes, with generation matching disposition, and to give regulators a defensible trail for water they scrutinize for both environmental and volumetric integrity. It draws on tank measurements, flow meters, and hauling tickets to reconcile the two sides.
The report has two sides that must agree. On the generation side is the total volume of produced water that came out of the ground over the reporting period, measured or estimated at the point it was separated from oil and gas. On the disposition side is the sum of everywhere that water went. The named destinations typically include injection into a permitted saltwater disposal well, recycling or reuse for hydraulic fracturing and other completions, hauling by truck to a third-party facility, and transfer or sale to another operator. A barrel has to land in exactly one of these categories, and the categories together have to add up to the generation.
The requirement that has been tightening is that this water balance actually closes. It is not enough to report that some water was injected and some was hauled; the total disposed, injected, recycled, and transferred is expected to reconcile against the total generated, within a reasonable measurement tolerance. A large unexplained gap between the two sides is precisely what draws regulatory attention, because it can suggest unpermitted disposal, unmetered discharge, or simply sloppy accounting that undermines every other number the operator reports. Closing the balance is the whole point of the exercise.
The reason regulators increasingly scrutinize this is that produced water sits at the intersection of environmental risk and volumetric honesty. Water that cannot be accounted for is water that might have been disposed of somewhere it should not have been. As water recycling for completions has grown, agencies also want to track reuse accurately, both to credit legitimate recycling and to make sure recycled volumes are not double-counted or used to paper over a shortfall. The disposition report is the instrument that forces an operator to put a number on every fate and make them sum to the whole.
Three kinds of field data drive the report, and each maps to a part of the balance. Tank levels tell you how much water is sitting in storage at the start and end of the period, which is essential because water in a tank is neither generated fresh nor yet disposed; it is inventory, and ignoring the change in inventory is a common way for a balance to appear not to close when it actually does. Flow meters on injection lines and transfer lines measure the volumes moving to their destinations continuously, and hauling tickets or manifests document each truckload that left the site, with a volume and a receiving facility.
Reconciling these sources is where the real work lives, because they are recorded in different ways and at different cadences. A disposal well flow meter produces a continuous, high-resolution record; a hauling manifest is a discrete event captured on a ticket, sometimes paper, when a truck loads; a tank level is a snapshot that changes constantly as water comes in and trucks or pumps take it out. Building a defensible disposition report means bringing all three onto the same timeline and the same units, then checking that generation minus the change in tank inventory equals the sum of the metered and ticketed dispositions. When those figures disagree, the gap is a signal that a meter is off, a ticket is missing, or a tank reading is stale.
This is exactly the kind of reconciliation that punishes manual, intermittent data collection. If tank levels are gauged by hand once a shift, injection volumes are read off a meter periodically, and hauling tickets pile up in a truck cab, the person assembling the monthly report is stitching together sparse and inconsistent records, and any gap is impossible to attribute. The more continuous and timestamped each source is, the more the balance can be trusted, and the faster a discrepancy can be traced to its cause rather than written off as noise.
A monitoring platform that already watches disposal wells and tank batteries carries most of the disposition report's raw material. Continuous flow measurement on injection and transfer lines gives an exact metered volume for the injected and transferred categories, and continuous tank level trends give the change in inventory over the period without anyone gauging by hand. When those signals stream into a cloud SCADA system such as Merobix, the injected, transferred, and inventory-change figures are available as historized data rather than gathered readings, which removes a large source of the error that makes balances fail to close.
The category that resists automation is hauling, because a truck leaving the lease is a physical event that a flow meter does not always see. This is where digitizing the hauling ticket matters. When each load is captured electronically, with a volume, a timestamp, and a receiving facility, the hauled category can be reconciled against the drop in tank level that the SCADA history recorded at the same time. A truck that supposedly took two hundred barrels should correspond to a two-hundred-barrel fall in the tank; when the digitized ticket and the trended tank level disagree, the operator has caught either a mis-measured load or a metering problem, which is the reconciliation regulators want to see performed rather than assumed.
The combined effect is a water balance that closes with evidence behind every line. Continuous SCADA data covers generation-adjacent measurement, tank inventory, and metered disposition, while digitized tickets cover the trucked volumes, and the two are cross-checked against each other on a shared timeline. When an agency questions the report, the operator can show the metered history and the ticket record side by side rather than defending a hand-assembled spreadsheet. As scrutiny of produced water grows, that ability to close the balance with traceable field data, rather than to merely assert that it closes, is what separates a defensible report from a vulnerable one.
It means the water generated over the period equals the sum of everywhere it went, accounting for the change in tank inventory. Generation minus the increase in stored water should equal injected plus recycled plus hauled plus transferred volumes, within measurement tolerance. A large unexplained gap between the two sides is what draws regulatory scrutiny, because it can imply unpermitted disposal or simply unreliable measurement.
Because trucked water is a disposition category that continuous flow meters usually do not capture, since a truck leaving the lease is a discrete physical event. Each hauling ticket documents a load volume and its receiving facility, which lets the hauled category be reconciled against the corresponding drop in tank level. Without the tickets, the trucked barrels are unaccounted for and the water balance cannot close.
Produced water sits at the intersection of environmental risk and volumetric honesty. Water that cannot be accounted for might have been disposed of improperly, and unmetered discharge is an environmental concern. As recycling for completions has grown, agencies also want accurate tracking so legitimate reuse is credited and recycled volumes are not double-counted to hide a shortfall, which is why the disposition report is expected to reconcile fully.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.