212 Loads by Your Count

The chopping's done, the bunker's covered, and you're at the farm kitchen table to settle up. Your number is 212 loads off the east 80. You know it's 212 because each truck driver clicked a tally counter every time he pulled away from the chopper, and you added the three counters up last night in the shop.

The farmer has a number too. His packing tractor driver kept a tally on the whiteboard in the cab, four strokes and a slash, a row for each day. It says 208.

You'll settle at 208. Not because he's right, but because his count is written down where the feed landed, and yours is one integer in a plastic clicker window with nothing behind it. At $150 a load across chopping and hauling, you just handed back $600 on one field. Run 18 farms a season and give back a handful at each, and harvest shorts you ten or eleven thousand dollars a year, a number you get to see for about a minute at each kitchen table and can prove exactly never.

Harvest outran the paper

Nobody decided to stop writing tickets. The chopper decided.

A self-propelled chopper in good corn fills a truck every nine or ten minutes. Three trucks cycle between the field and the bunker, and the economics of the whole day hang on the spout never waiting. A driver filling out a carbon ticket while the chopper idles is a driver burning your margin, so the ticket book stayed in the glovebox and the clicker came out. Click, pull away. It feels like the same record, only faster.

It isn't. A ticket is a record of an event: a load number, a time, a truck, a field, a destination. A count is just a number. No parts, no body. When your 212 meets his 208, there is nothing to reconcile, only something to negotiate, because neither number can be opened up. You can't find a missing load inside an integer.

Where the four loads went

Probably nobody stole them. One went to the overflow pile by the heifer lot, on the farmer's own instructions, where the packing driver never saw it land. Twice in one afternoon that driver climbed down to grease the push-off blade, and a truck dumped behind his back each time. The fourth is anyone's guess, a stroke he meant to make after a phone call and didn't, and that's just the week anybody can reconstruct. All four misses are his, and his is the board you'll settle from.

Notice that none of this is a dispute about work. The corn got chopped. Every one of those loads burned your diesel and a driver's hour. The only thing missing is the paperwork, and at the kitchen table, the paperwork is the whole game.

flowchart TD
  A["Load leaves the chopper"] --> B["Clicker: adds 1 to a total"]
  A --> C["Ticket: load number, field, time"]
  B --> D["Totals disagree at settlement"]
  D --> E["Negotiate, take the lower number"]
  C --> F["Line items reconcile load by load"]
  F --> G["Invoice defends itself"]

Written beats remembered

At settlement, specificity wins. His tally has rows: twelve loads Monday, forty-one Tuesday, rained out Thursday. Yours is a total. The side holding line items sets the figure, and the side holding a total signs it. And look at who keeps the written count in this arrangement: the one who pays the bill.

Plenty of operators will tell you it evens out, his count high one year, low the next, split the difference and stay friends. It doesn't even out. Disagreements settle toward the written number, the written number is kept by the buyer, and a count that can't defend itself loses by a little, in the same direction, every time. Splitting the difference just fixes the discount at half.

A count also can't carry a rate. If the far bunker pays a haul premium, or the east 80 belongs half to a landlord who gets his own bill, those distinctions have to survive the season in somebody's memory. A clicker holds one number. It all gets sorted out in February, by whoever's left to remember, which is the polite way of saying it doesn't.

The ticket died in the office, not in the cab

Here's the part worth arguing about: a paper ticket survives harvest pace just fine. A numbered book on the dash, circle the field, scrawl the time, drop the carbon in the coffee can nailed to the post at the bunker. Fifteen seconds, and the driver spends longer than that waiting for the packing tractor to clear the pile. Drivers wrote tickets at this pace for decades.

What the ticket couldn't survive was November. Seventy loads a day for a month is two thousand tickets, and somebody in a farm office was supposed to key every one, match them to fields, and build settlements out of the pile. Nobody had that somebody. So the trade got made: a paperwork problem you could see for a leakage problem you couldn't, and the clicker got called progress.

That trade is the part that's expired. A numbered book polices itself: if ticket 141 never comes out of the coffee can, the gap says so, which is more than any clicker ever told you. The office half is what Termco does. It reads the tickets as they come in, carbons and all, as written; a load number arriving twice gets caught instead of invoiced; per-field rates and the landlord split sit as billing rules; and the settlement assembles itself from the tickets that cleared. No driver installs anything, the book on the dash is the same book from the co-op counter, and the clicker can stay in the cab as the cross-check it should've been all along.

If any part of your operation already runs on tickets, send 10-20 of them to hi@termco.ai and you'll have findings back within 48 hours.

The farmer's 208 won the table because it was written at the pile, stroke by stroke, by the man who watched every load land. No referee would call that unfair. The count written where the goods arrive has beaten the count remembered on the road for as long as anyone has hauled anything. Next season, be the side with 212 line items.