Sample file

Carrier Selection File samples

These examples show what the evidence file looks like for Green, Yellow, Red, and Unverified outcomes under the published carrier_selection_policy_v1.3 policy. Unverified means material source data was not retrieved; it is not a clean proceed.

Generated Before Dispatch
Carrier Selection File - Evidence Record
dispatchdiligence | Load ID: LD-YELLOW-014 | Policy carrier_selection_policy_v1.3 | Evidence Record v1.0 | Confidential
Policy Outcome: Review Required
Generated
June 8, 2026 15:25:26 UTC
Brokerage
Enterprise Pilot Broker LLC
Load ID
LD-YELLOW-014
Policy version
carrier_selection_policy_v1.3 - Applied at dispatch time
Pre-dispatch timing governanceWithin 48h pre-dispatch window

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
Carrier Identity
Legal name
BLUE RIVER DEMO LINES LLC
USDOT number
2000001
MC number
MC-200101
Authority status
Active - Property authority confirmed
Safety rating
Satisfactory
FMCSA snapshot
June 8, 2026 15:21:44 UTC
Source: Synthetic FMCSA/QCMobile training snapshot
Policy Review - carrier_selection_policy_v1.3
Policy flags
R-003 Vehicle OOS above yellow thresholdR-006 Prior enforcement-review signalEVID-002 Approval details required
Policy result
REVIEW REQUIRED
Triggered rules
R-003, R-006, EVID-002
Insurance status
Insurance data displayed for COI/manual verification
Decision Record
Decision type
Controlled Proceed - Manager Approved
Decision timestamp
June 8, 2026 15:25:19 UTC
Approving manager
John Doe - Operations Manager
Dispatcher
T. Williams - Dispatch
Load details
Chicago, IL -> Dallas, TX
General freight - time-sensitive pickup
File stored
Stored evidence record - Append-only audit trail
Yellow - Review Required - controlled handling before load moves

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.

Exception reason
Vehicle OOS and prior enforcement-review signal required manager review.
Load-specific justification
No alternate approved carrier available before pickup cutoff.
Compensating controls
Fresh snapshot reviewed. Approval limited to this load. Increased check-call cadence.
Policy controls applied
These are sample thresholds from carrier_selection_policy_v1.3 preserved with the file.
Review Required
ControlPublished policy thresholdSource valueResult
Auto liability / BIPD filingInformational pending COI/manual verification workflow$1,000,000 confirmedDisplayed, not scored
Cargo filingInformational pending COI/manual verification workflow$100,000 confirmedDisplayed, not scored
Vehicle OOSGreen <= 20%; yellow > 20%; red > 25%22.1%Yellow / Review Required
Driver OOSGreen <= 8%; yellow > 8%; red > 10%6.1%Green
Crash totalGreen <= 1; yellow > 1; red > 31Green
Enforcement indicatorActive/elevated indicator = Yellow / Review RequiredPrior enforcement-review signalYellow / Review Required
Scope note: Controlled Proceed is a limited record of a human exception decision for this load. It does not certify that the carrier is safe, does not create a standing approval, and does not replace counsel review.
SHA-256 Evidence Hash
Database-written - Not user-editable - Append-only audit trail
ae343ba0110c4aed2682b2e88a928b31908d999416160b42104b1cb7e640b907