Driver eligibility

BOF driver records explain whether the TMS assignment can release.

TMS can show the assigned driver. BOF keeps credentials, documents, safety flags, and next actions together so dispatch does not guess from separate spreadsheets. BOF shows why M. Alvarez can support ASC-LD-10482 while another driver remains on hold.

Driver profile

M. Alvarez is ready for ASC-LD-10482.

Fleet-owned driver files

Each driver record has the paperwork a fleet owner expects to inspect.

BOF separates the fleet's own driver qualification files from outside carrier packet records. A carrier can be attached to the load, but BOF does not pretend the fleet owner controls another company's employee file.

Document groupRequired driver recordsCurrent proof for DRV-2048Release effect
Identity and licenseCDL, driver license image, license class, expiration, endorsementsCurrentDriver can stay assigned to ASC-LD-10482.
Medical and safetyMedical card, MCSA exam summary, MVR, clearinghouse, drug and alcohol policy acknowledgementCurrentNo safety blocker on the selected load.
Employment fileEmployment application, resume or work history, prior employer inquiry, road test certificate, annual reviewFiledSupports dispatch eligibility.
Emergency and contactEmergency contact, phone/email, home terminal, driver communication acknowledgementFiledBack office knows who to contact during exception follow-up.
Tax and settlementW-9 or I-9 status, payment preference, bank/settlement setup, owner-operator packet if applicableMasked and filedProtected details stay out of the public review but settlement readiness is visible.
Dispatch controlsELD/mobile acknowledgement, route notes, load assignment, safety hold status, dispatch eligibility noteEligibleDriver file does not block release.

Ready example

DRV-2048 shows a clear driver file: current license, medical card, MVR, employment file, safety acknowledgements, and dispatch eligibility.

High confidence

Watch example

DRV-1187 shows that a driver can be eligible while the load stays on watch because a BOL photo or carrier renewal still needs review.

Medium priority

Hold example

DRV-3301 shows a clear stop: the medical certificate update controls the lane until safety attaches and reviews the new record.

High priority

Driver readiness packets

Every driver status explains the BOF release consequence.

The driver view separates a TMS assignment that clears BOF review, a watch item tied to document review, and a credential hold that blocks dispatch. Each packet names the record, owner, and next action.

Ready Driver readiness packet Reviewed Jun 2, 2026

Ready Driver Packet · DRV-2048

DriverM. Alvarez
Assigned loadASC-LD-10482
Credential statusCDL, MVR, medical card, and acknowledgements current
OwnerSafety review · S. Turner
Dispatch consequenceEligible after ASC-LD-10482 release review

Readiness checks

CDL / MVRCurrent for assignment
Medical statusCurrent
Safety reviewNo active blocker affecting ASC-LD-10482
Next actionRelease only after BOL document review clears
DRV-2048 is ready for the Dallas to Memphis assignment. The remaining release gate sits with the document review, not the driver file.
Safety reviewer
Operations review
Ready
Watch Driver readiness context Reviewed Jun 4, 2026

Watch Driver Context · DRV-1187

DriverJ. Carter
Assigned loadBOF-1907
Driver statusEligible for Tulsa to Kansas City assignment
OwnerDispatcher and packet owner
Dispatch consequenceWatch before assignment

Watch checks

CDL / MVRCurrent
Medical statusValid through Oct 12, 2026
Driver gateDoes not block BOF-1907
Next actionClear document and carrier checks before assignment
DRV-1187 shows that a watch status does not always come from the driver file. The driver is eligible; the load stays watch because document and carrier evidence need confirmation.
Safety lead
Dispatcher
Watch
Hold Driver credential hold Reviewed Jun 5, 2026

Driver Credential Hold · DRV-3301

DriverT. Brooks
Assigned loadBOF-1931
Attached contextCarrier assignment context remains visible
OwnerSafety lead

Hold checks

CheckStatusOwnerDispatch consequence
Updated card requestedSentSafety leadDriver knows the record required.
Credential attachedPendingDriver / safety leadLoad remains held.
Safety review completedPendingSafety leadDispatch cannot assign.
Release gate updatedPendingOperations leadBOF-1931 stays blocked.
DRV-3301 gives dispatch a specific hold reason instead of a vague driver issue. The credential update controls whether the St. Louis lane can be assigned.
Safety lead
Operations lead
Hold

Driver Eligibility Summary

Assigned loadASC-LD-10482
EligibilityDispatch approved
OwnerSafety review · S. Turner
Credential recordCDL, MVR, medical card, and policy acknowledgements current
Dispatch consequenceCan release after ASC-LD-10482 document review clears

Who uses this

Dispatch, safety, and operations leads use the same eligibility answer instead of reconciling separate driver files.

Next action

Release ready drivers, keep watch drivers in review, and resolve credential holds before assignment.

Driver system access controls

Driver readiness includes how records are accessed and submitted.

Driver portal access, mobile uploads, ELD-related records, and acknowledgements are governed by written IT and data protection controls.

Acceptable use

Driver and back-office users operate inside clear expectations for system use, record handling, and responsible access.

DAT-IT-001

Password and authentication

Credential records and driver-system access are supported by authentication requirements and access discipline.

DAT-IT-007

Mobile Device and ELD

Driver uploads, ELD-related records, and mobile document capture have a written security basis.

DAT-IT-006

Remote access and communications

Remote follow-up, driver messaging, and back-office communications stay tied to controlled access expectations.

DAT-IT-009 / DAT-IT-010

Next step

Connect driver eligibility to safety and compliance.

Dispatch can trust the assignment when the safety view explains which credentials clear ASC-LD-10482 and which missing record keeps BOF-1931 on hold.

Open credential status →