For-hire carrier
Driver readiness, carrier packet, document gate, and release decision stay attached before dispatch commits the load.
Try release reviewTMS partner workflow
Follow an imported TMS load into a BOF release decision.
The partner workflow orients your team around TMS-LD-10482, a load that TMS manages while BOF checks driver compliance, carrier packet readiness, required documents, exception ownership, and the release decision.
OwnerDocsLoad
Decision map
Four partner imports show ready, hold, conditional release, and unmatched-driver review.
The operating review starts with TMS-LD-10482, then compares additional TMS load states so your team can see how BOF separates TMS activity from readiness control.
| Case | State | What it proves | Owner | Open record |
|---|---|---|---|---|
| TMS-LD-10480 | Ready | Driver, carrier packet, and pre-trip documents clear BOF review. | Operations lead | Ready decision |
| TMS-LD-10482 | Hold | TMS shows the driver assigned, but BOF medical-card review blocks release. | Safety/Compliance | Hold decision |
| TMS-LD-10483 | Condition | No legal blocker is active, but POD and lumper receipt follow-up remain visible. | Document desk | Conditional release |
| TMS-LD-10484 | Manual review | TMS lists a driver BOF does not recognize, so BOF creates an exception state. | Operations lead | Driver match review |
Sector lens
The same release review can support for-hire, private, and government-contracting fleets.
The demo stays centered on one TMS-connected release decision, but the operating logic also applies when a private fleet needs branch proof or a government contractor needs a cleaner audit packet.
Private fleet
Internal lanes, branch handoffs, driver files, and delivery proof can follow the same BOF readiness record.
View private fleet pathGovernment / contract fleet
Higher-scrutiny work gets evidence packets, named owners, and audit notes without implying a live agency system.
View government pathCredibility proof
The strongest parts of the demo are the artifacts a fleet owner can actually inspect.
BOF should not depend on polished truck photography to feel credible. The workflow is stronger when the buyer can open driver packets, DQF reviews, settlement and compliance records, exception notes, and load workflows that explain the release decision.
Field review
Records have to hold up at the dock, not only on a slide.
BOF connects the driver, paperwork, dock context, and next action so the review feels like a live operating workflow.
Driver files and DQF reviews
Open complete driver records with photos, readiness score, document requests, generated safety forms, and clickable paperwork.
Inspect DRV-001POD, photos, and post-trip proof
Review POD state, GPS/location, receiver detail, dock photo, empty cargo proof, and settlement consequence.
Open document packetHold reasons that explain the work
See how a medical-card hold, rate-review issue, missing proof, or correction request becomes an owner, blocker, and next action.
Open alert queueFrom TMS import to BOF decision
Trace the load through source-system import, BOF readiness review, release decision, and simulated handoff.
Open Command CenterOperating review packet
The partner workflow has a source system, BOF record, owner, consequence, and next action.
BOF starts with one imported TMS load, then compares ready, hold, conditional release, and manual-review states. That gives your team enough detail to see how BOF separates work that can move from work that still needs follow-up.
Operating review
TMS partner import packet
Prepared Jun 7, 2026 07:45 CT
Partner Release Review Packet · TMS-LD-10482 / BOF-RR-10482
Imported fromTMS load assignment
BOF release ownerSafety/Compliance · medical-card hold
Record chainRate confirmation, BOL, pickup instructions, BOF driver file, carrier packet
Comparison casesReady, conditional release, and unmatched-driver review
| Review item | Record to inspect | Operating answer | Next action |
|---|---|---|---|
| Partner import | TMS-LD-10482 | TMS shows the load assigned and ready for TMS handling. | Bring the load into BOF review. |
| Driver match | DRV-6198 · Caleb Price | Matched by email/phone, but BOF compliance controls eligibility. | Review medical-card expiration. |
| Document gate | Rate confirmation, BOL, pickup instructions | Pre-trip documents are present; compliance is the controlling blocker. | Keep documents attached to the hold decision. |
| Release decision | BOF-RR-10482 | Hold - Action Required. | Update medical card record or assign alternate driver. |
| Simulated handoff | Prepared decision payload | BOF hold reason is shown as part of the demo review. | Use it to explain the release decision. |
The operating review is intentionally narrow at first: one imported load, one BOF driver match, one readiness blocker, and one decision payload. The point is to show how BOF turns TMS activity into a record-backed release decision.
Operations lead
Dispatch review
Review
Operating path
One load, six decisions your team can trust.
Each step answers who uses it, what is blocked or cleared, which record supports it, who owns the next action, and what happens next. The result is a release decision your team can inspect instead of chase.
01
Begin with TMS-LD-10482
Follow one load from owner triage through record-backed release, using the same driver, carrier, document packet, and owner throughout.
Review the path02
Open command center
See ready loads, watch items, blocked work, owners, and the business impact behind each decision.
View dashboard03
Check dispatch consequence
See allowed, warning, review, and blocked decisions before the load moves so dispatch does not guess.
View dispatch issue04
Review document control
Use complete paperwork records with dates, IDs, reviewer status, signatures, and release-packet detail.
Review BOL issue05
Confirm driver and carrier status
Connect driver, safety, and carrier packet status to the release decision so the blocker is specific.
View driver issue06
Close with a BOF assessment
After the demo, bring one real load, driver file, document packet, or release issue so BOF can map the record chain around it.
Take the BOF Fleet AssessmentGovernance support
What governance supports this review?
The first BOF review can stay focused on release decisions while still showing that AI assistance, driver/mobile records, and vendor access are governed by written controls.
AI-generated assistance
AI Use & Governance supports human-reviewed operating answers, not unchecked automated decisions.
DAT-IT-008Driver, ELD, and mobile records
Mobile Device & ELD Security supports driver uploads, field records, and mobile document capture.
DAT-IT-006Vendor system access
Vendor & Third-Party Access supports TMS, ELD, carrier, and connected back-office systems.
DAT-IT-014TMS partner workflow
See how BOF reviews an imported TMS load without replacing the TMS workflow.
View integration previewData handling
Classification and information-security controls explain how sensitive operating records are handled.
Governance summaryHands-on layer
After the walkthrough, try one release decision.
The TMS partner workflow explains the operating model. The release scenario gives buyers a tighter hands-on path through TMS-LD-10482: inspect BOF-RR-10482 records, choose Ready, Conditional, or Hold, and see how the dispatch consequence and simulated handoff change.
Walkthrough
Use this path to understand the command center, role handoffs, records, and governance behind BOF.
Try Demo
Use the release scenario to make one decision and inspect the records that control the outcome.