What Field Service Scheduling Costs an Oil and Gas Services Firm in Windshield Time

The truck that drove out twice

A crew leaves the yard before sunrise, drives two hours of highway and forty minutes of lease road, and arrives at a location that is not ready. The pad is not staked, or the operator's company man is not expecting them, or the part on the truck is the one the ticket asked for and not the one the well needs. They drive back. Tomorrow, they drive out again.

On the scheduling report, that shows up as two jobs worth of travel for one job worth of revenue. If you have been pitched field service software this year, you have seen a slide promising to shrink the travel. It will, a little. It will not touch the second trip, and the second trip is where the money went.

What the vendor math measures

Windshield time is the unbillable hours a technician spends driving. The numbers that circulate come from the people selling the fix, so read them that way. One field service software glossary says well-optimised operations keep windshield time under 20 percent of the workday, and treats anything above 35 percent as a red flag. Those are urban service benchmarks, written with HVAC vans and city blocks in mind.

The pitch built on top of them is simple. Your crews drive too much between jobs, an optimiser sequences the stops better, the percentage falls, and you reclaim billable hours. Every figure in the demo is about the drive from job A to job B.

That is a real saving, and for an oilfield services firm it is usually the smaller half of the problem. The calculation assumes job A and job B were correctly scoped, correctly timed, and completable on arrival. Routing software optimises the order of trips. It takes the list of trips as given.

Why the oilfield version is different

Three things make windshield time in oil and gas services behave unlike the benchmark it is compared to.

The distances are not the same kind of distance. A service call in a metro area is fifteen minutes away. A location in a basin can be two or three hours, much of it on private roads. When a trip fails, you do not lose a quarter hour. You lose most of a crew day.

The last miles are not on the map. Even a fleet software vendor selling into the basin concedes that oilfield lease roads are privately constructed, never submitted to mapping databases, and change configuration as drilling programmes advance. A routing engine that cannot see the road cannot estimate the drive, and a dispatcher who has not been down that road recently cannot either. The optimiser is working from a map that is cleanest exactly where the drive is cheapest.

Readiness belongs to somebody else. An HVAC technician's customer is usually home. An oilfield crew's job depends on the operator's schedule, a rig's timing, a gate combination, a permit, a site that another contractor was supposed to finish first. None of that lives in your scheduling system. It lives in phone calls, text threads and the memory of whoever took the order.

Put those together and the expensive failure is not a crew that drove an inefficient sequence. It is a crew that drove a perfectly sequenced route to a job it could not do.

The second trip is a dispatch information problem

Look at why return visits happen and the pattern is consistent. The crew arrived without the right part. The location was not ready. The access information was wrong. The scope on the ticket did not match the work on the ground.

ServicePower, another vendor, names missing, incorrect or delayed parts as a top cause of first-time fix failure across field service organisations. A maintenance software vendor's case study of a single manufacturing campus found 18 percent of its work orders closed incomplete because the technician lacked the right part or the right information at the point of repair, and a further 11 percent were rework, return trips within 30 days because the root cause was never found. That is one facility in another industry, and we would not quote it as your number. We quote it because it describes the mechanism: roughly three in ten jobs went wrong on information that existed somewhere before the truck left.

Every one of those causes was decided before the truck rolled. They are inputs to dispatch, not outputs of it. A scheduling engine takes a work order, a crew, a location and a time window, and it produces an efficient plan. If the work order is incomplete, it produces an efficient plan to fail.

This is why the vendor claim and the operator's experience both hold at once. The software genuinely compresses the drive between jobs. The firm genuinely does not see the margin move. They are measuring different miles.

What the second trip actually costs

We will not hand you an industry figure for the cost of a failed trip in oilfield services, because we cannot find one that was not published to sell a product. The mechanism is easy enough to cost on your own numbers, and the shape of it is worth seeing.

A wasted first trip costs the full loaded crew hours for the round trip, the fuel and wear on heavier equipment than a service van, and the day the crew could have spent billing somewhere else. The second trip then costs all of that again, and it usually displaces a job that was already scheduled, which pushes that customer a day and starts its own chain.

Then there is the cost that never reaches the job ticket. The operator remembers that you were not ready. In a basin where the same few companies award most of the work, that memory prices into the next bid.

A routing improvement shaves a percentage off travel that was going to happen anyway. Eliminating a return visit removes a whole round trip, plus the disruption it caused. For a firm whose drives are measured in hours, one avoided second trip can outweigh a week of better sequencing. That is the comparison nobody on page one runs.

Why firms buy the optimiser anyway

It is not a foolish purchase, and we want to be fair to it. There are three good reasons it wins the budget.

It is visible. Travel time is already in the GPS data. A before and after chart is easy to produce and easy to present.

It has an owner. Dispatch has a manager, the software has a budget line, and a vendor will run the implementation.

It does not require anyone to change how orders come in. That is the real attraction and the real limitation. The information that causes the second trip is gathered by whoever takes the call from the operator: a salesperson, a field supervisor, an office coordinator, sometimes the crew lead on their cell phone. It is rarely one role, it is rarely written down the same way twice, and nobody's scorecard counts it.

If this sounds familiar from other industries, it should. We saw the same pattern with MRO shops automating work order intake before fixing parts data, and the arithmetic on MSP ticket triage fails for a related reason: the vendor counts the minutes it saves and not the ones its inputs waste.

What we would look at first

The honest sequence is not software first or process first. It is measurement first, of the thing nobody currently measures.

Most firms can tell you their average drive time. Very few can tell you how many jobs last quarter needed a second visit, and why. That number almost always exists in scattered form: in invoices with two mobilisation charges, in tickets that were reopened, in crew timesheets that list the same location on consecutive days. It has just never been assembled.

Once it is, the conversation changes. The questions that decide the outcome are which causes dominate for your firm, where in the order-taking process the missing information should have been caught, who owns catching it, and whether anything in your current systems can hold it. Sometimes the answer includes a scheduling platform. Often the first fix is a short list of facts that must be confirmed before a crew is released, with a named person accountable for confirming them.

Neither of those is a routing problem. A better route to the wrong location is still, in the most literal sense, a road to nowhere.

Where this gets specific

The pattern above holds across the oilfield service firms we have seen. The parts that decide your result do not generalise: how often your crews actually return, which of the causes is costing you most, who in your business takes the information that would have prevented it, and whether the software you are being pitched does anything about that at all.

That takes looking at your tickets, your timesheets and your order intake, not reading an article. If your scheduling looks efficient and your margin does not, talk to us. We will help you count the second trips before you pay to optimise the first ones.