DQ file, ongoing monitoring & ELP
Stage 1 · Driver Recruitment & Compliance
P2Initial MVP
Four-Lane View
Software Function
- ›Living DQ file (49 CFR 391): auto-assembled from onboarding artifacts Continuous MVR/CSA monitoring; Clearinghouse annual query scheduler Expiration engine: CDL, med cert, insurance, TWIC, UIIA, annual MVR ELP screening + in-app coaching modules (OOS offense since 6/2025)
Service Provider / Admin
- ›Compliance dashboard: fleet-wide currency %, expirations 30/60/90 Audit mode: one-click DOT audit package per driver Safety event workflow: violations → coaching → probation → removal
User — Driver / IOO
- ›One compliance score, always visible, with exactly what to fix Renewal reminders with in-app completion paths ELP practice modules — protection, not punishment
Logistics Company — FreightShift
- ›Fleet-wide compliance currency % as a standing company metric; one-click DOT audit package per FREIGHTSHIFT driver No capacity lost to preventable lapses: every expiring credential is a dispatch-planning event 60 days out, not a surprise The company’s safety rating and operating authority protected by system discipline, not heroics
Software Function
- ›Living DQ file (49 CFR 391): auto-assembled from onboarding artifacts Continuous MVR/CSA monitoring; Clearinghouse annual query scheduler Expiration engine: CDL, med cert, insurance, TWIC, UIIA, annual MVR ELP screening + in-app coaching modules (OOS offense since 6/2025)
Competitors
Tenstreet DQF/Safety Center, Foley, J.J. Keller, FleetCollect/FileFlo/Driver File Hub (SMB price attackers)
Differentiation
DQ files are static folders everywhere else. Ours is a live state machine wired to dispatch: non-current = not dispatchable, with the fix path in the driver’s hand.
Make It Better
Zero compliance surprises: no driver ever loses a week to an expired credential the platform saw coming 60 days out.