Broker guideReview a returning carrier before new work
Use earlier evidence as history while checking what is available now.
Updated 2026-09-13 · CarrierTrail product workflow
Open the existing record
Search for the saved USDOT carrier before adding a new entry. Read the previous decision and its date, then compare the current source observations. This preserves the relationship history and avoids hiding earlier concerns in duplicate records.
Revisit the changed circumstances
Identify whether contact details, source status, operational requirements or your team’s understanding have changed. An earlier approval concerned the information and circumstances at that time. If monitoring was paused, examine the available observations when resuming and document the current review.
Illustrative example
A carrier returns after several months with different shipment requirements. Even if the census fields look unchanged, your desk still needs to address the new requirements. Save the reason for the current decision instead of treating the earlier approval as a permanent certification.
Returning-carrier note
Previous decision/date: __. Current source dates: __. Changes reviewed: __. New shipment requirements: __. Monitoring state: __. Current decision and reason: __.
Worked review example
Illustrative scenario. A carrier returns after several months without work. Its previous decision remains in your workspace, but some contact and filing observations are newer. The earlier relationship can guide your questions; it does not establish that the old evidence still answers them.
A practical review sequence
Reopen
Read the last decision and its unresolved items before looking only at the current profile. Note when the carrier last worked with your team.
Compare
Review changes in identity, contacts, fleet declarations and filing observations since that decision. Keep unchanged fields separate from newly confirmed information.
Refresh
Obtain the confirmations relevant to the new shipment and document whether the prior decision remains appropriate or needs revision.
What to put in the review record
Record previous decision date, changes reviewed, new confirmations and the reason for the current outcome. If monitoring was paused, record the resumption separately from the review conclusion.
Before closing this review
Do not start over blindly, but do not rely on familiarity either. The useful question is what has changed and which parts of the prior evidence need to be checked again.
What if nothing appears to have changed?
Record which source versions and operational details were actually checked. No observed change within the available records is narrower than a claim that nothing changed during the whole period away. The team may still need a current shipment confirmation or clarification of an older open item. Use the previous decision as context, then state why the current review reaches its outcome. This gives continuity without turning familiarity into the evidence itself.
Should resuming monitoring count as approval?
Keep those actions separate. Monitoring determines whether later observations are followed; the review decision records the team's assessment of the carrier for its work.
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 →