Policy controls applied
You set the policy.
Your thresholds define what Proceed, Review, Controlled Proceed, and Do Not Proceed mean for a load.
Carrier selection evidence
A unanimous 2026 Supreme Court ruling held that the FAAAA preemption defense no longer bars safety-related negligent-selection claims against brokers of this type. DispatchDiligence creates the defensible record inside the dispatch workflow.
The question
Without a contemporaneous record, those questions have no good answer. That gap is the liability.
Policy controls applied
Your thresholds define what Proceed, Review, Controlled Proceed, and Do Not Proceed mean for a load.
FMCSA snapshot
The file keeps the current public FMCSA records available at the time the check was run.
Decision record
The outcome, timestamp, policy version, and evidence fingerprint stay together for later review.
Carrier Selection File
Sample data for illustration only - DEMO identifiers are not real USDOT or MC records.
Carrier identity
Policy controls applied
| Control | Source value | Result |
|---|---|---|
| Operating authority | Active property authority | Proceed |
| Vehicle OOS | 8.4% vehicle OOS; below customer threshold | Proceed |
| Driver OOS | 2.1% driver OOS; below customer threshold | Proceed |
| Crash total | 0 crashes in lookback | Proceed |
| Insurance signal | On-file signal present | Proceed |
Decision record
Proceed - policy satisfied
The carrier matched the customer's policy thresholds, and the load-specific decision was saved before dispatch.
SHA-256 evidence fingerprint
6f2c91b1dd5f 9a6a406ad1d5 c3cf7dc61273 f70bdf61e973 a1fcb74217d8 3d54
Sample data for illustration only. DEMO-USDOT and DEMO-MC identifiers are not real USDOT or MC records.
Q1
What did you know about this carrier before dispatch?
Q2
When exactly did you check them?
Q3
What public safety data did you review?
Q4
Who approved the exception?
Q5
Was this your standard process or a one-time call?
Q6
Show me your carrier-vetting policy as it existed that day.
What we do
The product creates the record that ordinary carrier vetting usually fails to preserve.
Set the policy
DispatchDiligence never sets the policy for you.
Apply it to every load
Every check uses current public FMCSA records available at the time of check.
Preserve the proof
The record is retrievable years later with the policy, source snapshot, decision, and audit trail.
Carrier Selection File
Sample data for illustration only - DEMO identifiers are not real USDOT or MC records.
Carrier identity
Policy controls applied
| Control | Source value | Result |
|---|---|---|
| Operating authority | Active property authority | Proceed |
| Vehicle OOS | 8.4% vehicle OOS; below customer threshold | Proceed |
| Driver OOS | 2.1% driver OOS; below customer threshold | Proceed |
| Crash total | 0 crashes in lookback | Proceed |
| Insurance signal | On-file signal present | Proceed |
Decision record
Proceed - policy satisfied
The carrier matched the customer's policy thresholds, and the load-specific decision was saved before dispatch.
SHA-256 evidence fingerprint
6f2c91b1dd5f 9a6a406ad1d5 c3cf7dc61273 f70bdf61e973 a1fcb74217d8 3d54
Sample data for illustration only. DEMO-USDOT and DEMO-MC identifiers are not real USDOT or MC records.
Carrier Selection File
Sample data for illustration only - DEMO identifiers are not real USDOT or MC records.
Carrier identity
Policy controls applied
| Control | Source value | Result |
|---|---|---|
| Operating authority | Inactive property authority | Stop |
| Vehicle OOS | 34.8% vehicle OOS; outside customer threshold | Stop |
| Driver OOS | 13.9% driver OOS; outside customer threshold | Stop |
| Crash total | 4 crashes in lookback | Review |
| Insurance signal | No on-file signal present | Stop |
Decision record
Do Not Proceed - policy stop
The carrier did not satisfy the customer's policy thresholds, and the stop decision was saved before dispatch.
SHA-256 evidence fingerprint
c84f5e11b91d 0d7bd294ea3e 6a4c870af5f1 be8e30b03ef6 b5278fd1450d 2a88
Sample data for illustration only. DEMO-USDOT and DEMO-MC identifiers are not real USDOT or MC records.
Production system
In use
Customer status
Active
Evidence path
Deterministic
Integrity anchoring
Sealed nightly with an independent timestamp
Who it is for
One load-specific file speaks to operators, compliance teams, counsel, and underwriters.
Document the carrier-selection process shippers increasingly ask about, while giving counsel a load-specific record if the decision is challenged.
As analogous exposure arguments develop, organizations that influence carrier selection need a diligence process they can explain. The evidence file creates a consistent record of the decision before the load moves.
Review policy versions, exceptions, file hashes, and approval history without rebuilding the story from inboxes and spreadsheets.
See a documented process, exception discipline, and file coverage instead of a promise that carrier vetting happens somewhere.
Pricing
The public entry tier makes the platform accessible; higher-volume operations are contact-us while larger conversations are live.
Overage applies only above the band; per-load rate decreases as tiers rise.
Request a demo
Bring your policy, your workflow, and one real carrier-selection scenario. We will show the record the product creates before a load moves.