Operations record

The TMS release decision has a complete BOF operating record behind it.

TMS manages the load. BOF keeps the driver, carrier packet, BOL review, release gate, owner, date, signature, and next action tied together so a fleet team can trust the decision before the load moves.

Partner release packet index

Open the records behind release, watch, and hold decisions.

Operating detail

Clear TMS-to-BOF decisions need more than a status color.

Each record below shows the status, owner, document reference, dispatch consequence, and next step behind the ASC-LD-10482 release decision.

Release-ready context

Each named TMS load, BOF driver record, carrier packet, document, and exception carries the record a back-office team needs to make the next call.

Managed back-office clarity

BOF turns scattered paperwork, owner notes, and release gates into one record the team can review together.

Release review Load release packet Updated Jun 5, 2026 15:40 CT

Trip Release Packet · ASC-LD-10482

LaneDallas, TX to Memphis, TN
Pickup appointmentJun 9, 2026 · 08:30 CT
Release gateReview pending BOF-RR-10482 readiness decision
Action ownerS. Turner · dispatch review

Attached release documents

DocumentReferenceStatusOwnerDispatch consequence
Rate confirmationRC-10482-DAL-MEMReadyDocument deskRate and lane terms are attached for review.
Bill of lading imageBOL-10482-IMG-02Needs reviewS. TurnerFinal release waits for image confirmation.
Driver qualification summaryDQF-DRV-2048ReadySafety leadDriver is eligible for this load.
Carrier packet summaryPKT-CAR-118ReadyCarrier opsCarrier can be used after trip packet review.
Dispatch release noteREL-10482-DECISIONPendingS. TurnerReleased only after BOL image is confirmed.

Release note

ASC-LD-10482 is not blocked by driver readiness, carrier packet status, or insurance. The remaining decision is narrow: finish BOF-RR-10482 document review, choose Ready, Conditional, or Hold, and keep the simulated handoff with the record trail.

S. Turner · dispatch review
Operations lead approval
Review
Ready Load tender and rate confirmation Issued Jun 4, 2026 09:18 CT

Rate Confirmation Summary · RC-10482-DAL-MEM

LaneDallas, TX to Memphis, TN
Pickup windowJun 9, 2026 · 08:30-10:00 CT
Delivery windowJun 10, 2026 · 13:00-16:00 CT
Equipment53 ft dry van · sealed trailer required
Document ownerDocument desk

Release terms checked

Pickup appointmentMatches dispatch board
Driver assignmentM. Alvarez · DRV-2048
Dispatch consequenceReady; does not block release

The rate confirmation is usable for the release packet. BOF keeps the commercial summary tied to the lane and appointment without exposing sensitive pricing detail in the first review.

Document desk
Operations review
Ready
Needs review Bill of lading image review Open Jun 5, 2026 15:40 CT

Bill of Lading Review · BOL-10482-IMG-02

Document sourceDriver image upload · mobile capture
Image receivedJun 5, 2026 · 15:21 CT
ReviewerS. Turner · dispatch review
Review itemConfirm signature block and load reference
Dispatch consequenceTrip remains in review until BOF-RR-10482 clears

Visible BOL checklist

CheckStatusReviewer noteNext action
Load number visibleReadyASC-LD-10482 appears in the upper reference block.No action
Pickup location visibleReadyDallas pickup line is readable enough for release review.No action
Signature blockReviewSignature area is present; reviewer must confirm it is not cropped.S. Turner confirms image
Delivery referenceReviewMemphis delivery line needs final visual confirmation.Compare to rate confirmation

This is the narrow blocker for ASC-LD-10482. Driver, carrier, insurance, and rate confirmation are ready; dispatch only needs the BOL image confirmed before the release packet can move out of review.

Governance basis: Data Classification Policy, Mobile Device & ELD Security Policy, and Information Security Policy support how the BOL image is captured, handled, and reviewed.

S. Turner · dispatch review
Document desk
Review
Driver ready Driver qualification file Reviewed Jun 2, 2026

Driver Qualification File Summary · DRV-2048

DriverM. Alvarez
Assigned loadASC-LD-10482
CDL statusClass A · Texas · current
Medical cardValid through Aug 18, 2026
MVR reviewReviewed Jun 2, 2026 by safety lead
Dispatch eligibilityEligible for Dallas to Memphis assignment

File contents checked

ApplicationComplete · signed
Prior employmentVerified · no open request
Policy acknowledgementSafety, ELD, and drug/alcohol policies on file
Safety reviewNo open event affecting ASC-LD-10482

Sensitive license, address, tax, and payroll details stay protected while the eligibility decision remains clear.

Safety reviewer
Driver acknowledgement
Ready
Current Medical certificate status Verified Jun 2, 2026

Medical Certificate Status · DRV-2048

Assigned loadASC-LD-10482
Certificate statusCurrent through Aug 18, 2026
Verified bySafety lead
Dispatch eligibilityDoes not block Dallas to Memphis assignment
Renewal watchNext reminder scheduled Jul 18, 2026

BOF separates this cleared driver record from the blocked BOF-1931 medical-card issue so dispatch can see why one load can proceed and another must stay on hold.

Safety lead
Operations review
Current
Packet ready Carrier readiness packet Verified Jun 5, 2026

Carrier Packet Release Summary · CAR-118

CarrierNorthline Freight
Assigned loadASC-LD-10482
Operating authorityActive · verified Jun 5, 2026

First-review packet boundary

Included for reviewAuthority, insurance status, agreement present, release consequence
Reserved for later reviewTax IDs, ACH details, private notes, commercial exceptions
Packet ownerCarrier operations
Dispatch consequenceEligible after ASC-LD-10482 release packet review

The carrier packet shows readiness without pulling tax, payment, or private commercial detail into the first release review.

Governance basis: Vendor & Third-Party Access Policy, Data Classification Policy, and Information Security Policy support the carrier packet boundary.

Carrier ops review
Release packet review
Ready
Current Carrier insurance certificate Verified Jun 5, 2026

Insurance Certificate Review · CAR-118

Assigned loadASC-LD-10482
Auto liabilityCurrent · certificate present
Cargo coverageCurrent · certificate present
Certificate holderBackOfficeFleet managed review account · verified for review
Dispatch consequenceInsurance does not block release

Certificate checks

Carrier nameMatches packet summary
Effective periodCurrent for planned pickup date
Coverage typeAuto liability and cargo present
OwnerCarrier operations

The insurance certificate supports ASC-LD-10482 release readiness. It remains visible as a release record without exposing private policy numbers or nonessential commercial details.

Carrier operations
Document desk
Ready
Present Carrier agreement and W-9 boundary Checked Jun 5, 2026

Carrier Agreement Summary · CAR-118

Agreement statusPresent and usable for release review
W-9 statusPresent · sensitive fields protected
Packet ownerCarrier operations
Dispatch consequenceNo carrier setup hold for ASC-LD-10482
Protected detailsTax IDs, ACH, private terms, and exceptions

This record gives the fleet team confidence that the carrier packet supports ASC-LD-10482 without turning the first release review into a payment or setup conversation.

Carrier operations
Release packet review
Ready
Pending Dispatch release decision note Prepared Jun 5, 2026 15:45 CT

Dispatch Release Decision · REL-10482-DECISION

Release stateReview
Cleared recordsDriver file, carrier packet, insurance, rate confirmation
Action ownerS. Turner · dispatch review
Next actionApprove packet or keep load in review

Decision summary

Release ASC-LD-10482 after S. Turner confirms the BOL image is readable, signed, and tied to the correct lane. If the BOL image does not clear, keep ASC-LD-10482 in review and request a corrected image before dispatch commits.

Governance basis: AI Use & Governance Policy, Information Security Policy, and Data Classification Policy support human-reviewed release decisions and controlled operating records.

S. Turner · dispatch review
Operations lead
Pending
Watch Watch load packet Open since Jun 5, 2026 11:10 CT

Watch Load Packet · BOF-1907

LaneTulsa, OK to Kansas City, MO
OwnerDispatcher
Next actionConfirm consignee name and signed delivery timestamp
Dispatch consequenceMay move after named BOL photo review clears

Watch packet status

RecordStatusOwnerConsequence
Driver eligibilityReadySafety leadDoes not block BOF-1907.
Carrier packetWatchPacket ownerRenewal evidence should be confirmed before assignment.
BOL photoWatchDispatcherPhoto can clear the load after confirmation.
Dispatch noteWatchDispatcherKeep watch until BOL and carrier renewal checks are complete.

The watch state is not a hard hold. It tells dispatch the load may move after a named BOL photo is reviewed, and it prevents the photo from becoming a vague dashboard note.

Dispatcher confirmation
Document desk
Watch
Watch Bill of lading photo review Open since Jun 5, 2026 11:10 CT

BOL Photo Review · BOL-1907-IMG-01

Load IDBOF-1907
Document sourceDriver image upload · mobile capture
Image receivedJun 5, 2026 · 11:02 CT
ReviewerDispatcher
Review itemConfirm consignee name and delivery timestamp
Dispatch consequenceWatch status clears after confirmation

Photo review checklist

CheckStatusReviewer noteNext action
Load number visibleReadyBOF-1907 reference is visible.No action
Consignee nameWatchName appears partially cropped in the image.Dispatcher confirms
Delivery timestampWatchTimestamp is present but needs reviewer confirmation.Compare to dispatch board
Signature blockReadySignature line is visible enough for the first review.No action

BOF-1907 stays in watch because the issue is narrow and fixable. Dispatch can see the exact photo item, the owner, and what must be confirmed before the Kansas City lane is trusted.

Governance basis: Data Classification Policy, Mobile Device & ELD Security Policy, and Information Security Policy support the BOL photo review.

Dispatcher confirmation
Document desk
Watch
Driver ready Driver eligibility summary Reviewed Jun 4, 2026

Driver Eligibility Summary · DRV-1187

DriverJ. Carter
Assigned loadBOF-1907
CDL statusClass A · Oklahoma · current
Medical cardValid through Oct 12, 2026
MVR reviewReviewed Jun 4, 2026 by safety lead
Dispatch eligibilityEligible for Tulsa to Kansas City assignment

The driver record does not block BOF-1907. The watch state comes from document confirmation and carrier renewal evidence, not driver eligibility.

Safety lead
Operations review
Ready
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

The carrier is not a hard hold, but renewal evidence needs a named owner so dispatch does not treat the watch item as a vague caution.

Governance basis: Vendor & Third-Party Access Policy, Cybersecurity Policy, and Data Classification Policy support renewal evidence handling.

Packet owner
Carrier operations
Watch
Watch Dispatch watch decision Prepared Jun 5, 2026 11:18 CT

Dispatch Watch Decision · REL-1907-WATCH

Release stateWatch
Cleared recordsDriver eligibility and signature block
Action ownerDispatcher and packet owner
Next actionConfirm photo details and renewal evidence before assignment

BOF-1907 is a watch item, not a blocked load. The record keeps it visible so the team can clear two narrow checks before the lane becomes a release problem.

Dispatcher
Packet owner
Watch
Hold Blocked load packet Due before assignment

Blocked Load Packet · BOF-1931

LaneLittle Rock, AR to St. Louis, MO
OwnerSafety lead
Dispatch consequenceDo not release until updated credential is attached

Required resolution

Attach updated cardPending
Safety reviewRequired after upload
Dispatch gateBlocked until credential clears
Next reviewerSafety lead

This hold shows why BOF does not merely color a row red; it explains the credential, owner, record required, and release consequence.

Safety lead
Driver file review
Hold
Hold Driver eligibility record Reviewed Jun 5, 2026

Driver Eligibility Hold · DRV-3301

DriverT. Brooks
Assigned loadBOF-1931
CDL statusClass A · Arkansas · current
MVR reviewReviewed Jun 1, 2026 by safety lead
Dispatch eligibilityNot eligible until credential clears

The CDL and MVR are not the issue. BOF isolates the medical-card record so the hold has a specific owner and a specific next action.

Safety lead
Driver file review
Hold
Missing update Medical certificate update Required before assignment

Medical Certificate Update Required · DRV-3301

Assigned loadBOF-1931
Credential statusUpdated medical certificate not attached
OwnerSafety lead
Dispatch gateBlocked until credential clears
Next actionAttach updated card and complete safety review

Resolution checklist

StepStatusOwnerDispatch consequence
Request updated cardSentSafety leadDriver notified.
Attach updated cardPendingDriver / safety leadLoad stays held.
Review credentialPendingSafety leadDispatch cannot assign.
Release gate updatePendingOperations leadBOF-1931 remains blocked.

This record gives the safety team a clear hold reason and prevents dispatch from treating BOF-1931 like a normal load with a generic red status.

Governance basis: Data Classification Policy, Acceptable Use Policy, and Password & Authentication Policy support the handling of protected driver credential records.

Safety lead
Operations lead
Hold
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

The carrier context does not clear the load by itself. BOF keeps it attached so the team sees the full assignment picture while the driver credential remains the controlling blocker.

Governance basis: Vendor & Third-Party Access Policy, Cybersecurity Policy, and Data Classification Policy support the carrier assignment context.

Operations lead
Carrier operations
Hold
Hold Hold resolution plan Prepared Jun 5, 2026 16:05 CT

Hold Resolution Plan · BOF-1931

Release stateBlocked
OwnerSafety lead
Next reviewerOperations lead after safety clears
Dispatch actionDo not assign until the credential record is current

This plan explains what must change before BOF-1931 can leave hold status. It protects dispatch from releasing a load because the carrier or lane appears otherwise available.

Safety lead
Operations lead
Hold

Record reviewed

Continue from the operating record into load readiness.

The major load, driver, carrier, watch, and blocked states now connect back to the same release decision.

Continue to load readiness →