The Archive You Rent

The letter is from the landowner's attorney, and it's polite. Your pit sits on leased ground, the lease pays him $0.85 for every ton that leaves it, and paragraph nine gives him the right to audit your haul records five years back. He's exercising it. Produce the tonnage records for 2022 and 2023, within thirty days.

In 2022 those records lived in the ticketing system you'd been running since 2016. You cancelled it in January 2024, for ordinary reasons: the price went up, the rollout had never fully taken, half the office had drifted back to paper anyway. The bookmark to the login still works. The login doesn't. Your password lands on a screen that says the account is inactive and offers a sales number.

Somewhere in a contract PDF is the clause you initialed without reading: upon termination, customer data is available for export for ninety days, after which it may be deleted. The ninety days ended two and a half years ago.

The original moved out of your building

Walk back to what that generation of software did on the day it went live. Before it, the record of a load was a carbon ticket: written at the window, signed by a driver, stored in a numbered book, filed in a drawer you own, in a building you hold the keys to. The system replaced that with a row in a database, and the database didn't live in your office. It lived on the vendor's server, and what you held was a login.

Nobody presented this as a custody decision, but that's what it was. The brochure said your data is always yours, and in the narrow legal sense it even was. What the subscription actually bought was the right to look at it. Access that renews monthly is access that can lapse, and it lapses at the worst possible distance from the event: records get written this year and get needed three, five, seven years out, when the dispute or the audit finally arrives. A royalty lease, a sales tax exemption file, a public road job, a workers' comp claim with a date on it. Every one of those reaches back further than most of these subscriptions ever last.

The on-premise era wasn't safer, just slower. The server in the closet held version 7's database, which only version 7 can open, and version 7 wants a license key from a vendor that was acquired in 2019. A backup you can't open isn't an archive. It's a brick with your company's history inside.

The export isn't the archive either

Say you were diligent and pulled the export inside the ninety days. What arrived was a zip file of CSVs. Tickets, 31 columns. Customers. Products. Rates. It's all technically there, and almost none of it can do an archive's real job, which is to be believed by someone who's against you.

The attorney auditing your royalties doesn't want a spreadsheet your own office produced, sortable and editable, telling him 212,400 tons. He wants the thing a signed ticket is: a contemporaneous record, written at the scale on the day, in sequence, in ink, with a signature from a man who had no stake in next year's argument. The export preserved your data and discarded your proof. None of its 31 columns holds a signature.

flowchart TD
    A["2022: load crosses the scale"] --> B{"Where does the record live?"}
    B -- "vendor's database" --> C["2024: subscription cancelled"]
    C --> D["Export window closes"]
    D --> E["2026 audit: no records produced"]
    E --> F["Settle on the landowner's number"]
    B -- "carbon book in the drawer" --> G["2026 audit: pull the 2022 books"]
    G --> H["Signed originals, in sequence"]

And when nothing can be produced, the audit doesn't stall. It proceeds on the other side's arithmetic. The lease says records you can't produce get estimated against you, or if it doesn't, his attorney will argue it should, and he'll be standing on the stronger ground. Call it a 40,000 ton disagreement at $0.85. That's a $34,000 conversation you're having without a single document in your hand.

The box on the shelf

Here's the claim the software-minded will fight: a cardboard box of used ticket books in a storeroom is a better archive than a vendor's database, and it isn't close.

The objections are real, so take them head on. Paper burns and it molds. True, and those are physical risks you can see and insure, and a $40 tote on a dry shelf handles most of them. The database's risk is contractual and invisible, and when it lands it takes everything at once, every ticket from every year, on a date set by a billing system. Paper can't be searched. Also true, and an archive is not a search problem. You don't query it weekly. You open it twice a decade, under pressure, and what you need from it then isn't speed. It's standing.

A used ticket book needs no license, no login, no vendor, no version. It will be readable in thirty years by anyone who can read, which is a compatibility guarantee no file format has ever offered. The owners who kept their books weren't hoarding paper out of habit. They were declining to put the company's memory behind someone else's subscription, and the ones who've since sat through an audit with the originals on the table know exactly what that was worth.

Keep the original, rent the reading

None of this means the drawer is enough on its own. A drawer full of unread paper is where billing leaks live; most of what we write about here is some ticket that never became an invoice line. The fix was never to replace the paper, just to read it.

That's the arrangement Termco is built on: the carbon book stays the original, written and signed and filed exactly as your operation already does it. The software digitizes each ticket as written, flags the ones that break a rule, holds your billing rules and reference data in one structured place, and assembles invoice totals from the tickets that cleared. The signed paper never stops being yours, because it never leaves your building. What you rent is the reading, and the day you stop renting it, your archive is still sitting on your own shelf, in sequence, in ink. If you want to see what that reading finds, send 10-20 sample tickets to hi@termco.ai and findings come back within 48 hours.

Whatever you decide about the software, try this tonight. Pick a load from three years ago, any load, and try to put its signed ticket on the table in front of you. Time how long it takes. If the answer runs through a login, check whose name is on the renewal invoice, because that's the person who decides whether your 2022 exists.