A carrier packet should make it easy to identify the contracting entity, understand the documents supplied, and record what was independently checked. It should not imply that a packet alone authenticates a carrier or guarantees insurance. Build the packet around dated evidence and a clear link to the specific company and load.
Practical checklist
Packet handoff essentials
What belongs in the packet
| Artifact | What to record with it |
|---|---|
| W-9 or legal-identity document | Named entity, DBA relationship, USDOT/MC identifiers, received date |
| Agreement | Parties, effective date, signature status, and any required authority or insurance terms |
| Authority-source capture | Motus/official source URL, docket, authority type, status, and time checked |
| Certificate and insurer confirmation | Named insured, requested coverage terms, producer or insurer contact path, confirmation date |
| Operations contacts | Dispatch, claims, payment, and the person authorized to approve an exception |
Core identity material
Start with the carrier’s legal name, DBA, USDOT number, MC/docket number where applicable, physical address, main phone, dispatch contact, and email domain. Reconcile these against HaulFacts lookup and current official sources. Keep the source and retrieval date with the comparison.
When a document lists a different company, treat it as a question to resolve. It may reflect a DBA, management company, affiliated entity, or an error. Ask who is contracting, who will physically transport the shipment, and who is authorized to make changes.
Documents to collect and describe
Your process may call for a signed agreement, tax and payment documentation, W-9, authority evidence, insurance certificate, and contacts for dispatch and claims. Requirements vary by contract and company policy. For each item, record what it purports to show, who supplied it, and the date received. Do not turn an uploaded file into a blanket “verified” label.
An insurance certificate deserves separate treatment. Confirm the required coverage for the shipment, then validate relevant terms directly with the insurer or authorized producer through independently found contact details. An FMCSA filing and a certificate are different evidence sources. Cargo insurance vs. auto liability explains why those records answer different questions.
A review order that catches inconsistencies
- Match the legal entity and federal identifiers across packet and public records.
- Confirm current relevant authority in the official current system.
- Read public safety information as dated context, not an approval score.
- Validate insurance for the actual cargo and terms.
- Confirm dispatch contact and pickup controls before tender.
For example, a packet may include an MC number, W-9 legal name, and certificate’s named insured, but the carrier profile shows a different DBA and phone. The next step is to reconcile the relationship through an independently published contact, not to silently choose the most convenient field.
Keep documents current and traceable
Store expiration dates, source links, receipt dates, verification notes, and any exception decision. Recheck material items before a new booking or when a contact, bank, domain, or authority detail changes. A methodical document carrier review is more useful than collecting a larger stack of files.
Pair the packet with carrier vetting before approval and identity verification before releasing a shipment.