Replacing Paper Field Tickets in the Permian: A Phased Plan

By Brian Phetteplace · May 25, 2026 · 9 min read

Most oilfield service companies in the Permian still run paper tickets. Not because they love paper — because the cost of switching looks bigger than the cost of staying. I ran Reliable Oilfield Services on paper for the first two years. I know the calculus. Here's the phased plan we used to move off paper without breaking billing, blowing up compliance, or losing the crew.

Why phased beats big-bang

The big-bang transition — "Monday morning everyone uses the new app" — fails for one reason: the office has no fallback. If the app glitches, the regulator audit shows up, or a customer needs a duplicate, you've lost the safety net. A phased rollout keeps paper in your back pocket while you build trust in the digital flow.

The phased plan also lets the crew win small before they have to commit. Field hands are reasonable people — if they see the new tool actually saves them time, they switch on their own. If you announce "we're going digital" without a demo, you get malicious compliance for six months.

Phase 1 (Week 1): Pick one ticket type and run it parallel

Look at your last 90 days of tickets. One type probably accounts for 40-60% of volume. For us it was the daily service ticket on routine PM accounts. For a hot oil company it might be the hot oil run sheet. For a swabbing crew, the swab log.

That high-volume ticket is your Phase 1 target. The reason: every hour you save on it has ten times the impact of saving an hour on a one-off form.

What "parallel" means

For one week, the crew fills out both the paper ticket AND the digital ticket on every run. Yes, that's more work in the short term. But it does three things:

• Surfaces gaps in the digital form. The crew immediately notices when the digital form is missing a field they actually use.
• Builds confidence in the office. The office manager compares the paper to the digital output, sees they match, stops being scared of the new system.
• Catches sync issues before they bite. If a digital ticket vanishes because of an offline sync bug, you still have the paper. You find the bug, fix it, move on.

At the end of week one, do an honest review with the crew. What worked, what didn't, what's missing? Update the digital form to fix the gaps.

Phase 2 (Weeks 2-3): Retire paper for that ticket type

Now the digital ticket goes solo. Paper for that ticket type is officially retired. The office stops printing the carbonless forms. The crew is told: this is how we do this ticket now.

Critical things to do in Phase 2:

• Print "digital backup" sheets. Half-page templates the crew can grab if the tablet truly dies. Make them ugly on purpose so nobody mistakes them for the real ticket flow.
• Add daily ticket counts to the morning huddle. Yesterday we ran 14 tickets, 13 closed digitally, one is still open — let's chase the missing one. Visibility creates discipline.
• Wire up the invoice handoff. If you're moving off paper but still typing the data into QuickBooks, you've only solved half the problem. The whole point is the ticket flows from truck to invoice without manual rekeying.

"You're not getting rid of paper. You're replacing the workflow that needs paper."

Phase 3 (Weeks 3-5): Bring in the next two ticket types

Now repeat Phase 1 → Phase 2 for the next two highest-volume tickets. Maybe it's flare service tickets and heater treater PMs. Maybe it's swab logs and fluid haul sheets. Whatever it is, follow the same pattern: one week parallel, two weeks digital-only, then move on.

By the end of Phase 3 you've covered 70-85% of your ticket volume with three workflows. The remaining 15-30% is a long tail of compliance forms, one-off customer-specific tickets, and edge cases. They'll come last because they're slowest to standardize.

Phase 4 (Weeks 5-8): The long tail and the compliance forms

This is where most projects stall. The long tail is annoying — every form is a special case. Three rules that get you through it:

• Batch the similar ones. Five customer-specific service tickets that vary by 10% can be one form with conditional fields. Don't build five forms — that's how you end up with the GoCanvas form-island problem we documented in our switch story.
• Build compliance forms in code, not in a generic form builder. EPA Method 22, OOOOa storage tank inspections, PSV testing logs — these have specific output requirements and they change when guidance changes. Code-built compliance tickets let you update them in 48 hours instead of rebuilding.
• Accept that 5% of forms will stay on paper. The annual safety policy sign-off, the one-time vendor onboarding doc — fine, leave them on paper. The cost of digitizing them isn't worth it.

What the crew actually needs to switch

Three things, in priority order:

• Ruggedized tablets that don't die in the heat. Cheap consumer tablets won't survive a Midland summer. Budget $400-600 per truck for a Samsung Galaxy Tab Active or equivalent.
• Offline mode that just works. If the app can't run on two bars of LTE out by the wells, the crew will be back on paper inside a week. Test this hard. Drive out to the worst-signal customer location you have, force airplane mode, run a full ticket, sync when you're back to town.
• An invoice flow that doesn't slow them down at quitting time. If the digital ticket adds five minutes to close-out, the crew will hate it. If it shaves five minutes off close-out (because customer info is pre-filled, photos are auto-attached, signature is one tap), the crew will love it.

The honest cost

For a typical 6-truck Permian service crew, here's what it ran us:

• Tablets: ~$3,000 one-time (6 trucks × $500)
• Software (ReliableTrack): subscription, see pricing page
• Custom build: included in subscription, 48-hour delivery
• Lost productivity during Phase 1 parallel week: ~20 crew hours (one week of double-entry)
• Office training: ~6 hours total

Payback for us was about six weeks. Mostly through eliminated double-entry in the office, faster invoicing (DSO went from 32 days to 21), and not paying for tickets that fell behind the truck seat. Your numbers will differ — but the order of magnitude is right.

One last warning

The biggest mistake I see operators make is buying software before they have a phased plan. They run the demo, get sold on the features, sign the contract, deploy company-wide on Monday, and watch it collapse by Friday. The software is the easy part. The plan is the hard part. Sketch out your phases first. Then go shopping.

If you want help mapping a phased rollout to your specific ticket mix, that's literally what our 30-minute spec call is for. We'll look at your last 90 days, identify the Phase 1 target, and ship the digital version of that ticket inside 48 hours.

Frequently asked questions