Truck Driver Onboarding: A Complete Guide for Small Fleets

Hiring a driver means collecting the same eighteen fields every time: name, date of birth, address, years of experience, licence number, state and expiry, DOT physical number and expiry, SSN, EIN, and the bank details you will pay them with. Then come the documents, which usually arrive as photos over text, at night, sideways.

Someone on your side re-types all of it.

Truck driver onboarding is the process of collecting a driver's personal information, licence and medical information, required employment paperwork, payment details, and driver qualification documents before adding that driver to your fleet.

For a small carrier, that process usually runs on phone calls, text messages, emailed PDFs, and manual data entry. It works, in the sense that the driver eventually gets set up. It also produces transposed routing numbers, medical cards nobody can find at audit time, and a dispatcher spending an afternoon chasing a photo of a licence.

This guide covers what you need to collect, what belongs in a driver qualification file, how a digital onboarding workflow replaces the chasing, and how that workflow runs in Truxo as one implementation of it.

---

Overview

• Driver onboarding is two jobs sharing one name: administrative setup and driver qualification. They overlap, but they are not the same thing.
• You need roughly eighteen fields and six categories of document before a driver can take a load and be paid for it.
• The driver qualification file is defined by regulation, and several of its items are the carrier's job to obtain rather than the driver's to upload.
• Digital onboarding moves the typing to the driver, who is the person who actually knows the answers.
• In Truxo, you send a link, the driver verifies by text message and fills in their own details, and approving the application creates the driver record with documents attached.

---

What is truck driver onboarding?

Truck driver onboarding is everything between "we want to hire this person" and "this person can be assigned a load."

Practically, it is two jobs wearing one name.

The first is administrative onboarding: the data your operation needs to function. Contact details, licence and medical information with their expiry dates, tax identifiers, and the bank details that settlements pay into. This is what dispatch and payroll consume.

The second is driver qualification: the records a motor carrier is required to keep proving that this driver is qualified to operate a commercial vehicle. This is what an auditor consumes.

Driver onboarding
       │
       ├── Administrative onboarding
       │     ├── Personal information
       │     ├── Payment information
       │     └── Employment forms
       │
       └── Driver qualification
             ├── Licence
             ├── Medical certificate
             ├── MVR
             ├── Employment application
             └── Other required records

Most small fleets run these as one messy process, which is reasonable, because they draw on the same conversation with the same driver. The trouble starts when they are also stored as one messy process: a licence photo that satisfies dispatch sitting in a text thread where it satisfies no auditor at all.

---

What information do you need from a new driver?

Before a driver can be dispatched and paid, you need enough to do four things: identify them, verify they can legally drive, contact them, and pay them.

Identity and contact. Full legal name, date of birth, home address, phone number, and email address. The phone number does double duty on any digital onboarding flow, because it is usually how the driver's identity gets confirmed.

Experience. Years of commercial driving experience. This is not just a hiring signal. It feeds insurance questions and, in systems that rank drivers for a load, it feeds assignment.

Licence. The commercial driver's licence number, the state or province that issued it, and its expiry date. The expiry is the field that matters most after onboarding, because an expired licence in your system is a driver you cannot legally dispatch.

Medical. The DOT physical number and its expiry date, backed by the medical examiner's certificate itself. Same logic as the licence: the expiry date is the part that has to live somewhere that will remind you.

Tax and payment. SSN or EIN depending on whether the driver is an employee or a contractor, the pay-to name, bank name, routing number, and account number.

That is eighteen fields, and every one of them is a field the driver already knows and you do not. Any process where a dispatcher types them is a process where a digit can move.

---

What documents do you need to onboard a truck driver?

The fields above are what the driver tells you. These are what the driver, or you, have to produce on paper.

Commercial driver's licence. A clear image of both sides. This is the document a licence number is checked against, and the most common thing to be chasing at 9pm.

DOT medical examiner's certificate. Proof the driver passed the physical, with the expiry visible.

Motor vehicle record (MVR). The driving record from the state licensing agency. Worth being precise here: this is a record the carrier obtains, not something the driver hands over. A driver-supplied copy is a starting point, not a substitute.

Employment application. The driver's completed application, which is a required record in its own right rather than just a hiring formality.

Tax forms. A W-9 for a contractor, or the I-9 employment eligibility verification for an employee. Which one applies depends on how you are engaging the driver.

Driver photo. Not a compliance item, but a practical one. It shows up in dispatch, on driver lists, and anywhere someone needs to match a name to a face.

Everything else that is specific to your operation, from a signed handbook acknowledgement to an equipment agreement, goes in the same place as the rest.

---

Truck driver onboarding checklist

Copy this and work down it. It is the same list whether you run it on paper, in a shared drive, or in a TMS.

Driver information

• Full legal name
• Date of birth
• Home address
• Phone number
• Email address
• Years of commercial driving experience

Licence information

• Licence number
• Issuing state or province
• Expiry date
• Image of the licence, both sides

Medical information

• DOT physical number
• Expiry date
• Medical examiner's certificate

Employment documents

• Driver application for employment
• Motor vehicle record (MVR)
• I-9 or W-9, depending on employee or contractor status
• Previous employer inquiries

Payment information

• Pay-to name
• Bank name
• Routing number
• Account number
• SSN or EIN

Other

• Driver photo
• Any documents specific to your operation

The two items on this list with dates attached, the licence and the medical card, are the two you will need to look up again. Store them somewhere they can be found and re-checked, not somewhere they were merely received.

---

Driver qualification files: what small fleets need to know

Onboarding paperwork and the driver qualification file overlap, but treating them as the same thing is where small fleets get caught.

Under 49 CFR 391.51, a motor carrier must maintain a qualification file for every driver it employs. The file holds records including the driver's application for employment, the investigation and inquiries into previous employment, the motor vehicle record obtained from each state where the driver held a licence, a road test certificate or a licence or certificate accepted in its place, and the medical examiner's certificate. Other records are added on a recurring basis, such as the annual review of driving record and the driver's annual list of violations.

Two differences matter in practice.

The DQF is not only collected from the driver. Several of its required items are things the carrier goes and obtains: the MVR from the state, the inquiries to previous employers, the road test or its accepted equivalent. A driver self-service form cannot produce those, and any tool that implies otherwise is overselling.

The DQF does not end at onboarding. Administrative onboarding is finished the day the driver is set up. The qualification file keeps accruing records every year the driver works for you. A folder that was complete on day one and never touched again is not a maintained file.

This section is a summary of the regulation, not legal advice. Read 49 CFR Part 391 directly, or check with your compliance advisor, before treating any checklist as sufficient.

---

The traditional driver onboarding process, and where it breaks

The usual version goes like this. A dispatcher calls the new driver and works down a list, typing while the driver reads out a licence number over road noise. The driver texts photos of their licence and medical card. Someone emails a W-9 as a PDF and waits. Somebody re-types the whole thing into the system that runs the operation.

It breaks in four predictable places.

Transcription. Every field read aloud and typed by a second person is a chance for a digit to move. The routing number is the expensive one, because the error does not surface until a settlement fails.

Chasing. Details arrive in pieces across several days and several channels. Somebody has to remember what is still missing, and that somebody is usually the person with the least spare attention.

Storage. Photos land in a text thread or a phone gallery. They are technically collected and practically unfindable, which is the same as not having them when someone asks.

Expiry. A licence expiry typed into a spreadsheet is a date nobody will look at again until it has already passed.

None of that is a discipline problem. It is what happens when the person entering the data is not the person who has it.

---

How digital driver onboarding works

A driver onboarding workflow inverts the flow. Instead of interviewing the driver and typing, you invite the driver and review. The shape is consistent across tools that do this well:

1. Send an invitation. The fleet sends a link to the new hire by email or text. No account, no app install.
2. The driver verifies their identity. Usually a one-time code sent to a phone number the fleet already has. Nothing sensitive is shown or accepted before this passes, because the link itself travels through forwardable channels.
3. The driver enters their information. The same fields a dispatcher would have typed, filled in by the person who actually knows them.
4. The driver uploads their documents. Tagged by type at the moment of upload, so a licence photo arrives labelled as a licence.
5. The fleet reviews. The submission sits in a queue as an application, not yet a driver.
6. The fleet approves or rejects. Approval creates the driver record with the documents already filed. Rejection tells the applicant why.

Step 5 is the one worth defending. A workflow that creates a driver the instant a stranger submits a form has replaced a data-entry problem with a data-integrity problem. The review is what keeps the fleet as the authority on its own roster.

---

How Truxo handles driver onboarding

Here is that workflow as it actually runs in Truxo, including the parts most guides leave vague.

Sending the onboarding link

Open Drivers and click Send onboarding link, next to Add Driver. It is gated by the same permission as creating a driver, so if you can add a driver, you can send a link.

Three fields:

Field	What it does
Full Name	Greets the driver in the email and labels the application in your queue
Email	Where the invite email goes
Phone Number	Where the confirmation code gets texted

The phone number matters more than it looks. It is the number the driver has to prove control of before the form opens, so a typo makes the link unusable by the person you sent it to.

Two things will stop a link from being sent, both deliberately. If the phone or email already belongs to a driver on your roster, Truxo names that driver and tells you to edit them instead. And there is one open invite per contact, so if a live link or an unreviewed application already exists for that person, Truxo points you at it rather than minting a second live link.

Click Send link, and Truxo creates the invite, emails it, and shows you the link.

Copy the link now if you plan to send it any other way. It is shown exactly once. If the email is slow or the address bounces, the dialog says so and reads "Link ready to share" instead of "Link sent". The invite is still valid, and the link is right there to text or message. Truxo also shortens the URL, which makes it easier to send by SMS or read out over the phone.

The email arrives under your organisation's name with your logo, subject "Complete your driver details", telling the driver they need no account, when the link expires, that verification is by text message, and that it takes about five minutes.

What the driver does

The link opens on a screen naming your company and showing a masked hint of the phone number rather than the full number. The driver taps Text me a code, enters six digits, and the form appears. Nothing sensitive is shown or accepted before that point.

The form is the driver-fillable half of Truxo's internal Add Driver form, in the same section order, so the submission reads in a familiar layout when you review it: Driver Information, Driver Licence, Medical, Your Documents, Payment Details. Name, phone, and email arrive pre-filled from what you typed, with a note telling the driver to correct anything wrong.

Documents are tagged from a fixed list: Driver Licence, Medical, MVR, Driver Application, I9, W9, Driver Picture, and Other. Each file uploads the moment it is picked rather than waiting for submission, which means a failed upload costs that one document and leaves the driver's typed answers untouched. The cap is 20 documents per application.

One thing worth telling a new hire up front: the verified session lasts 30 minutes. Documents already uploaded are kept, because those were stored as they went, but answers typed and not submitted are not. So the advice is simple. Have the licence, medical card, and bank details in front of you before opening the link, and finish it in one sitting.

On submit, the driver sees a confirmation saying your company will review and be in touch. No driver record exists yet.

Reviewing applications

Back on the Drivers page, Driver applications is your queue. When applications are waiting on a decision it turns amber with the count, for example "2 applications to review".

Filter	What it holds	What you can do
Awaiting review	The driver submitted and is waiting on you	Review, edit, approve, reject
Link sent	Link is live, not opened or not finished	Resend
Expired	Seven days passed unused	Resend
Approved	Already a driver on your roster	Nothing further
Rejected	Decided and the applicant was emailed	Send a fresh link if they reapply

It defaults to Awaiting review, since that is the only state where a decision is owed. The other filters exist so a link you just sent does not vanish the moment you close the dialog.

Click Review to open an application. You get every submitted field plus the documents, each with a View link, so you can open the licence photo and check it against the licence number they typed.

Submitted details are read-only until you click Edit details. That default is on purpose: approving what the driver actually submitted should be the easy path, and changing their answers should be deliberate. But the escape hatch matters, because approval writes a real driver record, and fixing a transposed routing number beats making someone refill the whole form. Toggling edit mode off discards your edits rather than keeping them in the background, so what is on screen is always what approval will write.

Approve and add driver creates the driver with the submitted details and files the uploaded documents against the new record under their document types, as one operation. You never end up with a driver missing their documents, or an approved application with no driver behind it. Truxo re-checks for duplicate phone and email at this moment, not just at send time, because your roster can change while an application sits in the queue. The applicant is emailed that they have been approved.

Reject asks for an optional reason that is shared with the driver in the rejection email. Something like "Licence expired, reapply once renewed" saves a phone call. Rejection is terminal for that invite but not for that person, so a driver who comes back with a renewed licence can be sent a fresh link.

Re-sending a stale link

Rows under Link sent and Expired carry a Resend button, and the same action sits inside the review panel.

Resend rotates the link rather than extending it. The moment it succeeds, the previous link stops working and a new one is issued with a fresh seven-day window. A driver who forwarded the first link to the wrong person does not leave a second working door open behind them. One invite can be re-sent up to five times, and you cannot resend an application that has already been submitted, approved, or rejected.

---

How Truxo secures the onboarding link

An onboarding link travels through text messages and email, gets forwarded, and sits in inboxes. It carries a request for an SSN and bank account details. That shapes a few decisions worth understanding before you fight them:

• The link alone is not enough. Opening it reveals only who is asking, so the driver can see the request is legitimate before typing anything. Everything sensitive sits behind the texted code.
• The link cannot be recovered. Truxo stores only a hash of it, so nothing in the system can show it to you twice. This is why the Copy link button is prominent, and why a resent link stays rendered on screen instead of only going to your clipboard, which can fail on some browsers.
• Codes and attempts are capped. Three code sends per ten minutes on any single link, and ten verification attempts per ten minutes. Room for a genuine mistyped code, no room for brute-forcing six digits.
• Links expire in seven days and work once. Long enough for a driver who is out on a run, short enough that an old message is not a live credential.
• Nothing is created until you approve. A submitted application is not a driver, which is what makes the review step meaningful rather than decorative.

Here is the honest limitation. This flow collects details and documents. It does not verify them. Truxo will not tell you whether a licence is valid or an MVR is clean, and it does not obtain the records that only a carrier can obtain. Keeping the driver qualification file complete and current is still your job. What the flow removes is the typing and the chasing.

---

Common driver onboarding problems

The driver never opens the link. Usually the email went to spam or to an address with a typo. Resend from the queue, and send the copied link by text instead.

The phone number is wrong. Nothing else works if this is wrong, because the code goes there. Resend with the corrected number if the invite has not been used.

The driver starts and does not finish. Their uploaded documents survive, their typed answers do not. Tell them to gather documents before starting.

The details are right but a field is wrong. Edit before approving instead of rejecting. Rejection is for applications you do not want, not for typos.

The person is already on your roster. Almost always a re-hire or a duplicate record. Edit the existing driver rather than creating a second one, which is why the check exists at both send and approve time.

Documents were collected but never filed. This is the one that only shows up at audit. It is also the whole argument for collecting documents inside the system that holds the driver record, rather than alongside it.

---

How long does truck driver onboarding take?

The paperwork itself is not the slow part. A driver with their licence, medical card, and bank details to hand fills the form and uploads documents in about five minutes from a phone. Review takes a couple of minutes, because everything is on one screen.

What sets the real timeline is everything the form does not touch: pulling the motor vehicle record, contacting previous employers, and any drug and alcohol testing your operation requires. Those run on external turnaround times, not yours.

Which means the honest answer is that digital onboarding does not make hiring a driver fast. It makes the part you control stop taking days of back and forth, so the remaining wait is the part that was always going to be a wait.

---

Driver onboarding FAQ

What is truck driver onboarding?

The process of collecting a driver's personal information, licence and medical details, employment paperwork, payment information, and qualification documents before that driver can be assigned a load. It covers both the administrative side that feeds dispatch and payroll, and the compliance side that feeds the driver qualification file.

What paperwork is required to onboard a truck driver?

Identity and contact details, date of birth and address, the CDL number with issuing state and expiry, the DOT medical examiner's certificate and its expiry, tax identifiers, and bank details for settlements. On the compliance side, 49 CFR Part 391 requires records including an employment application, previous employer inquiries, a motor vehicle record, a road test certificate or accepted equivalent, and the medical certificate.

What documents should be in a driver qualification file?

Per 49 CFR 391.51: the application for employment, the investigation and inquiries into previous employment, the MVR from each state where the driver held a licence, a road test certificate or accepted equivalent, and the medical examiner's certificate. Ongoing records include the annual review of driving record and the annual list of violations. Check the regulation directly rather than treating a summary as sufficient.

Can drivers complete their own onboarding paperwork?

Yes, and they should. The person who knows the SSN and the routing number is the person who should be typing them. A link-based flow lets the driver do exactly that from a phone with no account.

How can a small fleet automate driver onboarding?

Collect the details and documents directly from the driver, and have approval file them against the driver record automatically. In Truxo that is a link from the Drivers page, a texted code, a form the driver fills, and one approval that creates the driver with documents attached.

Does the driver need a Truxo account?

No. The link opens a public page with no login. Identity is proven by the six-digit code texted to the number you entered when sending the link.

How long is the onboarding link good for?

Seven days, single use. Re-sending issues a new link and immediately kills the old one, up to five times per invite.

---

The bottom line

Driver onboarding is a data collection problem that most small fleets solve by having the wrong person do the data entry. The driver knows every one of the eighteen fields. The dispatcher types all eighteen anyway, from a phone call, and then goes looking for the licence photo.

Moving the typing to the driver fixes the transcription errors, the chasing, and the documents that end up in a text thread. It does not fix the parts of qualification that only a carrier can do, and no tool honestly claims otherwise.

If you want to see the version of this with a review queue attached, open Drivers in Truxo and click Send onboarding link. Your next hire can start filling in their own details before you have finished the phone call.

Related reading: the best TMS for owner-operators and small fleets, and how to build a load from a rate confirmation.