← All articles

How to Audit DOT Rosters Before a Random Pull

How to Audit DOT Rosters Before a Random Pull

A DOT random selection can be perfectly generated and still leave your company exposed if the roster behind it is wrong. A driver who should have been in the pool but was omitted, or a former driver left in after termination, changes the integrity of the pull. That is why knowing how to audit DOT rosters is not a once-a-year cleanup task. It is a control you should run before every selection.

The goal is straightforward: make sure the eligible pool reflects the people who were actually subject to DOT random testing on the date you ran the draw. Then keep enough documentation to show exactly what you reviewed, what you changed, and why.

Start with the right definition of the DOT roster

A DOT roster is not simply everyone on payroll with a CDL. It is the current pool of employees performing safety-sensitive functions subject to the applicable DOT testing rules. For most motor carriers, that means CDL drivers operating commercial motor vehicles requiring a CDL under FMCSA rules.

Job titles are not reliable enough. A warehouse employee may hold a CDL but never drive in a safety-sensitive role. A dispatcher may occasionally move a qualifying vehicle and may need review depending on the duties performed. An owner-operator leased to your company can also belong in your testing program when your company is responsible for administering the program.

Build your roster around actual safety-sensitive status, not convenience. For each person in the pool, maintain a clear record of their full name, employee or driver ID, DOT agency or testing program, hire or activation date, employment status, and the reason they are included. If a driver is excluded, the file should make that decision understandable too.

How to audit DOT rosters before each selection

The cleanest process compares a current operational driver list against the pool used for the random draw. Do this before you lock the selection, not after notifications go out.

Start with your active-driver source. Depending on your operation, this may be payroll, dispatch, HR, fleet management, or a driver qualification file report. Pull the report as of a specific date and identify everyone currently assigned to safety-sensitive DOT driving duties.

Then compare it to the roster in your random testing system. Review every mismatch individually. Do not assume a name difference is harmless. A driver entered under a nickname, a changed last name, or two duplicate records can create a bad selection record and make it difficult to prove who was eligible.

Your review should answer three practical questions for every change:

  1. Should this person be in the DOT testing pool today?
  2. If yes, when did they become eligible?
  3. If no, when did their safety-sensitive status end, and is the reason documented?

A new driver should generally be added when they begin performing covered duties, not when someone gets around to updating a spreadsheet. A separated driver, a driver permanently moved to non-safety-sensitive work, or a driver no longer under your testing authority should be removed promptly. Keep the effective date and reason for every addition or removal.

The timing matters because the roster is the population from which your random selections are made. If your process only updates names once a quarter, you may be selecting from an outdated pool for weeks. That is an operational shortcut, not a defensible control.

Check the changes that cause most roster errors

Most roster failures come from routine personnel changes, not complicated regulations. Focus first on new hires, terminations, leaves of absence, transfers, acquisitions, and leased-driver arrangements.

New hires are often missed when HR completes onboarding before dispatch assigns a truck. On the other side, terminated drivers commonly remain in pools because no one closes the loop between HR and the designated employer representative. Temporary leaves deserve a written company rule. Whether a driver remains in the pool can depend on the facts, the duration of the leave, and whether the person remains employed in a covered role. Do not remove people automatically just because they are off the schedule for a few days.

Transfers need the same care. A driver moving into a non-driving job may no longer belong in the DOT pool. A mechanic, supervisor, or field employee who begins operating covered vehicles may need to be added. If multiple DOT agencies or separate company entities are involved, keep those pools distinct unless the applicable rules and your program structure support combining them.

Validate pool size and testing-rate math

A roster audit is also a math check. Your testing obligation is tied to the number of covered employees in the pool and the annual random testing rate set by the applicable DOT agency. The required rates can change, so use the current published rate for your program year rather than copying last year's worksheet.

Calculate your required annual tests using the appropriate pool average and rate methodology for your agency. Then compare that target to completed selections and completed tests. A driver selected in one period but never tested is not automatically equivalent to a completed random test. Your records should show the disposition: completed, pending, canceled for a documented reason, refused, or otherwise resolved under your policy and applicable rules.

This is where small fleets need to be especially disciplined. If you have a pool of 12 drivers, one missing driver is not a rounding error. It changes the eligible population by more than 8 percent. A larger fleet has more names, but it also has more turnover and more opportunities for departments to use conflicting lists.

Keep drug and alcohol selection records separate where your program requires separate rates or tracking. Do not assume a drug test satisfies an alcohol selection obligation, or vice versa, simply because the same driver appears on both reports.

Preserve the evidence, not just the final roster

An auditor may ask more than, “Who is in your pool now?” They may want to see who was eligible when a particular random selection occurred. A current roster cannot answer that question after names have been edited.

For each draw, preserve a locked snapshot of the eligible pool used at that moment. The record should show the selection date and time, total pool count, selected names, selection method, and the random-number or system-generated process used. It should also preserve later status changes without overwriting the original selection event.

That distinction matters. If a selected driver leaves employment before collection, you need to show that the driver was eligible at the time of selection, when notice was issued, and what happened next. Deleting the driver from the system may make the current roster look clean while destroying the audit trail.

Use a change log for roster maintenance. Each entry should identify who made the update, when it was made, what changed, and the reason. You do not need a complicated approval chain for every edit, but you do need a record that does not depend on somebody remembering the story six months later.

DTSMS Online is built around this control: eligible-pool snapshots can be locked at the time of selection, while timestamps and status histories document what happened after the pull. You run the pull, but the evidence remains intact.

Assign ownership so updates do not fall between departments

The most reliable roster process has one accountable owner, usually the designated employer representative, safety manager, or compliance lead. That person does not have to enter every personnel change personally. They do need a defined feed from the people who know when driver status changes.

Set a short cadence. HR reports hires, terminations, and job changes. Operations reports drivers activated for covered work, inactive drivers, and leased-driver changes. The roster owner reviews exceptions, updates the pool, and records the effective date. Before each random selection, the owner performs a final reconciliation.

Avoid letting dispatch maintain one list, payroll maintain another, and the testing coordinator maintain a third with no reconciliation. Spreadsheets can work for very small fleets, but only if version control is strict and historical copies are preserved. Once several people can edit a file, proving which version was used for a draw becomes harder than it needs to be.

Use a short pre-pull roster review

Before you generate the selection, confirm that all active covered drivers are included, inactive or separated drivers have been reviewed, duplicates are resolved, and recent job-status changes are reflected. Verify the pool count against your source report, then save the source report or review record with the selection documentation.

After the pull, do not edit the pool snapshot used for that draw. Handle notifications, collections, and results as separate status events. If a roster correction is needed the next day, make the correction for future draws and document why it was made.

A clean DOT roster is not paperwork for paperwork's sake. It is proof that every eligible driver had a fair chance of selection and that your random program is being managed, not merely generated. Build the review into your normal operating rhythm, and the next audit starts with records that already hold up.