Broker guideReview a carrier absent from the latest census snapshot
Understand retained records without interpreting absence as a regulatory decision.
Updated 2026-09-13 · CarrierTrail product workflow
Identify the actual observation
An absent-record notice means the USDOT record was not present in the latest official FMCSA census data snapshot. The page may retain previously observed details. Check the dates before copying those values into a current packet review, and distinguish retained information from a newly confirmed observation.
Check the identity through official sources
Confirm that the USDOT number was entered correctly and inspect the relevant official record. Absence from one official dataset does not establish that authority was revoked, that insurance ended or that the business closed. Record the result of your follow-up rather than inventing a cause for the absence.
Illustrative example
A previously saved carrier is absent from a new census file. Your team can preserve its prior decision and evidence while opening a new review of the missing record. That keeps the historical record intact without presenting the older snapshot as a current confirmation.
Absence review note
USDOT: __. Last present source date: __. Latest snapshot date: __. Official record checked: __. Findings: __. Current decision and unresolved questions: __.
Worked review example
Illustrative scenario. A previously visible carrier is absent from the next census snapshot, while an older profile remains available. The retained page helps explain what was previously observed, but it should not be mistaken for a fresh match in the current source.
A practical review sequence
Confirm
Check the exact USDOT identifier and the publication date associated with the absence. Rule out an entry error before interpreting the result.
Separate
Keep census presence distinct from authority and insurance observations. Absence in one source does not answer every question about the company.
Follow up
Check the official record directly and record the outcome. Keep the earlier observation dated so colleagues can see what information is historical.
What to put in the review record
Save last observed presence, the source in which the record was absent and the follow-up source checked. If the record returns, retain both events rather than deleting the absence from the review trail.
Before closing this review
Do not treat a retained profile as evidence that the carrier was present in the newest snapshot. Read the presence statement and the dates together before using the details for a decision.
Should the old profile be discarded immediately?
A retained, clearly dated record can help explain previous decisions and identify the company being investigated. The important distinction is whether it is presented as historical information or as a match in the current source. Keep the last observed data with its date, show the absence event and document the next official-source check. Discarding the earlier observation can remove useful context; presenting it without the absence notice can create a different misunderstanding.
What should happen if the carrier returns?
Record the later presence and its source date, then compare the available information with the prior observation. A return to a snapshot is not itself a new team approval.
Use these steps alongside your organization’s verification process. CarrierTrail presents public records and saves team decisions; it does not certify carriers or insurance coverage.
Read the data methodology → · All broker guides →