On the morning of 14 September, two men arrived at a warehouse in New Castle, Delaware, identified themselves as FedEx employees, and presented driver's licenses and shipping documents for a trailer holding more than $680,000 in electronics. The trailer was released. They hooked up and drove away, according to FreightWaves.

It was recovered days later in Newark, cargo intact, and one man was arrested. The charges filed by Delaware State Police describe the pickup better than any summary could: felony theft, two degrees of forgery, conspiracy, and a fictitious registration plate.

Every Artifact Was Inspected, and Every Artifact Passed

Work backward from those charges. The driver's licenses were fraudulent. The plate was fictitious. Each artifact was presented, each was looked at by someone doing their job, and each was accepted.

That is why "inspect the documents more carefully" is the wrong lesson. Authenticating what a visitor brings is an arms race against whoever made it: the visitor chooses what to bring, and has already decided it will survive the look it is going to get.

However, forged paperwork still has to name a real shipment. The PRO on it either matched a load the facility was expecting or it did not, so there was something to check it against. Whether anyone at the gate could check is another matter.

For many shippers the system of record at the point of freight release is a spreadsheet, a radio and somebody's memory. WMS and TMS seats cost money, so the yard jockeys and guards who actually hand over freight are the last people to get one. In a congested yard, a check that means walking inside to ask someone is a check that does not happen. Latency is what turns a procedure into a formality.

Four Questions at Every Handoff

A release looks like one decision. It is four. Most facilities answer the first two and assume the last two are unknowable. They are not.

The Answer Exists. It Is Rarely in One Place.

No public registry will answer the last two. Federal carrier data is carrier level, and the driver level record that does exist, the Pre-Employment Screening Program, is for motor carriers and requires the driver's written consent.

So the detail has to come from the carrier. None is obligated to tell a shipper who is driving; where it shows up, it shows up because someone asked, because the contract requires it, or because a platform in the middle passes it along. It is a commercial arrangement rather than a feature of the market, which means it is one a shipper can negotiate.

As far as the data available, when it does show up, it rarely arrives in one piece. The tender sits in a TMS. The appointment sits in a WMS. The driver's name and cell come over in a text, a WhatsApp thread or a call to the guard shack. The BOL is a photo on somebody's camera roll. The lumper keeps separate notes. The load board holds a version of the same shipment nobody reconciles against the other two. Carrier EDI has carried the structured part for decades, and load boards carry the equivalent through portals and APIs. But structured data is a slice. The rest is scattered across systems and habits never built to be read together, least of all by the person releasing the freight.

Some of it is disclosed plainly:

"Sharing carrier drivers' name, vehicle truck number and vehicle license number with third parties, such as a pickup facility."

"Sharing carrier drivers' names, vehicle license numbers, vehicle truck numbers, and location with other users, or third parties such as operators of a receiving facility, or the receiving party."

Privacy notice of one major digital freight platform, last modified June 2025

Read that for what it is. It covers freight through that platform, carried by carriers contracted to it: a channel rather than a source, holding the detail because its carriers supplied it.

Where the Proof Has to Come From

Which reframes the question at the gate. Not "how do I inspect this driver more thoroughly," but "does this driver match what the carrier told me was coming." No amount of forgery survives that, because the proof originates on the other side of the transaction, where the driver at the gate has no influence over it.

• The tender itself, which is where this starts. Carriers will not volunteer driver and equipment detail; it arrives reliably only on lanes where somebody made it a term of the load.
• The carrier on the load. Validate the DOT or MC number claimed against federal registration, then reconcile it against the carrier the load was tendered to.
• The driver on the dispatch. An impostor can type any number at a kiosk. What they cannot do is make it match the number the carrier put on the dispatch, or receive a link sent to the real driver's phone.
• The equipment on the dispatch. Compare the tractor, trailer and plate the carrier named against what rolled through the gate.

How Aquatio Works at the Handoff

At a facility running Aquatio, the driver finds the load at a kiosk tablet, searching by PRO, BOL or carrier. Nothing else happens until a specific shipment is identified. The driver checks in against that load and enters a contact number, and Aquatio sends a link to that phone, where the pickup is completed and signed in Aquatio Lite. On brokered freight the link goes directly.

That binding is what makes assembly possible. Because every artifact attaches to one shipment via multi-party workflow rather than to a clipboard or somebody's memory, the pieces spread across a TMS, a text thread, a load board and a photo land in one trusted custody execution record, in front of the person deciding whether the trailer leaves. And it persists through to proof of delivery, so the shipment carries one continuous history rather than a check-in log at one end and a signature at the other.

Today that number is the driver's own, which is exactly what makes it worth reconciling. Aquatio is building that comparison into check in, alongside the carrier and equipment checks.

What Aquatio is not is worth stating. It is not identity verification and it is not telematics; both belong in the stack. Aquatio contributes the trusted custody execution record itself: binding a driver to a shipment, assembling what is known about it where the decision is made, and carrying it through to delivery.