L001Acme Distribution - Cleveland, OH to Metro Fulfillment - Dallas, TX. BOF ties the shipper view to dispatch, proof, claims, and settlement actions so the exception has one source of truth.
BOF captured pickup seal SEAL-83921 before departure and later detected delivery seal SEAL-83920. That variance does not mean the pre-trip gate failed; it means the gate created the baseline that let BOF catch a downstream seal change, re-seal, or recording error before the load closed.
Acme Distribution - Cleveland, OH to Metro Fulfillment - Dallas, TX - BOF polyline on file
Estimated BOF savings
$0 0.0c/gal at or above corridor average
BOF US-30 East / Pilot Travel Center - Lima - $3.451
Lowest within 50 mi - $3.451 - 42 mi
Diesel plan record: corridor baseline, trip gallons, savings, and recommended stop are tied to this load lane.
Admin Time Reduced
Indexed engine outputs + dispatch URLs on one load record
22 BOF document links on file for this shipment
Required packet lines satisfied on this readiness snapshot
Customer, dispatch, settlement, and claims teams use the same load record instead of rebuilding the packet from emails.
Claims Exposure Reduced
Packet headline: Exception / claim review needed
0 open proof / required gap label(s) in combined view
Single shipper-facing surface reduces back-and-forth vs. scattered email threads
The exception view merges document readiness, proof photos, seal chain, and closeout action into one review surface.
The pre-trip gate captured the starting proof baseline. The current risk is the downstream variance against that baseline, not a missing pre-trip process.
A clean pre-trip can still produce a later seal variance if a facility opens and re-seals the trailer, a receiver records a replacement seal, or a manual entry is wrong. BOF is designed to catch that variance before closeout.
Each tile opens the evidence BOF uses to reconcile the seal variance, cargo condition, and dock custody trail for this load.
This is not a driver receipt chase. The trailer QR code authorizes the lumper, BOF captures dock and empty-trailer proof, then settlement closes once the Zelle payment record is matched to the load.
Simulated control action for load L001: BOF confirms the lumper at the dock, records payment, then releases the settlement hold without asking the driver to handle receipt paperwork.
Claim packet staged — submit to carrier / insurer per playbook
This shipment is flagged for dispatch, customer, settlement, and claims review because the seal chain changed after the pickup baseline was captured.
Generated exception / claim artifacts: MAR MAR-001Claim COMP-001
Supporting materials used by dispatch, claims, shipper review, and settlements to move the exception from detection to resolution.
Internal load record: /loads/L001
