The Pit With No Scale

Twenty-eight miles from your main plant there's a bank-run pit with a loader, a fuel tank, and no scale. Material sells by the load out there, because trucking it to the certified scale and back would eat the margin. The loader operator keeps count the way loader operators have kept count forever: grease pencil marks on the inside of the cab glass, one column for Voss Excavating, one for the township. At ten to five he calls the office. "Nineteen for Voss today, six for the township." Somebody writes that on a pad, and at month end it becomes two invoice lines.

Look at what just carried the revenue. Not a ticket. A phone call about a windshield.

A mark can't go missing

A scale ticket, even a bad one, is a document with an identity. It has a serial number, a time, a truck, a customer, a weight. If it disappears, it leaves a hole: a gap in the serial run, a load the driver remembers. Most of the work of tightening a billing office is the work of finding those holes.

A tally mark has no identity. It's a stroke of grease with no serial, no time, no truck. And that gives it a property no missing ticket has: it can't be missed. When a ticket vanishes, something, somewhere, can notice. When a mark never gets made, the record and the only check on the record are the same thing, one man's memory of a Tuesday. There's no second number anywhere in the world to disagree with the windshield.

That's the whole mechanism. Sit with it. The main plant leaks when paper gets lost or keyed wrong. The no-scale pit leaks earlier than that, at the moment of capture, and it leaks silently, because nothing was ever created to be lost.

Where the marks go wrong

None of what follows takes a dishonest person. It takes a busy one.

The fuel truck shows up at 9:30 and the operator climbs down to meet it. Two of Voss's quads cycle through while he's holding the nozzle. He waves them across the ramp, because making a customer's truck wait at an unattended pit is how you lose the customer. The marks for those two loads live in his intention to catch up, and by the 11 o'clock rush they're gone.

Then the columns blur. Voss is running quad-axles and the township sent two tandems, and by early afternoon there are marks on that glass that could belong to either column. He'll sort it out at the call. Sorting it out means the township, which doesn't argue, gets a couple of Voss's loads, or the reverse.

And the day ends in round numbers. Count the glass at 4:50 and it reads maybe 23, maybe 25, depending on whether two smudges are marks. Nobody phones in "maybe 25." The number that goes to the office is the one he'd bet on, and a man betting with your material rounds down, because the call he never wants is a customer disputing loads. Every close of day, the benefit of the doubt runs one direction, and it isn't yours.

One more, and it's the quiet one: the site bills by the load, and a load isn't a unit. A quad carries real tons more than a tandem. If the rate assumes a quad and half the day ran tandems, fine, that's rounding in your favor for once. If the rate was set on tandem loads years ago and the fleet has grown, every mark on that glass undersells the material it stands for, at a per-load price nobody has reread since.

Price the windshield

Put illustrative numbers on it, not a study, just arithmetic you can redo with your own rates. Say the pit runs 25 loads a day at $210 a load. One mark a day lost between the fuel stop and the round-down is $210. Across a 110-day season that's about $23,000 from one site, and here's the claim to argue with over coffee: that money is gone in a way the main plant's money never is. A lost ticket at the plant is recoverable for weeks, sometimes months. A mark that never hit the glass was unrecoverable by lunchtime the same day, because there is nothing to find. An owner who'd fire a clerk for losing $23,000 of tickets will run a no-scale pit on grease pencil for a decade and call it lean.

The thirty-year answer is coming, so meet it now: "we've sold bank run this way since my father ran the pit, never had a problem." Right, and the tally is why. A problem, from the office's chair, is a discrepancy, and a tally can't produce one. There's no count to reconcile it against and no serial run with a gap in it. The system isn't clean. It's unauditable, and unauditable feels identical to clean from the inside.

No scale required, no exceptions either

The fix isn't a scale. A scale out there may never pencil. The fix is giving every load an identity, which costs a numbered pad and thirty seconds: serial, truck, customer, date, and the operator's initials, written while the truck's on the ramp. Drivers wait thirty seconds at every drive-through in town. They'll wait at your ramp.

The part that has to be structural comes after the pad, because pads fill trucks' door pockets too. Those tickets get digitized the day they're written, so the site's record exists somewhere besides a windshield by nightfall. The truck list lives as reference data: which class each truck is, which customer it hauls for. A ticket claiming a township tandem that's actually Voss's quad gets flagged instead of blended.

The per-load price becomes a billing rule tied to truck class, so the load stops being a unit nobody defined. A day that arrives at the office as one lump line, nineteen loads and no serials behind them, isn't invoice-ready. It gets flagged as non-compliant that day, not priced on trust. Invoice totals get assembled from per-load tickets that cleared, and from nothing else. That machinery (digitizing, flagging, rules, reference data, totals) is the part Termco builds. The pad and the thirty seconds are yours.

flowchart TD
  subgraph W["The windshield today"]
    A["Bucket count at the loader"] --> B["Grease pencil mark on the glass"]
    B --> C["Phone call at close: 19 for Voss"]
    C --> D["Invoice line: 19 loads x rate"]
  end
  subgraph P["A ticket per load"]
    E["Numbered pad ticket, one per load"] --> F["Captured and checked that day"]
    F --> G["Priced against the load rate for that truck class"]
    G --> H["Invoice assembled only from tickets that cleared"]
  end

You can test your own site in one week without changing anything at the pit. Each regular driver keeps his own count, loads hauled per day, on whatever paper lives in his cab. Friday, set the drivers' counts against the tally that got phoned in. If the numbers agree all week, your operator is better than the setup deserves. Whatever daylight shows up between them, multiply it by your load rate and your season, and that's what the windshield costs.

If you'd rather have a second reader on it, send 10-20 sample tickets to hi@termco.ai. Include tally sheets and per-load invoices from unscaled sites, and we'll send back what we find within 48 hours.