Broker guideReport a carrier-data display problem precisely
Help distinguish a CarrierTrail display error from information in the public source.
Updated 2026-09-13 · CarrierTrail product workflow
Identify the page and field
Provide the USDOT number, public page URL and the exact field you believe is wrong. Include the source date shown and describe the expected value with its supporting source. A statement that the whole profile is incorrect gives the reviewer little to investigate.
Keep the request limited to the issue
Do not send passwords, payment data or unrelated private workspace notes. CarrierTrail can investigate how a value is retrieved or displayed; it does not directly amend an FMCSA source filing. If the underlying official record needs correction, use the relevant official process.
Illustrative example
A page displays a phone value differently from the dated official snapshot. Report both values and both dates so support can check formatting, freshness and import behavior. A newer source may explain the difference without indicating a display bug.
Correction request template
USDOT: __. Page URL: __. Field displayed: __. Value shown and source date: __. Expected value and supporting source/date: __. Steps to reproduce: __. Contact for follow-up: __.
Worked review example
Illustrative scenario. A company reports that its address on a profile differs from a newer official record. The screenshot alone does not show which source version was used. A correction request is easier to investigate when it identifies the field, the page and the evidence for the expected value.
A practical review sequence
Specify
Provide the profile URL, USDOT number and exact field at issue. Quote the displayed value and explain what you believe it should show.
Source
Include the official source URL and its publication or check date where available. Separate a newer source version from a display or calculation error.
Scope
Explain whether the issue concerns CarrierTrail's presentation or the underlying FMCSA record. Use the official process for changes to the source record itself.
What to put in the review record
A useful request includes affected URL, identifier, field, displayed value, expected value, supporting source and date. Omit passwords, payment information and unrelated personal documents.
Before closing this review
A newer document does not automatically mean an older dated snapshot was rendered incorrectly. The investigation should establish whether the source changed, the matching failed or the displayed value was wrong.
How can a correction request distinguish an old source from a display error?
Include the date of the source shown on the page and the date of the evidence you are supplying. If the evidence is newer, the question may be whether the next update has been published rather than whether the old value was rendered incorrectly. If the same source version contains a different value, identify that directly. This lets the investigation focus on source timing, identifier matching or presentation instead of treating every discrepancy as the same problem.
Who changes the underlying FMCSA record?
CarrierTrail can investigate its own matching and display. Changes to the official source record follow the relevant FMCSA process; a request to CarrierTrail does not itself amend that record.
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 →