ELD Clearance

From the day a truck is registered to the proof only its carrier can offer

A truck's whole working life can be a single signed ledger — one the carrier owns, that many systems write to, and that is tamper-evident: any later edit shows. Here is that life, start to finish, and why it ends in a proof the carrier can assemble and present that no database can match.

This is the system FreightProof is building. The working v1 runs end to end today on the data shapes the major ELD platforms return; going live needs one fleet's read-only authorization. The story below is told in the present tense — that is the design, not yet a deployed fleet.

THE SIGNED LIFE OF A TRUCK serviced → back to dispatch ① Registerwallet created · VIN-keyed ② Operatedaily signed records ③ Dispatchcheck-in → ④ Maintainbumper before red TRUCK WALLET · one ledger per truck many writers · carrier holds the keys · tamper-evident — any edit shows PROOFonly the carrier can offer Register → operate → dispatch → maintain → back to dispatch → a proof no database can match.

1. Registration — the truck gets a wallet

When the ELD is installed, the truck gets a data wallet: a per-truck ledger, keyed to the VIN. Genesis records are written and signed — the vehicle's identity, the carrier that operates it, the lease (signed by the lessor), the FMCSA safety record, the maintenance baseline. A QR goes in the cab; the driver carries their own QR — their identity. The carrier holds the keys.

From this moment the truck has a name that is math, not paint — and a ledger that will follow the iron, not the paperwork.

2. Daily operations — the ledger grows

Every day the truck works, its systems write to the ledger. The ELD signs hours-of-service, GPS, odometer, engine hours, the pre-trip inspection, the driver assignment. The fuel card writes a fuel event. The toll system writes a passage. The maintenance shop writes a service record. Each writer signs its own entry; the carrier owns the whole. Nothing can be altered after it is written without the change showing.

Over months the ledger becomes something you cannot fake after the fact — an un-backfillable record of exactly how this truck has lived. Tenure stops being a claim and becomes a record with receipts.

3. Dispatch — the green light

A load comes in. The carrier assigns it to a truck and a driver. The driver signs into the truck — their phone QR is their identity, and the ELD now binds driver → truck → location for the day. At the shipper's yard, the driver checks in. In that instant a zero-trust policy runs against the load's requirements:

  • Is this the dispatched driver, on the dispatched truck?
  • Is the truck actually here — confirmed by the live ELD GPS?
  • Does its safety record meet this load's minimum? Its insurance? Was a good walk-around done today?

    • Out comes a single answer — 🟢 GREEN, 🟡 YELLOW, or 🔴 RED. The broker sees the color and the carrier/driver/truck identity. Nothing else. RED means the truck cannot accept the load.

    That signed clearance is the record the question in Montgomery v. Caribe points to — what did you know about this carrier, driver, and truck when you committed to the load? (The fitness checks — safety, insurance, maintenance — can be answered the moment the carrier commits the truck, before it rolls; presence is confirmed here at pickup.) Steal the driver's QR and present it three states away and it fails — the live telematics don't put the genuine truck at the yard. We don't claim GPS can't be faked; we claim the bar moved from forging a $12 door sign to spoofing the real truck's live feed in real time without breaking a continuous, cross-referenced track — far harder, and detectable after the fact. And the broker keeps its own signed copy of the clearance: a receipt it holds, not a color it rents.

    4. Maintenance — the bumper before the wall

    Months in, the truck approaches a service interval. The carrier doesn't find out at the dock — the wallet tells them in advance: green today, but the PM is due in three days; this truck will go yellow Thursday and red next Tuesday if it isn't serviced. Zero trust, with bumpers.

    The carrier services the truck. The shop writes a signed "serviced" record, bound to the VIN. The truck never trips a red at a dock, because the carrier saw it coming — and because the shop's signature is bound to the VIN and sealed in the ledger, no one can quietly back-date a "serviced" record after a crash. (It can't prove the work was good — only the shop and the wrench can vouch for that — but it forecloses the after-the-fact paper trail, which is its own kind of defense.)

    5. Back to dispatch — cleared, and proven

    Serviced, the truck checks in for its next load and clears green. The maintenance event is now a permanent, provable part of the record — and because the ledger is keyed to the iron, it survives a DOT-number change, a new lease, a new operator. A chameleon carrier can repaint the door; the wallet remembers.

    6. The proof only the carrier can offer

    Here is the part the databases can't match. Every vetting tool in freight can check a record. The carrier — holding the keys to its truck's ledger — can assemble and present the whole of it: signed, sealed, continuous, cross-referenced, and tamper-evident — any later edit shows, and the ledger's fingerprints are anchored where even the keyholder can't quietly rewrite history. And the credibility doesn't rest on the carrier's word: it comes from the independent signers the carrier cannot forge — the lessor, the fuel and toll networks, the maintenance shop, the FMCSA snapshot. The carrier holds it; the issuers make it believable.

    When a broker, an insurer, a court, or the FMCSA asks "prove what was true," the carrier answers on short notice with provable details. Because the ledger's roots are anchored, the aim is that a withheld record shows up as a gap, not a clean story — selective disclosure that can't quietly become selective omission. It is the model the food industry is moving to under FSMA 204 (compliance extended to 2028): the owner keeps the traceability records and produces them — electronic and sortable — within 24 hours of a request.

    The data is the carrier's. The complete, owner-held proof is the carrier's to assemble and present — while every party it deals with keeps its own signed receipt of each clearance. The confidence is everyone's.

    This is what FreightProof is building: a DID provider on top of the ELD sync, a wallet that is a ledger per truck (the carrier's keys, the carrier's data), and a clearance that turns a driver's check-in into a green light a broker can trust and a carrier can prove. It runs on the ELD systems carriers already use — Samsara, Motive, Geotab — under the carrier's own authorization. See the technology, the Digital VIN, and the full zero-trust vision.