Signed by Somebody

Delivery tickets print in duplicate for one reason: so two people who watched the same load can keep the same story. The white copy rides back to your office. The yellow copy stays on the job. The thing that binds them is a signature at the bottom, and that scribble is doing more collections work than anyone in your building gives it credit for.

Most of the time you never find out, because most customers pay. The signature earns its keep on the loads that get argued, and by then it's eight months too late to go get one.

Ninety seconds of shared custody

One ticket, one billable event. The principle is usually read as an instruction to your office: don't lose paper, don't key it twice. But an event has two parties, and an invoice is a list of claims you're making against the other one. Twenty-two loads of base rock to the Harmon site in March isn't a fact because your tickets say so. It's a fact because somebody on their side agreed it happened, load by load, while it was happening.

There is exactly one window where that agreement is cheap. The truck is on the site. The rock is on the ground, visibly new. The superintendent, or the laborer he sent, is standing at the tailgate, and the driver is holding a book and a pen. Five seconds of that man's time converts your claim into a record both companies already accepted. Call it ninety seconds of shared custody per load, and it never comes back. By April the pile is spread and compacted under a slab. By closeout the super has moved two jobs down the road, and your white copy has quietly changed from a receipt into testimony.

What the closeout pays for

Run the version of this that shows up in collections. You supplied a commercial site for five months: 287 delivered loads, invoiced monthly, paid steadily minus retainage. At closeout the GC's project accountant does her job, which is matching your invoices against the yellow copies in the job trailer. She finds 31 of your loads with no signature and 6 more signed with a loop of ink nobody can attach to a name. Her letter offers payment on the balance and asks you to substantiate the rest.

Substantiate with what? Your own tickets, printed by your own scale, driven by your own driver. At 24 tons and $15.50 delivered, call it $370 a load, there's roughly $13,700 on the table, and your evidence for all of it is paper that only your side ever touched. You'll settle somewhere in the middle, and both of you will call it reasonable.

Notice what never gets argued: the 250 signed loads. Nobody writes a letter disputing a ticket their own foreman signed, dated, at 9:40 on a Tuesday. The fight only ever forms around the blanks, which means the blanks were never really billed. They were proposed.

The scribble deserves its own sentence, because "signed by somebody" is its own leak. A signature from a laborer who had no authority to receive material holds up worse than you'd hope when the GC's letter says, politely, that this is not a recognized receiver. You hauled the load. A stranger vouched for it.

flowchart TD
    A["Load delivered: 24 tons base rock"] --> B{"Ticket signed at the tailgate?"}
    B -- "yes, by the foreman" --> C["Both sides hold the same record"]
    C --> D["Closeout: matched and paid"]
    B -- "no, or a stray scribble" --> E["Only your copy tells the story"]
    E --> F["Closeout letter: substantiate these loads"]
    F --> G["Settle in the middle"]
    B -- "unsigned on purpose, per account" --> H["Decision on file, made in daylight"]
    H --> D

No signature, no silence

Here's the claim your dispatcher will fight: an unsigned ticket should be treated as an open problem the same week it's written, not as revenue with an asterisk. You already have a system for customers who take material without acknowledging it. It's called a credit decision. A site that won't sign is borrowing on terms nobody approved, and the current arrangement approves it one blank line at a time, by default, at the tailgate.

The pushback is real, and about half of it wins. Night paving doesn't stop so a driver can hunt a signer through the paver's light plant. Nobody is standing at a farm field when lime gets spread at 7am, and the stake by the driveway where you dumped the sand can't hold a pen. Fine. Those deliveries are unsigned on purpose, and that's a decision an owner can make once, in daylight, per account: this customer, this site, we deliver on our own record, because the relationship or the gate situation justifies it. What can't survive is the version where the driver makes that call 40 times a day by how hurried the site feels, and the office finds out which loads are testimony only when the letter comes.

The last era of software had an answer for this, and it was worse than the blank. The POD app: a phone thrust at a concrete finisher in the rain, who signs glass with a knuckle, when the app cooperates and the site has signal. Ask any driver who lived through one: receivers wouldn't touch it, so by the end of the season the drivers were signing it themselves at the end of the shift, which turned the evidence into something worse than nothing. The carbon book and the pen were never the problem. They're the most dispute-proof technology on the truck.

Find the blanks on Thursday

The fix is reading the paper you already have, sooner. Tickets digitized the day they're written, as written. A rule that says which accounts require a signed ticket, so a blank from a signature-required site gets flagged that day. The driver still knows it was the super's guy in the green vest, and he can get it corrected on tomorrow's run. Who's authorized to sign for each account is reference data, kept current, so your office can question a scribble in week one instead of at closeout. Invoices assemble from tickets that cleared. That's the slice Termco does, and nothing about it touches the truck: same book, same pen, same ninety seconds. The only thing that changes is how long a blank line stays invisible.

Count your testimony

The test takes an afternoon. Pull 90 days of delivered tickets and sort them into three piles: signed by someone you could name under oath, signed by somebody, and blank. Price the second and third piles at your average load. Then pull your last two project closeouts and look at which loads got credited. The overlap won't surprise you, but the total might.

If you'd like a second reader, send 10-20 sample tickets to hi@termco.ai, delivered loads especially, and we'll send back what we find within 48 hours, the blanks and stray scribbles included.