A field ticket that sits unapproved for nine days is not a delay. It’s an invoice you haven’t sent yet, on work you already paid your crew to do.
Most shops know their approval process is slow. Fewer know exactly where it stalls, which is why the usual fix, telling everyone to approve faster, changes nothing.
Here’s how to find the stall and clear it without loosening the controls that keep your invoices defensible.
First, measure the gap
Pick twenty tickets from last month. For each one, write down two timestamps: when the job finished, and when the ticket was approved for billing.
The average of those gaps is your approval cycle. Most paper-driven shops land somewhere between seven and fifteen days. Shops running digital capture with a clear approval chain sit under two.
Now look at the worst five. They usually share a cause, and that cause is your actual problem. Everything else is noise.
The four places tickets get stuck
The ticket never arrived. It’s in a truck, a jacket pocket, or a photo on someone’s phone. Nobody in the office knows it exists, so nobody is waiting for it. These are the tickets that go missing entirely, and they cost the industry 2 to 4 percent of revenue every year.
The ticket arrived incomplete. Consumables missing, hours unclear, no signature, or a signature from someone who left the company. Now it needs a phone call to the tech, who is on another job. That call happens when someone has time, which is Friday.
The approver is the bottleneck. One supervisor approves everything, and he’s in the field four days a week. Tickets queue behind one person’s evenings.
Nobody owns the queue. The ticket is complete and correct, sitting in a folder or an inbox, waiting for a person whose job description does not include watching that folder.
Three of those four have nothing to do with approval speed. They’re capture problems that look like approval problems.
Fix capture before you fix approval
The single largest gain comes from the ticket being complete when it leaves the wellsite. Not mostly complete. Complete.
That means the fields the office needs are required fields in the field, not optional ones the tech fills in if he remembers. Labor hours, equipment used, consumables, photos, and a customer signature captured on site, from the person who was actually there.
A field ticket app earns its keep here, and only if it’s designed for the conditions. If the ticket takes more than a couple of minutes to fill out in gloves, the tech will do it later in the truck, and half the detail goes missing. If it needs a signal to save, it will fail at half the pads in the Permian.
Get the ticket right at the source and the approval question changes from “chase the missing pieces” to “yes or no.”
Then make approval a real workflow
Once tickets arrive complete, approval speeds up on its own. A few rules push it further.
Name a backup approver. One person cannot be the only path to billing. Give the backup the same authority, not a lesser one.
Set a rule for what needs review at all. Not every ticket deserves the same scrutiny. A recurring job for a known customer at agreed rates needs a different level of attention than a job with a rate change and three subrentals. Decide the threshold and write it down.
Approve on a phone. Supervisors are not at desks. If approval requires a laptop, approval happens at night or on weekends, and often not at all.
Make the queue visible. Whoever owns billing should see every ticket, its status, and how long it’s been sitting. A queue nobody can see is a queue nobody clears.
Set an internal deadline earlier than the operator’s. If your customer’s submission window is thirty days, your internal target should be five. The gap is your margin for the ticket that goes wrong.
What not to do
Do not fix approval speed by removing approval. It’s tempting, and it works for about two months, until an operator disputes a line item and nobody can say who checked it.
The approval record is what makes an invoice defensible. Time stamps, who approved, what changed after the tech submitted it. That trail is worth more than the days it costs, provided it costs days and not weeks.
Do not solve it by hiring. Another admin processes the same broken flow faster. The gain disappears the next time volume goes up.
What good looks like
The tech closes the ticket on site with a customer signature. It syncs when he has signal, or when he reaches the yard. The office sees it that day, already complete.
Routine tickets clear the same day. Exceptions get looked at properly, because they’re the only thing anyone has to look at. The billing week closes on Friday.
One Permian shop measured 18 days from job done to invoice sent before they changed anything. Four weeks after switching to digital capture: 3 days, and zero missing tickets that month.
The approval process didn’t get faster. It got a cleaner input.
