Your Carrier Agreement Isn't as Signed as You Think

A freight broker I know got served papers two years after a crash involving a carrier he'd used a dozen times. Discovery asked for the carrier agreement. He went looking. What he found was an email from three years earlier with a PDF attached. No reply. No signature. Nothing. The carrier's attorney came right at him: the carrier had never acknowledged the indemnification clause, never confirmed they'd reviewed the insurance requirements, never agreed to anything in writing. He had a PDF he'd sent to an email address and silence on the other end. He settled for significantly more than the claim probably warranted — because his paper trail was garbage.

That story is not unusual. I've talked to enough brokers navigating litigation to know the carrier agreement problem is rampant, and nobody thinks they have a problem until they're in deposition.

What the Regulation Actually Requires

49 CFR § 371.3 requires brokers to keep records of each transportation transaction, including the name and address of the carrier and the compensation received. That's the regulatory floor — the minimum FMCSA cares about. But 371.3 isn't the standard plaintiffs' lawyers are holding you to after Montgomery v. Caribe Transport II.

Since the Supreme Court's unanimous ruling on May 14, 2026, state-law negligent selection claims against brokers are back on the table in every circuit. The question at trial isn't "did you keep a transaction record?" The question is "what reasonable care did you exercise in selecting this carrier, and what proof do you have?" At load-tender time, that means you need more than a rate confirmation with a link to a terms PDF nobody clicked. You need documentation that the carrier saw your requirements, agreed to them, and that you verified their current insurance before the load moved. A carrier agreement — specifically one that captures the carrier's warranty of their authority status, insurance coverage, and federal safety compliance — is part of that proof. When a carrier warrants they're compliant and later aren't, that shifts the inquiry from your negligence to their breach. But only if you can prove they actually agreed to it.

The Email Agreement Problem

Most brokers use one of two methods: they attach a carrier packet to an email, or they put a PDF link on a rate confirmation and assume the carrier read it. Neither creates an enforceable, documented agreement the way discovery demands.

Here's the problem with email. You send an attachment. The carrier responds about pickup time. You assume the agreement covers this load. You have no proof the carrier opened the attachment, read it, or agreed to anything in it. Their attorney argues they didn't — and depending on how your email provider logs attachments, you may not be able to prove otherwise.

Version control is another landmine. Did you update your carrier agreement last fall when you added a cargo value declaration requirement? Is the carrier operating under the new version or the one from two years ago? You won't know until discovery, and if you can't answer the question, neither can your attorney.

The named-insured mismatch on the COI is a third problem. You collected a certificate when you first approved the carrier. They switched insurers six months later. The new policy has a different named insured, a lower cargo limit, and a deductible you didn't know about. Your email inbox has one COI from two years ago. The carrier has been hauling for you under coverage you've never seen.

I had a carrier — MC-1247893, DOT-3567102, approved on paper, clean BASIC scores at the time — that ran a $180,000 high-value electronics load for a shipper I was moving freight for. Midtransit, we discovered their cargo coverage had dropped from $1M to $500K three months earlier when they switched insurers. Nobody caught it because we checked their COI at approval and never again. The exposure on that load was real: $180,000 in cargo against a $500K limit that already had $300K in pending claims from earlier in the week. That was a near miss I didn't have to have.

What Happens at Deposition

If you haven't sat through a deposition on a trucking claim, let me tell you what the first hour looks like.

"When did the carrier agree to your insurance requirements?" Your answer better not be "they were on our approved list." That's not an agreement. That's a list.

"What version of your carrier agreement was in effect at the time of this shipment?" If you can't name a version and a date, you're answering with a shrug.

"Did you verify the carrier reviewed your requirements before you tendered the load?" "I assume they did" is an answer that will be repeated back to the jury in closing.

"Do you have a signed copy of the agreement with this carrier?" If the answer is "there's an email I sent them in 2023," the follow-up is "and did they reply to that email?" Usually the answer is no.

Post-Montgomery, brokers who relied on "we have them on an approved list" are about to get an expensive education in what reasonable care actually requires. A signed agreement with a documented timestamp, a verified identity, and a version-controlled record of what the carrier agreed to is the difference between a defensible file and a settlement conversation.

The AI Document Review Gap

Most brokers check a COI when they onboard a carrier. Then they file it and never look again until there's a problem.

The issue isn't that you checked the COI. The issue is that a COI is only accurate on the day you received it. Carriers change insurers. Policies lapse. Coverage limits get adjusted at renewal. The certificate you collected fourteen months ago is a snapshot of a moment that may no longer exist.

Most broker shops catch this problem in one of two ways: they find out at the worst possible moment after a claim, or they catch it randomly when they happen to glance at an expiration date. Neither of those is a system.

The smarter check happens at submission — when the carrier is actively engaging with your onboarding packet, not months or years after the fact. If a COI expires in two weeks, that surface as a flag before you approve the carrier for a load. If the named insured on the COI doesn't match the carrier's FMCSA registration, that's a flag on the packet — not a mystery you're piecing together after a claim. If cargo coverage comes in below your threshold, it shows up before the carrier gets a READY FOR DISPATCH badge, not in discovery.

That gap between "we collected a document" and "we verified what's in the document" is where a lot of brokers are exposed right now. Collecting is not the same as reviewing.

How the DOTScreener Carrier Onboarding Packet Works

DOTScreener's Carrier Onboarding packet is the mechanism I use to close the gaps I've been describing. You configure it once — upload your broker-carrier agreement, set what documents you need to collect (COI, W-9, authority, NOA, voided check, driver and fleet lists, or custom items), add your logo and a welcome message. If you don't have a standard agreement on file, DOTScreener includes a professionally written industry-standard one, branded to you, so you're not starting from scratch.

Then you send it from any carrier profile or screening result. The carrier reviews your exact PDF and signs from their phone, tablet, or desktop. The signed copy comes back with a permanent Verification ID and a QR code that lets anyone confirm authenticity — or detect if the copy was altered — at dotscreener.com/verify/agreement. That Verification ID is your proof that the specific version of your agreement was reviewed and signed, at a timestamped moment, by an identified device. It's not an email with an attachment floating in someone's inbox. It's a record.

The AI document flags run at submission. A COI expiring in two weeks surfaces a flag on the packet before you sign off on the carrier. A named-insured mismatch between the COI and the carrier's DOT registration appears as an informational flag — not an auto-rejection, but something to resolve before you dispatch. Low cargo coverage shows up as a flag before the carrier hits your approved list.

Live status tracking shows you where every carrier stands: Sent → Opened → Started → Documents Uploaded → Completed. You get a READY FOR DISPATCH badge when it's done. You get an alert if a carrier stalls out at the "Started" stage and never finishes. You see the completion rate and average time across all your carriers, which tells you something about friction in your onboarding flow.

This doesn't replace the manual vetting work. You still pull SAFER, run BASIC percentiles, check the OOS rate, make the pre-tender call. The packet is what comes after you've decided you want to work with a carrier. It's how you document that you had a signed, verified agreement and collected their current documents before they ever moved a load.

How I Document This

When a carrier completes the packet, that becomes the anchor document in their carrier file. The Verification ID goes in the file. The signed copy lives in the system under the carrier's record. When the carrier agreement gets updated, I send a new packet — the new version gets its own Verification ID and its own timestamp. No ambiguity about which version the carrier agreed to and when.

For each shipment, I note the date of the carrier's most recent completed packet alongside the SAFER pull, the BASIC check, and the pre-tender call log. If something goes wrong and I'm in discovery two years from now, the question "when did this carrier agree to your requirements?" has a specific date, a specific version of the agreement, and a verification record anyone can authenticate at a public URL.

That's what a carrier file that holds up in deposition looks like. Not a PDF you emailed into silence.

— Mason Lavallet

Founder, DOTScreener.com