Questions buyers, counsel, and operators ask first.

A unanimous 2026 Supreme Court ruling, Montgomery v. Caribe Transport II, held that the FAAAA preemption defense no longer bars safety-related negligent-selection claims against brokers of this type. The standard is now ordinary care in how carriers are selected.

Montgomery dealt specifically with freight brokers, and its holding does not extend to shippers. That said, shippers may face similar liability arguments as the law develops, particularly companies that select carriers themselves while having access to public safety data. This is a potential risk to watch, not settled law.

Onboarding proves what was known months ago. The duty attaches to the load, and carrier safety profiles can drift. The question is not only whether a carrier was vetted once; it is what was known on the day the load was tendered and whether that record can be proved.

Indemnification transfers cost, not liability, and it is only worth what the carrier can pay. Insurance responds after a loss; it does not create the contemporaneous evidence that defends the selection.

No. A product cannot stop someone from filing a claim or promise a result. DispatchDiligence helps put the record in a stronger evidentiary position: contemporaneous proof that an organization set a carrier-selection policy and applied it to the load in question.

No. DispatchDiligence does not approve carriers, score them with AI, or set your standard. You set your own policy. The product produces objective evidence that you applied it, load by load.

No. The evidence path is fully deterministic: no AI, no black-box scoring. Every flag has a named rule, a source field, and a plain-language reason.

One file per load, created before it moves. It contains a timestamped snapshot of current public FMCSA records available at the time of check, the versioned policy that was applied, the result, and the documented human decision, sealed with a cryptographic fingerprint into a permanent, time-stamped record that can't be quietly rewritten.

Every file is digitally sealed with a SHA-256 fingerprint, anchored with an RFC 3161 timestamp, and preserved as a permanent, time-stamped record that can't be quietly rewritten, so later alteration leaves a visible trace. The technical term is tamper-evident.

That is the Controlled Proceed workflow. Instead of a silent workaround, the system requires a structured reason, named approver, load-specific justification, and compensating controls before the load moves.

Those tools can help vet carriers and manage data. DispatchDiligence is focused on producing a policy-anchored evidence record of your own selection decision at dispatch. Checking a carrier is not the same as proving how the decision was made.

The dispatcher enters the DOT or MC number; the system handles the snapshot, policy evaluation, green light, escalation, or stop decision. Batch CSV upload can flag a week's carriers before coverage begins.

The public entry tier is $250 per month for 0-500 monthly loads. Everything above that band starts with a pricing conversation while larger broker, shipper, and enterprise discussions are live. DispatchDiligence is never priced per carrier check.

You do. Your policy, selections, and evidence files are yours. DispatchDiligence does not resell customer data, and records are exportable.

Seven years by default, matched to the litigation horizons that matter in transportation, with the policy version that was in force preserved alongside every file.

Yes. A house policy can sit beside shipper-specific policies. When a load uses a shipper-specific requirement, the evidence file reflects that policy choice.