The verification workflow,
rebuilt for the road.
CDLVOE is built for one regulation. Every screen in it exists to get a driver's § 391.23 investigation sent, answered and documented before day 30.
Map your application once. Every one after it reads itself.
Point CDLVOE at the form you already use and mark where the fields sit — once. From then on every application on that form comes back as a driver record: personal details, CDL, and each prior employer as its own row instead of a block of text to retype.
- AReads PDF form fields, positioned text, and label anchors
- BEvery field carries a confidence score you see before you import
- CPrior employers arrive as records — company, dates, position, reason for leaving
Walk-ins fill in their own history.
Open the kiosk on any computer or tablet in the driver lounge. The applicant picks their name off the roster and works through four steps. The work-history step draws their last three years as a bar they have to cover before they can sign.
- 01Personal info
- 02CDL
- 03Work history
- 04Review & sign
Time out of work is recorded as a gap rather than an employer — it carries no § 391.23 inquiry, and the file says why.
Every employer, on the channel that will answer.
One launch covers the whole driver. CDLVOE resolves each employer's channel from the contact details on file — email first, then e-fax, then a print-ready letter you post yourself — stamps a reference code on it, and follows the electronic ones from queued to delivered.
- AChannel chosen per employer from the contacts you hold
- BSilent employers are chased at +24h and +48h, capped at three attempts
- CEvery attempt is logged with its channel, letter type and timestamp
Replies file themselves.
Employers answer to your own mailbox and your own fax line. CDLVOE reads what comes back, finds the reference code it sent, and files the reply against that driver and that employer. Anything short of certain is labelled and left for you.
- AInbound fax pages are OCR'd in-process — the images never leave your server
- BA reference-code match files itself; a partial match is scored and queued
- CBounces and out-of-office replies are recognised, not filed as answers
The file an auditor asks for.
Every attempt, reply, timestamp and signature lands in one record per driver, tracked against the nine items a § 391.51 qualification file has to hold. Export one driver, or a binder of up to 200.