Active authority evidence
MC / property authority and USDOT status are checked as separate fields. A lead should not be promoted because one identifier merely exists.
Orbit methodology · Truck dispatch
A verified carrier lead is not simply a company with an MC number, a phone number, or one positive status. For Orbit, verification is an evidence record: the lead should show which qualification checks were performed, what evidence supports each check, and when that evidence was last checked.
Check MC / operating-authority state and USDOT status rather than assuming one implies the other.
Record the evidence supporting insurance status and relevant cancellation signals. Do not convert missing evidence into “active.”
Qualify MC age, equipment, geography, OOS signals and the dispatcher’s current target.
Validate contact quality separately from regulatory status. A valid authority record is not automatically a reachable sales lead.
Definition
“Perfect Lead” is Urava's working term for a carrier prospect that satisfies the dispatcher’s chosen target and has sufficient evidence for the statuses being claimed. It is a qualification state, not a permanent label.
MC / property authority and USDOT status are checked as separate fields. A lead should not be promoted because one identifier merely exists.
Insurance status must be supported by evidence from the verification workflow. If current evidence is unavailable or conflicting, the result should remain unresolved.
Equipment, state, MC age, operating profile and other dispatcher filters are part of qualification, not optional decoration.
A verified record needs a last-checked time. Carrier data changes; verification should be treated as time-bounded evidence.
Recommended record
The useful output is not a green badge alone. The record should expose the exact checks behind the badge.
Status and the evidence used to support it.
Current DOT status recorded independently.
Insurance evidence plus relevant cancellation or uncertainty signals.
MC age, equipment, geography, OOS information and target-match fields.
Source context and last-checked timestamp so the dispatcher can judge recency.
Boundary
If a source is unavailable, a field conflicts, or a check has not been performed, Orbit should not silently produce a positive claim. The same rule applies to secondary enrichment such as WhatsApp availability: confirmed, detected or unknown is safer than inventing “not available.”