BackOfficeFleet

Lumper QR closeout - Load 502 L002

Midwest Foods - Chicago, IL to South Hub DC - Memphis, TN. BOF ties the shipper view to dispatch, proof, claims, and settlement actions so the exception has one source of truth.

In progressAt risk

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.

1. Lumper arrivesQR check-in at trailerThe lumper scans the QR code on the trailer to authorize presence and attach the dock event to this load.2. Empty proofTrailer empty confirmedDock proof or trailer camera evidence confirms the cargo bay is empty after unload.3. BOF paymentZelle payment record stagedBOF records the lumper payment workflow without requiring the driver to collect a paper receipt.4. Settlement closeoutAccessorial clearedQR authorization, empty proof, and payment confirmation stay attached to the load for settlement support.
Review QR dock proofOpen empty-trailer proofOpen settlement closeoutOpen BOF load record

Route fuel insight - Diesel

Midwest Foods - Chicago, IL to South Hub DC - Memphis, TN - BOF polyline on file

Estimated BOF savings

$9 9.4c/gal below corridor average

BOF OH Turnpike Rest Area MM 142 - $3.446

Lowest within 50 mi - $3.446 - 22 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

2 required packet line(s) still open in ops tools

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: Incomplete

2 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
In progress
Dispatch eligibility
At risk
Current risk detail
Proof, seal, or exception flags require ops review before calling lane fully cleared
Pre-trip proof baseline
Pickup seal SEAL-55219; 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 20, 2026, 11:37 PM -> May 22, 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-55219
Delivery seal #
SEAL-55219
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 20, 2026, 11:37 PM -> May 22, 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.

Pickup cargo condition
Uploaded
Delivery cargo condition
Uploaded
Cargo proof line
Complete
Seal proof line
Pickup Complete | Delivery Complete
Pickup seal SEAL-55219Pre-trip baseline captured before departureOpen proof
Delivery seal SEAL-55219Delivery seal differs from pickup baselineOpen proof
Pickup cargo conditionBefore-departure cargo and trailer conditionOpen proof
Delivery cargo conditionCargo condition available for customer and claims reviewOpen proof
RFID / dock custodyDock proof attached to the same load recordOpen proof

BOF lumper QR payment workflow

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.

QR dock authorizationLumper presence is tied to the trailer and dock eventOpen proof
Empty trailer proofUnload condition confirms cargo bay is clearOpen proof
Delivery dock photoFacility unload context attached to the same closeoutOpen proof
Open settlement closeoutOpen BOF load recordOpen empty-trailer proof

Lumper closeout control

Simulated control action for load L002: BOF confirms the lumper at the dock, records payment, then releases the settlement hold without asking the driver to handle receipt paperwork.

Dock QR authorizationPendingAuthorized
Empty-trailer proofOpen proof
Zelle payment$315 pending$315 sent
Settlement holdHeld for closeoutReleased
View QR dock proof

Documentation readiness

Outstanding: Cargo photo, Seal photo

Overall: IncompleteSettlement hold risk
Rate ConfirmationReady
BOLReady
PODReady
InvoiceReady
Lumper QR closeoutNot applicableNo lumper authorization required on this move

Linked documents & actions

Supporting materials used by dispatch, claims, shipper review, and settlements to move the exception from detection to resolution.

Pre-trip inspection & cargo condition reportPre-trip tablet (BOF)BOLPODInvoiceRate confirmationLumper proof

Internal load record: /loads/L002