Broker setup packets: what to send, what to refuse

The Sunday-night PDF stack that quietly decides what you’re liable for next quarter.

It’s 11 p.m. on a Sunday. A broker emailed a twelve-page setup packet Friday evening and needs it back before Monday dispatch. Pages four through nine are dense indemnification language. Page ten sets payment terms at net-45. You sign because you want the load.

That’s where small operators leak time, signal weakness, and sometimes legal exposure. The packet is not a formality. It’s a contract. The broker wrote it for the broker.

“Just sign it so we can move the load” is how operators inherit the broker’s risk

Most setup packets have a standard core that’s fair, plus a handful of clauses that aren’t. The rest is risk transfer, written by the broker’s attorney and sent to every carrier without explanation.

Packet field	Send	Refuse
MC + DOT	Yes	n/a
Insurance COI	Yes	n/a
Driver SSN	No	Refuse
Bank account	Only after first invoice	Refuse upfront

The five things that should always go in the packet

The broker needs all five to dispatch a load to your MC. Refusing any of them wastes everyone’s time.

• W-9. Current calendar year. Address matches your federal carrier registration filing. Send a fresh PDF, not a scan of a scan.
• Certificate of insurance. Auto liability, cargo, general liability. The broker named as certificate holder, exact spelling. Coverage limits matching the packet’s stated minimums.
• MC authority letter. Pulled fresh from the FMCSA SAFER system. Six months old is borderline. A year old gets your packet rejected.
• Voided check or ACH form. For payment routing. Direct deposit only. Paper checks are a workflow tax you don’t need.
• Signed broker-carrier agreement. Signed where indicated, dated, with the red-lines from the next section in place before you sign.

Build the packet folder once. Update the COI quarterly, pull a fresh MC letter every six months. The packet should ship in under five minutes when a broker asks.

The clauses worth red-lining or refusing

Not every setup needs a fight. Most boilerplate is fine. These are the clauses that show up on small carriers’ contracts more than they should, and the ones a working operator should push back on.

• Overly broad indemnification. Language that holds you responsible for the broker’s own negligence, third-party claims unrelated to your load, or “any and all” damages without cause. Counter with: indemnification scoped to losses caused by carrier’s own negligent acts.
• Exclusivity clauses. Some packets quietly forbid you from booking the same shipper through any other broker for 12-24 months. That clause turns a freight relationship into a non-compete. Strike it.
• Payment terms past net-30. Net-45 and net-60 are working-capital subsidies the carrier funds for the broker. Push for net-30. Some brokers will hold; many will move when you ask.
• Mandatory factoring through a broker-chosen factor. The broker dictates which factoring company gets your money first. Your factor relationships are yours. Strike or refuse.
• Blanket NDAs covering rate information. A clause that bars you from disclosing rates to anyone, ever, including a future dispatcher or accountant, is unworkable. Scope it to specific load files, not categorical.
• Automatic chargeback rights. Language allowing the broker to deduct disputed amounts from future settlements without notice. Counter with: written notice and 10-day dispute window before deduction.

Most brokers respond to a clear red-line. The ones who don’t are telling you something about how the relationship will run.

The dispatcher version of this is a templated workflow

An operator-aligned dispatcher runs setup packets through a checklist before they reach your inbox: current COI, MC letter pulled this month, red-lines pre-marked, packet back in business hours instead of at midnight. A truck dispatching service is built to handle exactly that.

That’s the workflow leverage you’re paying the fee for, not magic loads. A dispatcher’s desk runs thirty to sixty packets a year across the carrier book, so patterns repeat and red-lines get standardized.

What stays on you is the legal hook. Your MC signs the agreement. Your insurance covers the load. Your authority is on the rate confirmation. The dispatcher coordinates the packet flow. The exposure stays on the carrier, every time.

The self-dispatching operator’s version of this is a folder and a habit

Self-dispatch doesn’t mean the workflow disappears. It means it lives on your laptop. Build the system once, run it the same way every time.

• Single folder titled by year. Subfolders by broker name. Inside each broker folder: signed agreement, current COI, packet date, payment-terms note.
• A standing list of red-line clauses. Same language every packet. No reinventing the request at midnight.
• A 24-hour rule on packet turnaround. Read in business hours. Sign in business hours. Push back on brokers demanding Sunday-night signatures, except for genuine emergency loads.
• Quarterly refresh: COI updated, MC letter pulled, factor information current.

For a closer look at how dispatch fees and packet workflow connect, the fee-versus-workflow breakdown covers where the time leak shows up on a percentage fee.

Before you send the next broker packet, pull the last one and check what you handed over that you didn’t have to.

Quick decision rule

• If a packet asks for the standard five and a fair agreement, sign it inside business hours.
• If a packet contains net-45+ payment terms, send the red-line and hold the load until the broker confirms.
• If a packet contains a mandatory-factor clause or a 12+ month exclusivity, refuse the clause or refuse the broker.
• If a packet is sent at 7 p.m. Friday with a Monday dispatch deadline, it’s a workflow signal. Brokers who plan run packets Tuesday or Wednesday.
• If you signed a packet last year you wouldn’t sign now, pull it and renegotiate at the next renewal window. The broker won’t raise it for you.

Setup packets are where the relationship starts on paper. The dispatcher coordinates the flow; the MC carries the legal weight. The operator who treats the packet as a five-minute formality finds the cost three quarters later, in a chargeback they can’t fight.