Your Carrier Agreement Isn't Evidence. Here's How to Make It One.

Three months into litigation over a crash involving one of our approved carriers, the opposing counsel's discovery request came back with a specific flag I hadn't expected. They wanted the original carrier agreement, the metadata proving when it was created, and any record of who, specifically, had signed it on the carrier's behalf.

What I had was a PDF. The carrier contact had filled in the fields, printed it, signed it by hand, scanned it, and emailed it back to us. The metadata on the file showed it had been created on a Tuesday afternoon, by a user on a Windows 10 machine, four months before the crash. The scan was timestamped in our email system. The signature was a handwritten scrawl on a blank line. There was no way to know whether the person who signed it had any authority to bind the carrier, whether the document had been modified between the time it was signed and the time it hit our inbox, or whether the version we had on file was the version the carrier had reviewed before signing.

We spent six months and a not-small amount in legal fees establishing the provenance of a four-page PDF that nobody had tampered with. Because the carrier agreement's chain of custody was a mess, it looked like a mess, and a skilled attorney can make that work.

That was my education in the difference between a carrier agreement and a carrier agreement that functions as evidence.

What a carrier agreement is supposed to do

On paper, a carrier agreement is a contract between your brokerage and a motor carrier establishing the terms under which you'll tender freight. The carrier represents their authority is active, their insurance is current and meets your minimums, their drivers are qualified, their equipment is maintained, and they won't re-broker your loads without permission. You agree to pay within a certain window and follow certain claims procedures.

In practice, most broker–carrier agreements are templates from a legal form service, sent as PDFs to whoever answers the carrier's dispatch phone, signed by whoever happens to be standing there, and filed in a folder called "Carrier Packets" that nobody opens again until something goes wrong.

After Montgomery v. Caribe Transport II — the Supreme Court's May 2026 ruling that state-law negligent-selection claims against brokers are not preempted by federal law — that folder's contents are now part of your legal defense strategy whether you've thought about them that way or not.

The four questions a plaintiff's attorney will ask about your carrier agreement

Who signed it?

This sounds obvious, but think about what you actually know. You have a name on a signature line. Do you know whether that person had authority to bind the carrier? Do you know whether the person is still with the company? Do you have any way to verify, at the time the agreement was signed, that the signatory was who they said they were?

In a credible carrier onboarding workflow, the answer to all three is yes. In most actual carrier onboarding workflows, the answer to all three is "we don't know — we assumed."

When exactly was it signed, relative to the first load you tendered?

49 CFR § 371.3 requires freight brokers to keep records of each transaction, including the names of the parties, for three years. But that's about individual loads. The carrier agreement is supposed to predate the first load — it establishes the baseline relationship. If the agreement was signed three days after the first load moved, that sequence matters. A plaintiff's attorney will ask whether you were operating under a carrier agreement at the time of the first load, or whether you were patching together paperwork retroactively.

Most brokers can't answer this with precision because their carrier-packet workflow is informal. The load gets booked, the carrier gets added to the TMS, and the agreement request goes out whenever someone remembers to send it.

Was the document modified after it was signed?

With a scanned PDF, you genuinely cannot answer this question. You received an image of a signed page. Someone could have typed different terms into the base document after the fact — you wouldn't know from the scan. The carrier couldn't verify their copy hasn't been altered either.

This isn't a hypothetical attack. Document integrity disputes come up in commercial litigation regularly. The moment opposing counsel raises it, even if nothing was actually changed, you're spending money to prove the negative.

What did the carrier represent about their safety compliance?

This is the question that has the most teeth. A carrier agreement that says "Carrier represents it is in compliance with all applicable FMCSA regulations" is a legal platitude. A carrier agreement signed by a specific, identified individual — with a timestamp proving it was executed before the first load — that contains specific representations about authority status, insurance levels, driver qualification standards, and equipment maintenance is a document that creates real legal obligation on the carrier's side. And it's a document that shows, in discovery, that you took those representations seriously enough to get them in writing with a verified identity behind them.

The authority trail and why it matters under § 390.35

49 CFR § 390.35 makes it a violation for any carrier or driver to misrepresent their safety record or compliance status to a shipper, broker, or anyone else making a carrier-selection decision. This is a two-edged provision. It establishes that carriers have a regulatory duty not to lie to you. If a carrier misrepresented their safety status in your agreement, that's their violation, not yours — but only if you can show that you had them make those representations in a formal, documented way.

A verbal assurance on a T-call is not § 390.35 compliance. An email from the dispatcher saying "yeah we're good" is not § 390.35 compliance. A signed carrier agreement, with the carrier's specific representations on file, is at minimum evidence that you attempted to document compliance. That distinction can matter when the jury is deciding whether you were negligent in how you approved the carrier.

What most carrier agreements are actually missing

The gap isn't usually the agreement language itself. Most brokers use agreements that cover the right territory. The gap is in the execution record.

A signed PDF in an email thread is not an evidence-grade document. It doesn't have a signer identity that can be independently verified. It doesn't have metadata that proves the document's contents at the moment of signing. It can't prove the carrier reviewed the full document before signing — they might have clicked past everything and signed a blank page. And when the broker's paralegal printed it three years later and handed it to outside counsel, the chain of custody is already murky.

Take MC-1483726 / DOT-3892147, a carrier I'll call Ridgeline Transport as a stand-in for a scenario that plays out regularly. Two years after onboarding, Ridgeline is in a bad crash on I-70. The broker's attorney asks for the carrier agreement. What they find:

An unsigned master template in the carrier folder, last modified by someone's Windows username three years ago. A separate "signed version" — a scan of four pages that may or may not be the same version as the template. An email thread where dispatch said "attached is our agreement, LOL go ahead and sign." A timestamp on the scan of unknown reliability. No verification of the signatory's authority or identity.

The plaintiff's attorney doesn't need to prove the agreement was tampered with to use this effectively. They just need to show the jury that the broker's carrier-vetting process was so informal that the agreement might as well be worth nothing. That's enough to frame the entire approval as reckless.

What an evidentiary carrier agreement actually looks like

The standard I use now — and that I built DOTScreener's Carrier Onboarding packet around — has a few non-negotiable components.

The carrier reviews the exact PDF you want them to sign, not a fillable form that generates a different document on the backend. The signature is collected electronically, with the e-signature tied to the signatory's verified identity. The signed copy comes back with a professional signature certificate that includes a permanent Verification ID and a QR code — anyone can scan it and confirm at dotscreener.com/verify/agreement that the document is exactly what it was when signed, and that the signature is authentic.

That last piece is the one that ends the document-integrity question. When opposing counsel asks whether the carrier agreement was modified after signing, the answer is no — and that answer is independently verifiable by a third party, not just by our word.

The other components are table-stakes: the agreement goes out attached to a screening record that includes the carrier's MC and DOT, the packet is sent before the first load moves (not after), and the status trail from Sent → Completed is logged with timestamps so there's no ambiguity about sequence.

The carrier also pre-fills everything DOTScreener already knows — their name, authority number, insurance — and confirms it. That confirmation is part of the record. They're not just signing the agreement; they're affirming their compliance data at the time of signing.

The AI flag you don't want to miss

One of the things I didn't expect to matter as much as it does is the AI document review that runs on the COI and W-9 the carrier submits as part of the onboarding packet.

Specifically, it flags named-insured mismatches on the COI — situations where the entity insured is not the same entity with the MC authority. This comes up more often than you'd think. A carrier operates under one business name, hauls under a different DBA, and the policy was written to the holding company. The names don't match. If you don't catch this at onboarding, you catch it at claims time, and that's a much worse moment.

The flag doesn't auto-reject anything. It surfaces as an informational note on the packet — "Named insured on COI does not match carrier DBA on file; verify before approval." That's a five-minute check that could prevent a six-figure problem.

How I document this

Every carrier I work with goes through a carrier onboarding packet before the first load moves. The packet is configured with my broker–carrier agreement, my insurance minimums, and my ACH form. When the carrier completes it:

• The signed agreement has a Verification ID that's verifiable via QR code at any point in the future
• The carrier's MC and DOT are pre-filled and confirmed by them at signing
• Any COI or W-9 submitted is reviewed for insurance flags before I mark them Ready for Dispatch
• The packet completion timestamp is logged against the carrier's FMCSA screening record

In discovery, when I'm asked for the carrier agreement for MC-1483726 / DOT-3892147, I'm not producing a scanned PDF and hoping nobody asks hard questions. I'm producing a signed agreement with a verification QR code, a signature certificate, a completion timestamp, and a linked screening record. That package answers the four questions a plaintiff's attorney is going to ask.

The 49 CFR § 371.3 recordkeeping requirement isn't satisfied by the existence of a carrier agreement. It's satisfied by maintaining records that actually tell the story of how the carrier was approved, by whom, and when. A verified onboarding packet is the closest thing I've found to a record that holds up.

— Mason Lavallet

Founder, DOTScreener.com