The comparison · Last updated August 20, 2026

Pump by Exception vs Pump by Priority.Two operating models, one question apart.

Both terms live on the same lineage: management by exception, the philosophy that human attention should go only to deviations that matter. Pump by exception was the oilfield’s first implementation: detect the deviation, alarm, respond. Pump by priority is the next step: price the deviation, rank the field, route the crew, learn from the outcome.
See Your Wells RankedView a Sample 6 AM Plan

Pump by exception asks

Which wells have a problem?

Pump by priority asks

Which problem is worth solving first?

This is why WellOPS is the world’s most advanced Pump by Exception platform: the advancement is that it does not stop at the exception. It goes past flagging to pricing and routing, which is the whole difference this page walks through.

The same morning, twice

47 exceptions. One first truck.

A field team member opens the morning screen to 47 exceptions. An exception system can name every one of them: Well 104, line pressure low. Well 217, pump issue. Well 388, tank level rising. What the list does not carry is an order. Someone still ranks those 47, usually in the cab, usually by memory and windshield order.

Take an illustrative morning: WellOPS answers with the ranked version of it. Well 217 goes first: $8,400 per day at risk, 42 minutes away, a qualified crew on shift. Well 104 goes second at $3,100 per day. Well 388 already has a haul scheduled and holds. The other 44 are priced and sequenced, or parked because the value at stake does not pay for the drive. The ranking arrives with its reasoning, so it can be checked rather than believed.

What pump by exception hands the field
47 rows
  • FlagWell 104: line pressure low
  • FlagWell 217: pump issue flagged
  • FlagWell 388: tank level rising
  • Flagand 44 more, in the order they arrived

Every exception named, every row the same weight. The ranking still happens in someone’s head. Illustrative data.

What WellOPS hands the field
6:00 AM
TierThe stopAt risk a day
P1
Well 217: pump issue, 42 min away, qualified crew on shift
$8.4k/d
P2
Well 104: line pressure low
$3.1k/d
P3
Well 388: tank level rising, haul already scheduled
$0.6k/d
P3
44 more: priced, sequenced, or parked below visit economics
<$0.5k/d

The same 47 exceptions: priced in $/day, sequenced by dollars, drive time, and crew, staffed before the first truck rolls. Illustrative data.

The exception is not the decision. It is the input to the decision.

Side by side

Detection vs valuation. Alarms vs the ranked plan. Reacting vs operating.

The two models share the exception discipline. They part ways at what happens after the deviation is found.
The question it asksWhich wells have a problem?Which problem is worth solving first?
What it doesDetection: flags deviations from normal operating parameters.Valuation: prices every deviation and every open task in dollars, then ranks the whole field.
What the field receivesAn alarm list. Somebody still decides what it is worth and who goes first.A ranked plan: a constraint-sequenced route in the truck cab by 6 AM, priced per stop.
Economic contextNone. A stripper-well threshold trip and a high-value well drifting off forecast arrive with equal urgency.Every exception carries production at risk, working interest, lifting cost, and price. The 10x spread between two deviations is visible.
RoutingManual or proximity-based. The exception list is not a drivable day.Constraint-aware: geography, crew qualifications, hours of service, equipment on the truck.
LearningStatic thresholds. As wrong next year as the day someone set them.Closed loop: what the crew found today retrains tomorrow’s ranking.
Operating postureReacting: the day is built from whatever alarmed.Operating: the day is built from what pays, and the alarms are one input among many.

The industry evolution

Four generations of field operations.

Each generation answered the previous one's binding constraint. The exception generation moved the industry forward, and the industry is now one step past it.
  1. Generation 01

    Fixed Routes

    Visit every well.Every well on a calendar cadence. Complete coverage, bought with windshield time: most visits confirmed that nothing was wrong.
  2. Generation 02

    Pump by Exception

    Visit wells when something changes.SCADA put surveillance on every well and broke the fixed-cadence assumption. Real progress: fewer blind miles, faster response to real problems. The list still arrives unranked.
  3. Generation 03

    Pump by Priority

    Visit wells when the economics justify it.Every exception priced in dollars per day, ranked against every open job in the field, and sequenced into a drivable day. This is the generation WellOPS implements.
  4. Generation 04

    Intelligent Operations

    Continuously decide what the operation should do next.The loop runs continuously: Flag. Price. Rank. Route. Execute. Learn. The direction the industry is heading, and pump by priority is the step that makes it reachable.

Partial credit, specific failure modes

What pump by exception got right, and where a decade of attempts struggled.

Pump by exception deserves an honest accounting. It broke the assumption that every well needs a visit on a fixed cadence, it put SCADA data to work as an operating signal rather than a record, and wherever alarm discipline held, it genuinely reduced windshield time. Operators who adopted it were right to.

Where it struggled, three failure modes repeat almost universally. Alarm fatigue: static thresholds, set conservatively and rarely revisited, produce hundreds of exceptions a day with no dedupe and no ranking. The field learns that most alarms are noise, which means the field also learns to ignore the one that is not. No economic context: a threshold trip on a low-rate well and a high-value well drifting off forecast arrive on the same list with the same urgency, so crews work the list in whatever order the windshield suggests, and the deferred-production numbers do not move. No routing and no loop: an exception list is not a drivable day, and whatever the pumper found at the well never flows back into the logic.

Operators who lived through this era are right to be skeptical of the phrase. The failure was not the principle. It was an implementation that stopped at detection. That distinction is exactly why the next generation exists, and why WellOPS is the world’s most advanced Pump by Exception platform: it finishes what the exception era started.

The difference, on screen

An alarm queue is a list. This is a ranked plan.

The day's site list ranked by value, the highest-ranked open task expanded with its reasoning, and the route on the map beside it. Detection is in there. So is everything detection alone leaves out.
WellOPS ranked work plan: the day's site list with the highest-ranked open task expanded beside the live route map

Every stop priced, sequenced, and explained, before the first truck rolls. The same plan, typeset, is the ranked half of the 47-exception morning above.

The buying decision

When each model is the right purchase.

Pump by exception is the right purchase when the binding problem is visibility: wells go down and nobody knows until the next calendar visit. An operator with no alarm discipline at all should fix that first. Just price it as what it is: detection, without economics, routing, or learning. Do not book deferment-recovery economics against a detection purchase; there is no published case we know of where detection alone moved LOE or deferred production at portfolio scale.

Pump by priority is the right purchase when the alarm list already exists and the question has become which of these deserves a truck today, in what order, and who goes. That is a valuation and routing problem, and it is where the published full-loop numbers come from: at the deployed reference, a top 25 private producer running 5,000+ wells across the Western Anadarko, Permian, and Wyoming, the measured deployment figures are 15% more free cash flow on the same crew and 35% fewer miles driven for the same coverage.

Keep your SCADA. Keep your historian. Keep your exception system. The migration adds the layer that turns exceptions into economic decisions: scoring that prices the exceptions you already surface, routing that turns the scored list into a drivable day, and the feedback loop that makes tomorrow’s ranking sharper than today’s. The productized version of that migration is a 4-week stand-up: read-only integration in week one, scoring in week two, crews live in weeks three and four, one signed metric, and under the Impact Guarantee you owe no license fee unless it moves.

Frequently asked

Common questions

What is the difference between pump by exception and pump by priority?
Pump by exception asks which wells have a problem: SCADA thresholds trip alarms, alarms generate callouts, and the field responds to the exception list. Pump by priority asks which problem is worth solving first: every exception and every open task is scored in dollars, the scored list is sequenced into a constraint-aware route, and every field outcome retrains tomorrow’s ranking. The exception is not the decision. It is the input to the decision.
What is the difference between management by exception and pump by exception?
Management by exception is the management philosophy: leadership and field attention go to the deviations that matter rather than to routine confirmation that things are normal. Pump by exception is the oilfield’s first-generation implementation of that philosophy, built on SCADA alarms and callouts. The philosophy is sound; the first implementation struggled because it stopped at detection.
Why did pump by exception struggle for a decade?
Three failure modes repeat almost universally. Alarm fatigue: static, conservatively set thresholds produce hundreds of exceptions a day with no ranking, teaching the field that most alarms are noise. No economic context: all exceptions look equally urgent, so crews work them in windshield order. No routing and no learning: an exception list is not a drivable day, and the thresholds never improve. The failure was the implementation stopping at detection, not the principle.
Is a SCADA "pump by priority" feature the same as the pump-by-priority operating model?
No. Some SCADA packages ship a prioritization feature that ranks a down-well list by production impact against target. That is useful, and it is not the operating model: it ranks volumes rather than dollars, it hands the field a sorted list rather than a constraint-sequenced route, and the ranking does not learn from what the crew found. Three test questions: is the priority a dollar figure a controller would defend; does the output arrive as a routed day in the truck cab; and does yesterday’s field outcome change tomorrow’s ranking?
When is pump by exception enough?
When the binding problem is that nobody knows a well is down until the next calendar visit, detection alone is real progress: an operator with no alarm discipline should fix that first. But detection should be priced as detection. There is no published case we know of where detection alone moved LOE or deferred production at portfolio scale; the published full-loop results, including the 15% FCF uplift on the same crew at the 5,000+ well deployed reference, all come from systems that price and route the exceptions, not just flag them.
What is the migration path from pump by exception to pump by priority?
Keep your SCADA. Keep your historian. Keep your exception system. The migration adds the missing layers on top: economic scoring on the exceptions you already surface, constraint-aware routing that turns the scored list into a drivable day, and closed-loop feedback from the field. The productized path runs the full loop thin on one field in four weeks against one signed metric, then widens field by field.
What comes after pump by priority?
Field operations has moved in four generations. Generation one, fixed routes: visit every well on a cadence. Generation two, pump by exception: visit wells when something changes. Generation three, pump by priority: visit wells when the economics justify it. Generation four, intelligent operations: the system continuously decides what the operation should do next, running the full loop of flag, price, rank, route, execute, learn. Each generation answered the previous one’s binding constraint, and pump by priority is the step that makes the fourth reachable.

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

Pump by exception tells you where something changed. Pump by priority tells you where to send your people.

See the difference between an alarm queue and a ranked plan, on your own wells, in four weeks.

See Your Wells RankedView a Sample 6 AM Plan 

Continue the cluster