BlueLine Retail - Cleveland, OH to Lakeside Grocery - Dallas, TX. BOF ties the shipper view to dispatch, proof, claims, and settlement actions so the exception has one source of truth.
BlockedBlocked
What happened on this load
BOF keeps the driver out of the paper chase. The lumper scans the trailer QR code, dock and empty-trailer proof stay attached to the load, and the Zelle/payment record supports accessorial closeout without a paper receipt handoff.
BlueLine Retail - Cleveland, OH to Lakeside Grocery - Dallas, TX - BOF polyline on file
Estimated BOF savings
$10 10.4c/gal below corridor average
BOF I-55 South / Welcome Center - $3.481
Lowest within 50 mi - $3.481 - 29 mi
Diesel plan record: corridor baseline, trip gallons, savings, and recommended stop are tied to this load lane.
Admin Time Reduced
Centralized proof packet vs. manual gathering
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
Billing & dispute readiness
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.
Pre-trip & proof
The pre-trip gate and delivery proof stay visible while settlement resolves the specific packet item holding release.
Pre-trip status
Blocked
Dispatch eligibility
Blocked
Current risk detail
Maintenance report: Warning | Tire check: Warning
Pre-trip proof baseline
Pickup seal SEAL-26790; cargo and pickup proof on file for comparison.
BOF action
Hold clean closeout, reconcile the seal chain, and stage the claim / exception packet.
Target window
May 27, 2026, 11:37 PM -> May 29, 2026, 11:37 PM
Seal & compliance snapshot
Seal chain, driver compliance, and appointment details remain attached to the packet even when the active issue is settlement support rather than cargo custody.
Seal required
Yes
Pickup seal #
SEAL-26790
Delivery seal #
SEAL-26790
Seal verification
Pickup seal photo: Complete | Delivery seal photo: Complete | Recorded seal state: OK
Why this matters
Settlement can be held for one missing support item without turning the whole load into a claims event.
Driver compliance
No open compliance incidents on file for this driver.
Appointment window
May 27, 2026, 11:37 PM -> May 29, 2026, 11:37 PM
Proof stack tied to the exception
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 L009: BOF confirms the lumper at the dock, records payment, then releases the settlement hold without asking the driver to handle receipt paperwork.
Overall: Exception / claim review neededSettlement hold risk
Rate ConfirmationReady
BOLReady
PODReady
InvoiceReady
Lumper QR closeoutReadyDock authorization and payment support attached
Exception & claims visibility
This shipment is flagged for dispatch, customer, settlement, and claims review because the seal chain changed after the pickup baseline was captured.
Exception on file
Yes
Claim review needed
No
Exception reason
Dispatch / seal discrepancy — review proof stack
Resolution plan
Compare pickup seal photo, delivery seal photo, BOL, POD, and RFID dock proof. Confirm whether the facility or receiver opened and re-sealed the trailer after pickup. Hold clean closeout until dispatch or claims marks the seal chain reconciled.