Broker guideOrganize a first-time carrier review
Create a review record before converting a new candidate into a saved decision.
Updated 2026-09-13 · CarrierTrail product workflow
Anchor the review to the entity
Start with the identifier supplied for the performing carrier. Compare the reported legal name and location with the packet, resolving ambiguous matches before saving notes against a record. Keep the shipment requirements visible so the review addresses the proposed work rather than a generic company name.
Gather evidence in a usable order
Record identity comparison, available official filing information and operational confirmations separately. Note missing sources as gaps. When your team reaches a decision, explain the reason and the unresolved conditions rather than leaving only a checklist of page visits.
Illustrative example
A new candidate has matching identity details but your desk still needs an operational confirmation for the load. The review can record the completed identity work while leaving the decision pending. Finding a public profile is not the completion of onboarding.
First-review record
Proposed work: __. USDOT and packet identity: __. Sources and dates: __. Confirmed observations: __. Pending checks: __. Decision reason: __. Next review owner: __.
Worked review example
Illustrative scenario. A new carrier has no saved decision in your workspace. The packet is polished and a reference is familiar to one colleague, but neither replaces a documented first review. Establish the identity and the required evidence before building the ongoing relationship.
A practical review sequence
Establish
Resolve the USDOT identity, legal name and supplied docket information. Record how any differences in the paperwork were clarified.
Review
Examine current public observations and obtain the shipment-specific confirmations your team requires. Keep reference comments distinct from independently checked facts.
Start
Save the decision, its reasoning and the person responsible for follow-up. If monitoring begins, confirm who will review later changes.
What to put in the review record
Create the initial baseline with source dates, contact verification, shipment requirements, open questions and a named reviewer. A future reviewer should be able to distinguish the original baseline from later observations.
Before closing this review
A first review should leave a reusable record, not just a one-time approval message. Make the unresolved items visible even if the team decides how to proceed with them.
What makes the first saved baseline useful later?
It identifies the company, records the public evidence used and explains how the team handled its initial questions. Include the source dates and the shipment requirements that shaped the review. A later reviewer can then compare new observations against a defined starting point rather than against memory. Avoid treating a completed form as a baseline if it does not show who reviewed the material or why the outcome followed.
Should later reviews repeat every initial step?
They should address the current evidence and the work being considered. The baseline helps identify changes and unresolved issues; it does not remove the need to confirm information relevant to the new decision.
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 →