The Federal Record-Keeping Rule for Brokers Is About Money, Not Safety

A broker I know got his carrier files subpoenaed after a crash. He was proud of his compliance program. His office ran quarterly audits. They maintained signed carrier agreements, COIs, authority confirmations. He told me before the deposition that he wasn't worried — he kept all the records the law required.

The law required him to document who moved the freight, who got paid, and how much. He had all of that. He had nothing about why he chose that carrier, what he'd verified about their safety at the time of tender, or what their BASIC scores looked like on the date he booked the load.

The distinction cost him.

What § 371.3 Actually Says

49 CFR § 371.3 is the broker record-keeping regulation. It lives in Part 371, which governs property brokers (not household goods, which are Part 375). The section is short. Here's the substance:

A broker must keep a record of each transaction for three years. The record has to include the names and addresses of the consignor and consignee, the name and registration number of the motor carrier used, the bill of lading or shipment identifier, the compensation received by the broker for the brokerage service and who paid it, the total freight charges collected, whether charges were prepaid or collect, and any non-cash payments between the broker and carrier.

That's the regulation. It's a financial transaction record. It exists so FMCSA can audit whether brokers are operating on registered authority and so shippers can verify they weren't overbilled or double-dipped. It is specifically about money flows and party identification — not about safety due diligence.

Read it again if you need to. There's no line in § 371.3 that says "document what you verified about the carrier's BASIC scores." There's no line that says "retain evidence that you checked operating authority status at the time of tender." There's no line that says "note what you saw on SAFER and what you decided about it."

The regulation is silent on all of that. Which means if you've been building your compliance program around § 371.3, you've built something that will pass an FMCSA audit and fail a deposition.

The Litigation Standard Is Different

After Montgomery v. Caribe Transport II, LLC — the Supreme Court's unanimous May 2026 decision reversing 7th and 11th Circuit preemption precedent and opening state courts to negligent-selection claims against brokers — the question isn't whether you kept the federally required records. It's whether you exercised reasonable care in selecting the carrier.

"Reasonable care" isn't defined in Part 371. It's a state tort standard, defined by what a reasonably careful broker in your position would have done, evaluated by a jury that will hear expert testimony about industry standards. That standard is dramatically higher than what § 371.3 requires.

Here's what a plaintiff's attorney typically builds a negligent-selection case around:

Did you verify operating authority was active at the time of tender — not at onboarding, at tender? Did you check the carrier's BASIC scores and what did they show? Did you verify insurance was current, via L&I at fmcsa.dot.gov, not just via a certificate that might have been issued months earlier? Did you note any red flags — a BASIC alert, a recent OOS finding, authority under 12 months — and did you make a documented decision about them? Did you perform any additional diligence commensurate with the load value or commodity?

None of those questions can be answered with a § 371.3-compliant record. The § 371.3 record says you used MC-1847293 to move freight from Chicago to Memphis for a certain amount of money. It doesn't say you ran that MC number before you booked the load. It doesn't say you checked their 34th-percentile Vehicle Maintenance BASIC and decided it was acceptable for a dry van load under $50K. It doesn't say anything about safety at all.

In discovery, that silence is not neutral. Plaintiff's counsel reads it as: no record of safety verification means no safety verification happened. Whether or not that's technically true doesn't matter much — the burden of proof in a negligent-selection case is on the broker to show due diligence, and a financial transaction record doesn't discharge that burden.

The Paper Trail Plaintiff's Attorneys Actually Reconstruct

In my experience of working with people who've been through freight litigation, the first things plaintiff's attorneys request in discovery aren't your § 371.3 records. They start with:

The carrier's FMCSA snapshot as it existed on the load date, pulled from SAFER's historical data. They're looking to see what you should have seen when you screened. Then they request your screening records for that same date — what you actually pulled and when. If your file doesn't have a dated SAFER printout or a software-generated screening report for that load, you can't show those two pictures are the same. You can't even show you looked.

Then they want the insurance verification record — specifically, whether you ran L&I on the date you tendered, not just when you onboarded the carrier. Carriers who were clear at onboarding can lapse mid-year, switch insurers, or have a pending cancellation notice sitting in L&I for three weeks before you'd ever see it on SAFER. If you didn't pull L&I at tender, you don't know what the insurance looked like when you put freight on that truck.

Then any internal communications — Slack messages, emails, dispatch notes — about that carrier around the load date. You'd be surprised how many times "just saw their BASIC went yellow, going to monitor" shows up in an email chain alongside a tender record from the same week. That kind of note turns a general negligence theory into a specific knowledge-and-disregard argument.

Then the carrier agreement itself, signed and dated. Specifically the provisions about the carrier's obligation to maintain insurance and operating authority, and your right to verify both. Most broker-carrier agreements have these clauses. The question in discovery is whether you enforced them — and the answer to that question lives in your per-load records, not in the agreement itself.

None of these documents are required by § 371.3. All of them are what a competent defense requires.

The Three-Year Window

Here's what makes this particularly important: § 371.3 requires you to keep transaction records for three years. That three-year retention period is doing double duty — it satisfies the regulatory requirement AND sets the outer bound of how far back plaintiff's attorneys can reasonably expect your records to run.

If you keep § 371.3 records for three years but you're not keeping safety verification records for three years alongside them, you've created a filing system that proves you used a carrier but can't prove you screened them. Three years of "we paid MC-1234567 $3,800 to haul freight" alongside zero safety records for that same carrier is a coherent argument for negligence if that carrier was involved in a crash.

The fix isn't complicated. Keep the safety verification record — dated SAFER pull, dated L&I check, any notes from a pre-tender call, any BASIC concerns noted and resolved — in the same file as the § 371.3-compliant transaction record. The same three-year retention. The same organized structure. You're already keeping the transaction file; adding the vetting record is a discipline issue, not a systems issue.

What "Carrier Onboarding" Records Get Wrong

A lot of brokerage operations treat carrier vetting as an onboarding event. They pull SAFER once, verify insurance once, get a signed carrier agreement once, and then that carrier goes on the approved list. From that point on, their § 371.3 records prove they used an approved carrier. The onboarding file proves they screened the carrier at some point.

What neither record shows: the carrier's safety profile on the date of any specific load, months or years later.

This matters because BASIC scores change. Insurance lapses. OOS rates creep up. An authority that was 14 months old at onboarding is 26 months old now, and if their inspection count went from 8 to 47 and their Vehicle Maintenance BASIC went from 55th percentile to 83rd percentile, you'd want to know that before tendering a $280,000 load of electronics. The onboarding record doesn't know it. The § 371.3 transaction log doesn't know it. The only record that knows it is a per-load verification you ran on the tender date.

The cases that hurt brokers worst aren't the ones where they hired a carrier with a terrible record on the day of onboarding. Those are easier to defend against — the carrier wasn't screened properly, period. The cases that hurt are the ones where the carrier was legitimately clean at approval and deteriorated over time, and nobody caught it because "they're on the approved list" substituted for "I verified their safety on this load."

What the Per-Load Vetting Record Has to Say

I'm not going to tell you what software to use or what format to build. The content is what matters. A defensible per-load record, keeping pace with the § 371.3 transaction record, should be able to answer five questions for any load you moved:

What was this carrier's operating authority status on the date I tendered this load, and where did I confirm it?

What was the status of their FMCSA-filed insurance at the time of tender — not their ACORD 25, but L&I — and was there any cancellation notice pending?

What did their BASIC percentiles look like at the time of tender, and did any of them exceed intervention thresholds or require a documented decision?

Was there any red flag — authority age, recent OOS finding, carrier type, commodity mismatch — that I noted, evaluated, and documented a decision about?

If I made a pre-tender call, what was discussed and who did I speak with?

Five questions. The answers don't have to be long. A paragraph per question is fine. The point is that the answers exist, that they're dated, and that they're in a file you can produce three years from now.

The § 371.3 record tells the story of a transaction. The per-load vetting record tells the story of a decision. Courts are interested in decisions.

How I Document This

Every load I tender gets two attached records. The transaction record — parties, compensation, BOL number, the § 371.3-compliant content — goes in the load file. The vetting record goes in the same file with a timestamp:

"Vetting pull — [DATE/TIME]. SAFER authority status: Active. MCS-150 last updated: [DATE]. BASIC scores: Unsafe Driving 34th, HOS 29th, Driver Fitness 41st, VH Maintenance 58th, Controlled Substances/Alcohol no data, Crash Indicator 27th. No intervention thresholds exceeded. L&I insurance status: Active, [INSURER NAME], no pending cancellation notices. Authority tenure: 38 months. No pre-tender call conducted — standard dry van load, carrier has six prior moves in our system with no incidents. Load approved."

That paragraph takes three minutes to write. It answers every question a plaintiff's attorney will ask about what I knew when I tendered. It's not because I'm worried about every load — most loads are fine, most carriers are fine, and most of that paragraph is going to say "no issues." It's because I don't know in advance which load is the one, and writing this down when the information is in front of me is orders of magnitude easier than trying to reconstruct it three years later from fragments of memory and stale SAFER data.

The federal record-keeping requirement tells you to document the transaction. The litigation standard tells you to document the decision. Both are three-year obligations. Only one of them will help you in court.

— Mason Lavallet

Founder, DOTScreener.com