Founding Fleet application
Use this path if you want BOF to evaluate your fleet for one of the first 10 Founding Fleet slots.
Apply for a slotBOF working session
Bring one fleet record, driver file, document packet, or release issue. BOF will make the next move clearer.
Use the first conversation to work through a real trucking problem: driver readiness, carrier packet status, document hold, settlement hold, claim-support issue, or a release decision dispatch cannot fully trust yet. Founding Fleet prospects can apply for the first 10 fleet program with 20% off forever and a 2-week trial.
Session agenda
45 minutes around one operating decision
- Choose one load, driver, carrier, document, or release issue that slows the team down
- Map where your staff currently chases records, answers, and ownership
- Review how BOF organizes the release packet and next action
- Decide which back-office areas deserve a deeper operating review
Founding Fleet path
Want the early-member offer? Start with the Founding Fleet application.
The Founding Fleet path is for the first 10 accepted fleets: 20% off forever, priority onboarding, a 2-week trial with no integrations required, and workflow influence tied to real records.
General working session
Use this path if you want one focused BOF conversation around a load, driver file, document packet, or release issue.
Request general sessionWhat to expect
A focused working session around one real back-office release issue.
The goal is to see whether BOF can make a daily trucking decision easier to control without asking your team to start from scratch. You bring the operating pressure; BOF shows how the record, responsibility, handoff note, and next step become easier to see.
Fleet context
Fleet type, lane pattern, customer pressure, document volume, driver readiness process, and where dispatch loses confidence today.
Document readiness review
The release packet, missing records, reviewer notes, dates, owners, and follow-up items that determine whether the work can move cleanly.
Operating next step
Which back-office pressure should be handled first, what BOF would organize, and what your team should expect from the next working session.
Working-session packet
BOF can start with the same records your team already chases.
The first conversation stays practical: one operating pressure, the records that affect dispatch confidence, the owner of the next action, and the follow-up BOF would help organize.
Session ready
Founding Fleet review packet
45-minute working session
Sample Session Packet · Release Decision Review
Best starting pointBOF-RR-10482 release review
Operating pressureLoad looks ready, but one BOF record still controls release
Primary ownerFleet owner / operations lead
BOF focusTurn scattered follow-up into a visible release packet
| Session item | What BOF reviews | Record example | Decision it supports |
|---|---|---|---|
| Load pressure | Which load is close, held, or waiting on review. | BOF-RR-10482 | Whether dispatch can trust the release path. |
| Document readiness | What is ready, what is unreadable, and who owns the final check. | BOF-RR-10482 document gate | Whether BOF marks the load Ready, Conditional, or Hold. |
| Driver readiness | Whether driver file, medical card, and safety status support the assignment. | DRV-2048 | Whether driver status blocks the load. |
| Carrier readiness | Whether authority, insurance, agreement, and packet status are current enough for review. | CAR-118 | Whether carrier status affects release confidence. |
| Next action | Who owns the remaining follow-up and what happens if the record does not clear. | Dispatch release note | Approve release or keep the load in review. |
You do not need a polished in-house process before the session. BOF works best when the starting point is a real load, driver file, carrier packet, document issue, or release decision your team already has to control.
Fleet scenario
BOF review path
Ready
Session starting point
Choose the operating problem closest to what your team is dealing with.
The first call works best when it starts with one familiar pressure. Pick the scenario that matches your fleet, then BOF can map the records, owners, and next action around it.
Load looks ready, but one document still controls release.
Use this if dispatch often waits on BOL images, release packets, signatures, or final document confirmation.
Example record: BOF-RR-10482 release decision.
Request release-decision sessionLoad can probably move, but the team wants one more check.
Use this if watch items pile up because document details, renewal evidence, or owner confirmation are not clearly assigned.
Example record: BOF-1907 watch decision.
Request watch-item sessionDispatch should not move until a credential or packet issue clears.
Use this if held work needs a clearer owner, required record, safety review, and dispatch consequence.
Example record: BOF-1931 hold plan.
Request hold-resolution session