Four Yards on a Ten-Yard Truck

The batch ticket from Saturday morning is perfect. Four yards of 4,000 psi mix, water added on site, left the plant at 7:42, and every word of it is true. The truck it rode on holds ten. The invoice goes out Tuesday at four yards times $148, which is $592, and the clerk who keyed it would pass any audit you could run, because she billed exactly what the ticket says.

Your rate sheet says short loads under five yards carry a $175 fee. It has said so for years. The fee isn't on the ticket, it isn't on the invoice, and the distance between those two documents is what this piece is about.

The event is the trip

One ticket, one billable event. The principle sounds like it's about not losing tickets, and mostly it is. But it cuts a second way: the billable event is the whole event. A quantity of material understates the event. A delivery is a truck, a driver, a washout, forty minutes of road each way, and a ten-yard drum sent out more than half empty. The material is just the part of the event the batch plant can weigh.

That's why the minimum exists. The four-yard trip consumes nearly everything the nine-yard trip does; only the revenue shrinks. Your short load fee is the clause that keeps small orders survivable, and it was priced by somebody who understood that, probably after a season of driveway pours that lost money politely.

The same clause wears other uniforms up and down these industries. The 20-ton delivered minimum at the aggregate yard. The four-hour minimum on hourly trucking. The trip charge on a field service call, the minimum bushel charge on a short grain haul. Every one of them says the same thing: below this line, you're buying the trip, not the ton.

And every one of them shares a defect. The minimum lives on the rate sheet, and the rate sheet is not the document that reaches billing. The ticket is. The ticket reports what happened: four yards, or 11.3 tons, or two hours, whichever ticket your trade prints. And what happened is precisely the thing the minimum exists to overrule.

Three desks where the fee dies

Follow a short load from phone call to invoice and the fee gets three chances to disappear.

The first is the order desk. The customer hears "there's a $175 short load charge" and pushes back, and the dispatcher, who has a plant to keep busy and a competitor across town, says we'll take care of you this time. Maybe that's the right call. But it's a pricing decision, made verbally, at 7am, by the person most motivated to say yes, and it's recorded nowhere a billing clerk will ever look.

The second is the ticket itself. A batch ticket prints material. A scale ticket prints weight. Neither has a line for the fee, because the machine that prints them has never read your rate sheet. So the one document that travels from the truck to the office is the one document guaranteed not to know the fee exists.

The third is the billing desk, and this one is the quiet killer. The clerk bills the ticket. Of course she does: the ticket is the most defensible number in the building. Billing more than the ticket says feels like inventing a charge, and if she's wrong, the phone rings Friday and she's the one explaining a $175 line to an angry contractor. If she skips it, nothing happens. Nobody has ever called to report an invoice that was too small. Each desk defaults the same direction.

Count a month of it. Say your plant runs 26 loads under the minimum and the fee shows up on 4 of them, the ones where the customer was a stranger. That's 22 waived at $175, which is $3,850 a month, call it $46,000 a year if the season held, given away on exactly the deliveries that lose money without it. Your biggest loads subsidizing your smallest is a strategy some operations choose on purpose. The arithmetic above wasn't chosen by anyone.

flowchart TD
  A["Batch ticket: 4 yards, all of it true"] --> B{"What does the invoice bill?"}
  B -- "the ticket alone" --> C["4 yards at $148"]
  C --> D["Fee on the rate sheet never attaches"]
  B -- "ticket plus rule: under 5 yards, no exemption on file" --> F["Fee line attaches: $175"]

Enforce it or delete it

Here's the claim your sales side will fight: a short load fee that bills on 4 loads out of 26 isn't a fee. It's a bluff, and your regulars have called it. Either the fee attaches to every qualifying ticket automatically, with exemptions decided by name, in advance, in writing. Or you take it off the rate sheet, raise your small-order price to what small orders actually cost, and stop printing a number you don't collect.

The pushback is fair. Small loads are how you meet the contractor who pours the big job in June. The brother-in-law of your best account should probably not get a fee on his garage slab. The plant across town waives theirs every time. All true, and none of it requires the fee to die at a phone call. Exempt the account, by name, as a decision that survives the week and shows up wherever the billing gets done. What can't survive is the current arrangement, where the rate sheet states a policy and the invoice reports a mood.

There's a slower cost than the money. Customers who paid the fee eventually compare notes with the ones who didn't, and from then on every number on your printed sheet reads as an opening position.

Let the rule read the ticket

None of this needs a new ticket, a changed batch sequence, or a driver doing anything differently. The paper stays what it is; it was never the problem. The ticket's job is to be true, and it already is. The missing piece is a rule that reads it.

The minimum is a billing rule: the threshold, the fee, which products it rides on, with effective dates. Which accounts are exempt is reference data, keyed once when somebody actually decides. Tickets get digitized daily, and a ticket under the threshold with no fee line and no exemption behind it gets flagged as non-compliant that day, while dispatch still remembers the phone call. Invoice totals assemble only from tickets that cleared. That slice is what Termco builds: digitizing the tickets, flagging the ones that break a rule, structuring the billing rules, managing the reference data, assembling the totals. Who gets the fee waived stays entirely your call. It just becomes a call you made once, on purpose, instead of 22 times a month by default.

Pull the short tickets

The test takes an hour. Pull ninety days of tickets under your stated minimum, then pull the invoices they fed and count the fee lines. Two numbers. The gap between them, times your fee, is what the bluff cost you, and unlike most leaks this one names its own fix: the fee was already on the rate sheet. You wrote the policy years ago. The only question is whether your invoices have been reading it.

If you'd rather have a second reader on it, send 10-20 sample tickets to hi@termco.ai, loads under your minimum especially, and we'll send back what we find within 48 hours.