Broker risk
You Did the Due Diligence. Can You Prove It?
· 8 min read
Two brokers can vet the same carrier on the same day. The one with timestamped records has evidence. The one with a memory has exposure.
By LongMile
Carrier vetting documentation is what turns a good process into evidence.
After a crash, cargo loss, fictitious pickup, or negligent-selection claim, the issue is not only whether your team checked the carrier. The issue is what your team saw before tender, who reviewed it, and whether the file proves the decision.
A browser tab, a memory, or a note that says “carrier looked good” will not do the job. A defensible file connects the carrier, load, user, source, timestamp, and approval before the load moves.
Quick answer
A strong carrier vetting documentation file should show what was checked before dispatch and why the carrier was approved, rejected, or escalated.
At minimum, save:
- SAFER Company Snapshot for the USDOT number
- FMCSA Licensing and Insurance record for MC authority, BOC-3, and BMC-91 or BMC-91X filings
- Safety data reviewed, including rating, OOS rates, inspections, crashes, and SMS/BASICs when available
- Carrier packet, W-9, COI, cargo limit, and insurance producer confirmation
- Identity checks for legal name, DBA, address, phone, email domain, payee, and dispatch contact
- Pass, fail, or exception decision with approver, reason, and controls
- Final tender or dispatch record showing the check happened before pickup
Why this matters after Montgomery
In Montgomery v. Caribe Transport II, LLC, U.S. Supreme Court No. 24-1238, decided May 14, 2026, the Court did not give brokers a single federal carrier-selection checklist. That means plaintiffs may still argue what a broker knew or should have known from available records under applicable negligence theories.
That makes discovery a timestamp problem.
If the file was created after pickup, after a crash, or after an insurance change, it may not answer the key question: what was reasonably visible when the broker selected the carrier?
Public data changes
FMCSA records are live records. They are not frozen litigation exhibits. A carrier’s profile months later may not match the booking date.
| Data point | Public source | How it can change |
|---|---|---|
| Operating authority | FMCSA L&I | Granted, pending, inactive, or revoked status can change |
| BI/PD insurance | FMCSA L&I | BMC-91 or BMC-91X filings can be canceled or replaced |
| Process agent | FMCSA L&I | BOC-3 filing can appear, change, or be missing |
| Fleet profile | SAFER MCS-150 | Trucks, drivers, mileage, and address can update |
| Safety data | SAFER/SMS | Inspections, crashes, OOS rates, and BASICs refresh over time |
Operator note: the MCS-150 date matters. If the packet says 18 tractors but SAFER shows one power unit on an MCS-150 filed three weeks ago, document the explanation or reject the carrier.
The defensible file framework
Use this checklist when onboarding a new carrier and before elevated-risk loads, including high value, team service, after-hours pickup, new authority, conditional rating, unusual lane, or changed contact information.
| Step | What to save | Why it matters |
|---|---|---|
| Identify the entity | USDOT, MC, legal name, DBA, W-9 payee, physical address, phone | Separates the real carrier from an impersonator |
| Verify authority | Active property authority, L&I status, BOC-3 | Confirms the carrier can operate for-hire |
| Confirm insurance | BMC-91/BMC-91X, COI, cargo limit, policy dates, producer response | Shows coverage was checked, not assumed |
| Review safety | SAFER rating, OOS rates, inspections, crashes, SMS/BASICs | Shows what safety data was visible pre-tender |
| Compare identity | Packet contact, FMCSA phone, email domain, address, factoring, payee | Helps catch hijacked MCs and payment fraud |
| Record the decision | Approved, rejected, or exception with approver and reason | Proves the business judgment made at the time |
| Preserve the file | PDF or screenshot with source URL, timestamp, user, carrier ID, load ID | Creates a record that can survive a dispute |
Checks that deserve attention
| Check | Risk if ignored |
|---|---|
| USDOT and MC do not match | Identity theft or double brokering |
| Authority is inactive, revoked, or recently reinstated | Unauthorized or high-risk carrier selection |
| COI is accepted without producer verification | Load value may exceed real coverage |
| Safety rating is conditional or unsatisfactory | Negligent-selection argument |
| OOS or crash history is elevated | Public safety data was available but missed |
| MCS-150 data conflicts with promised capacity | One-truck carrier may be offering impossible volume |
| Contact, payee, or address does not align | Payment fraud or fictitious pickup risk |
Evidence strength
| Record in file | Strength | Problem |
|---|---|---|
| Dispatcher memory only | Low | Cannot prove source or timing |
| Screenshot without timestamp | Medium | Better than memory, weak on timing |
| Timestamped source PDF | High | Shows what was visible that day |
| PDF plus exception approval | Strongest | Shows review, decision, and control |
Red flags need an exception record
Do not leave these only in Slack, email, or someone’s head:
- Conditional or unsatisfactory safety rating
- Not Rated carrier on a high-value or sensitive shipment
- Authority less than 90 days old on an urgent load
- Pending or recent insurance cancellation filing
- COI producer cannot verify coverage using independently sourced contact information
- SAFER address, W-9, remittance, and packet address do not align
- New Gmail-style domain for a carrier with an older FMCSA record
- Carrier offers multiple trucks while MCS-150 shows one driver or one power unit
- Dispatcher will not provide driver, CDL, tractor, trailer, or plate before pickup
An exception is not automatically a rejection. It is a documented business decision. If you proceed, record who approved it, why, and what control was added, such as producer-confirmed cargo coverage, shipper photo verification, GPS check-in, or manager approval.
Manual vs automated workflow
| Process | Time-on-task | Best use |
|---|---|---|
| Manual tabs and screenshots | 8–15 minutes per new carrier | Low volume or unusual exceptions |
| Automated data pull | 30–90 seconds to review pulled records | Repeatable onboarding and monitoring |
| Hybrid workflow | Fast pull plus human approval | Litigation-ready files with business judgment |
Manual work can be defensible if it is disciplined. The problem is consistency. A busy desk will eventually skip a screen, forget the producer call, or overwrite a carrier profile with current data.
A hybrid process is usually stronger: automate the data pull, then require a human decision for exceptions.
How to save the record
Use a file name a claims adjuster, attorney, or owner can understand without calling the dispatcher.
Example: `2026-06-18_1014-ET_MC123456_Load98765_SAFER.pdf`
Save these fields with every verification:
- Date and time, including time zone
- User who performed the check
- Load ID, customer, pickup date, and commodity class if relevant
- USDOT, MC, legal name, and DBA
- Source name and URL, such as SAFER, FMCSA L&I, SMS, insurer, producer, or carrier packet
- Decision, approver, exception reason, and mitigation
Do not overwrite old carrier records with current ones. Append new records by date. If your TMS or cloud drive supports permissions, lock completed vetting files as read-only after delivery.
Common mistakes brokers make
- Checking only the MC number and not matching the USDOT
- Treating a COI PDF as verified coverage
- Saving current carrier data after an incident instead of pre-tender data
- Having a strict policy but undocumented exceptions
- Treating Not Rated as the same as safe
- Keeping one live carrier profile with no historical snapshots
- Approving a carrier verbally with no approver in the file
Carrier vetting documentation FAQ
Is a SAFER screenshot enough?
No. SAFER is important, but it does not prove cargo coverage, identity, payee legitimacy, or producer-confirmed insurance. Save SAFER, L&I, insurance verification, carrier packet, and the decision record together.
Should we document carriers we have used for years?
Yes. Familiar carriers change. Insurance can lapse, authority can be revoked, contacts can be hijacked, and safety data can deteriorate. Re-save records at re-vet intervals and before elevated-risk loads.
What if the carrier looked clean at booking but changed later?
That is why same-day records matter. A timestamped pre-tender file can show what was available when the selection decision was made. A current screenshot taken months later cannot.
How long should we keep vetting records?
Set retention with counsel and your insurer. As a practical rule, do not keep carrier vetting records for less time than your load documents, claims files, and insurance reporting obligations.
Does documentation eliminate broker liability?
No. It is not legal immunity. It gives you evidence of what was checked, when it was checked, who approved it, and how exceptions were handled.
Final thought
Carrier vetting documentation is not paperwork for its own sake. It is how a broker proves the carrier-selection decision that happened before the load moved.
If your current file would force you to reconstruct the day from memory, tighten the process now. If you want a cleaner way to verify, monitor, and preserve carrier checks, Longmile can help your team save the records brokers need before tender.
Tags: carrier vetting documentation, broker due diligence, carrier vetting records, FMCSA SAFER screenshot, same-day carrier verification, broker compliance documentation