A pump-off controller (POC) is one of the most widespread pieces of automation in upstream oil and gas. On any rod-pumped well, a POC is what keeps the pumping unit from beating itself to death when the reservoir isn’t supplying enough fluid to keep the pump full. It is the single piece of equipment-level automation that nearly every pumping well needs, and the payback period is usually under a year.

A pump-off controller senses when a rod pump is pumped off (pumping faster than the reservoir can supply fluid) and shuts down the pumping unit. After a programmed off-time or when fluid has recovered, the POC restarts the unit. The result is less rod wear, less motor wear, less electricity burned, and a pump that stays in service longer.

This is a plain-language guide to how POCs work in the field, why they matter, and where the operational-automation layer picks up where the POC leaves off.

POC Data Belongs in Your Pumper App, Not on the Pump Jack.

See how contract pumpers and small operators tie POC runtime into daily field data.

See TinyPumper →

What “Pumped Off” Actually Means

A rod pump lifts fluid from the bottom of the well using a reciprocating motion driven by the surface pumping unit. The pump has a standing valve (fixed) and a traveling valve (on the rods). On the upstroke, the traveling valve is closed and the pump lifts the fluid column. On the downstroke, the traveling valve opens and drops through the fluid.

A well is “pumped off” when the reservoir inflow cannot refill the pump barrel fast enough between strokes. The pump starts stroking partly-empty barrels, pounding fluid that isn’t there. That pounding: called fluid pound or gas pound: damages rods, tubing, pump internals, and the pumping unit itself. Left unchecked, it shortens equipment life dramatically.

The fix is simple: shut the pump down long enough for fluid to recover, then restart. That is what a POC does automatically, 24/7, without a pumper having to drive out.

How POCs Detect Pump-Off

Different POC technologies use different detection methods:

  • Dynamometer-based (load cell): the POC measures the load on the rod string at each point in the stroke. A pumped-off stroke has a characteristic load curve showing loss of fluid load on the upstroke. Modern dyno cards can distinguish fluid pound from gas interference with high accuracy.
  • Motor current / power: the POC monitors the motor’s current or power draw, which drops when the pump is lifting less fluid. Cheaper than a load cell but less precise.
  • Time-based (legacy): older timer-based controllers simply run the pump for X minutes and off for Y minutes, without sensing actual well conditions. Still common on very low-rate wells where a cheap solution is fine.
  • Vibration or sound: used occasionally on specific pump types. Less common in modern controllers.

The high-end POCs today are dynamometer-based with full stroke-by-stroke load analysis. Weatherford’s LOWIS, Lufkin’s SAM, and similar platforms can detect pump-off conditions within one or two strokes and either pause the unit or adjust stroke rate via a VSD.

Why POCs Pay Back

The math on a POC is rarely complicated:

  • Rod life extension: rod strings in wells running fluid pound can fail 30–50% faster than those in well-controlled wells. A $20,000 rod job every 18 months vs every 30 months is a real savings.
  • Tubing wear reduction: reduced pound means reduced tubing wear and fewer tubing jobs.
  • Motor efficiency: a motor driving a pump with less-than-full barrels is doing work for nothing. Electricity savings on a well running 10+ hours a day add up.
  • Pump intake wear: the pump internals last longer when they aren’t being fluid-pounded.

For any rod-pumped well producing more than 5–10 barrels per day, a POC typically returns its installed cost inside a year and keeps paying back for the life of the well. Even lower-rate stripper wells benefit, though the payback period stretches.

What POCs Don’t Do

A POC is an equipment-level controller. It watches and protects one pumping unit. What it does not do:

  • Tell the operator how much the well produced. The POC might know runtime and stroke count, but it doesn’t know tank levels, run tickets, or actual barrels sold.
  • Log downtime reasons. A POC shutting down on pump-off is not a “problem,” but a POC shutting down on a power outage or a mechanical failure is. The POC’s shutdown log doesn’t always distinguish, and the operator has to piece together the story from the pumper’s visit.
  • Feed the production report. Regulatory production reporting (Texas RRC Form PR, Oklahoma 300R, etc.) wants produced barrels and disposition, not stroke count.
  • Coordinate across wells. A POC on well #1 and a POC on well #2 have no knowledge of each other.

Those gaps are where the operational automation layer comes in.

POCs protect the pumping unit. Your pumper protects everything else.

TinyPumper ties pumper field visits: gauges, run tickets, downtime: to each well so the POC's data fits into the bigger picture.

See how TinyPumper works →

POCs and Pumper Workflow

On a well with a POC, the pumper’s visit changes. Instead of checking every well every day for pump-off conditions, the pumper can focus on:

  • Tank gauges: beginning and ending inventory, temperature, BS&W.
  • Run tickets: signed loads leaving the lease.
  • Visual checks: packing leaks, hot bearings, unusual sounds, stuffing box condition.
  • POC alarm review: anything the controller flagged that wasn’t normal pump-off behavior.
  • Workover needs: wells that are pumped off more than usual signal a reservoir or mechanical issue worth investigating.

Capturing that pumper visit data in a consistent place is where operational automation picks up. TinyPumper is designed for this exact workflow: the pumper logs the visit on a phone, the operator sees the data the same day, and POC data (where available) can be tied to the well record rather than living in isolation on the controller.

Wrong Fit for This Page

If you are researching pump jack kinematics, reservoir inflow theory, or designing a POC from scratch, this page is too practical for your purposes. This page is written for the operator, pumper, or contract pumper who wants to understand what a POC does in their field, when it pays back, and how it fits into the broader data chain.

FAQ

Can TinyPumper replace a pump-off controller?

No. The POC is a hardware device that runs control logic on the pump jack. TinyPumper is where the pumper’s field observations: including POC status at each visit: get captured. They work together, not in place of each other.

What is a pump-off controller?

A pump-off controller is an automation device that monitors a rod-pumped well and shuts down the pumping unit when the well is pumped off (pumping faster than reservoir inflow). After a programmed off-time, the POC restarts the unit.

How much does a pump-off controller cost?

POC installed costs vary widely. Basic timer-based controllers can run a few hundred dollars plus installation. High-end dynamometer-based controllers with cellular telemetry can run several thousand dollars installed. On a typical pumping well, payback is usually under a year.

Do all rod pump wells need a POC?

Almost all meaningful-rate pumping wells benefit from a POC. Very low-rate stripper wells (under a few barrels per day) may run continuously or on a simple timer, where the payback is thinner but still positive.

What is the difference between a POC and a VFD?

A POC senses pump-off conditions and shuts down or cycles the pumping unit. A variable frequency drive (VFD) or variable speed drive (VSD) adjusts the pumping unit’s stroke rate continuously to match reservoir inflow. Many modern setups pair a POC with a VSD for tighter control.

About the author: Greg Archbald is the founder of GreaseBook. He built the product from inside the oil patch and has spent 15+ years on the operator side of oil and gas technology.

A pump-off controller is one sensor on one well.

TinyPumper is a workflow layer across all your wells. When the pumper checks the well, the POC status, the gauge reading, and the downtime reason all land on the same dashboard. Because knowing the pump kicked off is useless if you don't know whether the pumper noticed.

See how TinyPumper handles pump-off data →
**P.S.** A pump-off controller without remote monitoring is a pump-off controller your pumper has to drive to. That defeats most of the point. If you are installing POCs, budget for the monitoring layer in the same capex line.