Skip to main content
← White papers
WorkSync · Research · Volume IV · June 2026

Taking Pump by Exception to the Next Level

A practical playbook for evolving exception-based operations into prioritized, economically ranked daily plans.

Pump by exception was the right idea with a ceiling: queues that outrun attention, a 5 BOPD stripper alarming like a 200 BOPD producer, thresholds drifting off declining wells. This paper is the operator-level playbook for the next level. Three moves, in order: prioritize the exceptions, score them in dollars, and turn the scored queue into a ranked daily plan, plus the operating-model changes that make the moves stick. Light on math by design: the formal treatment is Volume I, Pump by Priority. This is the field manual.

3
moves: prioritize, score, rank
90
days, gated implementation path
+15%
free cash flow, same crew
35%
fewer site visits
1.8 → 0.3
TRIR at the reference deployment
5,000+
wells, three basins
Preview · First 3 pages15 pages total
Taking Pump by Exception to the Next Level: white paper coverP.1
Taking Pump by Exception to the Next Level: abstract and introductionP.2
Download

Read the full paper

Get all 15 pages: the three moves (prioritized exceptions, economic scoring of alarms, the ranked daily plan), the operating-model changes that make them stick, the KPI swap, and the gated 90-day implementation path. We will follow up only if it makes sense.

15 pages · PDF

What is inside

  • Why mature pump-by-exception deployments hit a ceiling: alarm overload, equal-looking exceptions, threshold drift, no economic context, no learning.
  • Move one: prioritized exceptions. Alarm rationalization, per-well bands that follow decline, persistence rules.
  • Move two: economic scoring of alarms. The one formula the field needs, severity tiers, and the defensible no-visit decision.
  • Move three: the ranked daily plan. Constraints, overrides as data, and mid-shift re-ranking.
  • The operating-model change: how the morning meeting inverts, how the foreman role moves up a level, and the KPI swap.
  • A 90-day implementation path gated on evidence, not on the calendar.
  • The bridge to Pump by Priority: what the closed loop adds, and why the learning gap compounds.
  • Cross-referenced throughout to the formal Volume I research paper.

Where the playbook leads

The destination numbers, measured at the full Pump by Priority reference deployment: a top-25 private producer across three basins (Western Anadarko, Permian, and Wyoming), 5,000+ wells, same crews, against pre-deployment baselines.

MetricBaselineOutcome
Free cash flow, same crewbaseline+15%
Site visits per crew-shift1.000.65
TRIR (recordables / 200k hrs)1.80.3

Outcomes are specific to that deployment and calibration. New basins, equipment classes, or operating philosophies require a calibration period before results match these benchmarks.

Keep your exception system. Add the layers it is missing.

The playbook is the how. WellOPS is the system that runs it: the scored, constraint-aware, ranked plan in every truck cab by 6 AM, on top of the SCADA and rules you already own.