---
title: "The Handwritten Tubing Tally and the Faxed Rental Ticket: The Two Oilfield Documents Still Being Retyped by Hand in 2026"
description: "Carbon-copy field tickets, pencil tubing tallies and faxed rental tickets: what hand-keying 1,900 lines a month really costs, and what photo reading fixes."
canonical: https://callsphere.ai/blog/the-handwritten-tubing-tally-and-the-faxed-rental-ticket-the-two-oilfi
category: "Industry Solutions"
tags: ["oilfield services", "field ticket", "tubing tally", "document reading", "well service invoicing", "loss and damage claims"]
author: "CallSphere Team"
published: 2026-06-28T16:27:33.000Z
updated: 2026-09-04T15:53:22.811Z
---

# The Handwritten Tubing Tally and the Faxed Rental Ticket: The Two Oilfield Documents Still Being Retyped by Hand in 2026

> Carbon-copy field tickets, pencil tubing tallies and faxed rental tickets: what hand-keying 1,900 lines a month really costs, and what photo reading fixes.

## Four pieces of paper from one three-day workover

Count them on the next job you run. There is the carbon-copy field ticket the company man signed on a tailgate at 11 p.m., with the top copy going in your supervisor's binder and a thumbprint of pipe dope across the hours column. There is the tubing tally the derrick hand wrote out in pencil — 118 joints, three of them marked "DNR" for do not run. There is the rental ticket the tool house faxed in at 4 a.m., because that tool house has faxed everything since 1998 and is not going to stop. And there is the crane sub's invoice, scanned crooked, with a handwritten note in the margin adding two hours of standby and a set of initials next to it.

Not one of those four is typed. All four have to become typed lines before anybody gets paid. In most district offices that is still done by a person with a keyboard, reading off a screen at 7 a.m.

The 2026 development that matters here is unglamorous: document reading finally got good enough for ugly inputs. Not scanned contracts on white paper — a phone photo of a greasy carbon copy, taken at an angle, in a truck, with a shadow across the bottom third.

## What retyping a tubing tally actually costs when the count is wrong

A tubing tally is not a formality. It is the record of what went in the hole and what came out, and it drives the handling charge, the rental days on the elevators and slips, the disposal line if joints get scrapped, and — when a string parts eighteen months later — the argument about whose inspection missed it. When a clerk keys 113 instead of 118, three things happen: you under-bill the handling, your yard inventory drifts, and the next person who pulls that well works from a bad number.

**Multimodal document reading, in owner's terms, means the software looks at the actual photograph or fax of your field paperwork — the handwriting, the initials in the margin, the crossed-out line — and pulls the numbers off it, instead of waiting for someone to retype it into a clean form.**

```mermaid
flowchart TD
  A["Phone photo of signed carbon-copy field ticket"] --> E["Reader lifts hours, quantities, initials and change notes"]
  B["Faxed rental tool ticket from the tool house"] --> E
  C["Pencil tubing tally, 118 joints, 3 marked DNR"] --> E
  D["Crane sub invoice, scanned crooked"] --> E
  E --> F{"Signature block dated and legible?"}
  F -->|No| G["Held for supervisor to confirm with company man"]
  F -->|Yes| H["Invoice packet built, attachments in operator's required order"]
```

## What changed between the 2024 scanners and the 2026 readers

Plenty of service companies bought document scanning in 2023 or 2024, hated it, and went back to typing. The old readers were built for forms — same boxes, same places, printed. Oilfield paper is not that. The hours column runs into the description column because the tour ran long. The company man crosses out four hours and writes three with his initials beside it. The fax arrives at half resolution with the header line eating the first row. A form reader sees noise; a person sees a ticket.

The readers that shipped through 2026 handle it because they read the whole artifact the way a person does — the layout, the crossings-out, the initials, the relationship between the signature and the change above it — rather than looking for a box at fixed coordinates. That is the practical difference. You can hand it the photo your supervisor already took on his phone in the truck, which is the photo that already exists on every job you run.

Cost stopped being the barrier too. Running this on every ticket you generate is now a rounding error next to what you spend on shop rags — which is why it makes sense on all of them, not just the big ones.

## Tuesday, 7:15 a.m.: the photo becomes an invoice line

Your supervisor already photographs signed tickets before he leaves location, because he learned years ago that carbon copies go missing between the pad and the yard. In 2026 that photo is the input, not the backup.

He texts or uploads it. The reader pulls the well name, the date, the tour, the hours by category, the consumables, the joint count off the tally, and — this is the part that used to fail — the handwritten change with the initials next to it, which it holds as a separate note rather than silently overwriting the printed line. The faxed rental ticket gets matched to the same job by well name and date. The crane sub's scanned invoice gets matched to the pass-through line and the markup applied per that operator's agreement.

By 7:15 the billing clerk is not typing. She is looking at a screen with the photograph on the left and the extracted lines on the right, confirming the four items the reader marked as uncertain. The same flow catches the loss-and-damage case: when a rental crossover comes back galled, the phone photo of the damage goes on the claim with the tool number read straight off the body stamp, instead of a clerk squinting at a photo and typing a serial number that may or may not be right.

## The arithmetic: 1,900 hand-keyed lines a month

Stated assumptions, illustrative — substitute your own line counts from last month.

| Assumption | Value |
| --- | --- |
| Handwritten or faxed lines keyed per month | 1,900 |
| Keying time per line, today | 25 seconds |
| Review time per line with the photo read first | 4 seconds |
| Assumed keying error rate | 1 line in 100 |
| Average value of an error, when it goes against you | $310 |
| Billing clerk loaded rate | $28 per hour |

Time: 1,900 lines at 25 seconds is about 13.2 hours a month, or roughly $370. At 4 seconds it is about 2.1 hours, roughly $59. Saved: about 11 hours and $311 a month. That alone is not a reason to change anything.

The errors are the reason. One in a hundred lines is 19 wrong lines a month. Assume half go against you at $310 each: that is about $2,945 a month, or roughly $35,300 a year, walking out the door as under-billed handling, missed standby hours and rental days nobody charged. The other half go the wrong way and cost you a rejection, a dispute email, and thirty days. Even if your real error rate is a third of that, the recovered billing pays for the software several times over before you count the clerk's hours.

## Where to keep a human, and where to keep paper

Do not let a reader be the sole record of a signature. If your master service agreement says the operator's representative must sign the ticket, the signed artifact is your evidence in an audit or a dispute, and it needs to be stored and retrievable — the reading is a convenience layered on top, not a replacement. Keep the images filed against the job number.

Second, watch the change orders. A crossed-out four with initials beside it is the single highest-risk mark on an oilfield ticket, because it is where the operator's representative reduced your hours. The reader should surface every one of those to a person, every time, with the image. If it starts silently resolving them, turn that off.

Third, safety paperwork stays human. A job safety analysis, a pre-job meeting sign-in sheet, a lockout-tagout record — reading those into a database is fine for retrieval, but the OSHA 300 log entry and anything that goes into your ISNetworld file should be reviewed by your safety coordinator personally. That is not a place to save four seconds a line.

## Frequently asked questions

### Our hands' handwriting is genuinely terrible. Does it actually read it?

Better than a form scanner, worse than the pusher who has read that man's writing for six years. The right test is not accuracy in the abstract; it is what happens when it is unsure. A good setup gives you a confidence flag and the cropped image side by side, so an unreadable line takes a person three seconds instead of three minutes of hunting through a binder.

### Can it handle the fax machine at the tool house?

Yes, and faxes are actually one of the clearer wins, because faxed rental tickets are usually the same layout every time from the same vendor. The old problem was resolution, not layout. Start with your two highest-volume tool houses.

### What about tickets signed on a tablet — do we still need this?

Less so, and that is a good problem. But almost nobody is at 100% digital signature. Between contract hands, third-party subs, crane and roustabout crews, and the operator's representative who will not use your app, most districts still see a third or more of their supporting paper arrive as an image. Handle that third; do not rebuild the two-thirds that already works.

### How long before it pays for itself?

Measure recovered billing, not hours. Take one month, read every ticket both ways, and total the lines where the read version and the keyed version disagree on a quantity or an hour. Price those out. That number is your payback, and you will have it in thirty days.

## Start with one folder

Take last month's supporting paperwork for one crew — the field tickets, the tallies, the rental faxes — and run the whole folder through a reader before you commit to anything. You are looking for two numbers: how many lines came back clean, and how many disagreements were in your favour. If neither number moves you, walk away and spend the money on tongs.

One thing that reliably follows faster invoicing: more inbound calls from operator payables clerks and from tool houses chasing their own paperwork, usually in the last hour of the day. [CallSphere](https://callsphere.ai) builds AI voice and chat agents that answer the office line after hours, take the well name, job date and ticket number, and pass a clean message to your billing clerk instead of a voicemail she has to decipher at 6:40 the next morning.

---

Source: https://callsphere.ai/blog/the-handwritten-tubing-tally-and-the-faxed-rental-ticket-the-two-oilfi