Broker guideWhat to do when an MC lookup returns several carriers
Choose a result by evidence rather than its position in the list.
Updated 2026-09-13 · CarrierTrail product workflow
Compare identifiers and source fields
Keep the original MC number visible while examining each returned USDOT record. Compare legal name, DBA and reported physical location with the material you received. Similar company names should increase the care of your comparison; they do not justify choosing a record without an identifier match.
Keep an unresolved match unresolved
Do not save a decision against the first search result just to complete onboarding. Ask for the precise USDOT identity and follow your verification process. If the tool marks a result set as truncated, treat the displayed list as incomplete and use official sources for the unresolved question.
Illustrative example
Two records have similar names but different locations. Your packet names neither USDOT identifier. Record both candidates and obtain the missing identity information before adding either as the carrier for that packet. The lookup result is a set of candidates, not a recommendation.
Ambiguous-result note
MC searched: __. Candidate USDOT records: __. Packet details compared: __. Conflicts: __. Information requested: __. Person responsible for resolving the match: __. Decision pending until: __.
Worked review example
Illustrative scenario. An MC lookup produces more than one candidate. The first result is located near the pickup and therefore looks convenient, but location is not enough to select it. Treat the results as candidates that need comparison, not a ranked list of recommended carriers.
A practical review sequence
List
Preserve all returned USDOT candidates and their names. Do not discard another candidate merely because its address is farther away.
Compare
Match the supplied paperwork against each candidate's identifiers and reported company information. Record which field supports or contradicts each match.
Resolve
Obtain clarification for conflicting documents before saving a candidate as the performing carrier. Use the resolved USDOT for later monitoring and evidence.
What to put in the review record
A comparison note can use one row per candidate with matching fields, conflicting fields and the reason for the final selection. Keep the rejected candidates as context in the note rather than creating unnecessary watchlist entries.
Before closing this review
If the available material cannot distinguish the candidates, record identity unresolved. Selecting a result to finish the form would turn an unanswered question into an apparent decision.
How should candidates be compared consistently?
Build a small comparison with one row per returned USDOT. Use the same fields for every row: legal name, reported location, supplied paperwork and any conflicting identifier. Write the reason a candidate remains plausible or is ruled out. This prevents the first result, the nearest address or the most recognizable name from receiving an easier review. If none can be selected confidently, leave the identity unresolved and obtain clarification before treating one record as the performing company.
Should all candidates be added to monitoring?
Only add the carrier identities your team actually intends to monitor. A search candidate is not automatically a business relationship, and adding every result can create confusing records and unnecessary review 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 →