BOF Advantage
Documentation readiness & proof stack
Packet: Exception · 0 required gap(s)
9/10 proof lines complete (90%)
Seal / photo rules surface exceptions early
Counts come from BOF load proof items and dispatch packet rules on this load.
L009BlueLine Retail - Cleveland, OH → Lakeside Grocery - Dallas, TX · Asset T-111
Dispatch packet control: shipper, facility, requirements, compliance, proof, release review, and packet ownership in one BOF workflow.
Load tender (document viewer) · Supporting packet controls stay under Documents.
Start loads in Dispatch Packet Control (/dispatch/intake). Other cards open the BOF document viewer for packet records and the load tender. Supporting controls are labeled separately.
Lane: BlueLine Retail - Cleveland, OH to Lakeside Grocery - Dallas, TX
I-55 South / Welcome Center
29 mi~42 min dispatch ETA
Route support record: rest stops, parking status, and ETA are tied to this dispatch lane.
BOF Fuel Advantage
BlueLine Retail - Cleveland, OH to Lakeside Grocery - Dallas, TX - route polyline on file
Estimated BOF savings this trip
$10 total
10.4c/gal below corridor average at BOF network stop - ~100 gal planned burn
I-55 South / Welcome Center
BOF contract diesel within tolerance of lowest retail scan — default to network stop for controls and settlement.
I-55 South / Welcome Center
I-55 South / Welcome Center
Diesel plan record: corridor baseline, trip gallons, savings, and recommended stop are tied to this load lane.
BOF Advantage
Packet: Exception · 0 required gap(s)
9/10 proof lines complete (90%)
Seal / photo rules surface exceptions early
Counts come from BOF load proof items and dispatch packet rules on this load.
$2,400.00 linehaul
Backhaul pay $49.00
BOF dispatch block: pre-trip tire / asset defect requires manager review, WO-003 repair proof, and RFID readiness recheck before release.
Canonical trip packet for load 509. Settlement release requires required items to be Ready or Not applicable.
Settlement release supported — all required proof is on file.
| Document | Status | Link | Filename | Source | Notes |
|---|---|---|---|---|---|
| Core Trip Documents | |||||
| Rate Confirmationrequired | Ready | Open | rate-confirmation.html | Demo SVG evidence | — |
| Work Order / Trip Schedulerequired | Ready | Open | work-order.html | Demo SVG evidence | — |
| Bill of Ladingrequired | Ready | Open | bol.html | Demo SVG evidence | — |
| Proof of Deliveryrequired | Ready | Open | pod.html | Demo SVG evidence | — |
| Invoicerequired | Ready | Open | invoice.html | Demo SVG evidence | — |
| Proof & Media | |||||
| Pickup photo | Ready | pickup-photo.png | Real evidence | — | |
| Cargo photo | Ready | cargo-photo.png | Real evidence | — | |
| Seal pickup photorequired | Ready | seal-pickup-photo.png | Real evidence | — | |
| Seal delivery photorequired | Ready | seal-delivery-photo.png | Real evidence | — | |
| Delivery / empty-trailer proof | Ready | empty-trailer-proof.png | Real evidence | — | |
| RFID / geo proof | Ready | rfid-dock-proof.png | Real evidence | — | |
| Lumper QR closeout | Ready | lumper-receipt-photo.jpg | Real evidence | Dock QR authorization, empty-trailer proof, and payment support attached. | |
| Exceptions / Claims | |||||
| Exception Proof Preview | Ready | load009-exception-proof-cards.png | Real evidence | Visual proof-card summary. Individual BOL, POD, rate, seal, cargo, RFID, and closeout records remain the source of truth. | |
| Claim intake | Not applicable | Missing / Needs reviewView load reviewView driver reviewOpen DQF vault | — | Missing | No claim workflow. |
| Claim packet | Not applicable | Missing / Needs reviewView load reviewView driver reviewOpen DQF vault | — | Missing | No claim workflow. |
| Damage photo packet | Not applicable | Missing / Needs reviewView load reviewView driver reviewOpen DQF vault | — | Missing | No claim workflow. |
| Insurance notification | Not applicable | Missing / Needs reviewView load reviewView driver reviewOpen DQF vault | — | Missing | No claim workflow. |
| Settlement hold notice | Not applicable | Missing / Needs reviewView load reviewView driver reviewOpen DQF vault | — | Missing | No payroll settlement hold on file for this driver. |
| Factoring notification | Not applicable | Missing / Needs reviewView load reviewView driver reviewOpen DQF vault | — | Missing | Factoring notice is not required for this load. |
| Seal mismatch photo | Not applicable | Missing / Needs reviewView load reviewView driver reviewOpen DQF vault | — | Missing | No seal mismatch. |
| Reference Documents | |||||
| Delta Advanced Trucking, Inc. Master Services Agreement | Ready | Open | delta-advanced-trucking-master-services-agreement.pdf | Demo SVG evidence | — |
Each row is generated from BOF source data (SVG). Hover for preview; click for detail modal. URLs use /generated/… (rewritten to the document API).
Cannot clear for payment without RC on file
Unload window RFID/dock handshake recorded for load 509 (demo-derived).
RFID supports trailer presence, QR lumper authorization, empty-trailer proof, and payment closeout for payroll and claims.
RFID-aligned gate read proxy: pickup seal on file (SEAL-267…); custody checkpoint satisfied for fuel attribution. Confirm dwell / yard time vs planned route to rule out off-route fueling
Derived readiness from load volume on asset; schedule RFID yard confirmation. Book PM; verify RFID service-bay check-in
Confirm lumper QR authorization, empty-trailer proof, and Zelle payment timestamp
Unload window RFID/dock handshake recorded for load 509 (demo-derived).
Confirm dwell / yard time vs planned route to rule out off-route fueling
Book PM; verify RFID service-bay check-in
BOF readiness status for load 509 · Blocked · 2 checks still open
| Check | Status | Waiting on | Detail |
|---|---|---|---|
| Driver assigned | complete | None | Assigned DRV-009 |
| Truck assigned | complete | None | Asset T-111 |
| Trailer assigned | complete | None | TL-211 (TR-211) |
| Driver compliance/docs ready | complete | None | Credential and compliance blockers cleared. |
| Truck/equipment ready | complete | None | Equipment is available and clear for release after driver walk-around. |
| Empty trailer inspection complete | complete | None | Inspection confirmed. |
| Cargo photo / pre-trip requirements complete | complete | None | Cargo photo requirement complete. |
| Seal requirement complete / acknowledged | complete | None | Seal workflow acknowledged. |
| Special handling instructions acknowledged | complete | None | Acknowledged in ops flow. |
| Appointment confirmed | at risk | Dispatch | No appointment confirmation response yet. |
| Required BOL/POD/proof expectations defined | complete | None | Core proof lines are defined in BOF proof stack. |
| Dispatch released | at risk | Dispatch Manager | Load is still pending dispatch release. |
No readiness messages sent yet for this load.
Dispatch release, proof, claim, and finance documents tied to this load story.
RFID inactive — human proof remains primary.
| Template | Pack | Type | Readiness | Actions |
|---|---|---|---|---|
| Proof Requirements Sheet | BOF Driver and Dispatch Readiness Template Pack | Generated / Autofill Output | Ready to GenerateRequired Before Release Defines expected BOL/POD/seal/photo requirements. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextRFID: RFID inactive for this movement | |
| Appointment Confirmation Sheet | BOF Field Operations Template Pack | Generated / Autofill Output | Missing ContextRequired Before Release Updates appointment confirmation readiness check. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required facilityId · Missing required appointmentRequired | |
| Delivery Checklist | BOF Field Operations Template Pack | Editable Template | Missing ContextRequired Before Release Confirms delivery execution controls at facility level. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required facilityId | |
| Dispatch Release Checklist | BOF Driver and Dispatch Readiness Template Pack | Editable Template | Ready to GenerateRequired Before Release Final release authorization control. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextRFID: RFID inactive for this movement | |
| Driver Assignment Packet | BOF Driver and Dispatch Readiness Template Pack | Generated / Autofill Output | Ready to GenerateRequired Before Release Consolidated dispatch-ready reference for assigned driver/load. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextRFID: RFID inactive for this movement | |
| Facility Rules Sheet | BOF Driver and Dispatch Readiness Template Pack | Generated / Autofill Output | Missing ContextRequired Before Release Facility-specific compliance acknowledgment control. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required facilityIdRFID: RFID inactive for this movement | |
| Load-Specific Instruction Sheet | BOF Driver and Dispatch Readiness Template Pack | Generated / Autofill Output | Ready to GenerateRequired Before Release Dispatch instructions acknowledgment requirement. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin context | |
| Pickup Checklist | BOF Field Operations Template Pack | Editable Template | Missing ContextRequired Before Release Confirms pickup execution controls at facility level. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required facilityId | |
| Pre-Trip Readiness Summary | BOF Driver and Dispatch Readiness Template Pack | Generated / Autofill Output | Ready to GenerateRequired Before Release Readiness rollup gate to Ready / At Risk / Blocked. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextRFID: RFID inactive for this movement | |
| Special Handling Instructions Sheet | BOF Field Operations Template Pack | Generated / Autofill Output | Ready to GenerateRequired Before Release Requires acknowledgment before dispatch release. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin context | |
| Bill of Lading (BOL) | BOF Field Operations Template Pack | Generated / Autofill Output | Ready to GenerateRequired Before Release Required proof expectation for dispatch and billing packet release. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin context | |
| Carrier-Broker Agreement Summary | BOF Load Intake Template Pack | Generated / Autofill Output | Missing ContextRequired Before Release Flags legal/commercial controls before dispatch release. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required intakeId · Missing required customerId · Missing required contractSelection | |
| Cargo Photo Checklist | BOF Field Operations Template Pack | Editable Template | Ready to GenerateRequired Before Release Closes pre-trip and cargo evidence requirements. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin context | |
| High-Value Cargo Review Sheet | BOF Insurance and Claims Template Pack | Editable Template | Missing ContextRequired Before Release Major BOF control artifact for command center watch and dispatch block decisions. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required claimIdRFID: RFID inactive for this movement | |
| Seal Verification Form | BOF Field Operations Template Pack | Editable Template | Ready to GenerateRequired Before Release Updates seal acknowledgment readiness and exception logic. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextRFID: RFID inactive for this movement | |
| Compliance Reminder / Missing Doc Notice | BOF Driver and Dispatch Readiness Template Pack | Editable Template | Ready to GenerateRequired Before Release Creates waiting-on response loop for driver compliance updates. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin context | |
| Empty Trailer Photo Confirmation | BOF Field Operations Template Pack | Editable Template | Ready to GenerateRequired Before Release Closes trailer condition and pre-trip gate checks. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin context | |
| Load Tender | BOF Load Intake Template Pack | Editable Template | Missing ContextRequired Before Release Creates intake packet baseline and dispatch intake gate. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required intakeId | |
| Trip Schedule | BOF Load Intake Template Pack | Generated / Autofill Output | Missing ContextRequired Before Release Sets appointment and route schedule controls. — dispatch gate / release packet.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required intakeId · Missing required facilityId · Missing required destinationFacility · Missing required routeMemoryKey | |
| Proof of Delivery (POD) | BOF Field Operations Template Pack | Generated / Autofill Output | Ready to GenerateRequired Before Billing Settlement release control and dispute defense evidence. — supports dispatch and field execution.Present: Load 509 (L009) · Driver DRV-009 · Route / origin context | |
| Lumper Receipt Cover Sheet | BOF Billing and Settlement Template Pack | Editable Template | Missing ContextRequired Before Billing Clears lumper proof blockers on settlement. — supports dispatch and field execution.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required billingPacketId | |
| Rate Confirmation | BOF Load Intake Template Pack | Generated / Autofill Output | Missing ContextRequired Before Billing Defines commercial baseline for billing and proof expectations. — supports dispatch and field execution.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required intakeId | |
| Claim Support Packet Cover | BOF Insurance and Claims Template Pack | Generated / Autofill Output | Missing ContextRequired for Claim Packet Consolidates claim-support evidence for settlement and insurer review. — supports dispatch and field execution.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required claimIdRFID: RFID inactive for this movement | |
| Damage Report | BOF Insurance and Claims Template Pack | Editable Template | Missing ContextRequired for Claim Packet Feeds claim packet support stack and command center watch. — supports dispatch and field execution.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required claimIdRFID: RFID inactive for this movement | |
| Facility Insurance Requirement Notice | BOF Insurance and Claims Template Pack | Generated / Autofill Output | Missing ContextRequired for Claim Packet Links facility requirements to claims-sensitive controls. — supports dispatch and field execution.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required claimId · Missing required facilityId | |
| Multi-Trip Batch Sheet | BOF Load Intake Template Pack | Editable Template | Missing ContextWorkflow Document Groups multi-stop/multi-leg execution into one dispatch packet. — supports dispatch and field execution.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required intakeId | |
| Service Schedule / Work Order | BOF Load Intake Template Pack | Editable Template | Missing ContextLinked Proof Support Activates field operations schedule and proof checklist. — supports dispatch and field execution.Present: Load 509 (L009) · Driver DRV-009 · Route / origin contextMissing: Missing required intakeId · Missing required facilityId · Missing required appointmentRequired |
RFID inactive — human proof remains primary. (same summary object as template usage + trip release gates).
RFID is used for verification, attribution, checkpointing, and workflow confirmation — not direct engine fuel burn measurement.
RFID-aligned gate read proxy: pickup seal on file (SEAL-267…); custody checkpoint satisfied for fuel attribution.
Unload window RFID/dock handshake recorded for load 509 (demo-derived).
Yard / service-bay RFID confirms the asset entered a maintenance zone when the lane is equipped. PM status is inferred from the money at risk register and load volume on this asset.
T-111