The Backlog Behind the Badge: Where Field Supervisors and the C-Suite Disagree on Maintenance Risk

PetroMar Survey recently fielded a targeted survey of 412 US field supervisors and maintenance planners across mature basins—Appalachian, Midcontinent, Gulf Coast, Permian conventional, and San Joaquin Valley—alongside 87 executives at the same or comparable operators. The purpose was not to audit individual companies, but to test a simple proposition: whether the people who sign off on work orders and the people who sign off on capital budgets are looking at the same maintenance reality.

They are not.

A Survey Built to Test a Simple Proposition

Respondents were drawn from operators with at least 250 producing wells and from service companies that support them. Field supervisors and maintenance planners answered questions about work-order deferrals, critical-equipment service intervals, craft-hour availability, and the visibility of backlog data. Executives answered parallel questions about their assumptions for the same categories. The survey was not designed to produce a single industry-wide backlog figure. It was designed to measure the distance between two vantage points inside the same organizations.

That distance is wide and consistent.

The Numbers: A Consistent, Material Gap

The median field respondent reported that 24 percent of scheduled maintenance work had been deferred more than 90 days. Executives at comparable operators estimated the figure at 8 percent. The gap persists across basins and company sizes, though it narrows at large integrated operators with centralized work-management systems and widens at independent producers running multiple legacy assets.

The divergence is sharper on critical equipment. Fifty-eight percent of field respondents said at least one critical rotating-equipment train—compressors, pumps, generators—was past its original equipment manufacturer recommended service interval. Only 27 percent of executives believed that to be true. On safety-critical work orders, 34 percent of field respondents reported at least one deferral in the past year without a formal risk-acceptance record; executives estimated 11 percent.

Crew capacity tells a similar story. Seventy-one percent of field supervisors said the maintenance backlog exceeded available craft hours. Among executives, 39 percent agreed. And only 42 percent of field respondents said the backlog was tracked in a system that executives could access directly; the rest relied on spreadsheets, whiteboards, or local work-order logs that are summarized upward before they reach the boardroom.

Why the Gap Persists

The gap is not usually a matter of bad faith. It is a matter of aggregation. A monthly operating report may show preventive-maintenance compliance at 92 percent. That figure can be technically accurate while masking the fact that compliance on critical equipment is 68 percent. Work orders are closed as complete when a technician visits the site, even if the underlying repair is deferred. Backlog is measured in total work orders rather than in critical work orders by age. Each of these choices is reasonable in isolation. Together, they produce a boardroom picture that field supervisors do not recognize.

Budget pressure reinforces the pattern. When operators trim maintenance spending, the easiest deferrals are often the ones that do not immediately stop production. Those deferrals accumulate quietly. Field supervisors see the consequence in vibration readings, seal leaks, and repeat failures. Executives see a favorable cost line and a compliance metric that has not yet moved.

Production and Safety Consequences

The survey found a relationship between deferral rates and unplanned downtime. Field supervisors at sites reporting more than 20 percent of scheduled maintenance deferred beyond 90 days reported average unplanned downtime of 6.2 percent. At sites reporting less than 10 percent deferral, the figure was 2.8 percent. The survey does not establish causation, but the pattern is consistent with what maintenance planners have long argued: deferred work does not disappear; it returns as emergency work at a higher cost.

The safety dimension is harder to quantify and more important. Bypassed preventive maintenance on pressure-relief devices, corrosion monitoring, and emergency shutdown systems does not always produce an incident. It produces a lower margin of safety that is invisible until it is tested. The fact that one-third of field respondents reported safety-critical deferrals without formal risk acceptance should be treated as a leading indicator, not a lagging one.

A Simple Diagnostic for Closing the Gap

The survey points to a diagnostic that any operator can run in about 90 minutes. It requires raw work-order data, not a summary report. Pull all work orders from the last 90 days. Tag each as critical, essential, or routine. Calculate the share of critical work orders deferred more than 30 days. Compare that figure with the executive team's current assumption. If the gap exceeds 10 percentage points, the reporting system is not giving leadership a usable view of maintenance risk.

A second measure is critical preventive-maintenance on-time completion. A third is maintenance-induced downtime: production lost because equipment failed before scheduled service. Together, these three measures give executives a more honest view than a single compliance percentage.

What to Do With the Result

The point of the diagnostic is not to assign blame. It is to close a reporting gap before it becomes an operational surprise. Operators should require critical-work-order aging in the same monthly package that carries production and capital data. They should separate critical maintenance compliance from total compliance. And they should ask field supervisors to review the executive summary before it leaves the organization.

The confidence gap is not a morale problem. It is an information problem with production and safety consequences. The companies that close it will not eliminate maintenance backlogs. They will at least know how large those backlogs are before the next failure does the reporting for them.