Driver files
Driver eligibility, medical-card status, license evidence, safety review, emergency contact, and dispatch eligibility are opened as inspectable records.
Open driver files
Apply
2-week trial - no integrations required
The Founding Fleet trial starts with the work your team already chases: driver files, document packets, release blockers, owner follow-up, and the decision about whether a load is ready, conditional, or held.
Trial promise
What BOF reviews first
Each trial area answers the same buyer question: what is cleared, what is blocked, who owns it, and what should happen next?
Driver eligibility, medical-card status, license evidence, safety review, emergency contact, and dispatch eligibility are opened as inspectable records.
Open driver filesBOL, POD state, pickup instructions, delivery proof, dock photos, settlement watch items, and claim-support evidence stay tied to release consequence.
Open documentsBOF separates ready, watch, conditional, and hold states so dispatch does not guess from scattered emails or vague rows.
Open command centerEach issue gets an owner, required record, consequence, next action, and audit note so the back office can keep moving.
Inspect release note| Trial week | Focus | BOF operating answer | Next step |
|---|---|---|---|
| Week 1 | Record review | Which driver, document, carrier, or release records control movement. | Choose the most useful operating path. |
| Week 1 | Demo inspection | Whether BOF's command center and document records are clear enough for your team. | Open driver and document packets. |
| Week 2 | Workflow feedback | Which BOF views, records, and handoffs would matter most for your fleet. | Prioritize onboarding scope. |
| Week 2 | Founding decision | Whether your fleet should reserve one of the first 10 Founding Fleet slots. | Confirm discount and next onboarding step. |
Trial entry
The fastest way to test BOF is to bring one release issue, driver file, document packet, or follow-up problem into the Founding Fleet trial.