TMS partner workflow

Follow an imported TMS load into a BOF release decision.

The partner workflow orients your team around ASC-LD-10482, a load that TMS manages while BOF checks driver compliance, carrier packet readiness, required documents, exception ownership, and the release decision.

Isometric BOF fleet workflow showing driver readiness, document review, lane review, and load release
OwnerDocsLoad

Decision map

Four partner imports show ready, hold, conditional release, and unmatched-driver review.

The operating review starts with ASC-LD-10482, then compares the other synthetic TMS load states so your team can see how BOF separates TMS activity from readiness control.

CaseStateWhat it provesOwnerOpen record
ASC-LD-10480ReadyDriver, carrier packet, and pre-trip documents clear BOF review.Operations leadReady decision
ASC-LD-10482HoldTMS shows the driver assigned, but BOF medical-card review blocks release.Safety/ComplianceHold decision
ASC-LD-10483ConditionNo legal blocker is active, but POD and lumper receipt follow-up remain visible.Document deskConditional release
ASC-LD-10484Manual reviewTMS lists a driver BOF does not recognize, so BOF creates an exception state.Operations leadDriver match review

Operating 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 · ASC-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 itemRecord to inspectOperating answerNext action
Partner importASC-LD-10482TMS shows the load assigned and ready for TMS handling.Bring the load into BOF review.
Driver matchDRV-6198 · Caleb PriceMatched by email/phone, but BOF compliance controls eligibility.Review medical-card expiration.
Document gateRate confirmation, BOL, pickup instructionsPre-trip documents are present; compliance is the controlling blocker.Keep documents attached to the hold decision.
Release decisionBOF-RR-10482Hold - Action Required.Update medical card record or assign alternate driver.
Simulated handoffPrepared decision payloadBOF 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 ASC-LD-10482

Follow one load from owner triage through record-backed release, using the same driver, carrier, document packet, and owner throughout.

Review the path

02

Open command center

See ready loads, watch items, blocked work, owners, and the business impact behind each decision.

View dashboard

03

Check dispatch consequence

See allowed, warning, review, and blocked decisions before the load moves so dispatch does not guess.

View dispatch

04

Review document control

Use complete paperwork records with dates, IDs, reviewer status, signatures, and release-packet detail.

Review BOL record

05

Confirm driver and carrier status

Connect driver, safety, and carrier packet status to the release decision so the blocker is specific.

View driver status

06

End with a Founding Fleet path

Accepted early fleets can use the 2-week trial to test BOF against one real load, driver file, document packet, or release issue.

View trial

Governance 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-008

Driver, ELD, and mobile records

Mobile Device & ELD Security supports driver uploads, field records, and mobile document capture.

DAT-IT-006

Vendor system access

Vendor & Third-Party Access supports TMS, ELD, carrier, and connected back-office systems.

DAT-IT-014

TMS partner workflow

See how BOF reviews an imported TMS load without replacing the TMS workflow.

View integration preview

Data handling

Classification and information-security controls explain how sensitive operating records are handled.

Governance summary

Hands-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 ASC-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.

Founding Fleet demo path

One decision, with enough detail to judge the trial.

BOF keeps the path centered on ASC-LD-10482 so the release packet, owner, blocker, and next action stay easy to follow before a Founding Fleet applies.

Apply after the demo →