Labeled. Never bare. · Last updated August 20, 2026
The numbers, with their labels on.
Every proof point WorkSync publishes, in one place: the number, what it means operationally, where it comes from, and how it is measured. One figure on this page is modeled rather than measured, and it says so on its face; everything else is a measured deployment figure. If a performance number is not here, we do not claim it.
Wells under coverage
The scale of the largest live deployment: every producing well scored nightly and eligible for the ranked plan, across three basins (Western Anadarko, Permian, Wyoming).
Deployment fact · a top 25 private producer
How it is measured
Counted from the deployed asset hierarchy: wells integrated into DataHub and scored by the ranking engine, not a marketing estimate of wells "touched."
Free cash flow uplift on the same crew
The same wells, the same headcount, and the same trucks produce 15% more free cash flow, because the crew day is spent on the highest-value work instead of the calendar.
Deployment figure · measured across 5,000+ wells in live deployments
How it is measured
Measured against the pre-deployment baseline on the same asset base: production, deferment, and operating cost reconciled through the operator's own accounting close, not modeled from assumptions. "Same crew" is the control: no incremental headcount in the comparison window.
Fewer miles driven
Crews cover the same production responsibility while driving roughly a third fewer miles, because low-value stops fall off the route and the remaining stops are sequenced.
Deployment figure · same production coverage, measured across 5,000+ wells
How it is measured
Route logs before and after on the same field: total crew miles per period compared against the fixed-route baseline for the same well set. Fewer miles is a byproduct of ranking, not a route-compression target of its own.
TRIR across the deployment
Total recordable incident rate fell from 1.8 to 0.3 on a 12-month rolling basis: fewer exposure hours on the road and on low-value sites, and risk-adjusted dispatch that keeps unqualified workers off unsafe jobs.
Deployment figure · 12-month rolling, live deployment
How it is measured
Standard OSHA TRIR arithmetic on the operator's own recordable-incident log, compared across the pre- and post-deployment periods. The exposure-hours denominator comes from the same payroll records used for regulatory reporting.
Hydraulic model build effort
A hydraulic model build that consumed weeks of an engineer's attention in document archaeology and manual data entry now compresses to minutes of verification: FlowSync builds the model from the PDFs, GIS, and SCADA the operator already has, and the engineer reviews and signs.
Deployment account · FlowSync model builds in live use
How it is measured
Stated as the compression of elapsed engineer effort from source documents to a runnable model at the reference deployment, against the calendar-weeks history of the legacy manual workflow for equivalent systems. Published without endpoint hour figures: we state only what the deployment record supports.
Miles of pipeline modeled
The pipeline footprint whose hydraulic models run on the platform: gathering and transmission mileage reconciled into the model inventory, with models, data, and studies flowing through WorkSync.
Deployment fact · reconciled model inventory, live deployment
How it is measured
Summed from the deployed GIS records of the pipeline systems reconciled into the model inventory, and stated at the reconciled figure rather than a rounded-up estimate.
Lower liquid-hauling inventory
Barrels sitting in tanks waiting on a truck fell by 40%: hauling is scheduled against forecast tank levels instead of standing calendar pulls, so loads arrive when tanks need them.
Deployment figure · measured against the pre-deployment hauling baseline
How it is measured
Route-and-tank-forecast driven hauling scheduling, compared against the pre-deployment hauling baseline on the same tank-battery population: average barrels held in tank awaiting haul, before and after, from the operator's own tank and haul-ticket records.
Less redundant tank gauging
Six in ten manual gauging visits stopped happening, because telemetry plus the tank forecast already covered the reading. The visits that remain are the ones a person actually needs to make.
Deployment figure · same tank-battery population
How it is measured
A gauging visit counts as redundant only where telemetry and the tank forecast covered the reading it would have produced. The 60% is the share of pre-deployment gauging visits eliminated on that basis, counted from route and visit logs, not estimated.
Tank-induced shut-ins
Across the measured deployment period, no well on the covered tank-battery population was shut in because a tank reached capacity with no haul scheduled. Full tanks stopped being a reason to stop producing.
Deployment figure · across the measured deployment period, covered tank batteries
How it is measured
Counted from the operator's downtime records: shut-in events whose recorded cause was tank capacity. Zero occurred across the measured deployment period on the covered tank-battery population. Stated for that window and population, not as a forward guarantee.
The one modeled figure
Recovered deferred production is worth a 2 to 5% production uplift.
Production uplift from recovered deferred production
Deferred production is the gap between well capability and actual flow: down wells waiting on a truck, underperformers nobody scored, workovers queued behind smaller jobs. Recovering it by ranked, priced dispatch is modeled as worth 2 to 5% of total field production.
Modeled · aligned to the published Alvarez and Marsal worked example
Why this one is modeled
A field-level deferral uplift depends on the deferral share a field carries into deployment, so it is stated as a modeled range rather than a single measured aggregate. The model is aligned to the worked example Alvarez and Marsal published for exception-based surveillance, not quoted from it, and it never borrows a deployment label.
Kept apart from the measured tiles above
The label matters. Everything else on this page is measured; this figure is modeled, and any telling that presents it as a measured deployment result is exactly the kind of claim this page exists to prevent.
Methodology: deferred production is the gap between well capability and actual flow, measured from the operator’s downtime and variance records (deferred production, never “deferred downtime”). The modeled uplift expresses the recoverable share of that gap against total field production. The independent research base, including the Alvarez and Marsal study, is collected on Exception-Based Surveillance.
Where these numbers come from.
The deployment figures above were measured at the reference deployment: a top 25 private producer running 5,000+ wells across the Western Anadarko, Permian, and Wyoming, in live production. The full story of that deployment, including the 12-week first rollout and what the productized 4-week stand-up changed, is in the 3-basin case study. What the platform actually does to produce them is covered in Pump by Priority: The Complete Guide and on WellOPS.
Independent, third-party research on the operating framework behind these results (including the Alvarez & Marsal exception-based surveillance study) is collected on Exception-Based Surveillance and the State of Oil & Gas Operations data hub. For the chronology of how the 15% band became the industry operating floor, read The 3-Year Bar.
Why does every number carry a label?
House rule: no bare statistics. A number without provenance is marketing; a number with its measurement method is evidence. Every figure on this page is a deployment figure (measured on live operations against a pre-deployment baseline), a deployment fact (counted from deployed systems), a deployment account (reported from the deployment where a measured aggregate does not exist; we say which), or, in exactly one case, a modeled figure. The modeled figure is labeled modeled everywhere it appears and sits in its own section, never among the measured tiles.
Who is the reference deployment?
A top 25 private producer running 5,000+ wells across the Western Anadarko, Permian, and Wyoming. We do not name customers; the anonymity is deliberate. The scale, basins, and figures are stated exactly as measured.
Why is the deferred-production uplift modeled instead of measured?
Because modeled is the honest label for it. The 2 to 5% production uplift from recovered deferred production expresses recoverable deferral volume against total field production, aligned to the published Alvarez and Marsal worked example rather than quoted from it. It is stated with the modeled label everywhere it appears and kept apart from the measured deployment figures on this page.
Are your best people working on your most valuable work today?
The next number on this page could be yours.
Pick the metric that matters. Four weeks later, measure it against your own baseline. You owe no license fee unless it moves.