Digital carrier packets: minutes, not days.
The packet is where new-carrier momentum goes to stall. A truck you need today, held up by a W-9 nobody returned. Going digital fixes the paperwork speed — but the packet was never the risk decision. That happens earlier, when you pick which carrier gets invited. This page covers both: the packet done right, and the verification that belongs in front of it.
What goes in the packet
The contents haven't changed in decades — what changes is how fast they move. The standard file:
| Document | Watch for |
|---|---|
| Broker-carrier agreement | Signed by an officer of the carrier — not a dispatcher. |
| W-9 | Legal name and EIN must match the FMCSA registration. |
| Certificate of insurance | Your brokerage listed as certificate holder; check dates and limits against the FMCSA filing. |
| Operating authority | Verify status live against FMCSA — don't rely on the carrier's copy of the authority letter. |
| Banking / factoring details | Notice of assignment if factoring. Verify payment-detail changes by phone, not email. |
| Carrier profile | Dispatch contacts, equipment types, preferred lanes. |
Where PDF packets fail
- Round trips. Print, sign, scan, reply — per document. Each one is a chance for the packet to stall while the truck you wanted books elsewhere.
- Incomplete files. The agreement comes back unsigned on page 12. The COI expires next month. Nobody notices until an audit or a claim.
- No verification. This is the big one. A PDF packet checks that documents were received, not that they're true. A doctored COI and a borrowed authority letter pass a completeness check every time.
Digital packet flows — whether from a packet platform like MyCarrierPackets or RMIS, or your own forms — fix the first two problems. They don't fix the third, because completeness and truth are different checks.
The step before the packet
Sending a packet is an invitation — it signals you intend to work with this carrier. So the highest-leverage move in onboarding isn't a faster packet; it's making sure the invitation only goes to real carriers. Keelway is an AI platform that automates carrier email triage for freight brokers — turning 40+ carrier replies per posted load into a ranked, vetted shortlist in under a second. Before any packet is in play, every inbound carrier has already been checked: FMCSA authority, insurance filed by the insurer, safety history, and the identity signals fraud rides in on — email domains that don't match the registered contact, MC-DOT inconsistencies, chameleon patterns on fresh authorities. The result is a 0–100 trust score on the reply itself.
Keelway deliberately stops there. We don't collect W-9s or chase signatures — the onboarding page explains the boundary. Your packet process keeps the paperwork job; what changes is that packet volume drops to the carriers worth the paperwork, because the ones that would have failed vetting never get invited.
For the manual version of the pre-packet check, work through the 25-point carrier vetting checklist or the step-by-step vetting guide. For the automated version, the free CarrierVet extension runs 21 risk rules on any MC or USDOT, locally in your browser.
Frequently asked questions
What is a digital carrier packet?+
What goes in a carrier packet?+
Why do paper and PDF packets take days?+
Does Keelway collect carrier packets?+
Why does verification before the packet matter?+
What does this cost?+
Send packets only to carriers who already passed.
Related
The plain-English basics — contents, purpose, and where packets came from.
The pre-packet verification layer — FMCSA vetting on every inbound carrier.
The packet-platform incumbent, compared honestly.
Portal-based onboarding vs inbox-native vetting.
The 25-point pre-booking checklist — run it before any packet goes out.