eligible for assignment with authority and insurance current
Carrier readiness
Carrier packets show whether a TMS load has earned release confidence.
TMS identifies the carrier on the load. BOF keeps authority, insurance, agreement status, settlement hold context, and dispatch impact visible while sensitive tax, payment, and private packet details stay protected until they matter.
Packet statusReady for review
AuthorityInsuranceW-9
missing document, renewal evidence, or owner confirmation
ready for release review while sensitive payment details stay protected
| Carrier | Network / aggregator relationship | Authority | Insurance | Packet | Asset readiness | Dispatch impact | Owner |
|---|---|---|---|---|---|---|---|
| Northline Freight · CAR-118 | Carrier network: Midwest Reefer Alliance | Active | Current | Ready | Ready | Eligible for TMS-LD-10482 review | Carrier ops |
| Blue River Logistics · CAR-207 | Carrier network: Ohio Valley Carrier Partners | Active | Renewal pending | Watch | At Risk | Review before BOF-1907 assignment | Packet owner |
| Delta Yard Services · CAR-309 | No network or aggregator relationship shown | Hold | Current | Hold | Restricted | Do not release for BOF-1931 | Operations lead |
Carrier Registry relationships show whether a carrier belongs to no network, one carrier network, or one aggregator. Private customer, commercial, payment, and BOF relationship details remain protected outside this readiness view.
Release Packet Preview · Northline Freight
Carrier IDCAR-118
Assigned loadTMS-LD-10482
AuthorityActive · verified Jun 5, 2026
InsuranceAuto liability and cargo current
Dispatch gateEligible after release packet review
Sensitive tax IDs, ACH instructions, commercial terms, and private notes stay protected until the release decision requires that level of detail.
What it shows
Carrier readiness is connected to the same TMS import as driver, document, insurance, and BOL status.
Protected packet detail
Tax fields, payment details, and private packet notes stay protected until they are needed for the operating decision.
Packet consequence
Ready, watch, and hold carriers each get a clear operating answer.
The carrier view should explain why a packet supports release, why another needs owner confirmation, and why a held assignment should not move just because one document looks current.
Watch
Carrier renewal evidence
Due before assignment
Carrier Packet Watch · CAR-207
CarrierBlue River Logistics
Assigned loadBOF-1907
AuthorityActive
Insurance renewalEvidence pending packet owner confirmation
Packet ownerCarrier operations
Dispatch consequenceReview before BOF-1907 assignment
Owner checks
Renewal evidenceConfirm current certificate date and sender
Load impactKeep watch until carrier owner confirms the packet
Dispatch noteWatch decision remains visible
Next actionPacket owner confirms renewal before assignment
CAR-207 is not a hard hold. BOF keeps the renewal evidence visible so dispatch sees the owner and narrow check before the Tulsa to Kansas City lane moves.
Packet owner
Carrier operations
Watch
Hold
Carrier assignment context
Reviewed Jun 5, 2026
Carrier Assignment Context · CAR-309
CarrierDelta Yard Services
Assigned loadBOF-1931
AuthorityHold for assignment review
InsuranceCurrent
Packet ownerOperations lead
Dispatch consequenceDo not release while driver credential is blocked
Hold boundary
Carrier contextAttached for assignment visibility
Controlling recordDRV-3301 medical certificate update
Release gateBlocked until safety clears the driver credential
Next actionSafety lead resolves credential before carrier assignment is reviewed
CAR-309 shows why carrier readiness alone is not enough. The carrier context stays attached, but the driver credential still controls the BOF-1931 hold.
Operations lead
Carrier operations
Hold
Governance basis
Third-party access is controlled before connected systems are trusted.
When BOF discusses TMS, ELD, accounting, payroll, factoring, or vendor-system access, the trust layer frames those systems as controlled access points rather than casual data sources.
Vendor and third-party access
Carrier packets, vendor records, and connected system access have a written access-control basis.
DAT-IT-014Cybersecurity expectations
Sensitive carrier and vendor records are handled within security expectations before deeper packet detail is reviewed.
DAT-IT-002Data classification
Tax IDs, payment details, private notes, and commercial exceptions stay protected while release readiness remains clear.
DAT-IT-004Change and remote access
Vendor-system changes and remote access are treated as controlled review items, not informal shortcuts.
DAT-IT-011 / DAT-IT-009