Timestamped FMCSA snapshot
A record of current public FMCSA records available at the time of check, not a reconstruction years later.
Product
The product is the file.
DispatchDiligence creates one carrier-selection evidence file per load, before the load moves. Not a carrier approval system. Not a black-box score. A defensible record of the decision.
Current public FMCSA records captured at the time of check.
Policy version, thresholds, and outcome preserved with the load.
Human decision, approval path, hash, and audit trail kept together.
Built to answer
What did you know about this carrier?
When did you check?
Who approved the exception?
Carrier Selection File
Evidence Record
Sample data for illustration only - DEMO identifiers are not real USDOT or MC records.
Carrier identity
- Legal name
- Demo Carrier XXXXXX LLC
- USDOT / MC
- DEMO-USDOT-XXXXXX / DEMO-MC-XXXXXX
- FMCSA snapshot
- Captured before scheduled departure
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.
Anatomy
What a Carrier Selection File preserves
The file is designed for the moment a decision is tested by counsel, audit, customer review, or underwriting.
Versioned policy applied
The file preserves the exact policy version, thresholds, and rule treatment in force for that load.
Named decision-maker
Proceed, More Info Needed, Controlled Proceed, or Do Not Proceed is tied to a documented human action.
SHA-256 evidence hash
The file is digitally sealed with a SHA-256 fingerprint and RFC 3161 timestamp anchoring so later alteration leaves a visible trace.
Cannot be quietly rewritten
A permanent, time-stamped record that can't be quietly rewritten.
27 policy metrics verified
The current product catalog exposes 27 configurable carrier-selection policy metrics across authority, safety, crash, insurance, load fit, and data quality.
How it works
DOT entered. Source captured. Policy applied. Decision saved.
Fast enough for dispatch pressure, structured enough for later review.
01
DEMO-USDOT / DEMO-MC entered
Dispatcher enters the carrier. Roster context is checked first.
02
FMCSA snapshotted
Current public FMCSA records available at the time of check are stored with timestamp and provenance.
03
Policy applied
The customer's deterministic policy evaluates the source fields. No black-box scoring.
04
Decision documented
Human review, Controlled Proceed, approval, or stop decision is saved before the load moves.
Controlled Proceed
Most brokers will sometimes use imperfect carriers. The question is whether they document why.
Controlled Proceed is the workflow for conscious exception handling: structured reason, load-specific justification, compensating controls, named approval, and approval limited to the load.
We do not approve carriers. We do not score them with AI. We do not sell your data. We document your diligence.
Carrier Selection File
Evidence Record
Sample data for illustration only - DEMO identifiers are not real USDOT or MC records.
Carrier identity
- Legal name
- Demo Carrier XXXXXX LLC
- USDOT / MC
- DEMO-USDOT-XXXXXX / DEMO-MC-XXXXXX
- FMCSA snapshot
- Captured before scheduled departure
Policy controls applied
| Control | Source value | Result |
|---|---|---|
| Operating authority | Active property authority | Proceed |
| Vehicle OOS | 22.1% vehicle OOS; requires policy review | Review |
| Driver OOS | 6.1% | Proceed |
| Crash total | 1 crash in lookback | Proceed |
| Enforcement signal | Prior review signal | Review |
Decision record
Controlled Proceed - manager approved
Structured reason, load-specific justification, compensating controls, named manager, and approval limited to this load.
SHA-256 evidence fingerprint
ae343ba0110c 4aed2682b2e8 8a928b31908d 999416160b42 104b1cb7e640 b907
Sample data for illustration only. DEMO-USDOT and DEMO-MC identifiers are not real USDOT or MC records.
FAQ
Questions this page should answer
Do you approve carriers or tell us who is safe?+
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.
Is this AI deciding which carriers are safe?+
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.
What exactly is a Carrier Selection File?+
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.
Request a demo
Put the process in place before discovery tests it.
Bring your policy, your workflow, and one real carrier-selection scenario. We will show the record the product creates before a load moves.