Fictitious Pickups: How to Verify Who Is Collecting a Load

The carrier is approved. The pickup number is correct. A different driver arrives. Before releasing the load, your team needs to establish who that person is and whether the carrier assigned them.

Freight pickup verification connects the approved carrier, the driver who arrives, and the load being released. Driver identity verification helps establish who is collecting the freight. The release decision also needs a separate answer: is that person authorized for this specific assignment? A legitimate carrier record, a genuine ID, and a valid pickup number each answer only part of that question.

The useful place to connect them is before the asset leaves your control.

A real carrier record can still be used by the wrong person

FMCSA warns that freight fraud can involve someone using another carrier's USDOT number without authorization. Checking a company record is important, but it does not establish that the person at your gate represents that company.

In a fictitious pickup, someone poses as an authorized carrier or driver to collect freight. CargoNet describes fictitious pickups as cargo theft by deception, including carriers using fake IDs or fictitious businesses set up to divert and steal cargo. Plausible shipment details can make the request look routine without establishing that the person has permission to take the load.

Not every mismatch involves a knowing participant. A real, properly licensed driver may be following instructions from someone who has taken over the load or is posing as the carrier. An identity check helps establish who the driver is. It does not prove that the carrier assigned them to this load, which is why the assignment needs its own confirmation.

Consider a hypothetical warehouse pickup. The carrier is approved and the appointment is correct. Shortly before arrival, a message supplies a replacement driver and a new callback number. The truck arrives with the right reference.

Your team now has a changed assignment to resolve. Asking the person who supplied the new number to confirm the change creates a circular check. A better procedure confirms the change through a previously established carrier contact and names a person on your team who can authorize the update. A known dispatcher can legitimately report a change; what matters is that you do not rely solely on a new number or email supplied with it.

Use three separate checks

• Company. Question to resolve: which business did we approve? Example evidence: the carrier record and an established relationship.
• Person. Question to resolve: who is completing this pickup? Example evidence: appropriate identity evidence and a comparison to its holder.
• Assignment. Question to resolve: may this person collect this asset now? Example evidence: a confirmed dispatch assignment and release authorization.

Expand

Keep the answers visible to the release operator. A single green “verified” badge is difficult to use if nobody knows whether it refers to the company, the driver, or an earlier transaction.

Freight pickup verification: a six-step checklist

1. Establish the expected pickup and its owners. Before arrival, give the release team the approved carrier, expected driver, equipment details, and load reference through an established channel. Name the person who checks the arrival, the person who can approve a change, and the contact used to resolve a mismatch. If the driver, carrier, equipment, or instructions differ from the approved pickup, hold the release and resolve the difference through the established contact.
2. Give the driver clear instructions. Explain the identity check before arrival, who is requesting it, and how to recognize the legitimate request. Offer a support route for an incompatible phone or unsuccessful capture.
3. Check the person using an approved method. Depending on the workflow, this may involve physical-document inspection, document validation with a live-person comparison, or a supported digital credential. Choose the method for the risk and operating conditions. Reading a license barcode alone only extracts data; see how ID scanners work for what a scan does and does not prove.
4. Match the result to this pickup and the person at the dock. Connect the verification reference to the assigned driver and the load, and confirm that the person in front of you is that verified driver. A remote check alone does not establish who arrived. View the result in your approved system, linked to the pickup, rather than accepting a screenshot or a success message on the driver's phone. A previous result should have a defined validity policy; it should not silently become permission for every future release.
5. Check the equipment and resolve changes before release. Compare the carrier name and identifying numbers on the truck with the approved carrier, and record tractor and trailer plates, as FMCSA recommends. Treat an unexplained difference as a reason to hold the release, not as an automatic conclusion of fraud, and resolve it before the load leaves. Confirm replacement drivers, equipment changes, and altered instructions through a previously established carrier contact, not only a new number or email supplied with the change. Document the authorizer and the assignment they approved.
6. Record the release decision. Keep the decision, time, transaction reference, verification reference, and any exception approval. Limit access and retain information according to your policy and obligations.

Make the exception path usable

A failed scan, unavailable service, or driver change should trigger a defined next step. It should not force the gate operator to invent a new policy with a truck waiting outside.

For example, set a procedure for an unreadable card: explain the issue, permit an appropriate retry, and escalate to an approved alternative if it remains unresolved. Handle an assignment mismatch separately. Better lighting cannot establish dispatch authorization.

Also decide what happens when the system is offline. A lower-assurance fallback might be suitable for some activities and unacceptable for others. Name who makes that decision, what evidence they need, and whether release must wait.

Write the escalation plan down. Define who handles a changed driver or changed equipment, which loads call for additional checks, and how staff practice the procedure before they need it. Fit the controls and the training to the risk. Set baseline checks for every pickup, then define when the commodity, lane, carrier relationship, shipment value, or a last-minute change requires additional evidence or approval.

A controlled exception for a replacement driver

Return to the hypothetical pickup with a last-minute driver change. The gate operator puts release on hold and sends the change to the designated dispatch owner. That person contacts the carrier through a previously established channel, confirms the replacement driver's assignment to this load, and records who authorized the update. The operator then connects the replacement driver's identity check to the revised assignment.

If the carrier cannot confirm the change, the load stays on hold under the escalation procedure. A convincing explanation, a matching pickup number, or a successful identity check should not substitute for the missing assignment approval. The exception resolves the changed assignment before release rather than allowing staff to skip it.

Keep a minimal release record

The release record should let a colleague reconstruct the decision without collecting another copy of every identity document. A practical starting point is:

• The load reference, pickup location, and approved carrier.
• The assigned driver reference, observed carrier markings, and tractor and trailer plates, with any discrepancy and its resolution.
• The verification reference, result, and time relevant to this pickup.
• Any changed instruction, the person who approved it, and the confirmation channel used.
• The final release or hold decision, its owner, and the time.

Set access and retention rules for that record. Document images and other underlying evidence need their own purpose and controls; they should not automatically be copied into gate logs, email threads, and dispatch messages.

Keep the routine release log separate from incident evidence. If something goes wrong, have a process to promptly preserve the relevant camera footage, gate records, and vehicle details for investigators. That process does not require spreading copies of driver IDs across your systems.

Before requesting another emailed CDL image, ask which people need the underlying evidence and which only need the result. A release operator may need confirmation and a reference rather than another permanent document copy. Our article on the privacy risks of improvised driver verification explores that tradeoff.

Where Stile fits

Stile's identity verification software combines document checks, liveness, and face matching in a verification flow. Its logistics identity verification and carrier and driver identity pages describe applying person checks at onboarding, trip assignment, and pickup.

That addresses the person check. Your dispatch and release process still decides whether the verified person is assigned and authorized to receive the freight.

Start by reviewing one recent pickup with a driver change. Could a colleague reconstruct who checked the person, who approved the assignment, and why release was allowed? Any missing answer is a useful place to improve the procedure.

Sources: FMCSA, Broker and Carrier Fraud and Identity Theft; CargoNet, Identity Theft Submission Form. The checklist is Stile's proposed operating framework, not an FMCSA-mandated procedure.