Carrier selection · Compliance records
What Is a Carrier Vetting Compliance Record?
The evidence a freight broker should preserve for every carrier selection.
Vetting a carrier and being able to show it later are different things. The hard part is reconstructing, months or years afterward, what a brokerage actually knew about a specific carrier on the day it gave that carrier a specific load — and why it decided the carrier was acceptable. That gap is what a compliance record closes. It is an informational concept here, not a legal standard; no court or regulator prescribes a format.
Why the record matters now
In May 2026, the Supreme Court held in Montgomery v. Caribe Transport II that federal preemption is not a categorical defense to claims that a broker negligently selected an unsafe carrier. Since then, courts have been asking a practical question: what did the broker know, what did it check, and was the selection reasonable? Our Freight Broker Liability Case Tracker follows those decisions as they develop.
The cases cut both ways: some rulings have gone against brokers, and at least one has gone for a broker. But where claims proceed, the questions turn on facts about the selection decision itself — and those facts are hardest to establish exactly when a carrier's data has since changed, the dispatcher has since left, and the only surviving evidence is a carrier profile showing how things look today. A compliance record is how a brokerage answers those questions from the record rather than from memory.
A lookup is not a record
A common substitute for a compliance record is a saved lookup: a screenshot of the carrier's authority, a monitoring-service profile, a note in the TMS. Those show the carrier. They don't show the decision.
- What a data source said about the carrier
- Usually as of today, not as of the load
- Nothing about which rules applied
- Nothing about who decided, or why
- What the brokerage's own policy required for this load
- What each source said at decision time
- How every concern was weighed and resolved
- Who approved it, on what basis, and that nothing changed afterward
Put simply: the lookup preserves information. The record preserves the brokerage's decision process — the rules it set, the rules it followed, and the judgment a person exercised on top of them.
The anatomy of a compliance record
A complete record answers ten questions. Each element below notes where it appears in our specimen record, which uses entirely fictional data.
-
Which load was this decision about?
The record is anchored to one shipment: the lane, the dates, the equipment and commodity, and the declared value. Selection is a load-level decision, and a high-value or sensitive load may carry requirements an ordinary one doesn't.
IN THE SPECIMEN · Load block — lane, pickup and delivery dates, declared value that triggers a high-value tier -
Which carrier, exactly?
Legal name, any DBA, and the identifiers the decision was made against, confirmed against the federal record — along with authority status, safety rating, and fleet size as they stood at decision time, not as they stand today.
IN THE SPECIMEN · Carrier block — identity confirmed against the FMCSA record -
What policy did the brokerage apply?
The version of the brokerage's own written carrier-selection policy in force for this load, captured with the record. A policy that later changes shouldn't rewrite what an older decision was measured against.
IN THE SPECIMEN · "Policy applied" — policy version and tier, snapshot sealed with the record -
What sources were consulted, and when?
Each source by name, with the time its information was retrieved. Timestamps are what separate "the carrier was fine" from "the carrier was fine as of 2:29 p.m. on the day we booked it."
IN THE SPECIMEN · "Sources consulted" — each source with its retrieval time -
Did the carrier meet each requirement for this load?
The policy's requirements applied to this carrier and this load, with an outcome for each: passed, failed, or reviewed. This is where consistency becomes visible — the same rules, applied the same way, on every load.
IN THE SPECIMEN · Rules table — baseline and high-value-tier requirements, each with its outcome -
What concerns came up?
Anything in the evidence that deserved a closer look, stated plainly — not only the clean results. A record that shows no concerns at all can be less persuasive than one that shows a concern was noticed and dealt with.
IN THE SPECIMEN · "Current assignment review" — two findings, including an out-of-service event in the inspection history -
How was each concern resolved?
For every concern: what evidence was considered, what was concluded, who resolved it, and when. "Reviewed in context" is a legitimate resolution — as long as the context is written down.
IN THE SPECIMEN · Each finding closes with its resolution, the reviewer, and a timestamp -
What did the brokerage already know about this carrier?
Earlier determinations — a name discrepancy resolved last spring, an agreement on file — carried forward with their original dates and authors. Facts can carry forward; judgment on this load is new.
IN THE SPECIMEN · "Carrier review history (carried forward)" -
Who decided, and why?
A named decision-maker and a written basis for the approval, in their words or attested by them. This is the heart of the record: it shows a person exercised judgment, not that software returned a green light.
IN THE SPECIMEN · Decision block — reviewer name, written basis, approval time -
Can it be shown the record hasn't changed?
A timeline of how the decision unfolded, and an integrity seal — a cryptographic fingerprint taken at approval — so the record can later be checked against itself. A record that can be quietly edited after the fact is much weaker evidence than one that can't.
IN THE SPECIMEN · "Record timeline" and the SHA-256 "Integrity seal"
What a record should never claim
A compliance record is only as credible as its most careful sentence. The same discipline that makes it persuasive also sets its limits:
- No absence claims beyond what was checked. "No red flags" means nothing unless it says which sources were reviewed. An unchecked source is not a clean one.
- No borrowed verification. Information reported by a TMS or a third party should be labeled as such, not presented as independently confirmed.
- No reconstruction after the fact. A record assembled after a crash, from today's data, documents today — not the decision.
- No promise of an outcome. A good record shows what process was followed and that it was applied consistently. It does not make a broker immune from suit, and it shouldn't say so.
When a record should be created
At the moment of the selection decision for a specific load — after the evidence is refreshed and before the carrier is committed. Onboarding records establish who a carrier is; a compliance record establishes why that carrier was acceptable for this shipment on this day. For how current the underlying information needs to be, see how often freight brokers should recheck a carrier; for what to look at, see what to check before every load.
See a complete record
Our two-page specimen shows every element above in a single approved decision: a high-value load, a carrier with one out-of-service event in its history, and a reviewer who weighed it and wrote down why.
Every name, identifier, and event in the specimen is fictional — including the brokerage, carrier, load, insurer, and personnel.
Open the specimen record (PDF)CarrierBasis applies your brokerage's written policy to current carrier facts at the moment of selection, guides the reviewer through every concern, and seals each approved decision into a compliance record like the one above.
Watch the 60-second demo See how CarrierBasis works