Fleet owner
Starts at the command center to see ready loads, document gaps, release impact, and owner actions before anyone has to chase context.
Owner pathPartner role paths
Choose the seat reviewing the TMS import.
Each role sees the same partner release decision from their own seat: the owner sees risk, dispatch sees release gates, safety sees credential impact, and carrier operations sees packet readiness.
Path rule
Lead with TMS import TMS-LD-10482, then compare watch and hold.
- Primary caseTMS-LD-10482
- Watch caseBOF-1907
- Hold caseBOF-1931
Dispatcher
Reviews what can move, what is held, which release gate controls the decision, and who has to clear the blocker.
Dispatch pathDriver and safety
Checks credentials, document status, medical card timing, safety items, and dispatch eligibility in the same operating story.
Driver pathCarrier operations
Verifies packet readiness, insurance, authority, agreement presence, and release confidence.
Carrier pathExecutive review
Sees whether BOF creates a clearer operating rhythm: fewer mystery holds, cleaner records, and named next actions.
Executive pathRole decision map
Each role gets a different answer from the same three cases.
The review stays simple because every role works from the same TMS import and BOF readiness records. The difference is the question they need answered before the next dispatch decision.
Fleet owner
Question: which loads are ready, watched, or held, and who owns the follow-up?
Record: TMS-LD-10482 release decision.
Open release issueDispatcher
Question: can the lane move without guessing?
Record: TMS-LD-10482 BOL review.
Open BOL issueSafety lead
Question: which driver is eligible, and which credential blocks dispatch?
Record: DRV-3301 medical update.
Open credential issueCarrier operations
Question: which packet supports release and which packet needs renewal evidence?
Record: CAR-207 renewal watch.
Open renewal issueExecutive review
Question: does BOF make operating problems easier to see, assign, and resolve?
Record: BOF-1931 hold plan.
Open hold issueRole handoff packet
The same load gives each team a specific operating answer.
TMS-LD-10482 stays at the center, but the question changes by role. TMS keeps the load context; BOF keeps the answer tied to a readiness record, an owner, and a next action so each team can move without losing context.
Role review
Cross-team operating packet
Updated Jun 5, 2026 15:52 CT
BOF Role Handoff Packet · TMS-LD-10482
Primary laneDallas, TX to Memphis, TN
Dispatch stateRelease review
Controlling recordBOL image confirmation
| Role | Operating question | Record to open | Decision supported |
|---|---|---|---|
| Fleet owner | Which load creates near-term value, and who owns the final release step? | Dispatch release note | Keep focus on the one record holding release. |
| Dispatcher | Can the Dallas-to-Memphis lane move without guessing? | BOL image review | Approve release after the image clears, or keep the load in review. |
| Safety lead | Does driver status block this load? | DRV-3301 medical update | Confirm safety does not block TMS-LD-10482. |
| Carrier operations | Does the assigned carrier packet support release? | CAR-207 renewal watch | Confirm carrier readiness is not the blocker. |
| Executive review | Does the operating model make the problem easier to assign and resolve? | Trip release packet | See one load move from record review to a named next action. |
The role path is not a separate story. It is the same release decision translated into the questions each team needs answered before the next action is trusted.
Operations lead
Role owner
Review
Role consequence packets
Every role can inspect the records behind their decision.
The role paths stay focused, but they are not thin. Each role has a concrete release, watch, or hold record to inspect, with the owner and next action already named.
Owner operating answer
The owner sees which work can create revenue, which work needs attention, and which hold should not reach the road.
- Release reviewTMS-LD-10482 release note
- Watch itemBOF-1907 watch decision
- Hard holdBOF-1931 hold plan
Dispatcher operating answer
Dispatch sees what can move, what needs a final check, and what should stay out of assignment.
- Move after reviewBOL-10482 image review
- Watch before releaseBOL-1907 photo review
- Do not assignDRV-3301 medical update
Safety operating answer
Safety sees which driver record clears dispatch and which credential record controls a hold.
- Clear driverDRV-2048 qualification file
- Eligible driverDRV-1187 eligibility
- Blocked driverDRV-3301 hold record
Carrier operating answer
Carrier operations sees which packet supports release, which packet needs renewal evidence, and which assignment context stays held.
- Ready packetCAR-118 release summary
- Renewal watchCAR-207 packet watch
- Held contextCAR-309 assignment context
Executive operating answer
Leadership sees whether BOF creates a dependable rhythm: record, owner, consequence, and next action.
- Document controlReadable packets
- Load readinessThree load states
- BOF assessmentScenario selection
Step 1
Command center triage
Owner sees the operating picture first: what is ready, what is held, which record is missing, and who owns it.
Open command centerStep 2
Dispatch consequence
Dispatcher sees the release decision, release gate, carrier, lane, and next action before the load moves.
Open dispatch issueStep 3
Document and driver readiness
Paperwork, driver readiness, and safety status explain why TMS-LD-10482 is reviewable rather than blocked.
Open document issueStep 4
Focused BOF assessment
Bring a real release, driver, document, or carrier packet decision so BOF can map the record chain against your fleet's process.
Take the BOF Fleet AssessmentReview depth
Start simple, then open deeper operating detail when it helps.
The first walkthrough stays focused on the release decision. Teams that need more detail can still inspect the role-specific records behind the command view.
Homepage, solutions, overview, documents, and booking stay simple enough for a first operating conversation.
Quick orientationCommand center, dispatch, drivers, carrier readiness, and safety evidence are available when the team wants more detail.
Detailed recordsTMS-LD-10482 shows why the load is reviewed before release and which document confirmation clears it.
With contextSettlements, claims, accounting, maintenance, and setup detail wait until they support a specific fleet discussion.
Later conversation