How to Build a Defensible Carrier Vetting File (What to Document and Why)

After Montgomery v. Caribe Transport II, the strongest defense a broker has against a negligent-selection claim is no longer a legal argument — it is a file. Specifically, a contemporaneous record showing what you knew about a carrier when you tendered the load and why approving it was reasonable on that information.

Most brokerages do not have this file. They have fragments: a saved SAFER screenshot somewhere, an email thread, a row in a TMS, a carrier packet PDF. In discovery, fragments look like negligence even when the underlying work was sound. This article describes the anatomy of a vetting file that actually defends you.

The principle: prove what you knew and when you knew it

Reasonable care is judged at the moment of selection, on the information then available. The entire purpose of a vetting file is to freeze that moment so it can be reconstructed years later with documents instead of memory. Every design decision below serves that single goal.

A defensible file answers four questions without anyone having to testify from recollection:

1. What did you check?
2. What did the data show at that time?
3. What did you decide, and who decided it?
4. When did all of that happen?

The anatomy of a defensible vetting file

1. Carrier identity

• Legal entity name and DBA, USDOT and MC numbers, physical address
• W-9 and the EIN, matched against FMCSA registration and Secretary of State records
• A note of any identity mismatches found and how they were resolved

Identity is where chameleon-carrier and fraud exposure starts. Recording that you reconciled the entity — not just that you collected a packet — matters.

2. Authority verification

• Active operating authority status and classification at the time of selection
• Authority type matched to the operation (common/contract; not a brokerage-only authority hauling freight)
• Any pending revocation, suspension, or out-of-service indication
• The date and time this was checked

3. Insurance verification

• Coverage on file with FMCSA and the amounts, captured as of the selection date
• The certificate of insurance obtained directly from the carrier's agent or insurer, with named insured, limits, and effective dates
• Any discrepancy between the FMCSA filing and the COI, and its resolution

A useful nuance: FMCSA insurance filings are event-based. A filing that looks "old" often means the policy was continuously renewed with the same insurer and no new filing was generated — not that coverage lapsed. If coverage shows on file, an aged filing date is usually not a red flag on its own. Record the current on-file amount and the directly obtained COI so the file does not look like a gap that was never investigated.

4. Safety data — the point-in-time snapshot

This is the heart of the file and the part most brokerages get wrong by relying on a live link instead of a captured record. A link shows what the data says today; you need what it said then.

Capture, as of the selection date:

• The carrier's safety rating (or that it was unrated — the normal state for most carriers, not a red flag in itself)
• Inspection and out-of-service history, with enough context to show sample size
• Crash involvement, recorded with the explicit understanding that FMCSA crash data does not indicate fault
• Any adverse pattern you identified

Resist the urge to editorialize the data in the file beyond what a reasonable broker would conclude. Record what was shown and the reasonable inference, not speculation that a plaintiff's expert can mischaracterize.

5. The decision and the decision-maker

• The approve / decline / approve-with-conditions outcome
• The criteria applied and how this carrier met them
• If a borderline carrier was approved, the explicit, recorded rationale and the exception sign-off
• The name and role of the person who made the call

An undocumented "yes" is the single most dangerous artifact in a brokerage. A documented, reasoned "yes" — even on an imperfect carrier — is defensible.

6. The timestamp

Every element above needs a date, and the file as a whole needs to be tied to the specific load and tender. "We always check SAFER" is not evidence. "Here is the safety snapshot we captured on the date we tendered this load" is.

7. The ongoing monitoring log

Reasonable care does not end at onboarding. The file should continue to accumulate: re-vet dates, monitoring alerts received, and the actions taken (including holds). A file that stops at onboarding implies vetting stopped at onboarding. See continuous monitoring vs. one-time vetting.

8. Communications

Relevant carrier and internal communications about the selection belong with the file — and your retention policy has to actually keep them. This cuts both ways: disciplined, professional communications support the file; offhand messages that contradict it are exactly what plaintiff's counsel will surface.

What a defensible file looks like vs. what a liability looks like

| Defensible | Liability in discovery | |---|---| | Point-in-time safety snapshot captured at tender | A live SAFER link that now shows different data | | Recorded, reasoned decision with an approver | A TMS status of "approved," no rationale | | Consistent file structure across all carriers | One thorough file, hundreds of thin ones | | Exceptions documented with sign-off | Borderline carriers approved with no trace | | Monitoring log continuing after onboarding | File ends the day the carrier was added | | Retained per a written policy | Records purged or scattered, recovered in fragments |

The right-hand column is not necessarily a brokerage that did bad work. It is often a brokerage that did fine work and cannot prove it. After Montgomery, those are the same thing in front of a jury.

Operationalizing it

You do not need a bespoke system to do this — you need consistency and point-in-time capture:

• Standardize the file. Same fields, same order, every carrier. Inconsistency is itself evidence of an unreliable process.
• Capture, don't link. Store the safety picture as it existed at selection, not a pointer to live data.
• Make the decision a field, not a vibe. Force an explicit outcome, rationale, and approver.
• Set retention deliberately. Vetting files and related communications should outlive the statute of limitations for the lanes you run; align this with counsel.
• Keep the file alive. Append monitoring and re-vet activity so the record reflects the full relationship.

The bottom line

A carrier vetting file is no longer back-office paperwork — it is the exhibit your defense is built on. The brokerages that come through the post-Montgomery environment intact are the ones that can hand counsel a clean, timestamped, consistent record of what they knew and decided. Build the file as if it will be read aloud in a courtroom, because the ones that matter will be.

---

This article is for informational purposes only and is not legal advice. Consult qualified counsel about record retention and litigation readiness for your operations.