Carrier registry

Know which carrier can be used, why, and what must clear before release.

A carrier registry should not be a static vendor list. BOF keeps authority, insurance, W-9, agreement, ACH/payment setup, lane eligibility, equipment fit, customer approval, and packet exceptions tied to the operating record that depends on the carrier.

Open registry → Open readiness view Open BOF Vault Intake

Registry controlsAuthority, packet, owner

DOT / MCInsuranceClearance

Registry carriers12

participating carrier records with relationship and operating context

Ready now7

authority, insurance, agreement, lane, and packet gates clear

Review / blocked5

records with a named owner, reason, due date, and clearance path

Registry workbench

The carrier record should explain eligibility before a load depends on it.

Each row shows the carrier’s operating use, relationship, packet state, score context, and the action that clears review or blocked status.

Carrier	Relationship	Authority	Insurance	Tax / pay setup	Lane / equipment	Status	Reason and clearance path	Owner
Northline Freight CAR-118	Midwest Reefer Alliance	Active DOT / MC	Current auto and cargo	W-9 and ACH verified	Dry van / reefer eligible	Ready	Eligible for TMS-LD-10482 release review.	Carrier ops
Blue River Logistics CAR-207	Ohio Valley Carrier Partners	Active	Renewal evidence pending	W-9 current, ACH on file	Dry van eligible	Review	Confirm renewal certificate date and sender before BOF-1907 assignment.	Packet owner
Delta Yard Services CAR-309	Direct carrier	Assignment hold	Current	Payment setup protected	Yard support only	Blocked	Do not release while DRV-003 credential record is blocked.	Operations lead
Prairie Line Transport CAR-422	Aggregator Partner A	Active	Current, cargo limit review	W-9 received, ACH review	Flatbed eligible	At Risk	Customer approval and cargo-limit confirmation required before high-value load assignment.	Carrier desk
Harbor Road Carriers CAR-515	Direct carrier	Active	Current	W-9 and remittance current	Regional dry van	Ready	Ready with seal photo, BOL, POD, and lumper receipt rules attached.	Dispatch owner

Registry rules

Carrier eligibility should include DOT/MC authority, insurance limits, cargo coverage, W-9, agreement, ACH/payment setup, customer approval, and lane or equipment rules.

Reason before release

A review or blocked carrier should say exactly what failed: expired certificate, missing agreement, customer approval gap, low coverage, driver credential issue, or equipment mismatch.

Clearance path

Every exception needs an owner, due date, required proof, affected load, and release consequence so dispatch does not guess.

Protected data

Tax IDs, bank details, commercial terms, and private notes stay protected while the operational readiness answer remains visible.

Where the registry connects

Carrier records should feed dispatch, aggregator, documents, and settlements.

Dispatch release Load intake workbench Documents file cabinet Settlement readiness Aggregator command Joined operating record

Interactive carrier subset

Open carrier packet readiness inside the registry page.

The embedded registry shows authority, insurance, agreement, W-9, contacts, lane confirmation, exception escalation, and carrier-specific readiness without treating outside carrier files as employee records.