Built by a trucking defense litigator

Know your litigation exposure before a plaintiffs lawyer does.

CarrierMark grades every carrier file two ways: whether it survives the audit, and how it plays after a crash. Findings rank by exposure, so you fix the worst risk first. And what you decide is sealed the moment you decide it.

This page showcases the product. Run the two scores on a real carrier inside the live app.

For fleets, owner-operators, freight brokers, shippers, and the insurance carriers behind them.

CarrierMark
§ 01 The Scores

Two scores, never collapsed.

Compliance Status
0/100
At Risk
Would this survive a DOT audit?
Litigation Exposure
0/100
High
How badly does it play after a crash?

This file would mostly clear an audit but carries high litigation exposure. That gap is what a plaintiffs lawyer attacks.

Illustrative scores, not carrier data

Compliance Status

Would this file survive a DOT audit? Whether the record would pass a compliance review under 49 C.F.R. Part 385. The regulators question.

Litigation Exposure

How does it play after a crash? How strongly the file supports a negligent hiring, retention, or entrustment case. The plaintiffs lawyers question.

See it in motion

The record has to exist before the crash, not after.

Illustrative promo, not carrier data

§ 02 The Process

How Vault works

One system of record for every company the FMCSA touches.

01

Set your policy.

Define your carrier-selection criteria once: operating authority, insurance on file, safety rating, out-of-service history, whatever your standard requires. Policies are versioned. You can prove which rules were in force on any given date.

02

Decide the way you always decide.

At selection, Vault pulls the carriers public FMCSA record and seals it: a timestamped snapshot of exactly what was knowable on the day of your decision. Raw data preserved as pulled. Nothing summarized away.

03

Handle exceptions on the record.

When business requires an exception, it runs through a structured override with a documented justification and an approver. No free-text landmines. No silent workarounds.

04

Export the Defense Packet.

One click produces the decision-date record: the sealed snapshot, the policy version in force, the decision trail, bound in a tamper-evident chain proving nothing was altered after the fact.

Watch the 30-second walkthrough
§ 03 The Record

The defense exhibit that exists before the crash.

What you decide is sealed the moment you decide it: the carriers public FMCSA record and the decision you made, bound in a timestamped document with a cryptographic hash and a verified chain. The file proves on its face that nothing was altered after the seal, so years later the answer to what you knew and what you did is a document, not a memory.

Illustrative specimen, not carrier data
§ 04 Scope

What Vault is not

Vault is not an onboarding packet tool. It is not a monitoring subscription. It is not a carrier safety predictor. Keep the platforms you use to find, onboard, and track carriers. Vault sits alongside them as the evidence layer.

And one thing we will never do: tell you a carrier is safe. Nobody can promise you a carrier is safe, and a vendor who does is drafting a plaintiffs exhibit. Vault documents the thing the law actually asks of you: reasonable care, exercised with the information available, recorded when it happened.

§ 05 The Ruling

The rules changed on May 14, 2026

On May 14, 2026, a unanimous Supreme Court held in Montgomery v. Caribe Transport II, LLC that federal law does not preempt state negligent-selection claims against freight brokers. The preemption argument brokers leaned on for decades is no longer a reliable way out of these cases. Negligent-selection claims now proceed into full discovery, anywhere your loads run.

Discovery in these cases targets your selection process. What your software showed. What your monitoring logs recorded. Whether your own system flagged the carrier, and what your team did next. Plaintiff firms publish these target lists openly.

Here is the problem: the public record moves every day. Authority status, insurance filings, inspection history, safety ratings, all of it changes. The lawsuit arrives years after the decision. Without a decision-date record, your defense becomes testimony about what your process would have shown. An argument, where an exhibit should be.

From the record

In Montgomery itself, the plaintiff alleged the carrier held a conditional safety rating from FMCSA when the broker hired it. The case turned on what the broker knew, or should have known, that day.

§ 06 The Standard

The law asks for reasonable care. Vault is how you prove it.

As even plaintiffs counsel stressed, brokers should be able to successfully defend against state tort suits if the brokers have acted reasonably and arranged transportation with reputable trucking companies.
Montgomery v. Caribe Transport II, LLC, No. 24-1238, slip op. at 5 (U.S. May 14, 2026) (Kavanaugh, J., concurring)

Even the plaintiffs own lawyer told the Supreme Court a broker is not going to have a problem if its asking the hard questions of the carrier. Id. (quoting Tr. of Oral Arg. 45).

The Court did not make brokers the insurers of every truck on the road. It made your selection process the question. Reasonable care, documented when it happened, is a defense. Undocumented care is a story.
Vault is the record of asking the hard questions.

§ 07 Provenance

Built from the defense table

TMFounder

CarrierMark was designed by Thomas Murphree, founder of Murphree Holdings and a practicing trucking-defense litigator and CDL holder. It is built around the document requests plaintiffs counsel actually serves: the vetting file, the flag history, the override trail. Every design decision answers a question he has watched get asked under oath.

§ 08 Questions Asked Under Oath, and Otherwise

FAQ

If Vault flags a carrier and we proceed anyway, doesnt the record hurt us?

Your vetting decisions are discoverable with or without Vault. Silence is not protection; a gap in the file is. The override workflow exists so a business judgment is recorded as a judgment: what was known, what justified proceeding, who approved it. A documented decision can be defended. A missing one cannot.

FMCSA itself says its data has limits. Why build a record on it?

Because the legal standard is reasonable care with available information, not perfect information. Vault preserves what was publicly knowable at the decision. Your policy decides what weight each data point carries.

We already use an onboarding or monitoring platform.

Keep it. Those tools answer who is this carrier and how are they performing. Vault answers what did we know, and what did we do, when we selected them, in a form built for the courtroom rather than the back office.

Is our Vault data discoverable?

Assume yes, like the rest of your operational records. Vaults purpose is to make the discoverable record complete, contemporaneous, and tamper-evident instead of partial and reconstructed.

When can we start?

The founding cohort onboards within two weeks. The free snapshot tool is live now.

§ 09 Founding Cohort

Founding partner program

We are onboarding a founding cohort of 8 operations before general availability.

  • Founding partners get: locked founding pricing for life, direct input on the roadmap, priority onboarding, and first access as each module ships.
  • We ask for: real loads, real usage, and honest feedback.
Application for Founding Access
§ 10 Free Snapshot

See what a decision-date record looks like

Enter a DOT number and get a free snapshot of the carriers current public FMCSA record, formatted the way Vault seals it.

Free Carrier Snapshot

The record exists the day you decide, or it never does.

Founding cohort applications are open. The free snapshot tool is live now.