§COMPLIANCE Built for the regulator's eye

One regulation. Done exactly right.

CDLVOE is narrowly built for FMCSA § 391.23 verification of employment — the 30-day previous-employer investigation that quietly fails most carriers. Below is the line-by-line view of what we cover, how, and where the evidence lives.

01FMCSA Regulations covered
§ 391.21
DRIVER APPLICATION

Application for employment

CDLVOE's kiosk and PDF parser both produce a § 391.21 application: three years of employment, the accident and violation disclosures, licence history, and the driver's signed affirmation of accuracy.

3-YR EMPLOYMENTACCIDENT DISCLOSUREVIOLATION DISCLOSURELICENSE HISTORYSIGNED AFFIRMATION
§ 391.23
INVESTIGATION

Investigation and inquiries

The heart of CDLVOE. Every previous DOT-regulated employer is contacted inside the 30-day window on the channel your contact details support. Replies are matched, filed, and timestamped. When an employer cannot be reached, CDLVOE documents the three-attempt good-faith effort automatically.

30-DAY DEADLINE3-YEAR LOOKBACKCHANNEL PER EMPLOYERGOOD-FAITH DOCS
§ 40.25
DRUG & ALCOHOL VOE

Drug & alcohol prior-employer inquiries

The § 391.23 investigation isn't complete without § 40.25 — the prior-employer drug and alcohol testing record. CDLVOE bundles this inquiry into the same outbound request, captures the reply, and files it against the driver record.

2-YEAR LOOKBACKBUNDLED REQUESTCONSENT CAPTURE
§ 391.51
RETENTION

Driver qualification file retention

Every verification, every reply, every signature — held for the duration of employment and the three years past separation § 391.51(d) requires, then purged on the carrier's defined schedule.

3-YR POST-SEPIMMUTABLE LOGEXPORTABLE BINDER
02SECURITY How driver data is handled

Plain-English security. No theater.

We don't wave around audit logos we haven't earned. Here is exactly how driver data is stored, transmitted, and retained.

AES
256-GCM

Encrypted where it counts

Driver SSNs and every stored credential are sealed with AES-256-GCM before they reach the database, under a key held outside it. TLS in transit.

US
CONUS

US data residency

Hosted in US data centers. Inbound fax pages are OCR'd on the server itself, so § 391.23 page images are never handed to a third party.

§ 53
EMP + 3 YR

Retention on the federal clock

§ 391.53(c) requires a driver's investigation history for as long as they are employed, plus three years. CDLVOE refuses to delete a hired driver's verification record inside that window. The access log runs four years.

RBAC
§ 391.53(a)

Controlled access, logged

§ 391.53(a) limits who may see a safety performance history. Roles gate it record by record, and every retrieval is written to an append-only log with actor, role, IP and timestamp.

03AUDIT Inspection day

When the auditor knocks.

CDLVOE exports the qualification file as a binder: a § 391.23 summary PDF carrying every attempt, every reply and the investigator certification, the signed consent and rights notice, and each employer's response filed under that employer. One driver, or up to 200 in a single export.

9
§ 391.51 items tracked per driver
3
Attempts documented per employer, per § 391.23
200
Drivers in one binder export
4 yr
Access log retained by default
04DEMO Walk through your own DQ file

Bring a driver record.
We'll find the gaps in 20 minutes.