Operations concept · Last updated July 28, 2026
What is deferred production, and how do you cut it?
In plain terms
What is deferred production in oil and gas?
Deferred production in oil and gas is production a well was physically capable of making but did not make, because of downtime, a restriction or underperformance that could have been corrected.
Deferred production, in two sentences
It is measured by estimating each well’s capability for the period, subtracting the actual metered volume, and attributing the gap to a cause such as a failed pump, a full tank, a compressor outage or a workover that waited. It is distinct from decline, which is the reservoir delivering less over time, and from curtailment, which is a decision not to produce.
It is not decline and it is not curtailment. It is barrels you were set up to sell, lost to a queue: the down well that waited on a truck, the underperformer nobody scored, the workover parked behind smaller jobs.
The definition, precisely
Deferred production is a queue problem, not a reservoir problem.
Every producing well has a capability: what it should deliver today given its reservoir, its lift system, and its facility constraints. Deferred production is the gap between that capability and what actually flowed, accumulated across every well, every day.
The causes are ordinary: a well down overnight that nobody visits until Thursday because Thursday is when the route comes through; a plunger-lift well cycling badly for two weeks; a tank sitting full with no haul scheduled; a workover queued behind three jobs worth a fraction of its value.
Two things make it different from decline. First, it is recoverable: the barrels come back when the right work happens sooner. Second, it is controllable with the crew you already have, because the fix is almost never more people. It is the same people, pointed at the highest-dollar problem first.
One terminology note, because it changes how the problem gets measured: the term is deferred production, not deferred downtime. Downtime is one cause among several. An operator who tracks only downtime is measuring the visible minority of the deferral bucket.
Why you cannot see it
Three places deferred production hides.
- Pattern 01
Aggregation
Monthly production accounting rolls every daily loss into one average. A well that lost three days waiting on a truck and a well that ran clean all month arrive on the same report as slightly different monthly totals. The deferral is real cash, but by the time it is visible it is a variance line, not a decision. - Pattern 02
Downtime accounting
Downtime reports count wells that were flagged down. They do not count the well that ran well below capability for two weeks because a choke drifted, a compressor starved it, or the plunger cycle went wrong. Underperformance that never trips a down flag is deferred production that never makes any report. - Pattern 03
Alarm fatigue
The signal usually existed. It sat in a SCADA alarm list with two hundred other alarms, ranked by severity color instead of by dollars. When every alarm looks the same, the crew works the loudest one, and the most expensive deferral waits behind a nuisance separator alarm.
Lift and deliverability
How artificial lift and well deliverability reduce deferred production
Each well carries a model of its own expected behavior this week, built from its decline, its lift type and its recent history. A flag is raised on departure from that model, so the engine keeps working as wells decline and nobody re-tunes limits by hand across thousands of wells.
Rod pumps wear, ESPs fail, gas lift valves drift, and the preventative maintenance that prevents the next failure competes with today’s fires for the same crews. Who does that work, in what order, and at what cost is where a lift program turns into produced barrels or into deferred ones. Your lift systems keep wells tuned. WorkSync keeps them running.
These sentences are from the Work Engine page, the artificial lift optimization page and the gas lift page, where each lift type is covered in full.
Each lift type degrades in its own signature. The engine watches the signature, not the limit.
Rod pump
Peak and minimum polished rod load, pump fillage, card shape, runtime and cycle counts, and motor current draw.
A worn traveling valve, a rod part starting, and chronic pump-off all move the pattern before they move the production number, and each one carries a different repair and a different crew.
ESP
Intake pressure trend, motor temperature drift, drive frequency and current, and vibration signature where the well is instrumented for it.
Bearing wear and impeller erosion show in the signature well ahead of the drive fault, which is the difference between a planned pull and an unplanned one.
Gas lift
Injection rate against target, casing and tubing pressure, valve response, and unloading behavior.
Valve drift reads as an injection efficiency trend rather than as an alarm, so it is priced on the barrels it is quietly costing rather than ignored because nothing tripped. An unstable gas-lift well underperforms by 10-25% of potential because the lift gas is spent on cycling instead of continuous production (illustrative industry figures).
Plunger and chemical
Arrival times, cycle counts, and shut-in behavior on plunger wells; injection rates, tank levels, and corrosion coupon trends on the chemical system.
Paraffin, scale, and corrosion enter the queue priced as the deferment they will cause, so they compete with active failures on the same ruler.

The dollars-per-day math
Price the queue and the priority argument ends.
Take one well. A 60 BOE per day well that goes down Friday night and waits for the Monday route defers roughly 150 barrels of oil equivalent. At an assumed $70 per barrel realization, that is about $10,500 of gross revenue pushed out of the quarter by a single weekend of queue position (illustrative worked example at a stated price assumption, not a measured figure). The well did nothing wrong. The schedule did.
Now scale it. On a 500-well field where 5% of capability is deferred at any given time, the deferral bucket runs in the thousands of dollars per day, every day, spread thin enough across wells and routes that no single loss ever forces a decision. That thin spread is exactly why deferred production survives: each individual deferral is too small to escalate, and the sum never appears on one screen.
Unless the software prices it. The morning brief below is what a priced deferral bucket looks like at the start of a shift: the day's exceptions scored in dollars, summed at the top, ranked underneath (synthetic demo data).
One well, one weekend
- Well capabilityOne well
- 60 BOE/d
- Weekend in the queueFriday night to the Monday route
- 2.5 days
- Deferred production
- 150 BOE
- Assumed realizationStated assumption, not a measured price
- $70/bbl
- Gross revenue pushed out of the quarter
- $10,500
Illustrative worked example · stated price assumption · not a measured figure
A priced morning: $34,214/d of deferred production priced and ranked before 6 AM, across 148 wells. Synthetic demo data, generated.
What recovering it is worth
Recovered deferred production is worth a 2 to 5% production uplift.
How the recovery happens
Every exception is priced in dollars per day. Work above visit economics is ranked and routed, biggest dollars first. Exceptions priced below visit economics are logged and watched instead of driven to, so truck hours stay on the deferrals that pay.
The mechanism, not a metric
The label matters. The 2 to 5% is a modeled figure: recovered deferral volume expressed against total field production, aligned to the published Alvarez and Marsal worked example rather than quoted from it. The measured deployment figures WorkSync publishes, including the 15% free cash flow uplift on the same crew, carry their measurement basis on the numbers page.
Want the math on your own footprint? The route economics calculator models annual dollars recovered from your well count, your deferral rate, and your route miles, modeled conservatively, with the result shown on-page.
Where WorkSync fits
Cutting deferral is a ranking problem. Ranking is what the engine does.
Deferred production shrinks when three things happen in order: every exception is caught early (the signal is scored the night it appears, not the week the accounting closes), every exception is priced (dollars at risk, not severity color), and the day is sequenced so the biggest dollars get worked first. An exception queue on its own delivers only the first of the three, which is why detection alone leaves the expensive deferrals waiting. Pump by priority is that loop, productized: WellOPS scores every well overnight on the data already in your SCADA, historian, and accounting systems, and puts a ranked, drivable plan in every truck cab by 6 AM. The most sophisticated prioritization engine in the field, pointed at the least visible line on your income statement.
The adoption path is deliberately short: read-only integration in about a week, the ranked plan in the truck within the 4-week stand-up, measured against your own pre-deployment baseline. Don't leave production on the table because the wrong work was done first.
Deferred production, common questions
What is deferred production in oil and gas?
Is deferred production the same as downtime?
How is deferred production measured?
How much is recovering deferred production worth?
Do I need new sensors or a SCADA upgrade to reduce deferred production?
What does WorkSync actually do about deferred production?
How does intelligent lift reduce deferred production?
How does well deliverability reduce deferred production?
How does a gas lift strategy reduce deferred production?
Are your best people working on your most valuable work today?
Price your own deferral bucket.
Four weeks from read-only integration to a ranked plan in the truck cab, measured against your own baseline.