Carrier identity
A USDOT or MC number is resolved against the FMCSA QCMobile register to establish who a carrier is. Identity is recorded as identity — it is never treated as proof that the carrier is currently insured or currently safe to haul.
VaultPilot
FMCSA compliance, safety evidence and telemetry counts
VaultPilot treats government data as evidence with a source, a time and a verification state — not as a decoration. This page describes exactly how FMCSA records are used, what they are never used for, and how position telemetry is counted.
How FMCSA data is used
Operating authority
Authority status from the register is recorded with the date it was observed. A registration record on its own is not eligibility; eligibility requires the specific facts the coverage policy names, each of them fresh.
Safety facts and provenance
Every carrier fact keeps its source, the actor that fetched it, the time it was observed, and its verification state. Facts that were reported by an operator rather than reconciled against an authoritative source stay marked as operator-reported.
What FMCSA data is never used for
FMCSA is a register of identity, authority and safety history. It is not a position source. No vehicle location in VaultPilot is ever derived from FMCSA data, and no map provider is ever treated as telemetry.
Telemetry is counted, never assumed
How a position becomes a counted observation
- 01
Consent
A driver records consent before any position is accepted. Consent is stored in a ledger that browser sessions cannot read directly; it is read server-side, scoped to the organization it belongs to.
- 02
Signed delivery
Positions arrive at a provisioned ingress endpoint bound to one organization and one provider connection, authenticated by HMAC signature with a replay window and durable idempotency. An unsigned or unbound delivery is refused, not stored.
- 03
Measured counts
The counts shown in the product are the number of signature-verified deliveries and position observations actually stored. Before the first verified delivery, the state reads 'attested — awaiting first signed delivery'. It never reads live, and it never shows a zero as if it were an achievement.
Truth states used throughout the platform
What each state means
UNKNOWN
No authoritative observation exists. Unknown is terminal: it is excluded from metrics and never replaced by a favourable default value.
BLOCKED_EXTERNAL
The check cannot be completed because an external dependency — a credential, a provider connection, a government endpoint — has not answered. The system says so rather than degrading quietly.
VERIFIED
An authoritative source answered, and the answer is recorded with its provenance and freshness. Only verified facts can satisfy a policy that authorises action.
VaultPilot is a commercial freight platform. It is not affiliated with, endorsed by, or operated on behalf of the Federal Motor Carrier Safety Administration or any other government agency. FMCSA data is consumed through the public QCMobile service under its published terms, and remains the property of its publisher.
Evidence you can inspect
Inside the workspace, every carrier fact and every telemetry count can be traced to the observation that produced it, including the ones that are still unknown.