For mid and large motor carriers

Fix the worst-exposed gaps first.

CarrierMark grades every driver and equipment file two ways, then ranks the findings by litigation weight so your compliance team works the highest-exposure gaps before anything else. Continuous, across the whole fleet.

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

Back to the main page · See who else its for

§ 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.

§ 02 Why This Exists

The lawsuit reads your files before you do.

A crash pulls the driver’s qualification file, the unit’s maintenance record, and everything around them into discovery. Negligent hiring, retention, and entrustment cases are built from exactly the gaps CarrierMark measures, and plaintiff firms publish those target lists openly.

An audit asks the regulator’s question once a cycle. The litigation question arrives without an appointment, years after the file was made. At fleet scale the problem is volume: hundreds of drivers and units, each a file that can be attacked. Knowing every gap is not enough. You have to know which gap is the exhibit.

§ 03 Why CarrierMark

Built for a fleet that never stops moving

01

Continuous, not a once-a-year scramble

Every driver qualification file and equipment record is graded as the record changes, so nothing drifts out of compliance between audits.

02

Ranked by exposure, not alphabetically

Findings sort by how badly a file plays after a crash, so a thousand-unit fleet still knows the one file to fix this morning.

03

Two questions, kept separate

Whether a file survives a DOT audit and how it reads to a plaintiff’s lawyer are different questions. CarrierMark answers both and never averages them into one number.

04

Every unit with a DOT number

Drivers, tractors, trailers, the whole roster, under one system of record you can hand to counsel.

See it in motion

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

Illustrative promo, not carrier data

§ 04 The Process

How Vault works

One system of record for every company the FMCSA touches.

01

Set your policy.

Define your selection criteria once: operating authority, insurance on file, safety rating, out-of-service history, whatever your standard requires. Policies are versioned, so 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.

Want to see the scores run on a real DOT number? Open the live app

§ 05 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
§ 06 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.

On the litigation record

When a crash pulls a driver’s file into discovery, the record already exists, timestamped to the day you relied on it.

§ 07 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
§ 08 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.