Write Your Carrier-Vetting SOP So a New Hire Can Run It Without Asking You

I once watched a sales manager try to onboard a new broker rep by saying, three times in fifteen minutes, "and you just sort of get a feel for whether the carrier is sketchy." I'm not exaggerating. He genuinely believed his carrier-vetting "process" was teachable as a vibe. The new hire was twenty-two years old and had never tendered a load in her life.

That brokerage has been sued for negligent selection since then. I don't know how their deposition went, but I can tell you what the plaintiff's lawyer asked for in discovery: "Please produce the standard operating procedure your company uses to vet motor carriers prior to tendering loads." There was no SOP. There were three Slack threads, a half-finished Notion page from 2024, and the sales manager's vibes.

Don't be them. The written carrier-vetting SOP is one of the cheapest legal-defense artifacts you can produce, and it pays for itself on the first deposition. Here's how to write one that a new hire can actually run, and that holds up when a lawyer asks to see it.

What an SOP needs to do

Two jobs. One: tell a new hire — somebody who's been at your brokerage for two weeks — exactly what steps to take to vet a carrier, in what order, with what threshold for "pass" vs "ask supervisor" vs "decline." Two: produce a documented record of each step taken on each carrier, so the carrier's file shows what was reviewed and what conclusions were drawn.

If your SOP only does the first job, your brokerage is operationally aligned but legally exposed (you did the work but didn't record it). If it only does the second, you have a paper trail of unreasoned decisions. The point of writing the SOP is to fuse the two.

The five sections every SOP needs

I'll give you the structure I use. It's not the only structure that works, but it's a structure that holds up in litigation because it tracks the categories of evidence a plaintiff's lawyer will sequence through.

Section 1: Authority verification

What to check, in order:

• Pull the MC# or DOT# in SAFER. Confirm name and operating status are "Authorized."
• Confirm the carrier's operating authority on FMCSA L&I. Look for active common, contract, or hazmat authority as appropriate.
• Note the date authority was granted. **If under 18 months, escalate to senior broker for size-adjusted review (see Section 5).**
• Note any history of revocation in the L&I docket.

Documented output: a one-line note in the carrier file with the authority status, grant date, and any flags.

Section 2: Insurance verification

• Pull the carrier's L&I record. Confirm BMC-91 or 91X (BIPD) is in good standing, no cancellation effective date in the next 30 days.
• Note insurer name, policy number, and coverage minimum.
• Receive ACORD 25 from carrier.
• Call the producer listed on the ACORD 25. Confirm certificate is accurate as of today and the underlying policy covers this operation type.
• For loads over $50K declared value: confirm cargo coverage minimum, ask about commodity-specific exclusions.

Documented output: a note with the producer name, time of call, and what was confirmed. (One sentence — "Called Great West producer at 9:14am, confirmed Form 91X active for MC-1247893, no cancellation flag, no commodity exclusions on this lane" — is enough.)

Section 3: Safety performance

• Pull the carrier's BASIC percentiles. Note any category at or above intervention threshold (65% general / 60% hazmat / 50% passenger for high-risk BASICs; 80% / 75% / 65% for the others).
• Pull crash file. Note total count, breakdown by preventable / non-preventable / undecided.
• Pull driver and vehicle OOS rates. Compare to national averages (~5.5% driver / ~20.7% vehicle).
• Note FMCSA safety rating (Satisfactory / Conditional / Unsatisfactory / Not Rated) with date.

Documented output: a one-paragraph "safety snapshot" in the carrier file with the specific values. Not a screenshot — actual numbers in the file so the file is searchable.

Section 4: Attestation requirements

• For every load: collect a signed carrier safety attestation before dispatch (pre-trip done, driver fit-for-duty, valid CDL, vehicle safe, cargo securement, insurance in force, no undisclosed safety events, plus reliance + indemnification acknowledgments).
• For loads with risk modifiers (hazmat, oversize, reefer): attestation includes the corresponding additional representations.
• Capture signer name, IP, user-agent, timestamp.

Documented output: the attestation record itself, hash-chained to the review file.

Section 5: Escalation triggers

A specific list of conditions that move a load from "broker can approve" to "must escalate":

• Authority under 18 months
• Any BASIC at or above intervention threshold
• Conditional or Unsatisfactory FMCSA safety rating
• One or more preventable crashes in 24 months (or any fatal crash regardless of preventability)
• Insurance cancellation effective date within 30 days
• Carrier declines or is slow to provide attestation
• High-value freight (declared value > $X — set your threshold)
• Hazmat or oversize loads
• Carrier dispatcher uses an email domain that doesn't match the carrier's FMCSA-listed contact

Each trigger has a stated escalation path: who reviews, what they verify, what documentation gets added to the file.

The output format that holds up in deposition

The thing that separates a defensible SOP from a "we have one in Notion" SOP is that the output of every step is captured in a single, searchable, append-only carrier file. Not screenshots. Not "I called the producer" with no further detail. Specific values, captured at the moment of the lookup, timestamped.

Practical implementation: a single record per carrier-per-load that contains:

• The Authority snapshot (Section 1 output)
• The Insurance verification record (Section 2 output)
• The Safety snapshot (Section 3 output)
• The Carrier attestation (Section 4 output)
• A rationale paragraph from the broker who made the tender decision
• The date, time, and broker identity of every entry

When a plaintiff's lawyer asks "produce the diligence file for the tender that led to this crash," what you hand over is one tidy record per load that lays out, in order, what was checked, what was found, what was decided, and why. The file should be readable in two minutes by a person who's never met you.

A concrete scenario for the new hire

Walking through how this works in practice. Day three on the job, the new hire gets a load to dispatch. Carrier is MC-1247893 / DOT-3567102. They open the SOP.

Section 1 — Authority. New hire pulls SAFER. Authority active, granted 41 months ago. Not within the under-18-months escalation window. Note added to file: "Authority active, granted 2022-12-14, no revocation history. Operating status Authorized."

Section 2 — Insurance. L&I shows BMC-91X active with GREAT WEST CASUALTY, effective 09/14/2025, no cancellation flag. ACORD 25 received from carrier matches L&I. New hire calls the producer. Time-stamped: "Called GW Casualty producer 10:42am 5/21/26, confirmed policy current for MC-1247893, no commodity exclusions on this dry-van lane."

Section 3 — Safety. BASIC pull: Unsafe Driving 38%, HOS 27%, Vehicle Maintenance 49%, Driver Fitness 22%. Crash file: 1 crash in 24 months, classified Non-Preventable. OOS rates: DOOS 3.8%, VOOS 17.1% (both below national avg). Safety Rating: Satisfactory, last reviewed 2023-04-19.

Section 4 — Attestation. New hire sends the standard pre-load safety attestation to the carrier dispatcher. Carrier signs within 22 minutes. All eleven representations affirmed plus reliance + indemnification + continuing-duty acknowledgments. Record captured.

Section 5 — Escalation triggers. None apply. Authority is well-aged, no BASICs alert, no preventable crashes, insurance is current, attestation received, declared value is $42K (below the $50K threshold for additional vetting).

Rationale paragraph. New hire writes: "Routine vet. All five SOP sections complete. No escalation triggers. Tendered to MC-1247893 by [name] 11:08am 5/21/26."

That's nine minutes of work and a documented file that holds up under deposition. The new hire didn't need to ask anyone "is this carrier okay" because the SOP told her exactly what to check and what the thresholds were. The supervisor didn't have to teach her vibes.

The regulation, in plain English

There's no FMCSR section that requires brokers to maintain a written carrier-vetting SOP. The legal pressure is downstream: 49 CFR Part 371 (broker recordkeeping), the state-law negligent-selection cause of action that Montgomery v. Caribe Transport II preserved against FAAAA preemption, and the discovery rules in any jurisdiction where a broker gets sued. The SOP isn't required — what's required is that the broker exercised reasonable diligence, which is the standard the SOP is built to satisfy.

What this means at load-tender time: every load's carrier file should be the OUTPUT of an SOP step, not a one-off improvisation. The SOP itself should be a document that pre-exists the load. A plaintiff's lawyer who finds the broker drafted a "vetting process" the week after the crash is going to ask why.

How I document the SOP itself

The SOP document lives in version control. Every change has a date and an author. When I update the SOP — for instance, when the Montgomery ruling came down and I added the attestation reliance / indemnification language — the diff is preserved with the date of the change. If a plaintiff's lawyer asks "what was your SOP at the time of this load," I can show them the document AS IT EXISTED on the date of the tender, not the version that exists today.

That's a small detail. It's the kind of small detail that turns "you didn't have a process" into "here is the process, here is the version that was in force, here is the carrier file showing each step was completed."

— Mason Lavallet

Founder, DOTScreener.com

---

Sources

• [49 CFR Part 371 — Brokers of Property](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-371) — broker recordkeeping requirements
• [Hanson Bridgett — Supreme Court Unanimously Holds Negligent-Hiring Claims Against Freight Brokers Survive FAAAA Preemption](https://www.hansonbridgett.com/publication/260514_8509_supreme-court-faaaa)
• [Bricker Graydon Wyatt — SCOTUS: FAAAA Does Not Preempt Negligent-Selection Claims Against Freight Brokers](https://www.bricker.com/insights/publications/scotus-faaaa-does-not-preempt-negligent-selection-claims-against-freight-brokers-what-brokers-carriers-and-shippers-should-do-now)
• [FMCSA — Safety Measurement System Methodology (PDF)](https://csa.fmcsa.dot.gov/Documents/SMSMethodology.pdf)
• [Carrier411 — Hiring Carriers with Due Diligence](https://www.carrier411.com/duediligence.cfm)