Most brokerages keep vetting proof scattered across TMS notes, screenshots, and email threads. That is unusable if a claim is ever filed, and the reason is not sloppiness. It is that the record was never designed to be read by anyone other than the person who created it, a year before anyone asks for it.
This guide covers what a defensible vetting record has to contain, why the common approaches fail, and how to keep one per load without adding manual work to every booking.
Why this matters more than it did
Two changes have moved documentation from good hygiene to a real financial control.
The first is the volume of fraud. Cargo theft losses reached roughly $725 million across the US and Canada in 2025, up 60% year over year, with 22% of brokers reporting more than $200,000 in losses in a single six month period (Verisk CargoNet / TIA).
The second is legal. In Montgomery v. Caribe Transport II, the Supreme Court held unanimously in May 2026 that negligent hiring claims against brokers are not preempted by the FAAAA. The threshold defense that was ending these cases before discovery in several circuits is gone. What remains is a merits question about whether your carrier selection was reasonable, and that question is answered by your file or it is answered by a jury’s impression of you.
Small brokers already understand this intuitively. One described their process on r/FreightBrokers as a checklist sheet filled out for every single load, specifically “so that in the event of something happening I can prove I have documented” it. That instinct is exactly right. The problem is that a paper sheet is hard to produce, hard to authenticate, and easy to skip when the desk is busy.
What a defensible record contains
Six things, captured per load, at the time of booking:
- Carrier identity. DOT number, legal name, dba, address on file. Enough that a reader can confirm which entity you actually booked.
- Operating authority status and registration status, recorded separately because they routinely disagree. See MC number vs DOT number.
- Out-of-service status, checked immediately before tender.
- Safety rating and its date. If it is conditional, the file should show you saw it and note why you proceeded.
- Insurance, verified with the insurer rather than from a forwarded PDF: insurer, policy number, limits, effective and expiry dates.
- Cross-entity linkage. Carriers sharing the phone number or address, and the carrier’s explanation if there were any. This is the item most often missing and the one a plaintiff’s expert is most likely to raise.
Plus one thing that is not about the carrier at all: a timestamp, and evidence that the timestamp is real.
The three ways documentation usually fails
It is a screenshot in a TMS note
Screenshots capture what a page looked like, not when it was taken. Image metadata is trivially editable, TMS notes are editable by anyone with access, and neither carries any indication of tampering. Opposing counsel will point this out, and the honest answer is that you cannot prove the screenshot was taken before the load moved.
This does not make screenshots worthless. It makes them corroboration rather than proof.
It records the conclusion, not the evidence
“Carrier vetted and approved” tells a reader nothing. So does a checkbox. The value is in the specific values you saw: authority active, registration inactive, out of service no, conditional rating dated March 2024, three linked carriers on the phone number with an explanation from the carrier.
A record of what you concluded is testimony. A record of what you saw is evidence.
It cannot be reconstructed later
This is the failure that surprises people. FMCSA data is a live database, not an archive. A year after a load moves:
- Authority status may have changed several times.
- A linked entity that shared the carrier’s phone and address may be dissolved and gone from the census.
- The MCS-150 numbers may have been replaced by a newer filing.
- The carrier may be operating under an entirely new DOT number.
You cannot look up what the record showed on the day you booked. There is no “as of” query. Either you captured it then, or that evidence no longer exists anywhere, and the only remaining account of it is the other side’s expert report.
What “timestamped” has to mean
A date typed into a field is not a timestamp, because whoever typed it could type a different one. What makes a record credible is that it was generated by a system at a point in time, is not editable after the fact, and contains content that would have been impossible to fabricate later.
That last point does more work than people expect. A record containing a linked-carrier relationship that no longer exists in FMCSA’s current data is self-authenticating in a practical sense: you could not have produced it after the linkage disappeared.
Practically, a defensible record should be:
- Generated automatically from the source data rather than typed
- Immutable once created, with no edit path for the person who benefits from editing it
- Complete, capturing the values as they stood rather than a summary
- Attached to a specific load, with your own reference number
Fitting this into a real booking flow
The objection is always the same: nobody has time to do this on every load during a busy market. Fair. Three things make it survivable.
Capture at the decision point, not as a separate task. The record should be produced by the act of booking, not by remembering to document afterward. Documentation that depends on a second deliberate step is documentation that will be skipped exactly when the market is hot, which is exactly when fraud spikes.
Pull the data once. Authority, registration, out-of-service, safety rating, fleet, and cross-entity linkage should resolve from a single lookup rather than four tabs. Most of the per-load time cost is navigation.
Accept that two steps stay manual. Verifying insurance with the insurer and calling the number on the FMCSA registration cannot be automated, and they catch the most sophisticated attempts. Budget for them rather than pretending a tool replaces them. See the ten minute check.
What to do with the record afterward
Keep it for as long as your liability exposure runs, which is longer than most people assume. Personal injury claims can be filed years after the incident, and the limitation period varies by state.
Two habits worth adopting:
- Attach the load reference. A vetting record that cannot be tied to a specific shipment is much weaker than one that names the load it supported.
- Keep the declines too. A file showing you rejected carriers for stated reasons is powerful evidence that your standard was real and applied consistently. A file containing only approvals looks like a rubber stamp, and inconsistency is the first thing opposing counsel probes for.
The short version
Check the things that matter, record the values rather than the conclusion, make sure the record is generated rather than typed, tie it to the load, and keep the declines. The goal is not to prove you are careful in general. It is to prove what was true about this carrier on the day you gave them this freight, at a point in the future when that information no longer exists anywhere else.