Every regulatory source tells part of the story. None of them talk to each other, and none of them offer bulk API access, so someone ends up chasing four documents by hand for every renewal.
| Source | Covers |
|---|---|
| USDOT / FMCSA | Company safety rating, BASIC scores, out-of-service and crash/inspection history |
| PSP driver history | 5-year crash and 3-year inspection history per driver |
| CVOR (Ontario) | Carrier and driver abstract |
| Provincial profiles | AB / BC / QC carrier safety records |
Upload a driver's motor vehicle record. Violations and loss history are parsed and folded into that driver's combined score alongside telematics behaviour.
Every document is matched to the right driver or carrier with explicit confirmation, even at high AI confidence. Ambiguous matches route to a review queue instead of a silent reject.
Action-required flags track whether someone actually acted, not just that a flag fired. Outbound reminders, acknowledgement, and a full audit trail of what happened and when.
A narrowly-scoped estimate based only on speed-over-posted-limit events and night-driving percentage, shown as illustrative, never a guaranteed number.
Records don't sit forever by default. Retention is configurable, because unlimited storage of driver history is exposure, not a feature.
Every score states exactly what it's measured against. Seatbelt data is labelled as sensor-based, not camera-based, with its known limitations noted.
Whether you're a broker recommending this to clients or a fleet operator managing your own drivers, we'll walk through how the upload pipeline fits your data.