Load, carrier, driver, stops, status, and documents are imported for BOF review.
Partner workflow
TMS workflow + BOF: Load execution with back-office control.
The fleet's load system manages the trip workflow. BOF adds the readiness, compliance, document control, exception tracking, and audit layer needed before a load is released.
Partner import preview
BOF checks driver compliance, carrier packet, documents, exceptions, and audit trail.
BOF shows the release decision and hold reason as a simulated partner handoff.
How the simulated workflow works
TMS runs the load. BOF decides whether the load is ready, documented, compliant, and defensible.
Import the TMS load
Load number, customer, carrier, driver, stops, documents, and status are brought into BOF as a partner import.
Review BOF readiness
BOF checks driver compliance, carrier packet status, required documents, exceptions, and release blockers.
Show the decision handoff
BOF produces a release decision, next action, responsible party, audit note, and simulated handoff message.
Clear division of responsibility
BOF works beside TMS, not instead of it.
| TMS owns | BOF owns |
|---|---|
| Load creation, tenders, dispatch workflow, customer/carrier TMS records, load status, uploaded load documents, and accounting/TMS handoff. | Driver compliance rules, driver document vault, carrier packet review, load release decision, exception queue, settlement hold reasons, claims packet support, and audit trail. |
| What the TMS says is happening with the load. | Whether the load is ready, documented, compliant, and defensible before release. |
BOF driver database
BOF keeps driver records because they are dispatch eligibility records, not just contacts.
TMS can identify the assigned driver on a load. BOF keeps the compliance record that tells the team whether that driver can support the release decision.
Compliance status
CDL, medical card, MVR, I-9/W-9, safety/training status, and document expiration dates remain BOF-owned.
Dispatch blockers
Emergency contact, owner-operator packet, active safety holds, and dispatch-blocking reasons stay visible before release.
Settlement readiness
Bank and settlement setup stay attached so back-office follow-up does not disappear after dispatch.
Audit trail
BOF keeps the record of who reviewed the file, what blocked the decision, and what action comes next.
BOF-owned control layer
The partner path keeps release, exception, settlement, claims, and management decisions attached.
TMS remains the load workflow. BOF adds the back-office record that explains whether the load can move, who owns the blocker, and what evidence stays with the decision.
Exception ownership
Unmatched drivers, expired credentials, missing pre-trip records, and carrier packet issues get a named owner and next action before release.
Settlement holds
BOF keeps W-9/I-9, bank setup, owner-operator packet, and hold reasons visible without making TMS the compliance source of truth.
Claims packet support
POD, lumper receipts, seal photos, delivery proof, and claim evidence can remain attached as post-trip readiness and exception records.
Management decision record
The final release, hold, or conditional-release decision carries reason, blocker, reviewer, timestamp, audit note, and simulated handoff payload.
Demo path
A practical partner workflow for buyer review.
Step 1
Sample partner workflow
Show the operating model with representative TMS-import loads and BOF readiness checks.
Step 2
Role-based release review
Let a buyer inspect ready, hold, conditional release, and unmatched-driver scenarios without connecting to external systems.
Step 3
Simulated handoff payload
Display the decision, blocker, owner, next action, and audit note as a client-presentable handoff record.
Step 4
Interactive control-center demo
Carry the same partner-import story into the BOF product shell for clicks, alerts, records, documents, and release actions.