Category guide · Last updated July 30, 2026
Route planning software for oil and gas
Not the shortest route. The most profitable one.
A sample day in text, synthetic demo data:
Today’s plan, 06:00
- 01. Alderridge F-7H, High Fluid Level: $3,939/d, 8 mi
- 02. Pellmarsh 1-5, ESP Underload: $3,336/d, 17 mi
- 03. Sabelgate Unit 7, Compressor Down: $2,807/d, 15 mi
Crew A’s day: 7 stops, 2h 39m driving, $10,331/d
- 06:44 Alderridge F-7H, High Fluid Level: $3,939/d
- 08:20 Thanegate Unit 1, High Fluid Level: $2,262/d
- 09:19 Gildweir Unit 4H, High Tank Level: $1,100/d
Synthetic demo data
The definition
What route planning means in oilfield operations
| The problem | With WorkSync |
|---|---|
The inherited loop The problem:It leaks because it treats the well running clean and the well quietly dying as equal stops, forever. | With WorkSync:Every well is scored overnight on dollars at risk: deviation from its own learned baseline, production at risk, working interest, lifting cost, and the cost of deferring another day. |
The mileage router The problem:The fuel math improves and the blind spot does not move, because the most efficient possible tour of low-value stops is still a day spent on low-value stops. | With WorkSync:A plan built on value density will sometimes drive further to reach a well worth reaching, and will more often skip three nearby stops that earn nothing today. |
Read more
Most routing products an operator will be shown were built for a fleet delivering interchangeable things to interchangeable places, and they optimize miles beautifully. A producing field is not that problem.
What follows: what oilfield route planning has to solve, the constraints generic tools miss, how dispatch decisions get made, and five questions to ask any vendor.
A lease operator, pumper, or gauger is responsible for somewhere between 30 and 300 producing assets and has one shift to spend on them. The software decides which of those assets get a visit today, in what order, and by which crew.
Most operators run an inherited loop: a route drawn by a previous superintendent, driven the same way every Monday, Wednesday, and Friday. It survives because it is fair, predictable, and easy to staff.
It leaks because it treats the well running clean and the well quietly dying as equal stops, forever. The obvious upgrade looks like mapping software: minimize the miles, hand the crew a tighter loop.
The fuel math improves and the blind spot does not move, because the most efficient possible tour of low-value stops is still a day spent on low-value stops.
Why this is not a delivery problem
Delivery routing is a solved, well-engineered field, and the math behind it is excellent. It rests on one assumption that quietly does all the work: every stop is worth about the same.
When that holds, the value of the day is fixed the moment the stop list exists and the only remaining variable is cost. So you minimize distance, and you are right to.
On a producing field the assumption fails by orders of magnitude. A failing pump on a high-rate producer and a routine gauge on a stripper well appear on the same morning list, and one is worth a multiple of the entire rest of the route.
The value of the day is not fixed by the stop list, it is determined by which stops make the list. Distance is the second-order term.
That is the difference between distance and value density: dollars of production impact captured per crew-hour spent.
A plan built on value density will sometimes drive further to reach a well worth reaching, and will more often skip three nearby stops that earn nothing today.
The net effect still runs the direction people expect: 35% fewer miles driven at equal economic coverage, measured across 5,000+ wells in live deployments.
The consequence for an evaluation is blunt. A tool that minimizes miles first is optimizing the wrong number, and no amount of oilfield terminology layered on top changes the objective function underneath. Are your best people working on your most valuable work today?
A router cannot answer that. It was never asked to.
The constraint reality
Six constraints generic routing tools miss.
Crew qualifications and certifications
A stop is not assignable to whoever is nearest. H2S-certified crews belong on sour wells, pressure-vessel inspectors on PV assets, and an electrical isolation waits for the person carrying the card.
Qualifications belong inside the solver, not in a warning printed after the plan is built.
Hours of service and the shape of the shift
Shift length, mandatory breaks, travel from the yard, and the drive home consume the day before a single well is worked. Plans that ignore them get quietly re-cut in the truck, which means the ranking never reached the field.
Lease roads, gates, and access windows
Public road networks stop at the lease line. From there the day runs on caliche, cattle guards, locked gates, and surface-owner windows no commercial map layer has seen. Two wells a mile apart on the map can be forty minutes apart on the ground.
Escort, buddy, and H2S requirements
Sour service, confined space, and hot work cannot be done alone, which turns one stop into a synchronization problem across two crew calendars. Lone-worker exposure is the safety side of the same constraint: fewer, better-justified visits is a routing outcome, not a policy poster.
Equipment co-routing and synchronization joins
A rod-pump job needs a pulling unit on location when the crew arrives. A paraffin cut needs the hot oil truck. These are joins, not stops: two resources have to meet at one place inside one window, and an error in either leg wastes both.
Weather and seasonal access
Freeze-offs, spring thaw, and a wet caliche road change which locations are reachable and which work is worth doing today. In most basins this is not an exception to the plan, it is a recurring re-plan trigger.
And six classes of work competing for the same shift.
- 01Scheduled equipment maintenance
- 02Reactive failure response
- 03Regulatory inspections under hard deadlines
- 04Risk-based proactive visits
- 05Liquid management: oil hauling, water hauling, tank reconciliation
- 06Routine information collection and gauging
These classes interact, which is what makes the problem genuinely hard rather than merely large. A hauler dispatched late induces a shut-in. An electrician routed first lets a workover proceed. An inspection missed by an hour erases a month of capture credit.
The formal treatment, a multi-class vehicle routing problem with synchronization constraints and the solver built for it, is in the 40-page research white paper on optimal route planning. Class 02, reactive failure response, is the one most operations already generate automatically, from a SCADA threshold breach.
Where those flags come from and why they arrive unranked explains why a routing solver fed by an unpriced queue optimizes the wrong stops efficiently.
Dispatch
Who assigns the work, and why dispatch by geography fails
Geographic dispatch fails in a way that is easy to miss because it looks like efficiency.
Read more
A superintendent looks at overnight SCADA, the callout list, the open work orders, and their own memory of which wells have been acting up, then allocates crews by area.
It has worked for decades, and the people doing it are usually the most knowledgeable operators in the company. That is exactly the problem: the logic lives in one head, runs at the speed of a phone tree, and retires when they do.
Sending the nearest crew to the nearest work reliably produces a full, busy, low-mileage day, and it reliably fills that day with cheap stops, because proximity and value are uncorrelated.
The well that started failing at 2 AM sits on the far side of the asset and waits. Nothing in the dispatch loop surfaces what that wait cost, which is why the loss is invisible in every report the operator runs.
Operators searching for oil and gas dispatch software, oilfield dispatching software, or work order dispatch software are usually trying to fix the visibility half: the whiteboard into a system, the assignment onto a phone, completion back. Worth doing, and where most of this market stops.
It leaves the allocation decision exactly where it was. The operating model that moves the allocation decision, dispatching against sensor signal instead of a standing loop, is routeless operations.
What a ranked dispatch looks like
A ranked dispatch runs the decision before anyone logs in. Overnight, every asset is compared against its own learned normal, deviations are scored in dollars at risk, and candidate work is written as work orders automatically.
The scored list is filtered by qualification, constrained by hours, access, and equipment, then sequenced into a route per crew.
By the start of shift each crew has a plan in the cab with the reasoning attached: why this well, why this order, what to look for. The superintendent does not disappear from that loop and should not.
Their job moves from building the day to auditing it, and every override feeds back as signal.
The same structure applies wherever a field workforce serves a network of dispersed assets, which is why gas utility dispatch and midstream field dispatch run on the same engine with a different scoring model.
Those adaptations live in the use cases by vertical, and the work-generation layer underneath is oilfield work management.
The evaluation
How to evaluate route planning software
01 · Ask what the objective function actually is
Tools built for delivery and service fleets typically optimize miles, drive time, or stops completed, and they optimize those well: the routing math in that market is mature. The ceiling is that all three assume stops are worth roughly the same.
Ask the vendor to state the objective in one sentence. If it contains distance and not dollars, you get the cheapest possible tour of a list nobody scored.
02 · Ask where the stop list comes from
Routing and deciding are separate problems, and most of this market solves only the second. Generic field service management tends to assume the work already exists as tickets someone opened.
Operators have no customer opening tickets: the request is a pressure trend drifting since 2 AM. Without work generated and scored from production signals, the route inherits last night’s list.
03 · Ask which constraints are hard and which are advisory
Vendors verticalizing into energy usually show a qualifications field or a custom tag, which is real and useful. What matters is whether it is enforced inside the optimization or checked afterward.
Ask for a plan where an unqualified crew is the geographically obvious choice, and see whether the stop appears at all.
04 · Ask what happens at 10 AM
A morning plan is a snapshot and the field invalidates snapshots: a well goes down, a truck breaks, a lease road closes. Telematics-first providers typically report that well. Reporting a deviation and re-solving the remaining day across all crews are different capabilities.
Ask whether re-optimization is continuous or a once-a-morning batch.
05 · Ask whether the loop closes
The most durable difference is whether yesterday changes tomorrow. In most dispatch systems a closed job is archived and the story ends.
When the outcome feeds back into the scoring model, the ranking sharpens with every field observation and the same crew gets progressively more valuable.
Read more
The shared ceiling across those patterns is the same one: they tend to treat the stop list as an input rather than as the decision. Reasonable in every market they were built for, and the one choice a producing field cannot afford. The same evaluation applied to the wider category is on the pump by priority software guide.
How WorkSync does it
Rank the day first. Then route it.
- 35%fewer miles drivendeployment figure
- 15%free cash flow uplift on the same crewdeployment figure
- 5,000+wells in live deploymentsMeasured, live deployment
The ranking comes first, the route comes second
Every well is scored overnight on dollars at risk: deviation from its own learned baseline, production at risk, working interest, lifting cost, and the cost of deferring another day. The route gets shorter because the list got smarter.
A constraint-aware solver, not a shortest-path map
Qualifications, time windows, hours of service, vehicle capacity, equipment co-routing, and synchronization joins are hard constraints in the optimization. The multi-hour combinatorial solve compresses to seconds, which is what makes a 6 AM plan possible.
Continuous re-optimization through the day
A weather event, a vehicle down, or a new high-priority alert re-assigns the remaining stops across every crew without a call to dispatch. A living allocation of the crew-hours that are left, not a document printed at sunrise.
The plan reaches the truck cab
Mobile delivery with offline caching for cellular-dead zones, because a plan that only exists in an office is not a plan. Field completion feeds tomorrow’s ranking, which is where the compounding comes from.
Read more
Fit-for-purpose. Plug-and-play. The stand-up is four weeks, read-only, on the SCADA, historian, and accounting systems you already own. The module that carries this in production is the WellOPS Route Optimizer module, and the ranking that feeds it is pump by priority.
The whole field, one plan
Every route, drawn where the value is.
The operator-level playbook is on lease operator and pumper routes; the modeled dollar gap for your own field is on the route economics calculator.
More detail
Field operationsLease operator routes.
Not the shortest route. The most profitable one.
The pumper route is where field strategy becomes physical: whatever the plan says, what actually happens is where the trucks go. Most routes are still fixed loops drawn years ago, driven on a calendar. This page covers how lease operator routes get built, why the fixed loop leaks value every day it runs, and what changes when the route is rebuilt each morning from a dollar-ranked well list.
Crew hours are the scarcest resource in the field. The route allocates them.
Why the route is the leverage point
A lease operator's shift is a fixed budget: so many hours, so many miles, so many stops. The route is the spending plan for that budget. When the route is a fixed loop, the budget is spent by habit: every well gets its calendar visit whether it needs one or not, and the day's biggest problem gets whatever time is left after the schedule is served.
The waste compounds quietly. Value-dense stops and empty stops cost the same miles. The well drifting off forecast since 2 AM waits for its day in the rotation while the crew confirms that twelve healthy wells are still healthy. Add the drive time between stops that earned nothing, and a large share of the shift is spent producing certainty about wells that were already fine, which is the most expensive form of reassurance an operator buys.
There is a second cost hiding in the same miles: exposure. Vehicle incidents are the leading safety risk in field operations, and every mile a pumper does not need to drive is exposure the operation does not take. The same ranking that removes low-value stops from the route removes the road hours and the site hours that went with them, and risk-aware dispatch keeps unqualified workers off unsafe jobs in the first place.
The fix is not driving faster or adding a crew. It is changing what the route is made of: rank first, then route. Which is a software problem, because the ranking has to be rebuilt from the overnight data every single morning. Taken to its conclusion, the standing route stops existing at all, which is the shift described in dispatching without a fixed route.
Three generations of the pumper route.
How routes get made
Method 01
The inherited loop
The route a previous superintendent drew, driven the same way every Monday, Wednesday, and Friday. It survives because it is fair, predictable, and easy to staff. It leaks because it treats the well running clean and the well quietly dying as equal stops, forever.
Method 02
The shortest path
Mapping software that minimizes miles across a fixed stop list. Better fuel math, same blind spot: it optimizes the order of the wrong list. The most efficient possible tour of low-value stops is still a day spent on low-value stops.
Method 03
The value-ranked route
Score every well overnight on dollars at risk, drop the stops that earn nothing today, then sequence what remains into a drivable day with geography, lease access, qualifications, and daylight as constraints. The route gets shorter because the list got smarter. Not the shortest route. The most profitable one.
The measured difference between the loop and the value-ranked route: 35% fewer miles driven with the same production coverage, measured across 5,000+ wells in live deployments (deployment figure). The route shrinks because the stop list earns its place, not because anyone drives less carefully. The full labeled proof set is on the numbers page, and you can model your own miles and dollars in the route economics calculator.
The ranked plan and the route, on one screen.
6 AM, in the truck
The day opens on the highest-value well in the area, with the do-this-now call made explicit and the route heatmap showing where the dollars sit. Under 20 minutes a day of software; the rest is wrench time.
Rank first, then route. WellOPS does both, nightly.
Where WorkSync fits
WellOPS Route Optimizer takes the overnight ranking from the Work Engine and turns it into a drivable day for every crew: terrain, lease access, well status, crew skill, and daylight as constraints, with turn-by-turn for unmarked lease roads and re-optimization when the day changes. It works in the truck, offline. The operator keeps the override; the override feeds the score.
It stands up in weeks, not quarters: read-only integration on the systems you already run, ranked routes in the truck inside the 4-week stand-up, and the result measured against your own fixed-route baseline. Don't leave field capacity on the table driving loops the field outgrew years ago.
This page is about the operator's day. If you are evaluating the tooling category itself, including how oilfield routing differs from delivery routing, the constraints generic tools miss, and five questions to ask any vendor, start with the guide to route planning software for oil and gas.
See tomorrow's route, ranked by dollars.
Four weeks from read-only integration to ranked routes in every truck cab, measured against your fixed-route baseline.
Continue the cluster: Deferred Production · Oilfield Work Management · Route planning software for oil and gas · Route Optimizer, the product · 6:00 AM Clarity: a field day, before and after · The Most Dangerous Task on the Lease Is the Drive to It
Routeless OperationsKill the milk run.
Route crews by dollars, not by habit.
WorkSync builds each field team member’s day from the ranked work list and solves it against real drive times, crew qualifications, equipment, and hours of service. The plan is in the cab by 6 AM. Same windshield time, spent on the wells that move money.
The Pump by Priority™ platform: CMMS + Prioritization Engine + Work Management + Field Data Capture + Accruals, in one place.
- Live in 4 weeks
- 39 systems already connected, 15 industrial protocols
- License fees only when the metrics move
Read-only connections to the systems you already run. We flag the work, price and prioritize it, route it, and close the loop; a pilot reads from your source systems and stays read-only until you promote it. SOC 2 Type II in progress, report targeted Oct 30, 2026.
The schedule stops being a map of where the wells are. It becomes a ranking of where the value is.
“…transitioned approximately 40% of our onshore production to routeless operations.”
CEO, large US independent · Q2 2025 earnings call
WorkSync route optimization maximizes the impact of your team. It optimizes for value density, the dollars a crew-day recovers, rather than for the miles it covers. Distance is usually not the problem: compact, well-placed positions still bleed value, because the loss is in the sequencing rather than in the geography. 35% fewer miles driven (deployment figure, measured across 5,000+ wells in live deployments) falls out of the reordering rather than being the target of it.
Routeless is now an operating model that large independents describe to their own investors, and WellOPS is that machinery, productized: sensor- and exception-driven dispatch, value-ranked stops solved against real road time, and the paperwork (tickets, work orders, accruals) booked with the work, not at month-end. Live in 4 weeks (deployment figure), rather than a multi-year internal build. The exception queue is the input the ranking runs on, and software that prices what the queue flags is what turns it into a day worth driving.
The stop a fixed route makes every week and the stop a ranked day makes this morning are different stops. A fixed route allocates a crew hour by calendar and by geography. The engine allocates the same hour by what a well is losing this morning. Same hours, assigned on a different basis. Read the module detail on value density and the solve, or start from the route’s side of the argument: lease operator routes.
| P1 | Stop 1, Battery 14: ESP anomaly, 6 miles out | $8.4k/d |
| P1 | Stop 2, Well 233H: down, gas-lift restart | $5.1k/d |
| P2 | Stop 3, Well 118: rod pump check on the way back | $2.2k/d |
| P3 | Route 6 milk run: dropped from today, nothing at risk | $0.3k/d |
This is what 6:00 AM looks like.
One ranked list, one solved route, one screen in the field. The reason a well is on the list travels with it.
And this is what it looks like from the truck.
A ranked list is not a plan. Three steps turn one into the other.
How the drive day gets built
Ranking answers what matters most. Routing answers who goes, in what order, with what in the truck, and whether the day can be finished inside a legal shift.
STEP 1
Pull the ranked work
Every open job arrives carrying a dollars-per-day score, a qualification requirement, an equipment requirement, and a time window. Break/fix, PMs, hauling, gauging, and compliance checks all come from the same list, so nothing competes from a side queue.
STEP 2
Solve it
A constraint solver of the class used to route large delivery fleets assigns stops to crews against measured road distances, yard start and end, vehicle capacity, and site access windows. It maximizes dollars recovered across the whole crew-day rather than sites touched, and it solves in seconds what takes a foreman a morning.
STEP 3
Put it in the cab
Each crew gets its own sequence by 6 AM, cached for the cellular dead zones, with the reason each stop is on the list traveling with the stop. Completion feeds straight back into the ranking that builds tomorrow.
Six constraints, enforced inside the plan rather than checked after it.
What the solver holds constant
A plan that ignores a qualification, a weight limit, or a shift length is not a plan, it is a request. These bind every route before it reaches a truck.
Crew qualifications
H2S certification, pressure-vessel inspection, electrical work, well control. A stop that requires a qualification is assigned to a crew that holds it, which is also what keeps the audit trail clean without a post-hoc review.
Equipment and co-routing
Jobs that need a pulling unit, a hot oil truck, or a vac truck get the iron co-routed with the qualified crew rather than scheduled on a separate list that has to be reconciled by phone.
Real roads, real time
Measured drive times over lease roads, seasonal access, bridge weight limits, and gate conditions, rather than straight-line distance. Your own traversal data sharpens the estimate on the private roads no public map covers.
Hours of service
Shift length, mandatory breaks, and travel to the first site sit inside the solve, so the day that reaches the cab is a day that can be finished legally and safely by the crew it was built for.
Value density
The objective is total dollars recovered across the crew-day. A high-value stop thirty minutes out can outrank three low-value stops next door, and the plan shows the arithmetic that made that call.
Live re-solve
A well goes down at 10 AM and the remaining stops re-assign across crews: the crew passing nearby later picks up what the redirected crew drops. Continuous re-optimization, rather than one batch at sunrise.
The plan stays overridable, one tap with a reason code, because the field knows the lease road that washed out and the bearing somebody heard yesterday. The override is recorded as data: a stop the field consistently pulls forward is carrying information the scoring has not captured yet.
What operators get. In this order.
RESULT #1
Downtime Reduction
The solver puts the stop that stops deferment first, before the drive day fills up with routine.
RESULT #2
Optimal Liquid Management
Hauling and gauging stops earn their place in the same drive day as the wells, so trucks move against value instead of against the end of the month.
RESULT #3
Proactive Risk Management
Permit-gated, two-person, and lone-worker stops are sequenced with their constraints attached, so the day the solver builds is a day that can legally be run.
RESULT #4
The Full Picture of Value Sinks
Miles, windshield hours, and the value each stop returned land in one ledger, which shows you which parts of the drive day paid for themselves.
The plan rides in the cab, not on a clipboard.
Built to work with your lift program, your operations center, and the platform underneath
Your lift optimization, executed
Rod pump, ESP, and gas lift optimizers recommend. WorkSync prices each recommendation on deferment and failure cost, ranks it against everything else in the field, routes it to the right crew, and books the accrual with the work.
See the artificial lift story →
Your remote operations center, connected to the field
The control room and the field share one ranked queue, live in both directions. The center re-prioritizes and the cab sees it in seconds; the field closes work and the center sees status, downtime recovered, and cost.
See the remote operations story →
The platform underneath
Five components, one ranked work loop: the data layer, the engine that prices the work, equipment and safety management, and the accrual that closes with the job.
How the drive day gets solved
Terrain, lease access, well status, weather, and crew skill turn the ranked list into a sequence, and it re-solves when a well goes down mid-morning. Not the shortest route. The most profitable one.
How WorkSync fits in
Your systems flag it. WorkSync prices it, ranks it, and routes it: routeless, AI-driven operations that put every field team member on the highest-value work.
Your systems
- SCADA & alarms
- Lift optimization & surveillance
- ERP & production accounting
- Historians & PM schedules
WellOPS
- Flag: issues & preventative maintenance
- Price & prioritize: AI ranks by $ and risk
- Route: routeless dispatch to the right crew
- Close: ticket, accrual, downtime recovered
Your field team
- Lease Operators
- Technicians
- Roustabout Crews
- Mechanics & Electricians
The support that keeps your field equipment running. Driven by one ranked queue, with a UX field teams love: built for the cab, offline-capable, and held to a design standard of under 20 minutes a day of software per field team member.
See your wells, ranked by dollars, tomorrow morning.
Bring one field’s data. We’ll show you the ranked plan your crew would have run today, and what it was worth.
Route planning and dispatch, common questions
What is route planning software for oil and gas?
It builds the daily driving and work plan for pumpers, lease operators, and field technicians: which wells to visit, in what order, by which crew. It differs from delivery routing in objective and in constraints.
Oilfield stops differ in economic value by orders of magnitude on the same morning, and the plan has to respect crew qualifications, hours of service, lease-road access, escort requirements, and equipment that must arrive at the same place at the same time.
The objective is value captured per crew-day, not distance.
How is routing software for oil and gas different from delivery routing?
Delivery routing minimizes distance because every package is worth roughly the same, so the cheapest tour of the stop list is the best answer.
In the oilfield the stop list itself is the decision: a failing pump on a high-rate producer and a routine gauge on a stripper well are not equivalent stops.
Horizontal fleet-routing platforms verticalizing into energy tend to keep the delivery objective and add oilfield fields on top, which optimizes the order of the wrong list.
What is oil and gas dispatch software?
Dispatch software decides who works what, when, and in what order, then gets that assignment to the crew. Upstream, that has historically been a superintendent with a whiteboard and a phone, allocating people by geography and by memory.
Software-assisted dispatch replaces the geographic allocation with an economic one: work generated from field signals, priced by cash flow at risk, checked against qualifications and hours, sequenced into routes, and pushed to mobile before the shift starts.
Why does dispatching by geography fail on a producing field?
Geography is the right allocator when every stop is worth the same and travel is the dominant cost. On a producing field the dominant cost is deferred production on the wells nobody got to.
Dispatch-by-area sends the nearest crew to the nearest work, which reliably fills a day with cheap stops while the well that started failing overnight waits for its scheduled visit.
Can field service dispatch software built for service companies work for operators?
It can carry real weight, and the scheduling and mobile workflows in that category are mature. The structural gap sits upstream of dispatch. Those platforms are built around tickets a customer opened and a job that bills.
An operator is its own customer: nothing opens the ticket and no stop bills. Without a layer that generates and prices candidate work from production signals, the dispatch board is only as good as the list a human typed into it.
How does oilfield route optimization software handle crew qualifications and safety?
Properly implemented, they are hard constraints inside the solver rather than fields checked after the fact. H2S-certified crews are routed to sour wells, pressure-vessel inspectors to PV assets, and stops requiring an escort are scheduled as a synchronization join across two crew calendars.
The safety result is fewer lone-worker exposures, because the unqualified dispatch never leaves the yard and the low-value stop that carried the drive never enters the route.
What results should an operator expect from value-ranked routing?
Measured across 5,000+ wells in live deployments: 35% fewer miles driven at equal economic coverage and 15% free cash flow uplift on the same crew (deployment figures).
The tank and deferral figures that follow from the same ranked plan are on the numbers page, each with its methodology. The mechanism behind every one is the same: crews stop driving to stops that earn nothing today.
How long does route planning software take to stand up?
The WorkSync stand-up is four weeks, read-only, against the systems of record you already own: telematics and qualification data in week one, the optimization engine and your economics in week two, crews trained and running on mobile in weeks three and four. Fit-for-purpose. Plug-and-play.
The pilot is signed against one operating metric and your own baseline under the Impact Guarantee: we charge when your number moves.
What is a lease operator route?
The daily driving plan a lease operator (pumper or gauger) follows to check, gauge, and service the wells in their area of responsibility: which wells, in what order, doing what at each stop.
On most fields it is a fixed loop set years ago and repeated on a calendar cadence regardless of what changed overnight.
What is wrong with fixed pumper routes?
Fixed routes allocate the scarcest resource in field operations (crew hours) by calendar instead of by value. The well that started failing at 2 AM waits for its scheduled day while the crew visits wells that needed nothing.
The cost shows up as deferred production, excess miles, and windshield hours spent confirming that healthy wells are still healthy.
How should pumper routes be optimized?
In two stages, in order. First rank: score every well by cash flow at risk from the overnight data, so the stop list itself is worth driving.
Then route: sequence the ranked stops into a drivable day under real constraints (geography, lease roads, crew qualifications, required work windows). Optimizing mileage across an unranked stop list skips the stage where the money is.
How much do route miles actually drop?
35% fewer miles driven, measured across 5,000+ wells in live deployments (deployment figure), with the same production coverage. The reduction is a byproduct of ranking: low-value stops fall off the route, so the tour compresses.
Fewer miles also means less exposure, because the drive is the highest-risk part of most lease work.
Do lease operators lose autonomy under a ranked route?
The ranked plan is a decision aid with an override, not a leash. Operators skip or resequence stops with a reason code, and those overrides feed the next morning’s score, so local knowledge makes the ranking smarter instead of fighting it.
The plan arrives by 6 AM and the software asks for under 20 minutes of the operator’s day; the rest of the shift is wrench time.
What does it take to switch from fixed routes?
No new sensors and no rip-and-replace. WorkSync connects read-only to the SCADA, historian, production accounting, and GIS you already run; the productized stand-up takes 4 weeks from integration to ranked plans in every truck cab, measured against your own fixed-route baseline on one signed metric.
What training does the field need before the first shift?
The app is built for a truck cab at 6 AM in gloves: one screen at a time, offline capable, and it syncs when signal returns.
A field team member opens it to a day that is already assembled and already in order, so the first shift is the training.
Capture happens at the wellhead, by voice or in a couple of taps, rather than at shift end, and Willie walks a person through a JSA by voice.
Every stop carries the reason it is ranked where it is, and any stop can be resequenced or skipped in one tap with a reason code, which keeps local knowledge in charge of the day.
The rollout is gated rather than dated: flags tune against the field's own judgment first, and the ranked plan goes into a truck when the crews agree the ranking is right.
The measure that matters is whether the plan survives contact with the field, and establishing that on your own crews is what the four weeks are for.
How do we justify this internally?
Build the case from a method rather than a projection. First, you and your controller pick one operating metric and write it down before anything is connected: cash flow per BOE, operating cost per well, drive miles, or TRIR.
Second, run your own well count, crew count, and drive times through the route economics calculator on this site, which puts a dollar figure on a day of your field capacity using your inputs rather than ours.
Third, run the four-week pilot on one field against that single agreed metric, with the baseline set in week zero, so the business case is measured on your wells.
The Impact Guarantee carries the commercial risk while that happens: license fees only when the metrics move. What reaches your approver is your own baseline and your own delta, which is the only version of the number that survives a finance review.
Are your best people working on your most valuable work today?
See tomorrow's routes built on your own wells.
One operating metric, your own baseline, and we charge when your number moves.
Continue the cluster: Route Optimizer module · Lease Operator Routes · Route Economics · Research White Paper