Skip to main content

Shipment compliance: require driver documents on your loads

Configure the driver documents required on a load, apply them automatically by load type, and track each driver's compliance before dispatch.

Written by Tanuj Gupta

🎉 Premium feature — in beta. Shipment compliance lets you require and automatically verify driver documents on your loads. It's rolling out now, so some options may appear as they become available for your workspace.

What is shipment compliance?

Shipment compliance lets your workspace define the documents a driver must submit before a load is dispatched, apply those requirements automatically based on the type of load, and track each assigned driver's status right on the shipment. Chain checks every uploaded document automatically and flags anything that needs a human review — so your team only steps in when something can't be confirmed.

Shipment compliance vs. driver identity verification

Driver identity verification (a government-issued driver's license plus a live selfie) confirms the person picking up your load is who they say they are. Shipment compliance is the broader framework: it includes that identity check and adds equipment and freight document checks (cab card, truck VIN, license plates) and on-site confirmation. You can require identity as one step and add the others below.

This is separate from Verification on Chain, the company-level FMCSA email check that gives a carrier the blue verified icon. Shipment compliance is a per-driver, per-shipment check on the actual driver and equipment.

Document types you can require

  • Driver identity — government-issued driver's license and a live selfie. See Verify a driver's identity on a shipment for the full identity flow and what the driver sees.

  • Cab card — a photo of the vehicle's cab card / registration.

  • Truck VIN — a photo of the truck's VIN plate.

  • Truck license plate — a photo of the truck's license plate.

  • Trailer license plate — a photo of the trailer's license plate.

  • On-site confirmation — confirms the driver is physically at the pickup facility. See the Geofence Manager guide for how facility geofences are defined.

Every uploaded document is checked automatically. When a document can't be verified automatically, it's marked Needs review for a broker to approve or reject.

Set up compliance requirements

Workspace admins and owners configure compliance for the workspace (other members can view). You set a default set of required documents for every load, and add rules that require additional documents for specific kinds of loads.

  1. Set your default requirements — the documents required on every shipment. This can be left empty if you only want rule-based requirements.

  2. Add rules by load classification to require documents only when a load matches conditions such as high value, hazmat, commodity, carrier, customer, or origin/destination city, state, or warehouse (facility) name.

  3. Rules are evaluated in priority order — the first matching rule's documents apply; if no rule matches, your default requirements apply.

  4. Optionally set a completion window — how long the driver has to finish the required documents before the request expires.

  5. Save. New and updated shipments are evaluated automatically against your configuration.

Track compliance on a shipment

Open a shipment to see the Compliance panel. For each assigned driver it shows the required documents, each document's status, and an overall "X of Y complete" summary. Click a driver row to open the full verification detail — the uploaded documents, extracted data, and checks.

Review documents that need attention

When a document is marked Needs review, open the driver's detail from the Compliance panel and approve or reject each flagged document. The driver can also re-upload a flagged document from the driver app. A load isn't fully compliant until every required document passes.

Compliance statuses

  • Requested — documents have been requested from the driver but not started.

  • In progress — the driver has started uploading documents.

  • Needs review — one or more documents couldn't be verified automatically and need a broker decision.

  • Completed — all required documents passed.

  • Failed — one or more documents did not pass.

  • Expired — the driver didn't complete the documents within the completion window.

  • Canceled — the request was canceled by an admin or the driver.

Notifications

Your team can be emailed when a driver's required compliance passes, fails, or needs review. Team-member emails are opt-in per user — turn on the driver-verification (completed) email in your notification settings — and a workspace can also configure a shared alert email list for these events.

FAQ

Is driver identity verification still its own thing?
Identity verification is one requirement within shipment compliance. If you only need identity, use it on its own; if you need equipment or freight documents too, add them as compliance requirements. See Verify a driver's identity on a shipment.

What happens if a document fails or needs review?
A failed document blocks compliance until it's resolved. The driver can re-upload from the driver app, or a broker can approve or reject a "Needs review" document from the Compliance panel.

Did this answer your question?