Load Facts
Load, driver, unit, documents, proof, owner, and status are carried in one operating view.
Dispatch & Operations
Operational Control in Real Time
See load intake, driver readiness, exceptions, proof, and release decisions in one joined operating record.
Operations Overview
Every load shows status, blocker, owner, and release consequence.145Active LoadsVisible in queue
9At RiskNeeds review
24BlockedRelease held
Illustrative demo data shown for public operating context.
Operating Benefits
Dispatch decisions improve when load facts, driver readiness, proof, and exceptions stay joined.
Driver Readiness
Assignment decisions see credentials, HOS availability, equipment gate, and carrier rules before release.
Proof & Exceptions
Proof gaps, at-risk loads, and blocked records explain the cause, owner, due date, and consequence.
Release Control
Dispatch can see what must clear before a load moves, bills, or reaches settlement readiness.
Dispatch Dashboard Preview
A command view for active loads, blockers, and release paths.
View the Manager Portal Demo
Load Queue
Illustrative operating view
5Loads shown
3Need action
1Ready
BOF-1907POD review before billing releaseAt Risk
BOF-1931Credential record blocks assignmentBlocked
BOF-2064Driver, unit, and packet readyReadyOpen Load
Selected Load - BOF-1907
Demo action view
Tulsa, OK to Kansas City, MO
POD and renewal evidence review requires dispatcher confirmation before billing release.
StatusReview before release.
BlockerPOD and renewal evidence not aligned.
ReasonReceiver evidence and renewal support are not aligned to the packet.
OwnerDispatcher / packet owner
ClearanceConfirm POD, signed BOL, receiver evidence, and renewal evidence.
ConsequenceSettlement packet remains held until proof clears.
Dispatch Workflow
The load should move through a visible release path, not a chain of disconnected messages.
Dispatch works best when every load moves through one visible path: intake, assignment, readiness, tracking, exceptions, proof, review, and release.
1Intake
2Assign
3Readiness
4Track
5Exceptions
6Proof
7Review
8Release
Featured Cargo Securement Solution
Cargo Securement Before Release
BOF can make cargo-securement requirements part of the joined load record. Dispatch can assign the required securement method, provide driver instructions, capture installation proof, and review exceptions before the load is released.
Featured Solution
Freight Brace Securement Workflow
1Requirement identified
2Freight Brace selected
3Driver instructions sent
4Installation completed
5Photos uploaded
6Dispatch reviews proof
7Exception resolved
8Evidence retained
Securement methodFreight Brace
Installation proofReceived
Driver acknowledgmentComplete
Release statusReady
Evidence files3 photos attached
Connected recordsIntake, assignment, readiness, proof, exception, release.
Illustrative operating data. Freight Brace is shown as an approved featured solution, not a guaranteed release, compliance, or damage-prevention outcome.
Proof and Exception Management
Proof and Exceptions Stay With the Load
Load intake workbench
Capture shipper, lane, equipment, proof requirements, customer instructions, carrier constraints, and review owner before dispatch release.
Proof packet
BOL, POD, receiver evidence, seal photo, cargo securement, lumper receipt, and delivery notes stay attached to the load record.
Exception route
Blocked, delayed, at-risk, and under-review loads show the cause and the exact route back to release.
Joined record
Dispatch, safety, proof, settlement, and driver readiness all read from the same synthetic demo record.
See BOF in Action
See Customer Load Intake in Action
Customer portal load intake
The customer load-intake preview shows how load facts, proof needs, and release context can enter the same operating workflow.
Dispatch Readiness
Turn every dispatch exception into a clear operating decision.
The public page now points prospects toward the product behavior: what is blocked, why it matters, who owns it, and what clears it.