Every carrier in trouble with FMCSA is named in the file that says so.
Compliance work is bought under deadline, and the deadline is published. Audit due, rating gone conditional, MCS-150 overdue, BASIC over threshold — HAULVANE turns each into a dated row with the reason attached.
What ranks a carrier for compliance
These are the weights the scoring engine actually applies to this profile — not a description of them. Every signal is derived from a federal file and carries the date it changed.
| Signal | Weight | Why it means something to you |
|---|---|---|
| AUDIT_DUE | +100 | New-entrant safety audit due. A hard federal deadline. |
| RATING_COND | +94 | Safety rating went conditional. It has to be fixed or upgraded. |
| BASIC_ALERT | +90 | A BASIC crossed its intervention threshold. |
| MCS150_DUE | +86 | Biennial update overdue — deactivation follows if it is not filed. |
| AUTH_SUSPEND | +76 | Authority under a suspension notice, with a date on it. |
Only dormant carriers score negative here, at −40. This is the one profile where trouble is the qualification rather than the disqualifier.
What a row is worth
Engagement fee scaled by fleet size — about $2,400 plus $240 per power unit.
Every row carries this estimate so the queue can be ranked by money rather than by recency. The model is stated openly in the scoring documentation — it is an estimate, and it is shown as one.
Questions
Where do the audit and rating data come from?
The same federal files as everything else: the carrier census and the safety record, archived daily and diffed. Every row links back to its federal source.
Does this overlap with the free public Board?
The Board publishes only suspension notices with 14 or more days remaining and withholds the rest. The compliance profile scores nine signals, and the near-deadline rows the Board deliberately holds back are the ones carrying the most urgency.
See it against the live federal record
The demo runs the same engine on the same signals. The public Board is free and needs no account at all.
Open the demo