Release readiness workflow

Imported TMS loads become BOF release decisions.

Select a partner import record and see how BOF matches the driver, checks readiness, reviews documents, creates the release decision, and prepares a simulated handoff message.

Imported from TMS

Loading partner import

Review
BOF Release File
-
Customer
-
Carrier
-
Driver
-
Equipment
-
TMS Status
-
BOF Status
-

Sample partner imports

Switch between ready, hold, conditional release, and unmatched-driver scenarios.

TMS load imported Driver matched to BOF record Documents reviewed Compliance and carrier packet checked BOF release decision produced
Imported

TMS Data

BOF Match

Driver Match

BOF readiness review

BOF keeps the compliance and release decision records.

Driver Readiness

Loading driver readiness.

    Carrier Packet

    Loading carrier packet.

      Load Documents

      Loading load documents.

        BOF release decision

        Loading decision

        BOF is preparing the release decision.

        Owner of fix-
        Reviewed at-
        Next action-
        Audit note-

        Blocking or watch items

        • Loading items.

        Clearance route

        1. 01
          Loading route

          BOF is preparing the release clearance path.

        Simulated handoff

        Prepared for the demo handoff.

        This panel shows the simulated Phase 1 handoff: BOF explains the decision, blocker, owner, next action, and audit note while TMS remains the load workflow.

        Handoff status-
        {}

        Partner workflow

        TMS manages the load. BOF manages the release decision.

        The workflow keeps both systems in their lane while showing the audit-ready decision BOF adds before release.

        Back to overview →