Employment verification is one of the most time-consuming steps in driver onboarding. It's also one of the most important — FMCSA requires carriers to verify a driver's employment history going back at least three years before they can operate a commercial vehicle.

Today we're launching Employment Verifications in Double Nickel: an automated workflow that cuts verification turnaround from days to hours, keeps recruiters focused on hiring, and gives carriers a clean audit trail without the manual work.

Why employment verification slows carriers down

Under 49 CFR Part 391.23, carriers have to make a good-faith effort to verify a driver's employment history, accident record, and drug and alcohol testing results from the past three years. The information has to be documented in the Driver Qualification File and kept on record for the length of employment plus three years.

In practice, that means phone calls, emails, faxes, and spreadsheets. Recruiters chase down the right contact at a previous carrier, send a request, wait days for a response, follow up two or three times, and track every step for audit purposes. A carrier hiring even a handful of drivers a month is managing dozens of open verifications at once — and when verifications stall, onboarding stalls with them.

Qualified drivers sit on the sidelines waiting for paperwork. Recruiters burn hours on follow-up instead of hiring. And carriers carry the risk of an incomplete file if anything slips through.

How to speed up employment verification

A few practices that meaningfully cut down verification turnaround time, whether you're using software or not:

• Send requests the same day a driver applies. The clock on a 3-year verification doesn't start when you decide to hire — it starts when the request lands at the previous employer. Earlier outreach means earlier responses.

• Use multiple channels. Email alone has low response rates. Pair it with a phone call or fax, and follow up on a set cadence (every 2–3 business days is typical).

• Build a contact database. Most carriers verify against the same previous employers over and over. Saving DOT numbers, contact names, emails, and preferred verification methods turns a 20-minute hunt into a 30-second lookup.

• Get consent upfront. Have the driver sign FCRA-compliant consent at application, not after. Previous employers can refuse to respond without it.

• Document every attempt. FMCSA requires a good-faith effort, which means you need to show the work — dates, methods, contacts. Even unanswered requests count if they're documented.

• Automate the follow-ups. Manual reminders get dropped when recruiters are busy. Automated outreach keeps every open verification moving without anyone having to remember.

What changes with Employment Verifications in Double Nickel

The new Employment Verifications workflow is built around those exact practices — so recruiters don't have to think about them.

• Faster time-to-hire. Requests go out the moment a driver applies, so verifications start working in the background while the rest of onboarding moves forward.

• Recruiters stop chasing. Automated follow-ups run on a configurable cadence until a response comes back. No reminders, no dropped threads.

• Less time hunting contacts. Look up previous employers by DOT number and build a reusable contact database as you go — every verification gets faster than the last.

• Audit-ready by default. Consent, outreach attempts, and responses are logged automatically. When a DOT auditor asks, the file is already complete.

• Faster responses between carriers. When both sides use Double Nickel, the entire verification exchange stays in the platform — turning a multi-day back-and-forth into something that often closes the same day.

The result: verifications that used to take days of recruiter follow-up move through on their own, and qualified drivers get on the road faster.

See it in action

Employment Verifications are live now in Double Nickel. Book a call to see how it works, or if you're already a customer, head to the Verifications page to start using it.