The worst day starts three years later.
Before a load moves, DispatchDiligence creates the Carrier Selection File: a timestamped record showing what was checked, which policy applied, who reviewed the decision, and why the load moved.
This did not come out of nowhere.
The legal shift facing freight brokers has been building in the federal courts for years. May 14, 2026 was the resolution, not the beginning.
Shawn Montgomery loses part of his leg after a truck veers off course in Illinois. C.H. Robinson brokered the load. The negligent carrier-selection question enters federal litigation.
The Seventh Circuit rules in Ye v. GlobalTranz that FAAAA preemption bars negligent-selection claims against brokers. Other courts disagree. The industry keeps operating in uncertainty.
Montgomery v. Caribe Transport II, LLC. Unanimous. FAAAA preemption no longer automatically keeps negligent carrier-selection claims out of state court. Brokers now need a clearer dispatch-time record of their carrier selection process.
The operational question after Montgomery is simple: when risk data was available, did the broker ask the hard questions before choosing the carrier?DispatchDiligence framing of the post-Montgomery workflow problem
The product is the Carrier Selection File.
One file generated before dispatch. Not a score. Not a dashboard. The evidence record that shows how the carrier decision was made.
Checked 3h34m before scheduled departure. This timing flag is separate from the carrier risk outcome.
- Scheduled Departure
- June 8, 2026 19:00:00 UTC
- Check / File Time
- June 8, 2026 15:25:26 UTC
- Policy Window
- 48 hours before scheduled departure
Source: Synthetic FMCSA/QCMobile training snapshot
General freight - time-sensitive pickup
A configured policy rule produced a yellow consequence. Dispatch could not treat this as a clean proceed. A manager-approved Controlled Proceed was documented for this load.
| Control | Published policy threshold | Source value | Result |
|---|---|---|---|
| Auto liability / BIPD filing | Informational pending COI/manual verification workflow | $1,000,000 confirmed | Displayed, not scored |
| Cargo filing | Informational pending COI/manual verification workflow | $100,000 confirmed | Displayed, not scored |
| Vehicle OOS | Green <= 20%; yellow > 20%; red > 25% | 22.1% | Yellow / Review Required |
| Driver OOS | Green <= 8%; yellow > 8%; red > 10% | 6.1% | Green |
| Crash total | Green <= 1; yellow > 1; red > 3 | 1 | Green |
| Enforcement indicator | Active/elevated indicator = Yellow / Review Required | Prior enforcement-review signal | Yellow / Review Required |
You knew
What was visible in public FMCSA data at the moment of dispatch, not reconstructed after the fact.
You followed process
The same versioned policy applied to this carrier as every other carrier. The rule version is stored with the decision.
You documented judgment
When risk appeared, a human saw it and made a documented decision before the load moved.
Check the carrier. Apply policy. Save the file.
Designed for operators: fast enough that dispatchers use it under pressure, structured enough for counsel, underwriters, and internal audit to review.
Carrier meets all policy thresholds. File generated. Load proceeds.
Yellow is not approval. Customer policy requires human handling before dispatch.
Carrier should not be used unless the blocking issue is resolved and a new review is completed.
The customer decides what turns green, yellow, or red.
DispatchDiligence does not sell a generic carrier score. It applies the brokerage's published policy to the source fields available at review time, then preserves the exact policy version with the file.
Published rules
Users can see the policy in force: authority requirements, OOS bands, inspection rules, crash rules, source age limits, and review consequences.
Green / yellow / red bands
Numeric fields can be configured as green, yellow, or red. Some fields can be binary. Others can be excluded from the rating policy entirely.
Insurance by type
Auto liability, cargo, bond, and filing signals are handled as separate policy expectations, not one vague insurance checkbox.
Restricted admin setup
Policy editing, roster upload, approvers, permissions, and version history belong in Admin. Dispatchers use the published policy; they do not rewrite it during coverage.
Pre-dispatch tools
Batch intake and retrospective audit live away from the live dispatch screen, so managers can process bulk work without crowding the operator path.
Version history
Every change creates a policy history record so an old Carrier Selection File can show which rule set existed at the time of the decision.
Four people. One system of record.
DispatchDiligence answers the question each person in your brokerage will eventually face.
What is true today
DispatchDiligence is a founding-stage product. We will not pretend otherwise. Here is what is true today.
Put a documented carrier-selection process in place before discovery tests it.
When someone asks why you picked that carrier, have the file ready.
A small number of freight brokerages are being invited into the founding pilot. Contact us to talk through fit, timing, workflow requirements, and what an implementation would look like for your team.
Contact us
Tell us about your brokerage. We review every message and respond within 24 hours.