The Complete Guide · Last updated July 28, 2026
Pump by Priority: the complete guide.
Pump by priority ranks every field opportunity by dollars, risk, and practicality, then routes your people to the highest-value work first. It is how operators implement management by exception on producing wells, and it is the step past pump by exception that the exception era always pointed toward. This guide is the category definition: what pump by priority is, how it differs from what came before, how the engine works, and what it changes on a Tuesday morning.
The definition
What is pump by priority?
Pump by priority is the operating model in which every well, every anomaly, and every open task on a field is scored in dollars, the scored list is sequenced into a constraint-aware route a crew can actually drive, and the outcome of every completed job feeds back into tomorrow’s ranking.
Three elements define it, and all three have to be present. Economic scoring: production at risk, working interest, lifting cost, commodity price, and safety exposure combine into a single dollar-denominated priority per task. Constraint-aware routing: the ranked list becomes a drivable day that respects geography, crew qualifications, hours of service, and equipment on the truck, which is what separates route planning software for oil and gas from a delivery-fleet router. Closed-loop learning: what the crew found, fixed, or ruled out retrains the ranking before the next plan runs.
The definition matters because the term is starting to appear on vendor slides with much thinner meaning behind it. A prioritized down-well list ranked by production volumes is a useful input, and it is not pump by priority: it ranks barrels rather than dollars, it hands the field a sorted list rather than a sequenced route, and it does not learn from what the crew found. A system missing any of the three elements is something else wearing the name.
Not all exceptions are created equal. A stuck valve on a 5 BOPD stripper well is not the same problem as a failing rod pump on a 200 BOPD producer, and an operation that treats them the same is leaving value on the table every shift. Pump by priority exists to make that difference explicit, in dollars, before anyone starts a truck.
The terminology ladder
How pump by priority differs from pump by exception and management by exception.
Three terms, one lineage. Each rung keeps what the previous one got right and fixes where it stopped.
Management by Exception
Human attention goes only to meaningful deviations. Routine, in-spec activity runs on its own. Older than the oilfield: Taylor wrote it down in 1903.
The operating model →Pump by Exception
SCADA thresholds trip alarms, alarms drive callouts, and crews visit only deviating wells. Real progress past fixed routes, but detection is where it stops.
How pump by exception works →Pump by Priority
Every exception carries a dollar figure, the field is ranked by value and risk, the ranked list becomes a drivable route, and every outcome sharpens tomorrow’s plan.
The side-by-side comparison →The one-sentence version: management by exception decides where attention goes, pump by exception decides which wells get visited, and pump by priority decides what the visit is worth and in what order the day should run. The full side-by-side lives on Pump by Exception vs Pump by Priority.
The engine
Inputs in. Priority Score. Optimized Route. Cash flow out.
The most sophisticated prioritization engine in the field combines hundreds of operational, financial, engineering, and safety variables into one ranked plan.
The left side of the diagram is everything your operation already knows: production forecasts, SCADA signal, tank inventories, the economics of every well, artificial lift state, engineering rules, risk exposure, crew availability, and travel time. The engine turns those inputs into a Priority Score per task: a dollar figure a controller could defend. The scored list becomes an Optimized Route: the day, in drive order, per crew, with qualifications and hours respected. What comes out the other end is cash flow: the same crew, pointed at the most valuable work, every morning.
Priced at today’s deck, re-ranked every morning, delivered to every truck by 6 AM. Don’t leave value on the table.
A worked example
What a priced exception looks like before anyone rolls a truck.
Here is the difference in practice. Under pump by exception, a well that trips a tubing-pressure threshold overnight becomes an alarm in a queue. Somebody notices it, somebody decides whether it warrants a visit, and the decision is made on experience and proximity, because the alarm carries no dollar figure.
Under pump by priority, the same flagged well arrives already priced. The morning brief below is the actual operator surface: every stop on the day carries the dollars at risk behind it, the top exceptions each carry their own value, and the route is already sequenced around them. The pumper is not asked to triage an alarm queue at 6 AM. The triage happened overnight, in dollars, and the ranked plan shows the reasoning: which wells, worth how much, in what order.
That is the whole point of the model. The dollar impact of the exception is known before the first truck leaves the yard, so the crew’s day starts at the top of the value list instead of the top of the alarm list.
The priced day: dollars at risk, exceptions, and the route, on one screen.
The evolution
From management by exception to pump by priority.
Pump by priority did not appear from nowhere. It is the third generation of an idea the industry has been implementing for two decades, and each generation fixed the specific place the previous one stopped.
Management by exception
From Taylor’s Shop Management (1903) through Drucker, manufacturing, and IT operations: condense the reporting to the deviations, and spend management attention only where it changes the outcome.
Pump by exception
SCADA telemetry brings the philosophy to the wellhead. Visit only the wells whose signal moved. It works where alarm discipline holds, and it struggles everywhere alarms flood, baselines go stale, and every exception looks equally urgent.
Pump by priority
Economic scoring, constraint-aware routing, and closed-loop learning turn the exception list into a priced, drivable, self-sharpening plan. The advancement is not better flagging. It is pricing and routing what gets flagged.
The exception discipline was never the mistake. Stopping at detection was. The operators who lived through the alarm-flood years were not wrong to be skeptical; they were early. The framework’s own research history, including the independent benchmark work on exception-driven field productivity, is covered in Exception-Based Surveillance.
Where WorkSync fits
The best Pump by Priority platform, shipped as a product.
Most operators who want this model face a choice between a multi-year internal build and a stack of tools that were each designed for something else. WorkSync took the third path: it productized pump by priority. WellOPS is the field operations platform: economic scoring, constraint-aware routing, and closed-loop learning in one system, stood up on the SCADA, production accounting, and CMMS you already run. Fit-for-purpose. Plug-and-play.
The deployed reference is a top 25 private producer running 5,000+ wells across the Western Anadarko, the Permian, and Wyoming. The measured deployment figures: 15% free cash flow uplift on the same crew, 35% fewer miles driven for the same production coverage, and TRIR down from 1.8 to 0.3. The full labeled set, with methodology notes, lives on the numbers page.
The stand-up is four weeks, not four quarters: read-only integration in week one, scoring configured in week two, crews live on the ranked plan in weeks three and four. Under the Impact Guarantee, license fees only when the metrics move.
Pump by priority, common questions
What is pump by priority?
Pump by priority is how oil and gas operators implement management by exception on producing wells. It combines three things: economic scoring that ranks every well and every task in dollars, constraint-aware routing that sequences the ranked work into an executable crew day, and closed-loop learning that sharpens the ranking with every completed job. A sorted down-well list alone is not pump by priority; it is the input to it.
How is pump by priority different from pump by exception?
Pump by exception identifies problems by flagging deviations from normal operating parameters. Pump by priority takes the next step: it prices every identified issue, ranks the whole field by dollar impact and risk, and routes crews to the highest-value work first. Detection tells you something happened. A ranked plan tells you what it is worth and who goes first.
How does pump by priority relate to management by exception?
Management by exception is the management philosophy: human attention goes only to meaningful deviations. Pump by exception is its first oilfield implementation, built on SCADA alarms. Pump by priority is the next step in the same lineage: it keeps the exception discipline and adds economic scoring, constraint-aware routing, and closed-loop learning so the deviations are worked in the order they pay.
What data is needed for pump by priority?
You can start with whatever data you have. WellOPS uses statistical physics-based models to rank wells by risk to cash flow, environmental risk, failure risk, and personal-safety risk against the data sources you run: manual gauges, run tickets, lease files, production accounting, CMMS history, partial SCADA, or full SCADA. SCADA is not a prerequisite; where it is missing, the same models recommend where SCADA investment would pay back fastest.
What results can operators expect from pump by priority?
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 a 15% free cash flow uplift on the same crew, 35% fewer miles driven for the same production coverage, and TRIR down from 1.8 to 0.3. Recovered deferred production is worth a 2 to 5% production uplift (modeled figure, aligned to the published Alvarez and Marsal worked example).
How fast can pump by priority go live?
The productized stand-up is four weeks: read-only integration onto your existing SCADA, production accounting, and CMMS in week one, scoring configured in week two, crews live on the ranked plan in weeks three and four. It runs on the stack you already own, under the Impact Guarantee: license fees only when the metrics move.
Are your best people working on your most valuable work today?
See your field as a ranked, priced plan.
Four weeks from your data to a ranked plan in the truck cab. You owe no license fee unless the metric you anchored on moves.
Continue the cluster: Management by Exception in Oil & Gas Operations · Exception-Based Surveillance · WellOPS, the field operations product · The 4-Week Pump-by-Priority Pilot, Week by Week · How to Implement Management by Exception