A practical checklist of the documents a broker needs before your first load, and why missing paperwork stalls dispatch.
A load is booked, the rate is agreed, and then dispatch stalls because someone still needs a signed carrier agreement, a current certificate of insurance, or a voided check for payment setup. This happens constantly, and it is almost always avoidable. Brokers cannot legally tender freight to a carrier until a packet of documents is complete and verified, so the fastest way to start moving loads on schedule is to have that packet ready before the first call comes in.
Requirements vary by broker, but most carrier packets converge on the same short list:
None of this is unique to any one broker. It is the baseline the industry works from, because a broker's own liability and bond obligations depend on knowing exactly who is hauling the freight and that the carrier is properly insured and authorized.
Authority status, insurance, and safety scores are not static. A carrier can be in good standing one month and flagged the next, whether from a lapsed policy, a new out-of-service order, or a change in operating status. Because of that, packet review is not a one-time formality. Many brokers pull current data at the time of booking rather than relying on whatever was on file when the carrier first signed up, and some continue monitoring status between loads. Ellys works this way: carriers are vetted against live FMCSA data before dispatch, and that status is monitored on an ongoing basis rather than checked once and forgotten.
If freight is moving between the US and Mexico, the packet conversation usually expands to cover customs paperwork, the Mexican carrier or broker of record on the other side of the border, and language clarity in the carrier agreement itself. Requirements vary by lane and by commodity, so it is worth confirming directly with the broker what applies to a specific move rather than assuming one packet covers every corridor. Ellys focuses specifically on the US-Mexico corridor and operates bilingually in English and Spanish, which is part of why packet review on cross-border lanes tends to go faster when both sides can read the same document without translation delays.
The most common reasons a packet gets kicked back are simple: an expired COI, a policy that does not meet the broker's minimum coverage, a mismatch between the legal carrier name on the authority and the name on the insurance certificate, or a missing signature page. None of these are complicated to fix, but they do take time, and that time comes directly out of how quickly a new carrier can start hauling.
Carriers who want to see what a complete packet looks like before applying can start at /carriers.