See what needs attention before it costs you.

Your inspections, your violations by CSA category, and a time weight on each by age, plus the date every violation stops counting, 24 months out. Counts use FMCSA’s published method (3× in the last 6 months, 2× from 6 to 12, 1× from 12 to 24). FMCSA does not publish CSA percentiles for property carriers, so Fleetive does not show one and does not predict a score. FMCSA’s own monthly snapshot can differ (DataQs removals, timing).

Fleetive checks the public FMCSA data for your USDOT number every day, after FMCSA publishes its daily update. It is not real-time, and dates are FMCSA’s: an inspection can be reported days or weeks after the day it happened.

You confirm who was driving with a click, and Fleetive suggests a driver where it can. FMCSA’s public data never names drivers, so that click is what puts each violation on the right person’s card. Trucks need no click: they link to their inspections by VIN.

Fleetive emails the people who receive your compliance alerts whenever something new needs a look, and adds it to Alerts & Tasks. That means an inspection with violations or an out-of-service order, an insurance filing cancellation, an operating authority change, or a crash. Only insurance cancellations are monitored, not new filings. A clean inspection on its own never sends an email; it is noted at the bottom of one that had to go out. Daily readers get each update; weekly readers get the urgent ones, like an out-of-service order, an insurance cancellation or a revocation.

Open that inspection and mark it as disputing through DataQs, FMCSA’s challenge system, then work through the DataQs checklist in Fleetive. The challenge itself is filed with FMCSA; Fleetive cannot change FMCSA’s record.

Yes. Each company has its own Safety page; switch company in Fleetive to see another USDOT’s inspections, alerts and record changes. Emails name the carrier in the subject line.

The Safety page shows the date of the latest data it has. If FMCSA has not published anything new, it says so. If our own daily check runs late, the header says “Daily refresh is running late” and shows the last refresh, rather than an all-clear it cannot support.