Half This Load Goes Across the Road

The truck comes off the scale with 24.1 tons of crusher run and a ticket that says so: one weight, one product, one destination, one customer. Forty minutes later the foreman meets it at the gate and points with a rolled-up set of plans. "Drop fourteen here. Take the rest over to the Route 6 yard."

Reasonable request. Happens every week. The pit is nine miles out, the two sites are across the road from each other, and nobody's paying a truck to run half empty. The driver nods, dumps fourteen, and does what drivers do: writes "14 here / rest Rt 6" in the margin, gets the foreman's signature, and rolls.

Stop there and look at the paper. The scale printed that ticket when the load had one home. Now it has two. One billable event became two billable events, and the only record of the fork is a pen stroke that no system will ever read.

The ticket can't hold two answers

One ticket, one billable event. The rule usually gets broken by absence: the load that never got a ticket at all. A split breaks it from the other side. The ticket exists, the weight is right, the signature is real, and the document is now wrong about the one thing billing needs from it, which is who owes what.

Follow the serial to the office and watch the clerk try to key it. The system wants one customer, one job, one rate per ticket, because that's what a ticket is. The margin note offers arithmetic instead. So the clerk picks one of two bad exits. Key the whole 24.1 tons to the job printed on the ticket, and you've billed a customer for ten tons that went somewhere else, with their own foreman's signature apparently vouching for it. He signed for fourteen. His gate log says fourteen. That dispute writes itself, and it arrives with a credit memo attached and a customer who now reads your invoices line by line.

Or the clerk honors the note, bills fourteen to the first job, and now holds a remainder: 10.1 tons that need a customer, a job number, and a rate, none of which the ticket carries. If the Route 6 yard is a different job, it may be a different haul zone and a different price. If it belongs to a different customer entirely, the remainder stops being a keying question and becomes a missing account. Remainders like that get parked to sort out later. Some get sorted. The rest bill nobody, forever, on a ticket the count says is handled.

Farm operations run the same fork with bigger numbers on it. A tender truck leaves the plant with 12 tons of dry blend for two fields, and the second field is farmed on shares, with a landlord who pays his own fertilizer. The split lives in the applicator's head as acres, not tons. Call it five tons of the twelve on the landlord's side: at $520 a ton, that's $2,600 of product, and whether he's ever asked for it depends on a conversation the office never heard. Grain does it too: the last of the north field rides to town with the first of the south, one elevator ticket, two different share splits underneath it.

flowchart TD
  A["Scale ticket prints: 24.1 tons, one destination"] --> B["Foreman at the gate: drop 14 here, rest to Route 6"]
  B --> C{"Does the paper fork with the load?"}
  C -- "no: pen note in the margin" --> D["One serial, two drops"]
  D -- "exit one" --> E["Whole 24.1 tons bill to the job that took 14"]
  D -- "exit two" --> F["14 bills clean, the 10.1 remainder bills nobody"]
  C -- "yes: second ticket at the split" --> G["Each drop carries its own serial, job, and rate"]

Worse than lost

Your dispatcher will argue with this: a split load recorded in the margin is worse than a ticket that blows out the truck window.

The lost ticket at least fails loudly. It leaves a hole in the serial sequence, and a decent monthly count snags on holes. Somebody chases it, and the chase has a chance. The split ticket answers every count you run. One serial, present, keyed, billed. Sequence audit passes. Load count reconciles. And the whole time it's carrying an error in both directions at once: an overbill aimed at the customer most likely to catch it, and an unbilled remainder aimed at nobody at all. You built controls that count tickets, and this failure lives entirely inside one ticket.

The elevator down the road already refuses to live this way. Tell the scale window your corn is two-thirds yours and a third the landlord's, and the settlement splits at the ticket, by share, before anyone's memory gets involved. Elevators do that because they'd never accept a pen note as a division of ownership. Plenty of field operations accept pen notes as divisions of revenue all season long.

When the load forks, the paper forks

The fix is a rule you can say in one breath: a ticket names one drop, one payer, one quantity, and the moment reality stops matching that, somebody writes a second ticket. Fourteen tons stays on the first serial. The 10.1-ton remainder gets its own, cross-referenced to the first, signed at the second gate by the second site's people. Two minutes at the tailgate. Yes, it costs two minutes, and the objection that the truck's blocking the gate is real. So is the $2,600 riding on the applicator's memory.

The standing splits shouldn't depend on anyone's memory at all. A landlord share, or a customer whose orders always land across two yards: that's reference data, written down once with the percentages and the account each side bills to, so a split resolves to the right invoices without a conversation. Billing rules do the pricing: each drop against its own job's rate and zone, not both drops at whichever rate the original ticket happened to carry.

Then capture makes the leftover cases visible. Digitize tickets at turn-in and a ticket wearing margin arithmetic, or drop quantities that don't add back up to the printed weight, gets flagged as non-compliant the day it arrives, while the driver still remembers which yard took the rest. That's the piece Termco builds: tickets captured, the ones that don't reconcile to a single billable event flagged, standing splits held as reference data, and invoice totals assembled only from lines where the tons and the payer agree.

The check before any of that costs one afternoon. Pull a month of tickets and read the margins, not the fields. Count the ones with handwriting near the quantity, a second address, or the word "split" anywhere on the face. Then take any one of them and find where the remainder billed. If the answer takes more than five minutes to establish, you've found the leak, and every week your trucks make two drops on one ticket, it's running.

If you'd rather have the margins read for you, send 10-20 sample tickets to hi@termco.ai, pen notes and all, and we'll send back what we find within 48 hours.