Imported load
TMS supplies the load, lane, assigned driver, carrier, stops, and current TMS status for TMS-LD-10482.
Command center
The owner sees which TMS imports can release, which are blocked, and who owns the fix.
This is the first operating view after a TMS load enters BOF: dispatch readiness, document health, driver availability, carrier packet status, risk, and next action in one place. TMS-LD-10482 is close, but BOF shows what still needs review and who clears it.
Owner viewNext action visible
BOF-owned records
Driver file, carrier packet, insurance, and rate confirmation support the BOF release decision.
Waiting record
BOL image review is one document input inside the BOF-RR-10482 readiness decision.
Owner
S. Turner owns the document review, so the load does not sit in a vague dashboard state.
Next action
Choose Ready, Conditional, or Hold for TMS-LD-10482 after BOF reviews the readiness packet.
available for dispatch review with required records attached
blocked by document, driver, or carrier record issue
ranked by operating impact and assigned owner
Command scenario
TMS-LD-10482 is close to release, but still needs document confirmation.
The owner can see the load, lane, driver, carrier, release risk, and action owner before dispatch has to make a call. BOF avoids a generic KPI dashboard by showing the exact reason a load is reviewed instead of released.
- LaneDallas to Memphis
- DriverM. Alvarez
- CarrierNorthline Freight
- OwnerS. Turner
Release impact in view
BOL, POD plan, insurance, driver file, and carrier packet status are tied to the trip before release, so the owner sees what still affects dispatch confidence.
ReviewFinancial detail stays focused
The first view shows release consequence and owner action without pulling the team into accounting detail before it matters.
Later review| Priority | Load | Operating issue | Record | Impact | Owner | Next action |
|---|---|---|---|---|---|---|
| 1 | TMS-LD-10482 | Review | BOF-RR-10482 packet needs final review | Trip can move after readiness decision | S. Turner | Review release decision |
| 2 | BOF-1907 | Watch | BOL photo pending dispatcher confirmation | May delay Kansas City lane | Dispatcher | Confirm BOL image |
| 3 | BOF-1931 | Blocked | Driver medical card update missing | Do not release | Safety lead | Update driver file |
Owner triage packets
The command center explains why each priority deserves attention.
A fleet owner should not have to open five systems to understand the next move. BOF keeps the release state, controlling record, owner, consequence, and next action together.
Review
Owner triage note
Updated Jun 5, 2026 15:45 CT
Owner Triage · TMS-LD-10482
Operating stateClose to release after document confirmation
Controlling recordBOF-RR-10482 readiness packet
OwnerS. Turner · dispatch review
Business consequenceTrip can move after final document check
Next actionChoose release outcome
TMS-LD-10482 is the owner's narrow review item: the load looks ready, but the BOF-RR-10482 readiness decision still needs document, driver, carrier, and dispatch consequence review.
Owner review
S. Turner
Review
Watch
Owner triage note
Updated Jun 5, 2026 11:18 CT
Owner Triage · BOF-1907
Operating stateWatch before assignment
Cleared supportDriver eligibility and signature block
OwnerDispatcher and packet owner
Business consequenceKansas City lane may move after two narrow checks clear
Next actionConfirm watch decision
BOF-1907 stays visible because it needs attention without being treated as a full stop. The owner can see why it is watch, who owns it, and what clears it.
Dispatcher
Packet owner
Watch
Hold
Owner triage note
Updated Jun 5, 2026 16:05 CT
Owner Triage · BOF-1931
Operating stateHeld out of dispatch assignment
Controlling recordDRV-3301 medical certificate update
Attached contextCarrier assignment context remains visible
OwnerSafety lead
Business consequenceDo not assign the St. Louis lane until credential clears
Next actionResolve hold plan
BOF-1931 gives the owner a defensible hold reason: the driver credential controls release even if carrier context is attached.
Safety lead
Operations lead
Hold
Immediate actions
Every dashboard item explains what happens next.
The command center should not leave your team asking where to click next. Each item names the problem, the supporting record, the owner, and the action that changes the release state.
Review TMS-LD-10482 decision
The release decision is grouped by dispatch impact so your team sees the readiness reason, owner, and simulated handoff together.
Release truly ready loads
BOF separates dispatch-ready work from loads that still need document, driver, carrier, or safety review.
Send holds to the right owner
Safety, dispatch, carrier operations, and document-owner actions are named instead of buried in a dashboard note.
Dashboard reality
The command view should feel connected to real desks and real packets.
The dashboard is not just charts; it is a way to organize radio calls, pre-trip paperwork, carrier files, and safety reviews into a clean operating answer.
Dispatch desk tools
The command center should reflect how the desk actually works.
Pre-trip clipboard
Pre-trip readiness ties equipment, driver, and paperwork together.
Carrier packet desk
Packet readiness belongs in the same view as load readiness.
Safety review table
Corrective actions and safety forms should have owners and dates.