Nobody Bills the Weekend

Saturday, 6:40 in the morning. A paving contractor is chasing a Monday deadline, so your pit opens early to feed them. The office is dark. The weigh clerk is off until Monday, and the loader operator is running the scale between buckets, the way he does most weekends. By one o'clock, 38 loads have gone out the gate. Most of the tickets printed clean. Four came off the backup pad after the printer jammed at 9:20, and two of those carry job numbers the loader operator caught over the radio while a truck idled on the deck.

Nothing about that morning was sloppy. It was a good Saturday: big tonnage, a happy customer, no waiting. But look at what the operation just did. It sold six hours of material with the entire billing apparatus at home. Every load that left recorded itself once, in whatever form the moment allowed, and nobody will read any of it until Monday.

Your office runs Monday to Friday, eight to five. Your operation doesn't. That mismatch is a leak with a schedule.

Monday keys what Saturday remembers

Monday at 7:30, the weekend stack is sitting on the billing clerk's desk: printed tickets, pad tickets, a sticky note from the loader operator that says "Kramer took 2 more after I left, ask Danny."

Here's what goes wrong, in order. The missing ticket first: one pad copy rode home in the loader operator's coat and won't surface until it goes through the wash. That load has no paper on the desk at all. Nothing about the stack announces what isn't in it.

Then the duplicate. The printer jam got cleared at 9:40, and the scale software reprinted the load it had in the buffer, the same load a pad ticket already covers. So the stack still holds 38 pieces of paper, but they describe 37 loads: one load twice, one load never. Monday's clerk has no way to know that. She keys the printed ticket because printed tickets are what she keys, and she keys the pad ticket because pad tickets from the weekend are exactly what she's been told not to lose. One load, two lines, and the customer's project accountant will find the pair before you do.

And the miskey. "Job 4-11" over a scratchy radio becomes 411 on the pad, which happens to be a real job, a county job, with a different rate and a different haul zone. The load bills. It bills the wrong work at the wrong price, and every count you run says it's handled.

None of this needed a weekend to happen. All of it happens more on weekends, because the person recording the load is doing two jobs at once, the tools are the backup tools, and the keying happens two days later, by someone who wasn't there, working from paper and a sticky note instead of from the morning itself.

Your densest hours are your worst documented

Here's the part worth arguing about: Saturday isn't a smaller version of Tuesday. It's a different population of loads, skewed toward exactly the ones that leak.

Weekend work is rush work. Rush work means jobs that got set up by phone on Friday night, job numbers that don't exist in anyone's system yet, walk-in cash customers with no account, and rates quoted at the gate by whoever answered. Those are the hardest loads to bill on a Wednesday with a full office. On a Saturday they're being captured by a loader operator on a pad.

Put rough numbers on the season. Call it 20 working Saturdays between April and November, 35 loads each at a $310 average. That's $217,000 of weekend revenue. If each Monday stack quietly loses one load and underprices another, the season's weekend leak runs $8,000 to $10,000, hiding inside your best production days. The doubled load costs you separately: a credit memo, plus a customer who now reads every invoice with a pencil. If you can prove your stacks don't do this, skip the rest of this post. The Saturdays that felt the best, the ones with the most trucks, are the ones with the most pad tickets and radio job numbers in the pile.

An owner who has run weekends this way for fifteen years will say he's never had a problem. Ask him what a weekend problem would look like from where he sits. A Saturday that leaked and a Saturday that didn't produce the same Monday stack and the same paid checks. The absence of complaints is what this leak is made of. Overbill a customer and the phone rings. Drop your own load in a coat pocket and the only party who could complain is you, and you're the one who doesn't know.

flowchart TD
  A["Saturday load crosses the scale"] --> B{"Who records it?"}
  B -- "scale prints clean" --> C["Ticket in the tray until Monday"]
  B -- "printer jammed: backup pad" --> D["Pad ticket, radio job number"]
  D --> E["One copy rides home in a coat"]
  C --> F["Monday: clerk keys the stack cold"]
  D --> F
  F --> G["38 lines keyed for 37 real loads, one on Job 411"]

Give Saturday the same paper as Tuesday

You don't need to staff the office seven days. You need the record read the day the load happens, not two days later.

Digitize tickets as they're written, weekend included. A pad ticket photographed and captured at the gate on Saturday morning enters the same machinery as a printed one on a Tuesday: it gets checked against every ticket already captured, so the reprinted buffer load and the pad ticket that describe the same truck at the same minute get flagged as a duplicate that day, not discovered by the customer's accountant in October. A job number that matches nothing in your reference data gets flagged too, on Saturday, while the loader operator still remembers which contractor was on the radio and Danny still remembers what Kramer took.

The Friday-night job deserves paper before it deserves trucks. A standing rule, written where billing can see it: no load leaves against a job that isn't set up, and any ticket that does gets flagged as non-compliant at capture instead of parked in a folder. Rates quoted at the gate stop being quotes the moment they're keyed as billing rules with effective dates, so the Monday clerk prices against something written down instead of against what somebody remembers saying. Termco's part is that machinery and nothing more: capture the tickets whenever they happen, flag the ones that don't reconcile, hold the rules and reference data, and assemble invoice totals only from tickets that passed. Whether you open the pit next Saturday stays your call.

You can size your own weekend gap in an hour. Pull last month's Saturday tickets and read the keying dates against the haul dates. Then pick one Saturday and reconcile it hard: loader counts or dispatch notes against invoice lines, load by load. If everything ties out, your weekends are tighter than most. If it doesn't, you've found the day of the week your money leaks.

If you'd rather have a second reader on the stack, send 10-20 sample tickets to hi@termco.ai, weekend and pad tickets especially, and we'll send back what we find within 48 hours.